Code:
-
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
---------
-
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
---------
-
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.
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer
- Install the latest driver for the device once Windows starts.
Alternatively:
- Login as an adminstrative user.
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
- Restart your computer
- 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.