New
#1
Plagued by BSOD, win7 x64
I'm wondering if anyone can help me resolve an on-going issue that I am experiencing with repeated BSODs. It's starting to really annoy me!
I can't find any common thread as to when they occur and sometimes I can go days without a crash, other times I'll have multiple in one day, sometimes I find that it has crashed overnight when nobody was using the pc. As such I've hit a brick wall in trying to identify the culprit.
I keep windows updated and update drivers when I become aware of an update.
I ran WhoCrashed, the output of which is below. It suggests that the culprit is a driver, rather than hardware.
Can anyone help guide me through tracking down the error before my computer ends up out the window?
System Information (local)
computer name: JOHN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6432088064 total
VM: 2147352576, free: 1933463552
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 28/08/2011 09:11:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082811-239960-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3B4DE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
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 Sun 28/08/2011 09:11:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 20/08/2011 01:01:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-17331-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EE0BD0)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 19/08/2011 15:20:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-27050-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA8304DBD0B0, 0x2, 0x1, 0xFFFFF80002EC4CC8)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 16/08/2011 19:10:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-18189-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x109 (0xA3A039D89AD1551F, 0x0, 0x87A0D7183DDE773B, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 16/08/2011 14:30:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-17035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3B4DE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003214DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
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 Wed 10/08/2011 14:03:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-36098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xC5 (0xFFFFFA8018354C68, 0x2, 0x0, 0xFFFFF80003003B05)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 10/08/2011 13:47:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081011-26130-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x109 (0xA3A039D89AD195EB, 0x0, 0x18D66EF5EA34F3FF, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 27/07/2011 21:50:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072711-38423-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A00AF99000, 0x1, 0x0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 21/07/2011 23:31:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-32526-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF8A01C6C0938, 0x0, 0xFFFFF88001163039, 0x2)
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.
On Thu 21/07/2011 22:36:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-57049-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA8019098E7B, 0x2, 0x0, 0xFFFFF80002E8F533)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 12/07/2011 23:26:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071311-31090-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x935C6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB25C6, 0xFFFFF88003124888, 0xFFFFF880031240E0)
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 Mon 11/07/2011 16:25:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071111-26894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x109 (0xA3A039D89AD2058A, 0x0, 0x622AEA13417F2EEA, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 11/07/2011 11:51:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071111-71963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFFFFFB8797400, 0x1, 0xFFFFFA8009098E44, 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.
On Sun 10/07/2011 12:52:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071011-45521-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xA43DC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012C83DC, 0xFFFFF880031246A8, 0xFFFFF88003123F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
Quote