New
#1
BSOD - bugcode_usb_driver?
Hi I see that someone else recently got the same bug, please help! I attached dumps
Hi I see that someone else recently got the same bug, please help! I attached dumps
See USB Driver - General Fix for Problems for methods to fix USB crashes.Code:Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\wungchow\Windows_NT6_BSOD_jcgriff2\011512-13603-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`0329b670 Debug session time: Sun Jan 15 06:46:07.405 2012 (UTC - 7:00) System Uptime: 0 days 0:18:46.295 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, fffffa8009354b20} ************************************************************************* *** *** *** *** *** 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 --------- 4: 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: fffffa8009354b20, 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 fffff88001047a60 to fffff800030d2c40 STACK_TEXT: fffff880`03569ad8 fffff880`01047a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`03569ae0 fffff800`033c99e3 : fffffa80`09335050 00000000`00000001 ffffffff`dc3a58a0 fffff800`032732b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`03569b40 fffff800`030dd001 : fffff800`03273200 fffff800`033c9901 fffffa80`0671ab00 fffff800`032732b8 : nt!IopProcessWorkItem+0x23 fffff880`03569b70 fffff800`0336dfee : 00000000`00000000 fffffa80`0671ab60 00000000`00000080 fffffa80`0668eb30 : nt!ExpWorkerThread+0x111 fffff880`03569c00 fffff800`030c45e6 : fffff880`0336d180 fffffa80`0671ab60 fffff880`033780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03569c40 00000000`00000000 : fffff880`0356a000 fffff880`03564000 fffff880`03569830 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`01047a60 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 ---------
This happened because i used a temporary mouse (an old wireless one) and then when replugged in my wired one it crashed after a bit. Should I bother doing this fix unless it happens again?
How have things been since removing the wireless mouse? Have the wireless drivers still been causing conflicts, or was it a one time crash?