So recently, my computer has been undergoing random crashes. Like…sporadically random. I can't tell what it is I'm doing that decides to make the system crash. I ran Norton antivirus, and with the exception of a few cookies, nothing out of the ordinary was found. Ran a power cleaner, too, and still nothing. It seems like my system is just intent on crashing itself randomly. I wish I could find out what's wrong with it and put a stop to it, as it often happens when I'm in the middle of working on a project or something, and sometimes it catches me off guard before I can save the work.
Any tips, pointers, or suggestions as to what this may be and how I can stop it? Any help is much appreciated, and I give my sincerest thanks in advance.
Thank you!
This is what WhoCrashed had to say:
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 6/29/2012 1:33:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062812-27502-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 6/29/2012 1:33:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4C891)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. KMODE_EXCEPTION_NOT_HANDLED
On Wed 6/27/2012 4:26:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-34257-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1709A0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Tue 6/26/2012 9:16:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062612-34257-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88008FD99D0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 6/26/2012 5:09:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062612-36722-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xFFFFF8804B8687C6, 0x2, 0x8, 0xFFFFF8804B8687C6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 6/25/2012 9:48:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-27580-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x1, 0xB, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 6/25/2012 8:20:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-29499-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005973D18, 0xFFFFF88005973570, 0xFFFFF80002C7E0C5)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Mon 6/25/2012 6:58:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-36129-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC2AD3)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E2AD3, 0xFFFFF88008C52100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 6/23/2012 7:12:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062312-42744-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x818E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000C3218E, 0xFFFFF880033FCA28, 0xFFFFF880033FC280)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Fri 6/22/2012 6:31:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062212-32058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3D (0xFFFFF88009318FB0, 0x0, 0x0, 0xFFFFF80002C7763D)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/21/2012 11:38:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-27939-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4F072)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C6C072, 0xFFFFF88008D3B7C8, 0xFFFFF88008D3B020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/21/2012 9:44:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-28173-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x2, 0x8, 0x2)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/21/2012 9:28:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-33087-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x3477E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F477E, 0xFFFFF88007EB17A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 6/21/2012 7:30:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-36504-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C890C5, 0xFFFFF88008EF6B60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 6/21/2012 4:34:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-26488-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80042ECDB00, 0x1, 0xFFFFF80002CA8CA8, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
——————————————————————————–
Conclusion
——————————————————————————–
36 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer.
————
It would seem that this "ntoskrnl.exe" is behind the crashing, but I've no idea what to do. Any ideas? As always, any help is much appreciated.
