BugCheck 100000B8, {fffff880032e21c0, fffffa8013b0aa10, 0, 0}
*** WARNING: Unable to verify timestamp for xhcdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for xhcdrv.sys
Probably caused by : xhcdrv.sys ( xhcdrv+d7c4 )
Followup: MachineOwner
---------
10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffff880032e21c0, Original thread which is the cause of the failure
Arg2: fffffa8013b0aa10, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000
Debugging Details:
------------------
FAULTING_THREAD: fffff880032e21c0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xB8
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF88003306FB0
LAST_CONTROL_TRANSFER: from fffff800032c8602 to fffff800032c70aa
STACK_TEXT:
fffff880`032fe7a0 fffff800`032c8602 : fffff880`032e21c0 fffffa80`0fe9f020 fffffa80`0f880580 0000057f`0000000a : nt!KiSwapContext+0x7a
fffff880`032fe8e0 fffff800`032cc31f : 00000000`00000000 fffffa80`0f72cd30 00000000`00000042 fffff880`00e0a706 : nt!KiCommitThreadWait+0x1d2
fffff880`032fe970 fffff880`00e0f688 : fffff880`00e9ed00 fffff880`00000000 00000000`00000000 0000057f`f08d3700 : nt!KeWaitForSingleObject+0x19f
fffff880`032fea10 fffff880`00e42b5e : 00000000`00000000 fffff880`00000000 ffffffff`fd050f80 00000000`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x2bc
fffff880`032feac0 fffff880`0562f7c4 : fffffa80`0fe9f020 fffffa80`0f9066a0 fffff880`032fee40 fffff880`032fee48 : Wdf01000!imp_WdfIoTargetSendInternalIoctlOthersSynchronously+0x46e
fffff880`032fed70 fffffa80`0fe9f020 : fffffa80`0f9066a0 fffff880`032fee40 fffff880`032fee48 fffff880`032fedc0 : xhcdrv+0xd7c4
fffff880`032fed78 fffffa80`0f9066a0 : fffff880`032fee40 fffff880`032fee48 fffff880`032fedc0 00000000`00000000 : 0xfffffa80`0fe9f020
fffff880`032fed80 fffff880`032fee40 : fffff880`032fee48 fffff880`032fedc0 00000000`00000000 00000000`00000000 : 0xfffffa80`0f9066a0
fffff880`032fed88 fffff880`032fee48 : fffff880`032fedc0 00000000`00000000 00000000`00000000 fffff880`032fedd8 : 0xfffff880`032fee40
fffff880`032fed90 fffff880`032fedc0 : 00000000`00000000 00000000`00000000 fffff880`032fedd8 00000000`00000000 : 0xfffff880`032fee48
fffff880`032fed98 00000000`00000000 : 00000000`00000000 fffff880`032fedd8 00000000`00000000 00000000`00001000 : 0xfffff880`032fedc0
STACK_COMMAND: .thread 0xfffff880032e21c0 ; kb
FOLLOWUP_IP:
xhcdrv+d7c4
fffff880`0562f7c4 ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: xhcdrv+d7c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: xhcdrv
IMAGE_NAME: xhcdrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53870b3a
FAILURE_BUCKET_ID: X64_0xB8_xhcdrv+d7c4
BUCKET_ID: X64_0xB8_xhcdrv+d7c4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xb8_xhcdrv+d7c4
FAILURE_ID_HASH: {9fc99d3d-595b-3222-8f47-b70a857eed8b}
Followup: MachineOwner
---------
10: kd> lmvm xhcdrv
start end module name
fffff880`05622000 fffff880`05673000 xhcdrv T (no symbols)
Loaded symbol image file: xhcdrv.sys
Image path: \SystemRoot\system32\DRIVERS\xhcdrv.sys
Image name: xhcdrv.sys
Timestamp: Thu May 29 15:56:02 2014 (53870B3A)
CheckSum: 00054CDD
ImageSize: 00051000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
