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: Bug_Code_USB Driver problem

16 Jan 2012   #1

windows 7 home premium 64bit
 
 
Bug_Code_USB Driver problem

hi
I have blue screen problem for a few months. when my laptop becomes blue screen, it says the problem is Bug_Code_USB driver. I used TuneUp Utilities 2012 to fix it but still i have same problem. I try to update the all the drivers from device manager, and all driver softwares for my device is already installed. I attached the minidumps file and the error message to the below. How can i fix this problem? thanks

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: fe
BCP1: 0000000000000008
BCP2: 0000000000000006
BCP3: 0000000000000005
BCP4: FFFFFA8004F8EB20
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\011612-19812-01.dmp
C:\Users\Ricky\AppData\Local\Temp\WER-1505128-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

My System SpecsSystem Spec
.

17 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\rcpclskn\011512-17097-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 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`03016000 PsLoadedModuleList = 0xfffff800`03253e70 Debug session time: Sat Jan 14 23:44:06.756 2012 (UTC - 7:00) System Uptime: 0 days 1:19:46.210 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, fffffa80066d9b20} ************************************************************************* *** *** *** *** *** 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: fffffa80066d9b20, 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 fffff88003e559ec to fffff800030865c0 STACK_TEXT: fffff880`0337ec18 fffff880`03e559ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`0337ec20 fffff800`0337f973 : fffffa80`0669c050 fffffa80`063eef20 ffffffff`dc3a58a0 fffff800`0322b5f8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`0337ec80 fffff800`030937e1 : fffff800`0322b500 fffff800`0337f950 fffffa80`03cec680 00000000`00000000 : nt!IopProcessWorkItem+0x23 fffff880`0337ecb0 fffff800`033266fa : a87017ed`36d38990 fffffa80`03cec680 00000000`00000080 fffffa80`03cd39e0 : nt!ExpWorkerThread+0x111 fffff880`0337ed40 fffff800`03064b46 : fffff880`03167180 fffffa80`03cec680 fffff880`031720c0 18b410fc`041fb15f : nt!PspSystemThreadStartup+0x5a fffff880`0337ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`03e559ec 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: 4d8c0aaa 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\rcpclskn\011512-21730-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03245670 Debug session time: Sun Jan 15 20:02:00.037 2012 (UTC - 7:00) System Uptime: 0 days 0:45:41.990 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, fffffa8005028b20} ************************************************************************* *** *** *** *** *** 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: fffffa8005028b20, 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 fffff88003f8da60 to fffff8000307cc40 STACK_TEXT: fffff880`0357ec18 fffff880`03f8da60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`0357ec20 fffff800`033739e3 : fffffa80`04fed050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0321d2b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`0357ec80 fffff800`03087001 : fffff800`0321d200 fffff800`03373901 fffffa80`03cec000 fffff800`0321d2b8 : nt!IopProcessWorkItem+0x23 fffff880`0357ecb0 fffff800`03317fee : 3b7a2a76`d8f54b87 fffffa80`03cec040 00000000`00000080 fffffa80`03cd3890 : nt!ExpWorkerThread+0x111 fffff880`0357ed40 fffff800`0306e5e6 : fffff880`03367180 fffffa80`03cec040 fffff880`033720c0 c396ca27`af513240 : nt!PspSystemThreadStartup+0x5a fffff880`0357ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`03f8da60 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\rcpclskn\011612-19812-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a3670 Debug session time: Mon Jan 16 12:47:04.748 2012 (UTC - 7:00) System Uptime: 0 days 5:15:32.589 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, fffffa8004f8eb20} ************************************************************************* *** *** *** *** *** 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 --------- 6: 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: fffffa8004f8eb20, 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 fffff88005a42a60 to fffff800030dac40 STACK_TEXT: fffff880`03577c18 fffff880`05a42a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000005 : nt!KeBugCheckEx fffff880`03577c20 fffff800`033d19e3 : fffffa80`04f7c050 00000000`00000001 ffffffff`dc3a58a0 fffff800`0327b2b8 : usbhub!UsbhHubProcessChangeWorker+0xec fffff880`03577c80 fffff800`030e5001 : fffff800`0327b200 fffff800`033d1901 fffffa80`03ced600 fffff800`0327b2b8 : nt!IopProcessWorkItem+0x23 fffff880`03577cb0 fffff800`03375fee : 90a29ca2`a9c48984 fffffa80`03ced680 00000000`00000080 fffffa80`03cd3890 : nt!ExpWorkerThread+0x111 fffff880`03577d40 fffff800`030cc5e6 : fffff880`03367180 fffffa80`03ced680 fffff880`033720c0 b21a103a`61aa618b : nt!PspSystemThreadStartup+0x5a fffff880`03577d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: usbhub!UsbhHubProcessChangeWorker+ec fffff880`05a42a60 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 ---------
I note that you do not have Service Pack 1 installed. Update to SP1
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH


After updating to SP1, if you continue to have these crashes, follow the steps in USB Driver - General Fix for Problems.


Also, update the following drivers.

Code:
ASMMAP64	fffff880`03bf6000	fffff880`03bfd000	Sun Feb 04 12:52:56 2007 (45c63998)	00010ca3		ASMMAP64.sys
SCDEmu		fffff880`015c2000	fffff880`015db000	Mon Jul 07 01:58:16 2008 (4871cc98)	000185f0		SCDEmu.SYS
sncduvc		fffff880`061d5000	fffff880`061dda80	Mon Dec 29 02:14:26 2008 (495894f2)	00008e3e		sncduvc.SYS
ATK64AMD	fffff880`0558f000	fffff880`05597000	Tue May 12 19:04:54 2009 (4a0a1cb6)	000096a6		ATK64AMD.sys
GEARAspiWDM	fffff880`05567000	fffff880`05574000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
RtHDMIVX	fffff880`05ab6000	fffff880`05ae5b00	Wed May 20 04:04:50 2009 (4a13d5c2)	00034355		RtHDMIVX.sys
You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
  1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
  2. Driver Search Methods provides driver manufacturers and links to their homepages.
There are a few methods for updating drivers.
  1. Installing and updating drivers in 7
  2. Driver Install - Add Hardware Wizard
  3. Driver Install - Device Manager

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

Alternatively:
  1. Login as an adminstrative user.
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer
  11. Install the latest driver for the device once Windows starts.
We also do not recommend using TuneUp Utilities 2012 as Windows 7 is much better than its predecessors at managing itself and keeping optimized. Automated software for "fixing" Windows 7 tends to cause errors and corruption in the system. In the future, if you need help with optimizing Windows 7 or solving blue screen crashes, please seek help in these forums where experienced users can guide you to a solution. Performance & Maintenance is an excellent source to optimize your computer if you post a thread there for assistance. There are also useful tutorials in that forum.
My System SpecsSystem Spec
Reply

 Bug_Code_USB Driver problem





Thread Tools



Similar help and support threads for2: Bug_Code_USB Driver problem
Thread Forum
Driver Problem Graphic Cards
Solved Driver Problem Drivers
Solved Driver Problem Help !!! Drivers
AMD Driver 11.6 Driver Update Problem Graphic Cards
DVD/CD driver problem Drivers
ATI Driver problem ? BSOD Help and Support
driver problem Drivers

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 03:02 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33