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 usb_bug_code


14 Jan 2012   #1

Windows 7 64 bit
 
 
Bsod usb_bug_code

I just very recently started getting the BSOD BUGCODE_USB_DRIVER and a DRIVER IRQL NOT LESS OR EQUAL ERROR, I do not understand why and they are becoming very much annoying up to two times a day I get these. I have gone ahead and zipped the minidump and Health Report, which are attached. My Specs are as follows.
System Model: Custom Built
CPU: Q9550
GPU: 1024MB Geforce 520 GT
RAM: G-Skills 8MB DDR3 Ram
OS: Windows 7 Home Premium x64 OEM
Age: I can't say for certain I bought it off someone. I'd guess not much older than a few years.
Nothing in the system has been or will be overclocked.
I do have alot of usb devices attached, such as Razer Death Adder, Razer Lycosa, Razer Nostromo, and a Tritton AX PC PRO. I did not have this problem until installing the drivers for the Tritton headset, I uninstalled them Reinstalled and tried previous versions but I still seem to get the error. I'm assuming it's nothing major that is causing this issue, but it is quite annoying. I'm a heavy gamer and getting BSOD in the middle of a firefight is really suckish. I've tried uninstalling and reinstalling updating and removing almost every driver for my usb devices on my computer and I can not seem to dodge receving this error.

I would be very greatful with any feedback helping with this matter. Thanks in advance.

Kyle.

My System SpecsSystem Spec
.

14 Jan 2012   #2

Win 8 Release candidate 8400
 
 

Two things pop out Immediately.

First asacpi.sys (yours 2005)

Asacpi.sys

The pre 2009 version of this driver is a known bsod cause.
Quote:
Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).
Second, your Symantec.

I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST



http://us.norton.com/support/kb/web_...080710133834EN


Microsoft Security Essentials - Free Antivirus for Windows
My System SpecsSystem Spec
14 Jan 2012   #3

Windows 7 64 bit
 
 

The driver listed now dates 2009 and not 2005 after updating it. Im also currently in the process of uninstalling norton. Thank you very much!
My System SpecsSystem Spec
.


14 Jan 2012   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by DawnZero View Post
The driver listed now dates 2009 and not 2005 after updating it. Im also currently in the process of uninstalling norton. Thank you very much!

Good luck and let us know if you need help.

BTW if you feel the problem is solved please return and use the red triangle to ask that it be solved.
My System SpecsSystem Spec
14 Jan 2012   #5

Windows 7 64 bit
 
 

Been running all day no BSOD yet. Thanks a ton!
My System SpecsSystem Spec
14 Jan 2012   #6

Windows 7 64 bit
 
 

Just got a BSOD BUGCODE_USB_DRIVER again. Going to add the zipped stuff shortly.
I think the health report might be telling me something...it's clearly pointing to my card reader which I do not use anyway...

Device Manager now has the yellow triangles over the portable devices, assume the 4 listed are the 4 slots more my card reader I clicked properties and have this message.

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

I followed the health report and uninstalled the devices, and reinstalled them. They now seem to be "working properly". For some reason tho, it still doesn't actually "work",
My System SpecsSystem Spec
14 Jan 2012   #7

Windows 7 64 bit
 
 

Just got another BSOD BUGCODE_USB_DRIVER. So it obviously didn't work. I will post the new files here shortly.

Until I can get help with this I am going to try uninstalling them from device manager.
My System SpecsSystem Spec
14 Jan 2012   #8

Windows 7 64 bit
 
 

Still having issues with this.
My System SpecsSystem Spec
14 Jan 2012   #9

Windows 7 64 bit
 
 

I'm really at a loss trying to solve this myself. Anyone at all have any suggestions please!
My System SpecsSystem Spec
14 Jan 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\DawnZero\Windows_NT6_BSOD_jcgriff2\011712-26348-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02eac670 Debug session time: Tue Jan 17 17:53:37.413 2012 (UTC - 7:00) System Uptime: 0 days 5:48:05.755 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {4, fffffa8009ae8c60, fffffa8009adf5d0, fffffa800b31f9a0} Unable to load image \SystemRoot\system32\drivers\CM10664.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for CM10664.sys *** ERROR: Module load completed but symbols could not be loaded for CM10664.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : CM10664.sys ( CM10664+287ac ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp that is already pending in the USB bus driver. Arg2: fffffa8009ae8c60, Address of IRP Arg3: fffffa8009adf5d0, Address of URB Arg4: fffffa800b31f9a0 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 *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88004a16f4b to fffff80002ce3c40 STACK_TEXT: fffff880`039ec798 fffff880`04a16f4b : 00000000`000000fe 00000000`00000004 fffffa80`09ae8c60 fffffa80`09adf5d0 : nt!KeBugCheckEx fffff880`039ec7a0 fffff880`04a2244a : fffffa80`08a76000 fffffa80`09ab1610 00000000`00000000 fffffa80`08a76050 : USBPORT!USBPORT_Core_DetectActiveUrb+0x127 fffff880`039ec7f0 fffff880`04a2ae74 : fffffa80`09ae8c60 fffffa80`091c000a fffffa80`09ae8c60 fffffa80`09adf5d0 : USBPORT!USBPORT_ProcessURB+0xad6 fffff880`039ec8a0 fffff880`04a04af4 : 00000000`00000000 fffffa80`091c4050 fffffa80`0a7e91a0 fffffa80`09ae8c60 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138 fffff880`039ec8e0 fffff880`050d5566 : fffffa80`091cf050 fffffa80`09ad6060 fffffa80`09ae8c60 fffffa80`091cf1a0 : USBPORT!USBPORT_Dispatch+0x1dc fffff880`039ec920 fffff880`05105d8f : 00000000`00000000 00000000`00000000 fffffa80`09ad6060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde fffff880`039ec950 fffff880`050d3fb7 : fffffa80`09ad7b58 00000000`00000000 fffffa80`09ae8c60 fffffa80`09ace1b8 : usbhub!UsbhPdoInternalDeviceControl+0x373 fffff880`039ec9a0 fffff880`05d26ec4 : 00000000`00000000 fffffa80`09ace2b8 00000000`00000000 fffffa80`09ace1b8 : usbhub!UsbhGenDispatch+0x57 fffff880`039ec9d0 fffff880`05d23812 : fffffa80`09ad7b58 fffffa80`09ae8c60 00000000`00000324 fffffa80`09ae8c60 : usbccgp!UsbcForwardIrp+0x30 fffff880`039eca00 fffff880`05d23aba : fffffa80`09ace1b8 00000000`00220003 fffffa80`09ae8c60 fffffa80`09ad7b58 : usbccgp!DispatchPdoUrb+0xfa fffff880`039eca40 fffff880`05d2172e : 00000000`0000000f fffffa80`09ad7b50 fffffa80`09ad7b58 fffffa80`09ae8c60 : usbccgp!DispatchPdoInternalDeviceControl+0x17a fffff880`039eca70 fffff880`03c357ac : fffffa80`09ad7a00 00000000`00000001 00000000`00000000 00000000`00000103 : usbccgp!USBC_Dispatch+0x2de fffff880`039ecaf0 fffffa80`09ad7a00 : 00000000`00000001 00000000`00000000 00000000`00000103 fffffa80`09ade248 : CM10664+0x287ac fffff880`039ecaf8 00000000`00000001 : 00000000`00000000 00000000`00000103 fffffa80`09ade248 fffff880`03c3673d : 0xfffffa80`09ad7a00 fffff880`039ecb00 00000000`00000000 : 00000000`00000103 fffffa80`09ade248 fffff880`03c3673d fffffa80`09adde88 : 0x1 STACK_COMMAND: kb FOLLOWUP_IP: CM10664+287ac fffff880`03c357ac ?? ??? SYMBOL_STACK_INDEX: c SYMBOL_NAME: CM10664+287ac FOLLOWUP_NAME: MachineOwner MODULE_NAME: CM10664 IMAGE_NAME: CM10664.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac47ec3 FAILURE_BUCKET_ID: X64_0xFE_CM10664+287ac BUCKET_ID: X64_0xFE_CM10664+287ac Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\DawnZero\Windows_NT6_BSOD_jcgriff2\011812-28657-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02ea5670 Debug session time: Wed Jan 18 07:35:25.215 2012 (UTC - 7:00) System Uptime: 0 days 12:13:17.558 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {4, fffffa8009239b10, fffffa8009afddd0, fffffa8007982010} Unable to load image \SystemRoot\system32\drivers\CM10664.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for CM10664.sys *** ERROR: Module load completed but symbols could not be loaded for CM10664.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : CM10664.sys ( CM10664+287ac ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp that is already pending in the USB bus driver. Arg2: fffffa8009239b10, Address of IRP Arg3: fffffa8009afddd0, Address of URB Arg4: fffffa8007982010 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 *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff88004a16f4b to fffff80002cdcc40 STACK_TEXT: fffff880`03fce798 fffff880`04a16f4b : 00000000`000000fe 00000000`00000004 fffffa80`09239b10 fffffa80`09afddd0 : nt!KeBugCheckEx fffff880`03fce7a0 fffff880`04a2244a : fffffa80`08a28000 fffffa80`09a931f0 00000000`00000000 fffffa80`08a28050 : USBPORT!USBPORT_Core_DetectActiveUrb+0x127 fffff880`03fce7f0 fffff880`04a2ae74 : fffffa80`09239b10 fffffa80`091a000a fffffa80`09239b10 fffffa80`09afddd0 : USBPORT!USBPORT_ProcessURB+0xad6 fffff880`03fce8a0 fffff880`04a04af4 : 00000000`00000000 fffffa80`091af050 fffffa80`0b1f3540 fffffa80`09239b10 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138 fffff880`03fce8e0 fffff880`050ee566 : fffffa80`091c5050 fffffa80`09aa3060 fffffa80`09239b10 fffffa80`091c51a0 : USBPORT!USBPORT_Dispatch+0x1dc fffff880`03fce920 fffff880`0511ed8f : 00000000`00000000 00000000`00000000 fffffa80`09aa3060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde fffff880`03fce950 fffff880`050ecfb7 : fffffa80`09abe1b8 00000000`00000000 fffffa80`09239b10 fffffa80`09ab6b58 : usbhub!UsbhPdoInternalDeviceControl+0x373 fffff880`03fce9a0 fffff880`05da0ec4 : 00000000`00000000 fffffa80`09ab6c58 00000000`00000000 fffffa80`09ab6b58 : usbhub!UsbhGenDispatch+0x57 fffff880`03fce9d0 fffff880`05d9d812 : fffffa80`09abe1b8 fffffa80`09239b10 00000000`00000324 fffffa80`09239b10 : usbccgp!UsbcForwardIrp+0x30 fffff880`03fcea00 fffff880`05d9daba : fffffa80`09ab6b58 00000000`00220003 fffffa80`09239b10 fffffa80`09abe1b8 : usbccgp!DispatchPdoUrb+0xfa fffff880`03fcea40 fffff880`05d9b72e : 00000000`0000000f fffffa80`09abe1b0 fffffa80`09abe1b8 fffffa80`09239b10 : usbccgp!DispatchPdoInternalDeviceControl+0x17a fffff880`03fcea70 fffff880`03c617ac : fffffa80`09abe060 00000000`00000001 00000000`00000000 00000000`00000103 : usbccgp!USBC_Dispatch+0x2de fffff880`03fceaf0 fffffa80`09abe060 : 00000000`00000001 00000000`00000000 00000000`00000103 fffffa80`09af9df8 : CM10664+0x287ac fffff880`03fceaf8 00000000`00000001 : 00000000`00000000 00000000`00000103 fffffa80`09af9df8 fffff880`03c6273d : 0xfffffa80`09abe060 fffff880`03fceb00 00000000`00000000 : 00000000`00000103 fffffa80`09af9df8 fffff880`03c6273d fffffa80`09af6408 : 0x1 STACK_COMMAND: kb FOLLOWUP_IP: CM10664+287ac fffff880`03c617ac ?? ??? SYMBOL_STACK_INDEX: c SYMBOL_NAME: CM10664+287ac FOLLOWUP_NAME: MachineOwner MODULE_NAME: CM10664 IMAGE_NAME: CM10664.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac47ec3 FAILURE_BUCKET_ID: X64_0xFE_CM10664+287ac BUCKET_ID: X64_0xFE_CM10664+287ac Followup: MachineOwner ---------
  3. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\DawnZero\Windows_NT6_BSOD_jcgriff2\011812-32089-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 Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e61670 Debug session time: Wed Jan 18 08:35:15.787 2012 (UTC - 7:00) System Uptime: 0 days 0:52:28.130 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {4, fffffa8008ec4c60, fffffa8008063010, fffffa800a1259a0} Unable to load image \SystemRoot\system32\drivers\CM10664.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for CM10664.sys *** ERROR: Module load completed but symbols could not be loaded for CM10664.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* Probably caused by : CM10664.sys ( CM10664+287ac ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp that is already pending in the USB bus driver. Arg2: fffffa8008ec4c60, Address of IRP Arg3: fffffa8008063010, Address of URB Arg4: fffffa800a1259a0 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 *** *** *** ************************************************************************* CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff880044b6f4b to fffff80002c98c40 STACK_TEXT: fffff880`05268798 fffff880`044b6f4b : 00000000`000000fe 00000000`00000004 fffffa80`08ec4c60 fffffa80`08063010 : nt!KeBugCheckEx fffff880`052687a0 fffff880`044c244a : fffffa80`07f40000 fffffa80`08eba5f0 00000000`00000000 fffffa80`07f40050 : USBPORT!USBPORT_Core_DetectActiveUrb+0x127 fffff880`052687f0 fffff880`044cae74 : fffffa80`08ec4c60 fffffa80`0849000a fffffa80`08ec4c60 fffffa80`08063010 : USBPORT!USBPORT_ProcessURB+0xad6 fffff880`052688a0 fffff880`044a4af4 : 00000000`00000000 fffffa80`08499050 fffffa80`0a42a8c0 fffffa80`08ec4c60 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138 fffff880`052688e0 fffff880`048cf566 : fffffa80`0849b050 fffffa80`08ebd060 fffffa80`08ec4c60 fffffa80`0849b1a0 : USBPORT!USBPORT_Dispatch+0x1dc fffff880`05268920 fffff880`048ffd8f : 00000000`00000000 00000000`00000000 fffffa80`08ebd060 00000000`00000801 : usbhub!UsbhFdoUrbPdoFilter+0xde fffff880`05268950 fffff880`048cdfb7 : fffffa80`08eaa658 00000000`00000000 fffffa80`08ec4c60 fffffa80`08e98758 : usbhub!UsbhPdoInternalDeviceControl+0x373 fffff880`052689a0 fffff880`05b49ec4 : 00000000`00000000 fffffa80`08e98858 00000000`00000000 fffffa80`08e98758 : usbhub!UsbhGenDispatch+0x57 fffff880`052689d0 fffff880`05b46812 : fffffa80`08eaa658 fffffa80`08ec4c60 00000000`00000324 fffffa80`08ec4c60 : usbccgp!UsbcForwardIrp+0x30 fffff880`05268a00 fffff880`05b46aba : fffffa80`08e98758 00000000`00220003 fffffa80`08ec4c60 fffffa80`08eaa658 : usbccgp!DispatchPdoUrb+0xfa fffff880`05268a40 fffff880`05b4472e : 00000000`0000000f fffffa80`08eaa650 fffffa80`08eaa658 fffffa80`08ec4c60 : usbccgp!DispatchPdoInternalDeviceControl+0x17a fffff880`05268a70 fffff880`05c567ac : fffffa80`08eaa500 00000000`00000001 00000000`00000000 00000000`00000103 : usbccgp!USBC_Dispatch+0x2de fffff880`05268af0 fffffa80`08eaa500 : 00000000`00000001 00000000`00000000 00000000`00000103 fffffa80`0806b698 : CM10664+0x287ac fffff880`05268af8 00000000`00000001 : 00000000`00000000 00000000`00000103 fffffa80`0806b698 fffff880`05c5773d : 0xfffffa80`08eaa500 fffff880`05268b00 00000000`00000000 : 00000000`00000103 fffffa80`0806b698 fffff880`05c5773d fffffa80`0806be88 : 0x1 STACK_COMMAND: kb FOLLOWUP_IP: CM10664+287ac fffff880`05c567ac ?? ??? SYMBOL_STACK_INDEX: c SYMBOL_NAME: CM10664+287ac FOLLOWUP_NAME: MachineOwner MODULE_NAME: CM10664 IMAGE_NAME: CM10664.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ac47ec3 FAILURE_BUCKET_ID: X64_0xFE_CM10664+287ac BUCKET_ID: X64_0xFE_CM10664+287ac Followup: MachineOwner ---------
Probably caused by : CM10664.sys ( CM10664+287ac )

The blue screen crashes are caused by C-Media USB Audio. Do you know what that is, or do I need to do research to help you determine the problem? I would recommend re-installing the device driver for it, or if it is software related, re-install the software. 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.

If that does not work, replace the device or software that is causing the crashes.
My System SpecsSystem Spec
Reply

 Bsod usb_bug_code




Thread Tools



Similar help and support threads for2: Bsod usb_bug_code
Thread Forum
BSODs becoming more frequent USB_BUG_CODE error BSOD Help and Support
BSOD Randomly- USB_BUG_CODE BSOD Help and Support
Bluescreen: USB_BUG_CODE 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 06:51 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