New
#1
My BSOD
I built this PC at the end of Jan and it's been running fine since then. However, yesterday I got a BSOD. I tried some basics such as reinstalling video and LAN drivers as I suspect a conflict between the two is the source of the fault (see below) but no luck! And as you'll see from below, I've had a string of crashes since then!
Some info as follows:
64 bit version of Windows 7
Clean installed
All brand new hardware
I've been running WHOCRASHED to try and self-diagnose the issue, and it's coming back with different errors each time. They are as follows:
On Thu 10/03/2011 21:01:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031011-31481-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x6F3F)
Bugcheck code: 0xD1 (0x504562EB, 0x2, 0x1, 0xFFFFF880042C8F3F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 10/03/2011 21:01:45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x6F3F)
Bugcheck code: 0xD1 (0x504562EB, 0x2, 0x1, 0xFFFFF880042C8F3F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 10/03/2011 20:40:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031011-27222-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD02BB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880131A72BB, 0xFFFFF88006E0E978, 0xFFFFF88006E0E1D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 266.58
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 266.58
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 266.58 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 10/03/2011 19:57:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031011-29047-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x58B7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880014268B7, 0xFFFFF88008577A90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 10/03/2011 19:46:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031011-45240-01.dmp
This was probably caused by the following module: habu.sys (habu+0x89E)
Bugcheck code: 0xC4 (0xF6, 0x180, 0xFFFFFA80083B7B30, 0xFFFFF88005D4589E)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\habu.sys
product: Diamondback USB Optical Mouse
company: Razer (Asia-Pacific) Pte Ltd
description: Diamondback USB Optical Mouse Driver
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: habu.sys (Diamondback USB Optical Mouse Driver, Razer (Asia-Pacific) Pte Ltd).
Google query: habu.sys Razer (Asia-Pacific) Pte Ltd DRIVER_VERIFIER_DETECTED_VIOLATION
On Thu 10/03/2011 19:24:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031011-41309-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009192C48, 0xFFFFF880091924A0, 0xFFFFF880012EAC04)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 09/03/2011 21:09:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-30934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF880072EFE45, 0x1, 0xFFFFF88014AF371E, 0x0)
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 Wed 09/03/2011 20:59:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-30061-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008889B30, 0xFFFFFA8008889E10, 0xFFFFF800033C62D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 09/03/2011 20:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-28267-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD1CEF)
Bugcheck code: 0xD1 (0x2DFC680, 0x8, 0x1, 0xFFFFF88013CD1CEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 266.58
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 266.58
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 266.58 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 09/03/2011 19:37:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030911-24663-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x31A2)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF8801487E1A2)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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.