Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Plagued by BSOD, win7 x64


24 Oct 2011   #1

windows 7
 
 
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.



My System SpecsSystem Spec
.

24 Oct 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jhob View Post
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

Code:
  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. 


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.



My System SpecsSystem Spec
24 Oct 2011   #3

windows 7
 
 

Please find attached the dump files and other bits using the jcgriff2 utility.

Thanks in advance for anyone able to offer help.
My System SpecsSystem Spec
.


24 Oct 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jhob View Post
Please find attached the dump files and other bits using the jcgriff2 utility.

Thanks in advance for anyone able to offer help.
Various causes but I think they all point towards asacpi.sys I would try that first.


1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).

My System SpecsSystem Spec
24 Oct 2011   #5

windows 7
 
 

Thanks very much for the help there, I really appreciate it. I have installed the new version of ATK0110 driver (14/5/2009), will see how I get on now.

cheers
John
My System SpecsSystem Spec
24 Oct 2011   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jhob View Post
Thanks very much for the help there, I really appreciate it. I have installed the new version of ATK0110 driver (14/5/2009), will see how I get on now.

cheers
John
Good Luck John.
My System SpecsSystem Spec
31 Oct 2011   #7

windows 7
 
 

Still getting them I'm afraid, had one late last week and another just now. Neither have produced a minidump despite me definitely having minidumps turned on. The latest one said something about ntfs.sys, I'll take a screenshot if it happens next time.

I have a theory that it may be something to do audio as it always seems to happen when I'm listening to music, however I do listen to music for much of the time that I am at the computer.

Can anyone help to point me in the direction for what to try next?

Thanks in advance for any help offered.
My System SpecsSystem Spec
31 Oct 2011   #8

windows 7
 
 

I have just updated the audio driver from generic windows to RealTek HD Audio 6.0.1.5859. Will see if that makes any difference.
My System SpecsSystem Spec
07 Nov 2011   #9

windows 7
 
 

Well, the BSODs continue :-(

For some reason crash dumps are still not being written to the minidump folder, despite the message on the BSOD screen claiming that they have been.

I've attached screenshots of the last 2 BSODs in case that gives anything more to go on with tracking the problem down.

I appreciate any help offered.

cheers
John
My System SpecsSystem Spec
18 Nov 2011   #10

windows 7
 
 

Still getting BSODs, can anyone offer some guidance as to what I should try next?

Crash dumps still aren't getting written. I've attached an image of the latest BSOD. Problem with volsnap.sys this time. I wasn't listening to any music when this one occurred, just had firefox open from what I recall so it rules that out as being the root cause.
My System SpecsSystem Spec
Reply

 Plagued by BSOD, win7 x64




Thread Tools



Similar help and support threads for2: Plagued by BSOD, win7 x64
Thread Forum
BSOD Bugcheck 0x116 Win7 x64 DV6 2090eo random BSOD's BSOD Help and Support
Just recently been plagued with Blue screens BSOD Help and Support
New Build, Plagued with BSod BSOD Help and Support
Solved BSOD Please Help.... in new Win7 BSOD Help and Support
BSOD Win7 X64 error! changed major components and still BSOD! BSOD Help and Support
Windows plagued by 17-year-old privilege escalation bug News
BSOD..again and again on win7 x64 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 08:35 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33