Forum Discussion
DRIVER_POWER_STATE_FAILURE (0x9F) on ASUS X870E-E & Ryzen 9 9950X3D
Hello,
I am experiencing frequent BSODs with the stop code
DRIVER_POWER_STATE_FAILURE (0x9F).
Hardware:
- ASUS ROG Strix X870E-E Gaming WiFi
• AMD Ryzen 9 9950X3D
• Windows 11
• Latest AMD chipset drivers installed from the ASUS website
• BIOS 2306 (the issue also occurred before updating to this BIOS)
Symptoms:
• Random BSODs during very light workloads (Outlook, Chrome, PDFCreator).
• Today I experienced four BSODs within 20 minutes.
• Sometimes the PC can run for about an hour before crashing.
• The computer also wakes from sleep by itself every 10 to 15 minutes.
Troubleshooting already performed:
• BIOS updated.
• AMD chipset drivers completely removed and reinstalled.
• OCCT CPU and memory stress tests completed without errors.
• No WHEA errors reported.
• Normal CPU and motherboard temperatures.
WinDbg analysis:
Bugcheck: DRIVER_POWER_STATE_FAILURE (0x9F)
IMAGE_NAME: pci.sys
Failure Bucket:
0x9F_3_ACPI_IMAGE_pci.sys
Power IRP blocked in ACPI.
Device identified:
PCI\VEN_1022&DEV_14DB
I also found another ASUS ROG Strix X870E-E Gaming WiFi user reporting the same
DRIVER_POWER_STATE_FAILURE (0x9F). In that case, WinDbg identified
Usb4HostRouter.sys instead of pci.sys.
Could this indicate an AMD chipset, ACPI, USB4 controller or motherboard PCIe
power management issue?
I can provide the minidump files, the complete WinDbg analysis and the Windows
Event Viewer logs if needed.
Thank you.
1 Reply
Yes, the evidence points to a device power transition, but it does not identify the motherboard or AMD chipset as defective. Microsoft defines 0x9F with Arg1 3 as a device object blocking a power IRP too long. In WinDbg, use Arg4 with !irp and the Arg2 PDO with !devstack; the driver holding the pending IRP and DeviceInst or ServiceName are more useful than IMAGE_NAME pci.sys. Compare several fresh dumps. For the repeated wakes, run powercfg /lastwake, powercfg /waketimers, and powercfg /devicequery wake_armed after a wake. If USB4 or the same AMD stack appears consistently, test with USB4 devices disconnected, disable only that device’s wake permission, and collect matching System log events. Send the WinDbg outputs, wake results, BIOS version, and driver versions to ASUS. Microsoft also recommends checking for updated ACPI, BIOS, or firmware; another user’s different module is not enough to prove one root cause.
