Quote:
Originally Posted by urnammu
Here is the file.
Thanks for looking into this!
|
I did a windbg check on the BSOD in your log file:
Quote:
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe000bb8208e0, Physical Device Object of the stack
Arg3: fffff803c505d930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000b9f9b010, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52678625
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff8018719c000 usbccgp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFF803C5064FB0
STACK_TEXT:
fffff803`c505d8f8 fffff803`c3808c1e : 00000000`0000009f 00000000`00000003 ffffe000`bb8208e0 fffff803`c505d930 : nt!KeBugCheckEx
fffff803`c505d900 fffff803`c3808b3e : ffffe000`bb2d7970 00000000`ffffffff 00000000`00000000 fffff803`c3669240 : nt!PopIrpWatchdogBugcheck+0xde
fffff803`c505d960 fffff803`c3665810 : 00000000`00000000 fffff803`c505dab0 ffffe000`bb2d79a8 fffff803`c37e6e24 : nt!PopIrpWatchdog+0x32
fffff803`c505d9b0 fffff803`c3763aea : fffff803`c38f2180 fffff803`c38f2180 fffff803`c3959a00 ffffe000`bbe79080 : nt!KiRetireDpcList+0x4f0
fffff803`c505dc60 00000000`00000000 : fffff803`c505e000 fffff803`c5058000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.16442
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_mwlu97w8x64_IMAGE_usbccgp.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_mwlu97w8x64_IMAGE_usbccgp.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_mwlu97w8x64_image_usbccgp.sys
FAILURE_ID_HASH: {c93e44a1-5efb-2702-ae7a-870293645b59}
Followup: MachineOwner
---------
|
The BSOD is caused by
usbccgp.sys, so looks like it is caused by something on the USB bus.
We do have a Surface Pro here that we test on and not seen this BSOD. Do you have any other USB devices connected? Would be worth disconnecting USB devices to try and see what the offender is.
Wim