Random USB Related BSODs, minidump included

[jjfishtank]

Hello.
I've been getting completely random BSODs related to my USBHUB. I think It may be my headset that causes the issue because it randomly looses power and I have to plug it back in again. I already checked that I have more than enough power supply.
WINDBG ANALYSIS:

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be70
Debug session time: Sun Jan 22 23:18:00.542 2012 (GMT-8)
System Uptime: 0 days 1:35:57.492
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 6, fffffa8008726160}

Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

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

2: 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: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa8008726160, TimeoutContext - PortData

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


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800516c9ec to fffff80002e7e5c0

STACK_TEXT:
fffff880`03168c18 fffff880`0516c9ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx
fffff880`03168c20 fffff800`03177973 : fffffa80`08801050 fffff800`03083f00 ffffffff`dc3a58a0 fffff800`030235f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`03168c80 fffff800`02e8b7e1 : fffff800`0316e500 fffff800`0316e5ac fffffa80`06a3bb60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`03168cb0 fffff800`0311e6fa : 00000000`00000000 fffffa80`06a3bb60 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`03168d40 fffff800`02e5cb46 : fffff880`03088180 fffffa80`06a3bb60 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03168d80 00000000`00000000 : fffff880`03169000 fffff880`03163000 fffff880`03168970 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0516c9ec cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc2d

FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner

Thanks for any help.

 

[zigzag3143]

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.

If you are overclocking STOP

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.

 

[jjfishtank]

Not at my computer atm.
1) I'm not overclocking.
2) A few weeks ago I installed a new motherboard, 8 gigs of ram, AMD Graphics Card, and Processor. (I don't know if this is relevant.)
3) I reformatted my hard drive 3 days ago because of this BSOD. I am still getting the blue screen. It happens on average once or twice every couple days.
4) I tried uploading memory.dmp, but It takes too long and the upload page times out. I'll try to upload it to mediafire later today.

 

[jjfishtank]

Here's the minidump dump file:

Loading Dump File [C:\Windows\Minidump\012312-32370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be70
Debug session time: Sun Jan 22 23:18:00.542 2012 (GMT-8)
System Uptime: 0 days 1:35:57.492
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 6, fffffa8008726160}

Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

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

2: 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: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa8008726160, TimeoutContext - PortData

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800516c9ec to fffff80002e7e5c0

STACK_TEXT:
fffff880`03168c18 fffff880`0516c9ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx
fffff880`03168c20 fffff800`03177973 : fffffa80`08801050 fffff800`03083f00 ffffffff`dc3a58a0 fffff800`030235f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`03168c80 fffff800`02e8b7e1 : fffff800`0316e500 fffff800`0316e5ac fffffa80`06a3bb60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`03168cb0 fffff800`0311e6fa : 00000000`00000000 fffffa80`06a3bb60 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`03168d40 fffff800`02e5cb46 : fffff880`03088180 fffffa80`06a3bb60 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03168d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0516c9ec cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc2d

FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner

Link to the file itself: 012312-32370-01.dmp

 

[jjfishtank]

Bump

 

[zigzag3143]

Bump

USBHUB.SYS eiether caused by AVG or Related to danew.sys Razer DeathAdder USB Optical Mouse Driver from Razer (Asia-Pacific) Pte Ltd. I would re-install newest version available. Yours is ~1 year old


AVG can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide

Microsoft Security Essentials - Free Antivirus for Windows