J
Jeramy K
Getting BSOD on reboot. Looks related to the Xbox 360 Common Controller for Windows Driver. I have read that there were issues with the 2009 version, xusb21.sys, but I have verified that I am using xusb22.sys so I suspect it is interacting badly with something? Any ideas?
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe48335ca2040, The thread currently holding on to the Pnp lock.
Arg4: ffffa503ca28f780, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
------------------
Implicit thread is now ffffe483`35ca2040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6FOVGSQ
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe48335ca2040
BUGCHECK_P4: ffffa503ca28f780
DRVPOWERSTATE_SUBCODE: 4
DRIVER_OBJECT: ffffe48332a85ad0
IMAGE_NAME: xusb22.sys
MODULE_NAME: xusb22
FAULTING_MODULE: fffff80189da0000 xusb22
DEVICE_NODE: ffffe483305316b0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_STACK_POINTER: ffffa503ca28f748
STACK_TEXT:
ffffa503`ca28f748 fffff801`78d06ff6 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe483`35ca2040 : nt!KeBugCheckEx
ffffa503`ca28f750 fffff801`791ae926 : 00000000`00000000 00000000`00000001 00000000`00000080 ffffa700`a0a97180 : nt!PnpBugcheckPowerTimeout+0x76
ffffa503`ca28f7b0 fffff801`78abf682 : ffffa503`cad97230 ffffa700`a0a97180 ffffa503`ca28fa18 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffffa503`ca28f7e0 fffff801`78ae4a2d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`002f2c21 : nt!KiProcessExpiredTimerList+0x172
ffffa503`ca28f8d0 fffff801`78bf8d7e : 00000000`00000000 ffffa700`a0a97180 ffffa700`a0aa2240 ffffe483`35c2a040 : nt!KiRetireDpcList+0x5dd
ffffa503`ca28fb60 00000000`00000000 : ffffa503`ca290000 ffffa503`ca289000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.19041.208
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_4_STACKPTR_ERROR_IMAGE_xusb22.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {57d062a0-50fc-45fd-90cf-066e77f16170}
Followup: MachineOwner
---------
Continue reading...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: ffffe48335ca2040, The thread currently holding on to the Pnp lock.
Arg4: ffffa503ca28f780, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
------------------
Implicit thread is now ffffe483`35ca2040
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-6FOVGSQ
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 9f
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe48335ca2040
BUGCHECK_P4: ffffa503ca28f780
DRVPOWERSTATE_SUBCODE: 4
DRIVER_OBJECT: ffffe48332a85ad0
IMAGE_NAME: xusb22.sys
MODULE_NAME: xusb22
FAULTING_MODULE: fffff80189da0000 xusb22
DEVICE_NODE: ffffe483305316b0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
BAD_STACK_POINTER: ffffa503ca28f748
STACK_TEXT:
ffffa503`ca28f748 fffff801`78d06ff6 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffe483`35ca2040 : nt!KeBugCheckEx
ffffa503`ca28f750 fffff801`791ae926 : 00000000`00000000 00000000`00000001 00000000`00000080 ffffa700`a0a97180 : nt!PnpBugcheckPowerTimeout+0x76
ffffa503`ca28f7b0 fffff801`78abf682 : ffffa503`cad97230 ffffa700`a0a97180 ffffa503`ca28fa18 00000000`00000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffffa503`ca28f7e0 fffff801`78ae4a2d : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`002f2c21 : nt!KiProcessExpiredTimerList+0x172
ffffa503`ca28f8d0 fffff801`78bf8d7e : 00000000`00000000 ffffa700`a0a97180 ffffa700`a0aa2240 ffffe483`35c2a040 : nt!KiRetireDpcList+0x5dd
ffffa503`ca28fb60 00000000`00000000 : ffffa503`ca290000 ffffa503`ca289000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.19041.208
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_4_STACKPTR_ERROR_IMAGE_xusb22.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {57d062a0-50fc-45fd-90cf-066e77f16170}
Followup: MachineOwner
---------
Continue reading...
