BSoD's. Tons of them.

Flying Jack · 03 Sep 2010

Hello there !

So the title covered it pretty much, i get many BSoD randomly, with different error messages each time. The frequency is pretty random, but i hardly spend an hour on my computer without a BSoD.
I did a memtest and removed one of my memorys because it was corrupted , but still get these

I really think this could be from my MB since I re-installed the OS without any change, but I can't be sure and would like to have your thoughts.

I am running Win7 ultimate 64 bits

CPU : AMD Phenom II X4 955
MB : Gigabyte GA-890GPA-UD3H
Graphic Card : Radeon HD 5770

Tell me if my post is'nt as needed, thank you for reading !

**cluberti** · 03 Sep 2010

Looks like a USB device problem:

Code:

1: kd> kn
 # Child-SP          RetAddr           Call Site
00 fffff880`08f27128 fffff880`04fa414d nt!KeBugCheckEx
01 fffff880`08f27130 fffff880`04f7cf2d USBPORT!USBPORT_AssertSig+0x25
02 fffff880`08f27170 fffff880`04f7e131 USBPORT!USBPORT_AcquireEpListLock+0x21
03 fffff880`08f271a0 fffff880`04f89414 USBPORT!USBPORT_ReferenceEndpoint+0x29
04 fffff880`08f271f0 fffff880`04f991c4 USBPORT!USBPORT_Core_AllocTransferEx+0x2c4
05 fffff880`08f27280 fffff880`04fa1d44 USBPORT!USBPORT_ProcessURB+0x944
06 fffff880`08f27330 fffff880`04f7bad4 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
07 fffff880`08f27370 fffff880`0525e566 USBPORT!USBPORT_Dispatch+0x1dc
08 fffff880`08f273b0 fffff880`0528ecab usbhub!UsbhFdoUrbPdoFilter+0xde
09 fffff880`08f273e0 fffff880`0525cfb7 usbhub!UsbhPdoInternalDeviceControl+0x373
0a fffff880`08f27430 fffff880`053d6ec4 usbhub!UsbhGenDispatch+0x57
0b fffff880`08f27460 fffff880`053d3812 usbccgp!UsbcForwardIrp+0x30
0c fffff880`08f27490 fffff880`053d3aba usbccgp!DispatchPdoUrb+0xfa
0d fffff880`08f274d0 fffff880`053d172e usbccgp!DispatchPdoInternalDeviceControl+0x17a
0e fffff880`08f27500 fffff880`029b0729 usbccgp!USBC_Dispatch+0x2de
0f fffff880`08f27580 fffff880`029b0b92 usbaudio!USBType1BuildIsochUrbRequest+0x5a1
10 fffff880`08f27640 fffff880`03e14277 usbaudio!USBType1ProcessPin+0x22a
11 fffff880`08f276a0 fffff880`03e14764 ks!CKsPin::ProcessingObjectWork+0xe3
12 fffff880`08f276f0 fffff880`03e12e27 ks!CKsPin::Process+0x70
13 fffff880`08f27720 fffff880`03e13bb1 ks!CKsQueue::AddFrame+0x1e7

1: kd> lmvm ladfDHP2amd64
start             end                 module name
fffff880`029c9000 fffff880`029d6c00   ladfDHP2amd64 T (no symbols)           
    Loaded symbol image file: ladfDHP2amd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfDHP2amd64.sys
    Image name: ladfDHP2amd64.sys
    Timestamp:        Fri May 15 16:24:42 2009 (4A0DCF8A)
    CheckSum:         00011628
    ImageSize:        0000DC00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Dumping the raw stack from pointer to base indicated the driver I dumped out above, and I believe that's a Logitech Headset driver - it's also known to cause bugchecks in Win7 (you'll notice it predates Win7 GA by about 4 months, so it wasn't designed for Win7 either). There's an updated one on Logitech's site from July of 2009, but that's still before Win7. I'd still suggest upgrading the driver, though.

Jonathan_King · 03 Sep 2010

Welcome!

Your post is certainly necessary. We have a very high success rate here!

Start by updating your Logitech headset drivers. They were blamed by one dump, and are quite old.

If that doesn't work, I suspect your ATI drivers. Post back here first, before messing with them, because I am wondering if this driver should be watched out for.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 1 for BSoD files Jack.zip\Windows_NT6_BSOD_jcgriff2\090310-24616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Fri Sep  3 11:57:04.459 2010 (GMT-5)
System Uptime: 0 days 0:42:35.207
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, fffffa8004c4b010, 4f444648, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ladfDHP2amd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ladfDHP2amd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfDHP2amd64.sys
Probably caused by : usbaudio.sys ( usbaudio!USBType1BuildIsochUrbRequest+5a1 )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)
	has been corrupted.
Arg2: fffffa8004c4b010, Object address
Arg3: 000000004f444648, Signature that was expected
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88004fa414d to fffff80002a7b740

STACK_TEXT:  
fffff880`08f27128 fffff880`04fa414d : 00000000`000000fe 00000000`00000006 fffffa80`04c4b010 00000000`4f444648 : nt!KeBugCheckEx
fffff880`08f27130 fffff880`04f7cf2d : fffffa80`72745045 00000000`00000000 00000000`00000018 fffffa80`04bfd1a8 : USBPORT!USBPORT_AssertSig+0x25
fffff880`08f27170 fffff880`04f7e131 : fffffa80`01d86010 00000000`00000628 00000000`00000690 fffff880`04f78045 : USBPORT!USBPORT_AcquireEpListLock+0x21
fffff880`08f271a0 fffff880`04f89414 : fffffa80`01d86010 00000000`00000278 fffffa80`04c63048 fffffa80`035ea158 : USBPORT!USBPORT_ReferenceEndpoint+0x29
fffff880`08f271f0 fffff880`04f991c4 : fffffa80`035e9050 fffffa80`00000398 fffffa80`0431c010 fffffa80`05cca850 : USBPORT!USBPORT_Core_AllocTransferEx+0x2c4
fffff880`08f27280 fffff880`04fa1d44 : fffffa80`05cca850 fffffa80`0378000a fffffa80`05cca850 fffffa80`04c63048 : USBPORT!USBPORT_ProcessURB+0x944
fffff880`08f27330 fffff880`04f7bad4 : 00000000`00000000 fffffa80`03789050 fffffa80`05aaa7f0 fffffa80`05cca850 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138
fffff880`08f27370 fffff880`0525e566 : fffffa80`040d8050 fffffa80`040ca440 fffffa80`05cca850 fffffa80`040d81a0 : USBPORT!USBPORT_Dispatch+0x1dc
fffff880`08f273b0 fffff880`0528ecab : 00000000`00000000 00000000`00000000 fffffa80`040ca440 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde
fffff880`08f273e0 fffff880`0525cfb7 : fffffa80`043481b8 00000000`00000000 fffffa80`05cca850 fffffa80`0433bb58 : usbhub!UsbhPdoInternalDeviceControl+0x373
fffff880`08f27430 fffff880`053d6ec4 : 00000000`00000000 fffffa80`0433bc58 00000000`00000000 fffffa80`05cca850 : usbhub!UsbhGenDispatch+0x57
fffff880`08f27460 fffff880`053d3812 : fffffa80`043481b8 fffffa80`05cca850 fffffa80`00000324 fffffa80`05cca850 : usbccgp!UsbcForwardIrp+0x30
fffff880`08f27490 fffff880`053d3aba : fffffa80`0433bb58 00000000`00220003 fffffa80`05cca850 fffffa80`043481b8 : usbccgp!DispatchPdoUrb+0xfa
fffff880`08f274d0 fffff880`053d172e : 00000000`0000000f fffffa80`043481b0 fffffa80`043481b8 fffffa80`05cca850 : usbccgp!DispatchPdoInternalDeviceControl+0x17a
fffff880`08f27500 fffff880`029b0729 : fffffa80`04348060 fffffa80`04c0d701 fffffa80`05cca800 fffffa80`05ccab18 : usbccgp!USBC_Dispatch+0x2de
fffff880`08f27580 fffff880`029b0b92 : fffffa80`043490d0 fffff880`029afe54 00000000`0000fd00 fffffa80`056e4900 : usbaudio!USBType1BuildIsochUrbRequest+0x5a1
fffff880`08f27640 fffff880`03e14277 : 00000000`00000000 fffffa80`04c0d740 fffffa80`04c2bb08 00000000`00000100 : usbaudio!USBType1ProcessPin+0x22a
fffff880`08f276a0 fffff880`03e14764 : fffffa80`04c2bb08 00000000`000006e4 fffffa80`056e4900 fffffa80`04c4bd00 : ks!CKsPin::ProcessingObjectWork+0xe3
fffff880`08f276f0 fffff880`03e12e27 : fffffa80`04c4bcc0 fffffa80`056e4900 fffffa80`04c21820 fffffa80`04c4bcc0 : ks!CKsPin::Process+0x70
fffff880`08f27720 fffff880`03e13bb1 : fffffa80`04c4bcc0 fffffa80`056e4948 fffffa80`056e4620 fffffa80`04c21820 : ks!CKsQueue::AddFrame+0x1e7
fffff880`08f27760 fffff880`03e2c04b : 00000000`00000000 fffff880`029d383a fffff880`08f27860 fffffa80`01a43048 : ks!CKsQueue::TransferKsIrp+0x4a1
fffff880`08f277f0 fffff880`03e2b01b : fffffa80`04349010 fffffa80`04320b30 0000ac44`0008fffe fffffa80`0337d280 : ks!CKsPin::DispatchDeviceIoControl+0x20b
fffff880`08f27850 fffff880`03e12620 : 00000000`00000000 00000000`00000001 fffffa80`0434e6e0 fffffa80`056e4620 : ks!KsDispatchIrp+0xdb
fffff880`08f27880 fffff880`029d3a01 : fffffa80`056e4930 00000000`00000000 00000000`00000000 00000000`00000000 : ks!CKsDevice::PassThroughIrp+0xc0
fffff880`08f278c0 fffffa80`056e4930 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000001 : ladfDHP2amd64+0xaa01
fffff880`08f278c8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`00000001 fffffa80`00000001 : 0xfffffa80`056e4930


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbaudio!USBType1BuildIsochUrbRequest+5a1
fffff880`029b0729 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  f

SYMBOL_NAME:  usbaudio!USBType1BuildIsochUrbRequest+5a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME:  usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0xFE_usbaudio!USBType1BuildIsochUrbRequest+5a1

BUCKET_ID:  X64_0xFE_usbaudio!USBType1BuildIsochUrbRequest+5a1

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

1: kd> lmvm ladfDHP2amd64
start             end                 module name
fffff880`029c9000 fffff880`029d6c00   ladfDHP2amd64 T (no symbols)           
    Loaded symbol image file: ladfDHP2amd64.sys
    Image path: \SystemRoot\system32\DRIVERS\ladfDHP2amd64.sys
    Image name: ladfDHP2amd64.sys
    Timestamp:        Fri May 15 16:24:42 2009 (4A0DCF8A)
    CheckSum:         00011628
    ImageSize:        0000DC00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Flying Jack · 03 Sep 2010

Hey, thanks for quick answers !

The driver is already updated, i downloaded it 3 days ago

It's the latest on logitech's site, 07-26-2009. T_T

I re-installed it to be sure. I really think it's not the logitech driver, because i have these BSoD's since about a month and have the headset since 4 days.

**cluberti** · 03 Sep 2010

OK, so I took a look at some of the older ones (your minidumps only go back to 8/28), and found all kinds of things - a network card crash, this USB crash, and ATI driver crashes. However, the most common crash (by far) was in your ATI video driver's kernel. I'd test memory to make sure it's not an underlying hardware issue, but you might want to go back to older ATI drivers (you may have to test many versions) to see if any one version is more stable than another.

Flying Jack · 03 Sep 2010

Okay, i'll try older drivers (already tried some of them, but never before 10.0)

The minidumps go back to 8/28 because i re-installed the OS, hoping this would solve the problem. :O

I'll let you know if i get more BSoD or not - and i have a question about that : do you need all the files again or only the minidump files ?

See you

Jonathan_King · 03 Sep 2010

Go ahead and use the BSOD Posting Instructions again. I hate it when I need some info but don't have it.

Better too much info than too little.

Flying Jack · 07 Sep 2010

Hello again !

So, i've been trying new drivers, and still have BSOD. But i think i have a problem with driver uninstallation.

I couldn't find any way to unsinstall the CCC within the program itself, so i used the device manager to uninstall the driver of the display adapter, then used DriverCleaner in safe mode to remove everything. But when starting again, my screen was already in 1680x1050, and when i tried to install the driver, i get an error message saying it is already installed and up to date.

So i think the graphic card drivers problems encountered so far are beacause of this, but dunno how to solve it x)

(You can find BSOD files attached to this post)

Jonathan_King · 07 Sep 2010

First, remove Avast as it was running at the time of the first crash: http://files.avast.com/files/eng/aswclear5.exe

Replace it with MSE: http://www.microsoft.com/security_essentials

Install this Realtek driver: Realtek

Remove Daemon Tools Lite, as it uses SPTD. Then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v172-x64.exe

SPTD is well-known for causing BSODs in Vista and Windows 7.

Try uninstalling the Catalyst Control Center in Programs and Features. Then install these older ATI drivers: https://a248.e.akamai.net/f/674/9206...win7_64_dd.exe

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 05:55:25.836 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:26.194
BugCheck 24, {1904fb, fffff88006110c18, fffff88006110480, fffff80002aa8518}
Probably caused by : Ntfs.sys ( Ntfs!NtfsWriteLog+525 )
BUGCHECK_STR:  0x24
PROCESS_NAME:  AvastSvc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 05:54:16.865 2010 (UTC - 4:00)
System Uptime: 0 days 1:41:20.239
BugCheck D1, {60, 2, 0, fffff88003fecb9a}
*** WARNING: Unable to verify timestamp for LHidFilt.Sys
*** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
Probably caused by : mouhid.sys ( mouhid!WppAutoLogTrace+12 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep  6 10:12:45.438 2010 (UTC - 4:00)
System Uptime: 0 days 14:14:54.811
BugCheck 119, {7000000, fffffa8003e95410, fffffa8001a5f010, fffffa8004fb6870}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 18:36:35.517 2010 (UTC - 4:00)
System Uptime: 0 days 0:41:12.269
BugCheck 119, {7000000, fffffa800406f010, fffffa8001d31af0, fffffa8001e404e0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Flying Jack · 07 Sep 2010

Ok i have two problems here : CCC does not appear in Program and Features, and your link to ati drivers leads to an "Unauthorized Download"

Any idea ? :O