插拔xbox360手柄蓝屏

Question

Dear All,

这边插拔手柄的时候偶现电脑蓝屏，下方为dump文件log。

Error: Change all symbol paths attempts to access 'D:\Windows Kits\10\Debuggers\x64\sym\XUSB22.pdb\E63E8421CAB472585B2E84639D4D648E1\XUSB22.pdb' failed: 0x0 - 操作成功完成。

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Error D:\Windows Kits\10\Debuggers\x64\sym\XUSB22.pdb\E63E8421CAB472585B2E84639D4D648E1\XUSB22.pdb

Microsoft (R) Windows Debugger Version 10.0.22621.2428 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\052324-10906-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Error: Change all symbol paths attempts to access 'D:\Windows Kits\10\Debuggers\x64\sym\XUSB22.pdb\E63E8421CAB472585B2E84639D4D648E1\XUSB22.pdb' failed: 0x0 - 操作成功完成。

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Error D:\Windows Kits\10\Debuggers\x64\sym\XUSB22.pdb\E63E8421CAB472585B2E84639D4D648E1\XUSB22.pdb

Symbol search path is: srv*;D:\Windows Kits\10\Debuggers\x64\sym\XUSB22.pdb\E63E8421CAB472585B2E84639D4D648E1\XUSB22.pdb

Executable search path is:

Windows 10 Kernel Version 17763 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Kernel base = 0xfffff8071da0a000 PsLoadedModuleList = 0xfffff8071de24850

Debug session time: Thu May 23 09:56:00.022 2024 (UTC + 8:00)

System Uptime: 1 days 20:08:28.234

Loading Kernel Symbols

...............................................................

................................................................

................................................................

.....................................

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

5: kd> !analyze -v

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

---

DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000001, The system cumulatively spent an extended period of time at

DISPATCH_LEVEL or above. The offending component can usually be

identified with a stack trace.

Arg2: 0000000000001e00, The watchdog period.

Arg3: fffff8071df4b380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

---

*** WARNING: Unable to verify timestamp for ctxusbm.sys

---

---

---

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

---

*** For some commands 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: TickPeriods ***

---

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 6625

Key  : Analysis.DebugAnalysisManager

Value: Create

Key  : Analysis.Elapsed.mSec

Value: 17145

Key  : Analysis.Init.CPU.mSec

Value: 3140

Key  : Analysis.Init.Elapsed.mSec

Value: 8085

Key  : Analysis.Memory.CommitPeak.Mb

Value: 124

Key  : WER.OS.Branch

Value: rs5_release

Key  : WER.OS.Timestamp

Value: 2018-09-14T14:34:00Z

Key  : WER.OS.Version

Value: 10.0.17763.1

FILE_IN_CAB: 052324-10906-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8071df4b380

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff00c280be070 -- (.trap 0xfffff00c280be070)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000001 rbx=0000000000000000 rcx=ffffd181545993b0

rdx=00002e7eaba66cb8 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8071db25e70 rsp=fffff00c280be200 rbp=0000000000000000

r8=0000000000000105 r9=fffff807393f53f0 r10=fffff8071db25db0

r11=0000000000000105 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!KxWaitForSpinLockAndAcquire+0x30:

fffff8071db25e70 488b07 mov rax,qword ptr [rdi] ds:0000000000000000=????????????????

Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:

ffffbf80a13d7ba8 fffff8071dc069ad : 0000000000000133 0000000000000001 0000000000001e00 fffff8071df4b380 : nt!KeBugCheckEx

ffffbf80a13d7bb0 fffff8071da6dc5f : 00019528d6f25cec ffffbf80a13b9180 0000000000000286 00000000009b2f0f : nt!KeAccumulateTicks+0x1956cd

ffffbf80a13d7c10 fffff8071e47c481 : 0000000000000000 ffffd1813c704a00 fffff00c280be0f0 ffffd1813c704ab0 : nt!KeClockInterruptNotify+0xcf

ffffbf80a13d7f30 fffff8071dacded5 : ffffd1813c704a00 fffff8071db0c637 ffffd1813c704b00 ffff9a0fd365d92a : hal!HalpTimerClockIpiRoutine+0x21

ffffbf80a13d7f60 fffff8071dbc5b7a : fffff00c280be0f0 ffffd1813c704a00 0000000000000000 ffffd1813c704a00 : nt!KiCallInterruptServiceRoutine+0xa5

ffffbf80a13d7fb0 fffff8071dbc6387 : 00000000a50b2909 fffff00c280be0f0 ffffd1813c704a00 fffff80732ec5542 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff00c280be070 fffff8071db25e70 : fffff00c280be390 ffffad8649631ab8 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff00c280be200 fffff8071db25e37 : ffffd181545993b0 ffffbf80a13b9180 a5047b987e25f69d 00000000f712292d : nt!KxWaitForSpinLockAndAcquire+0x30

fffff00c280be230 fffff80731802531 : ffffd181530d6de0 ffffd18154599340 ffffad866097f870 000000000000001d : nt!KeAcquireSpinLockRaiseToDpc+0x87

fffff00c280be260 fffff807393e4e02 : ffffd18158b4c200 ffffd18154599340 fffff807393e6700 ffffd18158b4c2e0 : Wdf01000!imp_WdfSpinLockAcquire+0x71 [minkernel\wdf\framework\shared\support\fxspinlockapi.cpp @ 141]

fffff00c280be2a0 fffff807393e5ae4 : ffffd18158b4c200 fffff807318025ee 00002e7ea52b4c88 fffff807393ec628 : xusb22!DriverGlobals::GetBusDevice+0x2a

fffff00c280be2d0 fffff807393e5928 : ffffd18158b4c2e0 fffff807393e6760 00002e7ea52b4c88 ffffd18158b4c350 : xusb22!GamepadInformation::NotifyJumpedDevice+0x34

fffff00c280be300 fffff807393e6792 : ffffd18158b4c2e0 ffffd1815c134cf0 fffff807393e6760 00002e7ea52b4c88 : xusb22!GamepadInformation::GamepadDisconnected+0x50

fffff00c280be330 fffff807393ecce3 : ffffd181563e6e00 fffff8071e005c04 0000000000000000 ffffd18100000003 : xusb22!GamepadInformation::OnWriteComplete+0x32

fffff00c280be360 fffff807318031a9 : ffffd1815ad4b370 0000000000000001 fffff807393ecc70 ffffd18152302bd0 : xusb22!WdfUsbPipeWrapper::WriteBufferCompleteCallback+0x73

fffff00c280be390 fffff8073180ae28 : 00002e7ea52b4c88 ffffd1815ad4b370 ffffd1815ad4b370 0000000000000000 : Wdf01000!FxRequestBase::CompleteSubmitted+0xe9 [minkernel\wdf\framework\shared\core\fxrequestbase.cpp @ 530]

fffff00c280be420 fffff8071db107c6 : ffffd18159ce2950 ffffd18141626302 0000000000000000 ffffd1815d2048a0 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe8 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 2448]

fffff00c280be490 fffff8071daa9f9d : ffffd1815d204f5b fffff00c280be569 0000000000000000 0000000000000000 : nt!IopUnloadSafeCompletion+0x56

fffff00c280be4c0 fffff8071daa9db7 : ffffd1815d2048a0 fffff8071dc1c100 0000000000000001 0000000000000001 : nt!IopfCompleteRequest+0x1cd

fffff00c280be5d0 fffff8073180898d : 00000000c000000e ffffd1815df6b8b0 0000000000000002 ffffad8636cf02d0 : nt!IofCompleteRequest+0x17

fffff00c280be600 fffff8073180845b : ffffd18158c7a302 fffff807394b139a ffffd1815d2048a0 00000000c000000e : Wdf01000!FxRequest::CompleteInternal+0x22d [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]

fffff00c280be690 fffff807318031a9 : ffffd1815df6b8b0 ffffd1815df6b8b0 0000000000000001 ffffd181527b8850 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]

fffff00c280be6f0 fffff8073180ae28 : 00002e7ea2094748 ffffd1815df6b8b0 ffffd1815df6b8b0 ffffd1815020b9f0 : Wdf01000!FxRequestBase::CompleteSubmitted+0xe9 [minkernel\wdf\framework\shared\core\fxrequestbase.cpp @ 530]

fffff00c280be780 fffff8071db107c6 : ffffd1815408c950 ffffd18141626602 ffffd18100000d4e ffffd1815d2048a0 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xe8 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 2448]

fffff00c280be7f0 fffff8071daa9f9d : ffffd1815d204f13 fffff00c280be8c9 0000000000000000 ffffd1815408c950 : nt!IopUnloadSafeCompletion+0x56

fffff00c280be820 fffff8071daa9db7 : ffffd1815d2048a0 0000000000000000 ffffd1815d2048a0 0000000000000002 : nt!IopfCompleteRequest+0x1cd

fffff00c280be930 fffff80735a56105 : 0000000000000000 fffff00c280be9c9 ffffd18178e24ce0 fffff8071dd5504d : nt!IofCompleteRequest+0x17

fffff00c280be960 fffff80731801c4e : ffffd1815d2048a0 ffffd1815020b9f0 ffffd1815d2048a0 ffffd1815020b9f0 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0x1065

fffff00c280bea30 fffff80733072351 : ffffd1815020b9f0 0000000000000000 fffff80731801a60 0000000000000000 : Wdf01000!FxDevice::DispatchWithLock+0x1ee [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]

fffff00c280bea90 ffffd1815020b9f0 : 0000000000000000 fffff80731801a60 0000000000000000 0000000000000001 : ctxusbm+0x2351

fffff00c280bea98 0000000000000000 : fffff80731801a60 0000000000000000 0000000000000001 ffffd181527b8850 : 0xffffd181`5020b9f0

SYMBOL_NAME: xusb22!DriverGlobals::GetBusDevice+2a

MODULE_NAME: xusb22

IMAGE_NAME: xusb22.sys

IMAGE_VERSION: 10.0.17763.379

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2a

FAILURE_BUCKET_ID: 0x133_ISR_xusb22!DriverGlobals::GetBusDevice

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {696f131a-8fc5-b47b-7bf4-bcbb8ac54603}

Followup: MachineOwner

---

BRS

Ye.Zhi-Peng

Answer 1

Hello

DPC_WATCHDOG_VIOLATION (133) indicates that the system has been stuck at IRQL DISPATCH_LEVEL or above for a long time.

xusb22.sys is the Xbox 360 Windows Universal Controller driver. It is recommended to uninstall the driver and reconnect the controller to see if the operating system will download a working version of the driver.