DRIVER_POWER_STATE_FAILURE (stop code 0x0000009F) means a device driver failed to handle a power-state transition such as sleep, hibernate, or wake, so the first fix is to update or roll back the offending driver. Windows raises this bug check when a driver does not complete a power request within the time allowed (about ten minutes), leaving it in an inconsistent power state. Graphics, Wi-Fi, and chipset drivers are the usual culprits, so identifying the named .sys file in the minidump points the fix at one device. Microsoft documents it as a software driver bug, not a hardware fault, which is why updating drivers, disabling Fast Startup, and adjusting device power management resolve most cases.
This guide explains what the stop code means, names the common culprits, and gives the step-by-step fixes that resolve it. Apply the fixes in order and test a sleep and wake cycle after each one, because a single driver usually causes this stop code. The full crash workflow is covered in the guide to fixing the Blue Screen of Death, and the meaning of each code in reading BSOD stop codes.
What Causes DRIVER_POWER_STATE_FAILURE?
The error comes from a driver that mishandles a power-state transition, and four sources account for nearly every case. Each one leaves a driver unable to signal that it finished entering or leaving a low-power state, so the kernel halts to avoid an inconsistent state.
Graphics driver
Network driver
Chipset and power management
Fast Startup
How Do You Fix DRIVER_POWER_STATE_FAILURE?
Work through the fixes below in order, from the most common driver correction to isolating a single device, and test a sleep and wake cycle after each step. The first step names the failing driver so the rest of the work targets one device.
- Check the minidump for the driver name. Open C:\Windows\Minidump in BlueScreenView and read the Caused By Driver column to find the responsible .sys file, or open the dump in WinDbg and run !analyze -v. When the first parameter is 0x3, the !irp command often reveals the blocked driver. Match it to its device in Device Manager, usually a GPU, Wi-Fi, or chipset driver.
- Update or roll back the named driver. In Device Manager, right-click the matching device, choose Update driver, then Search automatically. Install the newest driver from the device or PC maker if Windows reports none. If crashes began after an update, open the Driver tab and click Roll Back Driver. This resolves most cases.
- Reinstall the graphics driver cleanly. When a GPU .sys file is named, download the latest driver, run Display Driver Uninstaller from Safe Mode to remove every trace, restart, then install the fresh driver and pick a clean installation if offered.
- Update the chipset driver and BIOS. Install the latest chipset package from the motherboard or PC maker first, then restart. Update the BIOS following the maker instructions without interrupting power during the flash, because firmware corrects power-management faults at the platform level.
- Disable Fast Startup. Open Control Panel, Hardware and Sound, Power Options, then Choose what the power buttons do. Click Change settings that are currently unavailable, clear the Turn on fast startup (recommended) checkbox, save, and restart.
- Turn off device power management for the culprit. In Device Manager, open the named adapter or USB Root Hub, and on the Power Management tab clear Allow the computer to turn off this device to save power. In Power Options advanced settings, set PCI Express Link State Power Management to Off and USB selective suspend to Disabled.
- Run SFC and DISM, then reset the power plan. In an administrator Terminal, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files. Then run powercfg -restoredefaultschemes to reset power plans, and powercfg /energy to flag any remaining device that blocks sleep.
- Isolate a single device to confirm. If the minidump does not name a driver, disable the suspected device in Device Manager, or unplug external USB drives, docks, and hubs, then run several sleep and wake cycles. When the crash stops, update or replace that device driver. Driver Verifier (for all non-Microsoft drivers) forces a crash that names a hidden culprit.
External drives, docks, and hubs introduce their own power-management drivers, so a peripheral can trigger the stop code on a system that is otherwise stable. Reconnect each device one at a time, testing sleep after each, to find the one that returns the crash, and update its firmware and driver or replace a faulty cable or hub.
DRIVER_POWER_STATE_FAILURE Symptoms and Causes
The table maps each symptom to its likely cause and the first fix to try, so you can match the behavior you see to a targeted step.
| Symptom | Likely Cause | First Fix |
|---|---|---|
| Crash when the PC enters sleep | Driver fails the suspend transition | Update driver, disable Fast Startup |
| Crash on wake from sleep | Driver fails the resume transition | Update driver, adjust power management |
| Crash after a driver update | Incompatible new driver | Roll back the driver |
| Wi-Fi adapter named in dump | Network adapter power-down setting | Disable adapter power saving |
| GPU driver named in dump | Graphics driver power fault | Clean reinstall of the GPU driver |
How Do You Stop Sleep and Hibernation Crashes Long Term?
Keeping sleep and hibernation stable depends on current drivers and a clean power configuration. A few routine actions prevent the error from returning.
- Keep GPU, Wi-Fi, and chipset drivers current. Install them from the device maker rather than a generic updater, because these drivers handle the power transitions.
- Leave Fast Startup off on systems prone to the error. The hybrid shutdown reintroduces resume faults on some hardware.
- Avoid aggressive device power saving. Disable the option to power down the network adapter and USB hubs to keep their drivers responsive.
- Keep the BIOS updated. Firmware updates correct power-management faults at the platform level.
- Rebuild the hibernation file if resume fails. Run powercfg /h off and then powercfg /h on to replace a corrupt file.
If the error appears only on battery or only when plugged in, the power plan for that condition holds a setting that drives a device into an unrecoverable state, so reset that plan to defaults. For the wider set of slowdowns, freezes, and boot faults, the hub on common PC problems collects the matching guides.
Last Thoughts on DRIVER_POWER_STATE_FAILURE
DRIVER_POWER_STATE_FAILURE is resolved by identifying the driver that fails the power transition and correcting it, because bug-check 0x0000009F always points to a power-state fault rather than failing hardware. Read the minidump to name the .sys file, then update or roll back the GPU, Wi-Fi, or chipset driver, disable Fast Startup, and stop Windows from powering the device down too aggressively. Test a sleep and wake cycle after each change, and reach for Driver Verifier only when the dump does not name a culprit.
This stop code sits alongside the other power and kernel faults that interrupt sleep and wake. Related crashes are handled in the steps to fix KERNEL_SECURITY_CHECK_FAILURE, and the wider set of slowdowns, freezes, and boot errors is collected in the hub on common PC problems.
Key Takeaways:
- The stop code 0x0000009F is a power-transition fault: a driver failed to enter or leave a sleep, hibernate, or wake state in time.
- It is a software driver bug in almost every case, not failing hardware, per Microsoft documentation.
- Read the minidump in BlueScreenView or WinDbg to name the failing .sys file and target the fix at one device.
- Updating or rolling back the GPU, Wi-Fi, or chipset driver resolves most cases.
- Disable Fast Startup and turn off device power management for the named device to remove the common triggers.
- When the dump is empty, Driver Verifier forces a crash that names the hidden power-management driver.
Frequently Asked Questions (FAQs)
What does the stop code 0x0000009F mean?
It means a driver failed to complete a power request within the time Windows allows, usually around ten minutes, during a sleep, hibernate, shutdown, or wake transition. Microsoft documents it as the driver being in an inconsistent or invalid power state, and it is almost always a driver fault rather than failing hardware.
Is DRIVER_POWER_STATE_FAILURE a hardware problem?
Usually no. Microsoft classifies the typical 0x9F case as a software driver bug, not a hardware fault. A driver that mishandles sleep or wake is the common cause, so updating, rolling back, or cleanly reinstalling the named driver resolves most crashes before any hardware is suspected.
Why does the crash happen only when my PC sleeps or wakes?
Because 0x9F is triggered by a power-state transition. The driver does not signal that it finished entering or leaving a low-power state, so the kernel halts to avoid an inconsistent state. That is why a crash on suspend or on resume points to a power-management driver, not a running application.
How do I find the exact driver behind the crash?
Open the minidump in C:\Windows\Minidump with BlueScreenView and read the Caused By Driver column, or open it in WinDbg and run !analyze -v. When the first parameter is 0x3, the !irp command often reveals the blocked driver, usually a graphics, Wi-Fi, or chipset .sys file.
Does disabling Fast Startup fix DRIVER_POWER_STATE_FAILURE?
It resolves many cases. Fast Startup uses a hybrid shutdown that can leave drivers in a power state they cannot resume from cleanly, so clearing the Turn on fast startup checkbox in Power Options stops a frequent trigger. Pair it with updating the named driver for the most reliable result.
What do I do if the minidump does not name a driver?
Enable Driver Verifier for all non-Microsoft drivers. It stresses each driver and forces a crash that names the failing power-management driver in the next minidump. Run verifier /reset afterward to turn it off, then update or replace the driver it identified.
