Share via

User getting repeat BSOD's and noticing his USB stops working with connecting and switching between docking stations and using VMWare workstation.

Anonymous
2023-04-13T19:36:30+00:00

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


Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-09-05T20:28:37+00:00

    I have this exact same problem.

    • Windows 11 laptop fully updated
    • All dell drivers fully updated

    I have the win 11 laptop plugged into a kvm (a dell monitor with kvm feature) and a desktop plugged into the kvm/monitor. I have a kb/mouse that I use with both machines. Every so often when I switch to the laptop the kb/mouse won't register anymore (the kb/mouse on laptop still work).

    At this point none of the usb ports on the laptop work either. If I unplug everything and plug in a usb mouse or usb flash drive, it doesn't register at all. When I reboot it takes a few minutes then I get a generic bsod 0x0000009f which seems to be related to power, but have no idea what to do. The solution for that bsod is to update all drivers, which are done.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-04-16T21:38:00+00:00

    This may be completely unrelated but I've started encountering problems with USB devices and I also use VMware Workstation. The effect I see is that some USB devices disappear from utilities like UsbTreeView and aren't accessible in the VMware Workstation client OS. I'm also getting more BSODs that before. My suspicion is that recent Windows update has introduced some instability but that's an anecdotal observation.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-04-13T20:21:37+00:00

    Hi Chris,

    My name is Cindy. I am sorry you are having this problem. I know it is really frustrating. I will do my best to help you with this problem.

    Please note: This is a user-to-user community forum. We are users just like you who help others. We are not employees of Microsoft.

    This is the error you are receiving. 0x9F_4_USBXHCI_IMAGE_pci.sys

    The thing you should do is update your computer. I am showing the computer has not been updated in some time. Here are the directions on how to update the computer.

    Type the word update in the search and see if there are any new updates. Update if necessary.

    On the same page click on the advanced or additional updates.

    Update. not been updated in some time.

    ___

    The problem you are having is associated with the iaStorA.sys Intel Matrix Storage Manager driver from Intel Corp

    Click on the support tab.

    Then select Auto update your drivers.

    This will download a program that will scan your computer for updates.

    Update the computer with the recommended updates.

    ___

    You could also be having a problem with the power.

    The drivers for your battery may have become corrupted or out of date. Uninstalling and reinstalling the driver will usually fix this problem.

    1. Please type the words Device Manager into the search and open the page.
    2. Scroll down the page and click on battery.
    3. You should see the battery driver. Right-click and uninstall them.
    4. Restart the computer. Windows will automatically reinstall the drivers.
    5. Check to see if the problem has been fixed.

    If you do not see a battery driver, it can be downloaded free of charge from the maker of the computer such as Dell, Lenovo, HP, etc. They are responsible for making sure they have the drivers so their equipment will work with Windows.

    ___

    Here is the information on how to run the Hardware troubleshooter.

    Please press Windows key + R Key at the same time.

    Paste the command below into the run box and press Enter:

    msdt.exe -id DeviceDiagnostic

    Hit Enter.

    ___

    Here are directions on how to run the Troubleshooter for the Power.

    1. Please type Troubleshoot in the search and open the page. (The troubleshooting can be found on the taskbar.)
    2. Then click on other troubleshooters.
    3. Scroll down the page and click on the run key in the Power.
    4. Follow the prompts.

    I hope this helps fix the problem. Please let me know if you have any questions.

    Sincerely,

    Cindy

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments