Solved BSOD randomly

[vikti]

Hi,

Someone could help me ? I get reccurent BSOD (average each two days )

My configuration :
- 4 years old
- Windows 7 ultimate x64
- ASUSTeK P5K (Intel P35 Express)
- Intel Q6600 2.4ghz non overclocked
- 4go Kingston HyperX DDR2-SDRAM PC8500 CL5 - KHX8500D2K2/2G
- RADEON HD5700

I have built it on my own.

Kind regards,

 

[writhziden]

[list=1]

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\vikti\Windows_NT6_BSOD_jcgriff2\010312-16099-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03454670
Debug session time: Tue Jan  3 08:16:44.367 2012 (UTC - 7:00)
System Uptime: 0 days 7:16:05.193
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 4, fffffa8007ab0060, fffffa800548a860}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
Probably caused by : HIDCLASS.SYS ( HIDCLASS!CollectionWaitWakeIrpCancelRoutine+f7 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000004, USBHUB_PDO_TRAP_FATAL
Arg3: fffffa8007ab0060, Context if next arg null, else PDO
Arg4: fffffa800548a860, Context if not null

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbhub!_DEVICE_EXTENSION_HUB                  ***
***                                                                   ***
*************************************************************************

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8800544a387 to fffff8000328bc40

STACK_TEXT:  
fffff880`033bd6f8 fffff880`0544a387 : 00000000`000000fe 00000000`00000008 00000000`00000004 fffffa80`07ab0060 : nt!KeBugCheckEx
fffff880`033bd700 fffff880`054541fb : fffffa80`07ab0a08 fffffa80`07abe180 fffffa80`0548a860 fffffa80`0547cc80 : usbhub!UsbhDecPdoIoCount+0xaf
fffff880`033bd750 fffff800`032386f0 : fffffa80`0548a860 fffffa80`0548a800 fffffa80`0548a800 fffffa80`07abe180 : usbhub!IopCsqCancelRoutine+0x77
fffff880`033bd780 fffff880`04b8fda7 : fffffa80`0548a400 fffffa80`0548a480 fffffa80`0548a860 00000000`00000000 : nt!IoCancelIrp+0x60
fffff880`033bd7c0 fffff800`032386f0 : fffffa80`07abe180 fffffa80`0c518f20 fffffa80`07abea00 c5d0e708`56836b63 : HIDCLASS!CollectionWaitWakeIrpCancelRoutine+0xf7
fffff880`033bd800 fffff880`053aae1b : fffffa80`04544000 fffffa80`07abead0 fffffa80`07abead0 fffffa80`07abe980 : nt!IoCancelIrp+0x60
fffff880`033bd840 fffff880`053ab27e : fffff880`04b933b8 fffffa80`07abe980 fffffa80`0c518f20 fffffa80`07abead0 : mouclass!MouseClassRemoveDevice+0x37
fffff880`033bd870 fffff800`034f6af9 : fffffa80`07abe980 00000000`c00000bb fffff880`033bd988 fffffa80`0c518c10 : mouclass!MousePnP+0xca
fffff880`033bd8d0 fffff800`03674f71 : fffffa80`0548a330 00000000`00000000 fffffa80`0541ad90 00000000`00000000 : nt!IopSynchronousCall+0xc5
fffff880`033bd940 fffff800`0366f968 : fffff8a0`0f0b81d0 fffffa80`0548a330 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
fffff880`033bda00 fffff800`03674ab7 : fffffa80`0541ad90 00000000`00000000 00000000`00000003 fffff880`033bdcb8 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff880`033bda40 fffff800`03674bd0 : 00000000`00000000 fffff8a0`11f23800 fffff8a0`0f0b81d0 fffff880`033bdb98 : nt!PnpDeleteLockedDeviceNode+0x37
fffff880`033bda70 fffff800`037054cf : 00000000`00000002 00000000`00000000 fffffa80`05eae6d0 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`033bdae0 fffff800`0370608c : fffff880`033bdcb8 00000000`00000000 fffff8a0`0bd3b500 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff880`033bdc20 fffff800`035ef34e : 00000000`00000000 fffffa80`03d300d0 fffff8a0`14267480 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`033bdc50 fffff800`03296001 : fffff800`034f5998 fffff8a0`11f23800 fffff800`0342c2b8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x5b3cb
fffff880`033bdcb0 fffff800`03526fee : efff75ff`47fbfeff fffffa80`03a03040 00000000`00000080 fffffa80`039f0400 : nt!ExpWorkerThread+0x111
fffff880`033bdd40 fffff800`0327d5e6 : fffff880`03163180 fffffa80`03a03040 fffff880`0316dfc0 fff7ffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
HIDCLASS!CollectionWaitWakeIrpCancelRoutine+f7
fffff880`04b8fda7 488b5c2440      mov     rbx,qword ptr [rsp+40h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  HIDCLASS!CollectionWaitWakeIrpCancelRoutine+f7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xFE_HIDCLASS!CollectionWaitWakeIrpCancelRoutine+f7

BUCKET_ID:  X64_0xFE_HIDCLASS!CollectionWaitWakeIrpCancelRoutine+f7

Followup: MachineOwner
---------

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\vikti\Windows_NT6_BSOD_jcgriff2\011312-21590-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`03451670
Debug session time: Fri Jan 13 10:57:50.044 2012 (UTC - 7:00)
System Uptime: 0 days 9:48:35.495
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800032a51a8, fffff8800b6fbcd0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectSafe+18 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032a51a8, Address of the instruction which caused the bugcheck
Arg3: fffff8800b6fbcd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObReferenceObjectSafe+18
fffff800`032a51a8 f0490fb10a      lock cmpxchg qword ptr [r10],rcx

CONTEXT:  fffff8800b6fbcd0 -- (.cxr 0xfffff8800b6fbcd0)
rax=0b74f6850002ef5c rbx=0000000077b2f7a0 rcx=0b74f6850002ef5d
rdx=fffff800034bbc40 rsi=0000000077b2fbc0 rdi=fffffa8003e0eb60
rip=fffff800032a51a8 rsp=fffff8800b6fc6b0 rbp=fffff8800b6fcca0
 r8=00000000fffffffb  r9=fffffa800a6456d0 r10=0000000077b2f770
r11=0000000000000000 r12=0000000000000000 r13=fffffa800a6459a8
r14=0000000000000011 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ObReferenceObjectSafe+0x18:
fffff800`032a51a8 f0490fb10a      lock cmpxchg qword ptr [r10],rcx ds:002b:00000000`77b2f770=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  KiesPDLR.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800032a51a8

STACK_TEXT:  
fffff880`0b6fc6b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectSafe+0x18


FOLLOWUP_IP: 
nt!ObReferenceObjectSafe+18
fffff800`032a51a8 f0490fb10a      lock cmpxchg qword ptr [r10],rcx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObReferenceObjectSafe+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

STACK_COMMAND:  .cxr 0xfffff8800b6fbcd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectSafe+18

BUCKET_ID:  X64_0x3B_nt!ObReferenceObjectSafe+18

Followup: MachineOwner
---------


[/list]

Please update the following drivers.

wacommousefilter	fffff880`054cf000	fffff880`054d7000	Fri Feb 16 11:12:17 2007 (45d5f401)	00005ace		wacommousefilter.sys
sncduvc			fffff880`07fb2000	fffff880`07fbac00	Tue Jul 15 20:59:31 2008 (487d6413)	0001070d		sncduvc.SYS
hxctlflt		fffff880`07fbb000	fffff880`07fdc000	Mon Feb 09 00:43:09 2009 (498fde8d)	0001baad		hxctlflt.sys
snp2uvc			fffff880`07c3d000	fffff880`07fa0480	Wed Apr 22 01:46:04 2009 (49eecb3c)	0036b112		snp2uvc.sys
GEARAspiWDM		fffff880`063e6000	fffff880`063f3000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
PxHlpa64		fffff880`01277000	fffff880`01282e00	Tue Jun 23 17:16:35 2009 (4a416253)	000111b7		PxHlpa64.sys

• Wacomm Wacom(tablet) Mouse Filter driver: Drivers | Wacom Americas
• sncduvc Suyin USB 2.0 Webcam driver: Search Google for "Suyin USB 2.0 Webcam Windows 7 Driver" without quotes or let us know what webcam you have and we can help
• hxctlflt driver: http://ts.hercules.com/eng/index.php?pg=files_faq
  snp2uvc Suyin USB 2.0 Webcam driver: Search Google for "Suyin USB 2.0 Webcam Windows 7 Driver" without quotes or let us know what webcam you have and we can help
• GEARAspiWDM CD-ROM Class Filter Driver by Gear Software driver: GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering
• PxHlpa64 CD/DVD software driver: Depends on your DVD/CD software; see pxHelp20.sys programs for possible software and determine which you have on your system. If you need help finding the driver after determining the software, let us know.

Your first blue screen crash was related to USB/Human Interface Devices.

See http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html to start. Also, update any Bluetooth device drivers and gaming controller/joystick/gaming mouse drivers.

There are a few methods for updating drivers.

1. http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html
2. http://www.sevenforums.com/tutorials/99402-driver-install-add-hardware-wizard.html
3. http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html

To fully re-install a driver, use the following steps.

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

Your second blue screen crash is system related or hardware related.

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors.

Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
​

 

[vikti]

I passed the whole test without any errors.
I have upgraded my drivers (those I have found) and I have not get any BSOD for one month.

But now I am working on a project with Unity3D, 3DS and more open at the same time... 4 crashs in one hour... I made a new thread here.

 

[writhziden]

Alright, I have subscribed to the thread to help out if needed. You are in good hands with zigzag3143 at the moment.