User getting repeat BSOD's and noticing his USB stops working with connecting and switching between docking stations and using VMWare workstation.
Usually a restart brings USB devices back but the problem repeats. Including the Crash Dump below. I am not great at reading them but I did see a failure bucket ID and Faulting module but could not find anything specifically for those listed. Any info anyone familiar with issue can give would be a great help.
Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\Snc59218\c$\Windows\Minidump\041323-19937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80314600000 PsLoadedModuleList = 0xfffff8031522a310
Debug session time: Thu Apr 13 11:07:31.146 2023 (UTC - 7:00)
System Uptime: 0 days 2:26:01.497
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
Loading User Symbols
Loading unloaded module list
..............................................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffe183ee0f1140, The thread currently holding on to the Pnp lock.
Arg4: fffff8031b477180, nt!TRIAGE_9F_PNP on Win7 and higher
Debugging Details:
Implicit thread is now ffffe183`ee0f1140
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 11796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 22135
Key : Analysis.Init.CPU.mSec
Value: 1796
Key : Analysis.Init.Elapsed.mSec
Value: 17033
Key : Analysis.Memory.CommitPeak.Mb
Value: 97
Key : WER.OS.Branch
Value: vb\_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 041323-19937-01.dmp
BUGCHECK_CODE: 9f
BUGCHECK_P1: 4
BUGCHECK_P2: 12c
BUGCHECK_P3: ffffe183ee0f1140
BUGCHECK_P4: fffff8031b477180
DRVPOWERSTATE_SUBCODE: 4
IMAGE_NAME: pci.sys
MODULE_NAME: pci
FAULTING_MODULE: fffff80319c70000 pci
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff8031b477148 fffff80314b0acf6 : 000000000000009f 0000000000000004 000000000000012c ffffe183ee0f1140 : nt!KeBugCheckEx
fffff8031b477150 fffff80314fb3716 : 0000000000000000 0000000000000001 0000000000000080 fffff803126c0180 : nt!PnpBugcheckPowerTimeout+0x76
fffff8031b4771b0 fffff80314887892 : fffff1854f586c30 fffff803126c0180 fffff8031b477418 0000000000000000 : nt!PopBuildDeviceNotifyListWatchdog+0x16
fffff8031b4771e0 fffff8031489f2fd : 0000000000000000 0000000000000000 0000000000140001 00000000000519a8 : nt!KiProcessExpiredTimerList+0x172
fffff8031b4772d0 fffff803149fea0e : 0000000000000000 fffff803126c0180 0000000000000000 fffff80315327a00 : nt!KiRetireDpcList+0x5dd
fffff8031b477560 0000000000000000 : fffff8031b478000 fffff8031b471000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e
IMAGE_VERSION: 10.0.19041.2673
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x9F_4_USBXHCI_IMAGE_pci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7ce378e5-a465-4985-c21f-acbd63aa41dc}
Followup: MachineOwner