Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD bugcode_usb_driver FE

13 Jan 2012   #1
Simbab

Windows 7 professional x64
 
 
BSOD bugcode_usb_driver FE

Hello everybody,

Could you help me to identify what is causing the BSOD ?

I updated the drivers, thought the problem was gone, but today again.

Computer: HP Probook 4520S
Windows 7 professional x64

BSOD when attached: Wimax USB internet adapter (mezon), Logitech USB mouse.
Mostly happens when i click something with the mouse.

Code:
  BCCode: fe
  BCP1:    0000000000000008
  BCP2:    0000000000000006
  BCP3:    0000000000000005
  BCP4:    FFFFFA8006BEAC80
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1
Logs and minidumps: Download BSOD.zip from Sendspace.com - send big files the easy way

Thank you


My System SpecsSystem Spec
.
13 Jan 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010412-13072-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`03005000 PsLoadedModuleList = 0xfffff800`0324a670 Debug session time: Wed Jan 4 05:12:45.531 2012 (UTC - 7:00) System Uptime: 0 days 3:33:46.702 Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list .................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006b48c80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006b48c80, TimeoutContext - PortData 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 *** *** *** ************************************************************************* OVERLAPPED_MODULE: Address regions for 'ipnat' and 'ipnat.sys' overlap CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff880071a0a60 to fffff80003081c40 STACK_TEXT: fffff880`033a8c18 fffff880`071a0a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033a8c20 fffff800`033789e3 : fffffa80`06b3e050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032222b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033a8c80 fffff800`0308c001 : fffff800`03222200 fffff800`03378901 fffffa80`03b68b00 fffffa80`03b68b60 : nt!IopProcessWorkItem+0x23 fffff880`033a8cb0 fffff800`0331cfee : fedfffbf`ffffdfff fffffa80`03b68b60 00000000`00000080 fffffa80`03b4e9e0 : nt!ExpWorkerThread+0x111 fffff880`033a8d40 fffff800`030735e6 : fffff880`031d3180 fffffa80`03b68b60 fffff880`031ddfc0 d3f96bdb`f5513eff : nt!PspSystemThreadStartup+0x5a fffff880`033a8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`071a0a60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010412-13369-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`03017000 PsLoadedModuleList = 0xfffff800`0325c670 Debug session time: Wed Jan 4 05:15:27.778 2012 (UTC - 7:00) System Uptime: 0 days 0:01:50.949 Loading Kernel Symbols ............................................................... ................................................................ .......................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006b72c80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) 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: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT Arg3: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006b72c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff8800c6cfa60 to fffff80003093c40 STACK_TEXT: fffff880`035afc18 fffff880`0c6cfa60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`035afc20 fffff800`0338a9e3 : fffffa80`06b8d050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032342b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`035afc80 fffff800`0309e001 : fffff800`03234200 fffff800`0338a901 fffffa80`03b82600 fffffa80`03b82680 : nt!IopProcessWorkItem+0x23 fffff880`035afcb0 fffff800`0332efee : 00002000`00000009 fffffa80`03b82680 00000000`00000080 fffffa80`03b689e0 : nt!ExpWorkerThread+0x111 fffff880`035afd40 fffff800`030855e6 : fffff880`033d3180 fffffa80`03b82680 fffff880`033ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`035afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`0c6cfa60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010412-20685-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`03055000 PsLoadedModuleList = 0xfffff800`0329a670 Debug session time: Wed Jan 4 13:14:54.006 2012 (UTC - 7:00) System Uptime: 0 days 7:58:42.193 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006c10c80} ************************************************************************* *** *** *** *** *** 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 : 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006c10c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff880076a6a60 to fffff800030d1c40 STACK_TEXT: fffff880`033a1c18 fffff880`076a6a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033a1c20 fffff800`033c89e3 : fffffa80`06bf6050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032722b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033a1c80 fffff800`030dc001 : fffff800`03272200 fffff800`033c8901 fffffa80`03b82000 fffff800`032722b8 : nt!IopProcessWorkItem+0x23 fffff880`033a1cb0 fffff800`0336cfee : 00000000`00000000 fffffa80`03b82040 00000000`00000080 fffffa80`03b689e0 : nt!ExpWorkerThread+0x111 fffff880`033a1d40 fffff800`030c35e6 : fffff880`031d3180 fffffa80`03b82040 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`076a6a60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  4. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010412-12948-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`0305b000 PsLoadedModuleList = 0xfffff800`032a0670 Debug session time: Wed Jan 4 13:35:03.364 2012 (UTC - 7:00) System Uptime: 0 days 0:14:56.909 Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006c25c80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006c25c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff88007509a60 to fffff800030d7c40 STACK_TEXT: fffff880`033afc18 fffff880`07509a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033afc20 fffff800`033ce9e3 : fffffa80`06c19050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032782b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033afc80 fffff800`030e2001 : fffff800`03278200 fffff800`033ce901 fffffa80`03b82600 fffffa80`03b82680 : nt!IopProcessWorkItem+0x23 fffff880`033afcb0 fffff800`03372fee : 00000000`00000000 fffffa80`03b82680 00000000`00000080 fffffa80`03b689e0 : nt!ExpWorkerThread+0x111 fffff880`033afd40 fffff800`030c95e6 : fffff880`031d3180 fffffa80`03b82680 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`07509a60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  5. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010612-13119-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`0304b000 PsLoadedModuleList = 0xfffff800`03290670 Debug session time: Fri Jan 6 11:19:57.897 2012 (UTC - 7:00) System Uptime: 0 days 9:33:02.068 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006b78c80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006b78c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff88008853a60 to fffff800030c7c40 STACK_TEXT: fffff880`033afc18 fffff880`08853a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033afc20 fffff800`033be9e3 : fffffa80`06b43050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032682b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033afc80 fffff800`030d2001 : fffff800`03268200 fffff800`033be901 fffffa80`03b68600 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`033afcb0 fffff800`03362fee : 05b7fffb`fffffcff fffffa80`03b68680 00000000`00000080 fffffa80`03b4e9e0 : nt!ExpWorkerThread+0x111 fffff880`033afd40 fffff800`030b95e6 : fffff880`031d3180 fffffa80`03b68680 fffff880`031ddfc0 02adfab8`bf7edfff : nt!PspSystemThreadStartup+0x5a fffff880`033afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`08853a60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  6. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010612-13369-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`0304d000 PsLoadedModuleList = 0xfffff800`03292670 Debug session time: Fri Jan 6 12:07:25.941 2012 (UTC - 7:00) System Uptime: 0 days 0:46:35.487 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ..................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006c10c80} ************************************************************************* *** *** *** *** *** 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 : 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006c10c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff880088fea60 to fffff800030c9c40 STACK_TEXT: fffff880`033a1c18 fffff880`088fea60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033a1c20 fffff800`033c09e3 : fffffa80`06c09050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0326a2b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033a1c80 fffff800`030d4001 : fffff800`0326a200 fffff800`033c0901 fffffa80`03b82000 fffff800`0326a2b8 : nt!IopProcessWorkItem+0x23 fffff880`033a1cb0 fffff800`03364fee : 00000040`00600001 fffffa80`03b82040 00000000`00000080 fffffa80`03b689e0 : nt!ExpWorkerThread+0x111 fffff880`033a1d40 fffff800`030bb5e6 : fffff880`031d3180 fffffa80`03b82040 fffff880`031ddfc0 00000000`00400000 : nt!PspSystemThreadStartup+0x5a fffff880`033a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`088fea60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  7. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010612-17144-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`03002000 PsLoadedModuleList = 0xfffff800`03247670 Debug session time: Fri Jan 6 12:16:30.697 2012 (UTC - 7:00) System Uptime: 0 days 0:07:54.868 Loading Kernel Symbols ............................................................... ................................................................ ............................................. Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006beac80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006beac80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff880074f5a60 to fffff8000307ec40 STACK_TEXT: fffff880`033b6c18 fffff880`074f5a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033b6c20 fffff800`033759e3 : fffffa80`06bcc050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0321f2b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033b6c80 fffff800`03089001 : fffff800`0321f200 fffff800`03375901 fffffa80`03b81000 fffffa80`03b81040 : nt!IopProcessWorkItem+0x23 fffff880`033b6cb0 fffff800`03319fee : 00000000`00000000 fffffa80`03b81040 00000000`00000080 fffffa80`03b689e0 : nt!ExpWorkerThread+0x111 fffff880`033b6d40 fffff800`030705e6 : fffff880`031d3180 fffffa80`03b81040 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`074f5a60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
  8. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Simbab\Windows_NT6_BSOD_jcgriff2\010912-12043-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`03013000 PsLoadedModuleList = 0xfffff800`03258670 Debug session time: Mon Jan 9 02:38:35.104 2012 (UTC - 7:00) System Uptime: 0 days 1:01:42.291 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {8, 6, 5, fffffa8006657c80} ************************************************************************* *** *** *** *** *** 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 : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec ) Followup: MachineOwner --------- 0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent Arg4: fffffa8006657c80, TimeoutContext - PortData 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: 0 LAST_CONTROL_TRANSFER: from fffff8800419ca60 to fffff8000308fc40 STACK_TEXT: fffff880`033a1c18 fffff880`0419ca60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`033a1c20 fffff800`033869e3 : fffffa80`0664d050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032302b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`033a1c80 fffff800`0309a001 : fffff800`03230200 fffff800`03386901 fffffa80`03b68000 fffffa80`03b68040 : nt!IopProcessWorkItem+0x23 fffff880`033a1cb0 fffff800`0332afee : 30ffefff`ffffbfff fffffa80`03b68040 00000000`00000080 fffffa80`03b4e9e0 : nt!ExpWorkerThread+0x111 fffff880`033a1d40 fffff800`030815e6 : fffff880`031d3180 fffffa80`03b68040 fffff880`031ddfc0 00f7533f`76ad7b0d : nt!PspSystemThreadStartup+0x5a fffff880`033a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`0419ca60 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: 4d8c0c15 FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec Followup: MachineOwner ---------
Run through the steps in USB Driver - General Fix for Problems to troubleshoot your USB issues.
My System SpecsSystem Spec
25 Jan 2012   #3
Simbab

Windows 7 professional x64
 
 

Thanks for reply.

However, after trying that few times i still experiencing same error. Seems more rarely but still annoying as hell.

I would be very grateful if somebody could scan my crashlogs and point me to the driver that's causing BSOD.

Thanks,
Simon
My System SpecsSystem Spec
.

25 Jan 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.[/B]
  • If you are overclocking anything, please stop.


  • Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


  • 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).


  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.



It also appears that you have a conflict with your firewall. What antivirus software are you using?

Due to the firewall issue causing a USB crash, I must ask, is your wireless adapter a USB device?
My System SpecsSystem Spec
25 Jan 2012   #5
Simbab

Windows 7 professional x64
 
 

AVAST free + Comodo firewall free.

I will remove daemon tools, and will do other steps. Thanks
My System SpecsSystem Spec
25 Jan 2012   #6
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Simbab View Post
AVAST free + Comodo firewall free.

I will remove daemon tools, and will do other steps. Thanks
AVAST is known to cause blue screen crashes on some systems, and since your problem was firewall based, I also would think Comodo might be at fault. Please uninstall both and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least for testing.

To uninstall AVAST, use the avast! Uninstall Utility

Remove Comodo through Control Panel's Uninstall a program feature.

Recommend doing so before running Driver Verifier to see if it improves stability first.
My System SpecsSystem Spec
26 Jan 2012   #7
Simbab

Windows 7 professional x64
 
 

Quote:
BSOD when attached: Wimax USB internet adapter (mezon), Logitech USB mouse.
Wireless is integrated.

Quote   Quote: Originally Posted by writhziden View Post
Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.[/B]
  • If you are overclocking anything, please stop.
  • Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
  • 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).
  • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
    a. Backup your system and user files
    b. Create a system restore point
    c. If you do not have a Windows 7 DVD, Create a system repair disc
    d. Run Driver Verifier

    If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

    Thanks to zigzag3143 for contributing to the Verifier steps.
    If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.



It also appears that you have a conflict with your firewall. What antivirus software are you using?

Due to the firewall issue causing a USB crash, I must ask, is your wireless adapter a USB device?
My System SpecsSystem Spec
26 Jan 2012   #8
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by Simbab View Post
Quote:
BSOD when attached: Wimax USB internet adapter (mezon), Logitech USB mouse.
Wireless is integrated.
Alright, let us know if your system is stable after the steps are completed. Best wishes!
My System SpecsSystem Spec
16 Feb 2012   #9
Simbab

Windows 7 professional x64
 
 

Hey guys,

i followed steps and did not had crash for a half month, but today again.

Please, somebody analyze my BSOD dump file. Maybe you can find driver that's causing the BSOD.

Thank you very much.

Dump file: Download dump.dmp from Sendspace.com - send big files the easy way
My System SpecsSystem Spec
16 Feb 2012   #10
writhziden

Windows 7 Home Premium 64 Bit
 
 

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


Loading Dump File [F:\BSODDmpFiles\Simbab\dump.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`03009000 PsLoadedModuleList = 0xfffff800`0324e670
Debug session time: Thu Feb 16 03:36:41.942 2012 (GMT-7)
System Uptime: 0 days 0:49:15.487
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 5, fffffa800730ec80}

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

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

0: 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: 0000000000000005, TimeoutCode: Timeout_PCE_Suspend_Action3 - PortData->PortSuspendEvent
Arg4: fffffa800730ec80, TimeoutContext - PortData

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


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88004a12a60 to fffff80003085c40

STACK_TEXT:  
fffff880`033afc18 fffff880`04a12a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx
fffff880`033afc20 fffff800`0337c9e3 : fffffa80`07308050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032262b8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`033afc80 fffff800`03090001 : fffff800`03226200 fffff800`0337c901 fffffa80`03b68600 fffffa80`03b68680 : nt!IopProcessWorkItem+0x23
fffff880`033afcb0 fffff800`03320fee : 00000000`00000019 fffffa80`03b68680 00000000`00000080 fffffa80`03b4e9e0 : nt!ExpWorkerThread+0x111
fffff880`033afd40 fffff800`030775e6 : fffff880`031d3180 fffffa80`03b68680 fffff880`031ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033afd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`04a12a60 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:  4d8c0c15

FAILURE_BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID:  X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner
---------
The crash files are still pointing to your USB devices. Do you have a USB wireless device, by chance? I do notice a bluetooth USB device...

Please follow the http://www.sevenforums.com/crashes-d...tructions.html and upload the files to your next post (not to a third party site). There is information included in the files generated through those instructions that will help us provide more informed troubleshooting steps.
My System SpecsSystem Spec
Reply

 BSOD bugcode_usb_driver FE




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Bugcode_usb_driver bsod
Have been getting BUGCODE_USB_DRIVER crash pretty randomly for about the last month or so. I didn't make any big hardware or software changes so I can't figure out what the problem is. It doesn't seem to be linked to any specific USB device being connected either. I reformatted my system when...
BSOD Help and Support
BUGCODE_USB_DRIVER bsod
.......it happened to me when I tried to restart my computer. It just happened once, but it was very weird because everything's been very stable. I just want to know if I there is something I shoud update/fix/takecare/uninstall in order to not suffer from this type of BSOD in the near future. ...
BSOD Help and Support
BSOD Bugcode_usb_driver
It's been crashing repeatedly at random intervals. I don't know how to interpret the dump files so I come to you guys for help. Any assistance would be fantastic thanks. Dump files are attached.
BSOD Help and Support
'bugcode_usb_driver' bsod
Hello. I just got a BSOD saying "BUGCODE_USB_DRIVER" and then it restarted by itself. I attached the necessary files in zip. What should I do?
BSOD Help and Support
Bugcode_usb_driver BSOD
Hey guys, As the thread title states im having a Bugcode_usb_driver BSOD problem.. I have an Acer Aspire with Windows 7 Home Premium x64, that i have had for about 10 months... I have attached the files as requested... Thanks in advance for your help...
BSOD Help and Support
BSOD bugcode_usb_driver
Hi I have had this a few times on my computer. Please could you help? OS Name Microsoft® Windows Vista™ Home Premium Version 6.0.6002 Service Pack 2 Build 6002 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name HOMEPC System Manufacturer HP-Pavilion System...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 18:37.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App