Plagued by BSOD, win7 x64

J

jhob

New member
Local time
5:50 PM
Messages
12
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?
[FONT=Segoe UI, Arial]
System Information (local) [/FONT]
[FONT=Segoe UI, Arial]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
[/FONT]

[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x3B4DE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002EE0BD0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA8304DBD0B0, 0x2, 0x1, 0xFFFFF80002EC4CC8)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x109 (0xA3A039D89AD1551F, 0x0, 0x87A0D7183DDE773B, 0x101)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x3B4DE0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003214DE0, 0xFFFFF88003124988, 0xFFFFF880031241E0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0xC5 (0xFFFFFA8018354C68, 0x2, 0x0, 0xFFFFF80003003B05)
Error: [FONT=Segoe UI, Arial]DRIVER_CORRUPTED_EXPOOL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x109 (0xA3A039D89AD195EB, 0x0, 0x18D66EF5EA34F3FF, 0x101)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A00AF99000, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFF8A01C6C0938, 0x0, 0xFFFFF88001163039, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0xA (0xFFFFFA8019098E7B, 0x2, 0x0, 0xFFFFF80002E8F533)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x935C6)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB25C6, 0xFFFFF88003124888, 0xFFFFF880031240E0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x109 (0xA3A039D89AD2058A, 0x0, 0x622AEA13417F2EEA, 0x101)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7FD00)
Bugcheck code: 0x50 (0xFFFFFFFFB8797400, 0x1, 0xFFFFFA8009098E44, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]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: [FONT=Segoe UI, Arial]ntfs.sys[/FONT] (Ntfs+0xA43DC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880012C83DC, 0xFFFFF880031246A8, 0xFFFFF88003123F00)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]
 

My Computer My Computer

At a glance

windows 7
OS
windows 7
jhob said:
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?
[FONT=Segoe UI, Arial]
System Information (local) [/FONT]
[FONT=Segoe UI, Arial]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
[/FONT]
Code: 
[FONT=Segoe UI, Arial][SIZE=4][B]  Crash Dump Analysis[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump  directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash  dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT][/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sun 28/08/2011 09:11:11 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\082811-239960-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x3B4DE0) 
Bugcheck code:  0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988,  0xFFFFF880031241E0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sun  28/08/2011 09:11:11 GMT your computer crashed[/B]
crash dump file:  C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code:  0x7E (0xFFFFFFFFC0000005, 0xFFFFF800031C3DE0, 0xFFFFF88003124988,  0xFFFFF880031241E0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sat 20/08/2011 01:01:19 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\082011-17331-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7CC40) 
Bugcheck code: 0xA (0x28,  0x2, 0x0, 0xFFFFF80002EE0BD0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Fri  19/08/2011 15:20:48 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\081911-27050-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7CC40) 
Bugcheck code: 0xA  (0xFFFFFA8304DBD0B0, 0x2, 0x1, 0xFFFFF80002EC4CC8)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue  16/08/2011 19:10:09 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\081611-18189-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7CC40) 
Bugcheck code: 0x109  (0xA3A039D89AD1551F, 0x0, 0x87A0D7183DDE773B, 0x101)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 16/08/2011 14:30:37 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\081611-17035-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x3B4DE0) 
Bugcheck code:  0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003214DE0, 0xFFFFF88003124988,  0xFFFFF880031241E0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed  10/08/2011 14:03:00 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\081011-36098-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0xC5  (0xFFFFFA8018354C68, 0x2, 0x0, 0xFFFFF80003003B05)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+DRIVER_CORRUPTED_EXPOOL"]DRIVER_CORRUPTED_EXPOOL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed  10/08/2011 13:47:38 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\081011-26130-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0x109  (0xA3A039D89AD195EB, 0x0, 0x18D66EF5EA34F3FF, 0x101)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Wed 27/07/2011 21:50:10 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\072711-38423-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0x19  (0x22, 0xFFFFF8A00AF99000, 0x1, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+BAD_POOL_HEADER"]BAD_POOL_HEADER[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 21/07/2011 23:31:21 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\072211-32526-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0x50  (0xFFFFF8A01C6C0938, 0x0, 0xFFFFF88001163039, 0x2)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+PAGE_FAULT_IN_NONPAGED_AREA"]PAGE_FAULT_IN_NONPAGED_AREA[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 21/07/2011 22:36:14 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\072111-57049-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0xA  (0xFFFFFA8019098E7B, 0x2, 0x0, 0xFFFFF80002E8F533)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue  12/07/2011 23:26:31 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\071311-31090-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x935C6) 
Bugcheck code: 0x1000007E  (0xFFFFFFFFC0000005, 0xFFFFF80002EB25C6, 0xFFFFF88003124888,  0xFFFFF880031240E0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Mon  11/07/2011 16:25:29 GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\071111-26894-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0x109  (0xA3A039D89AD2058A, 0x0, 0x622AEA13417F2EEA, 0x101)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CRITICAL_STRUCTURE_CORRUPTION"]CRITICAL_STRUCTURE_CORRUPTION[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Mon 11/07/2011 11:51:58 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\071111-71963-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x7FD00) 
Bugcheck code: 0x50  (0xFFFFFFFFB8797400, 0x1, 0xFFFFFA8009098E44, 0x5)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+PAGE_FAULT_IN_NONPAGED_AREA"]PAGE_FAULT_IN_NONPAGED_AREA[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sun 10/07/2011 12:52:12 GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\071011-45521-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntfs.sys"]ntfs.sys[/URL][/COLOR][/SIZE][/FONT] (Ntfs+0xA43DC) 
Bugcheck code: 0x1000007E  (0xFFFFFFFFC0000005, 0xFFFFF880012C83DC, 0xFFFFF880031246A8,  0xFFFFF88003123F00)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.
[/COLOR][/SIZE][/FONT]
Click to expand...


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 Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Please find attached the dump files and other bits using the jcgriff2 utility.

Thanks in advance for anyone able to offer help.
 

My Computer My Computer

At a glance

windows 7
OS
windows 7
jhob said:
Please find attached the dump files and other bits using the jcgriff2 utility.

Thanks in advance for anyone able to offer help.
Click to expand...

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 Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
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 Computer My Computer

At a glance

windows 7
OS
windows 7
jhob said:
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
Click to expand...

Good Luck John.
 

My Computer My Computer

At a glance

Win 8 Release candidate 8400[email protected]4 gigsNvidia 9600M
Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
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 Computer My Computer

At a glance

windows 7
OS
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 Computer My Computer

At a glance

windows 7
OS
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 Computer My Computer

At a glance

windows 7
OS
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 Computer My Computer

At a glance

windows 7
OS
windows 7
You must log in or register to reply here.

Similar threads

BSOD - Driver Power State Failure
Replies
1
Views
999
wither 2
W
LOTS OF BSODS Lately out of nowhere While Playing Fifa21
Replies
6
Views
3K
Megahertz07
Megahertz07
BSOD STOP 0xc9
Replies
3
Views
996
martinlest
M
BSOD booting Windows
Replies
4
Views
955
SylverX
S
Random Crash issues, many different modules involved
Replies
11
Views
3K
axe0
A
Back
Top