How to Fix DRIVER_POWER_STATE_FAILURE

DRIVER_POWER_STATE_FAILURE is a Windows stop error with the bug-check value 0x0000009F, and the most common cause is a device driver that fails to handle a power-state transition such as entering or leaving sleep. The error appears when the system tries to suspend, hibernate, or wake, and a graphics, Wi-Fi, or chipset driver does not respond in time. This article explains what the error means, names the common culprits, and gives the step-by-step fixes that resolve it.

Each fix names the exact Windows tool, including the minidump, Windows Event Viewer, Device Manager, and the power settings. The fixes are ordered from the most common, such as updating or rolling back the driver and disabling Fast Startup, to BIOS and chipset updates and isolating a single device. Apply the fixes in order and test a sleep and wake cycle after each one, because a single driver usually causes this stop code.

What Does DRIVER_POWER_STATE_FAILURE Mean?

DRIVER_POWER_STATE_FAILURE means a driver did not complete a power-state transition that Windows requested, so the kernel halted to avoid an inconsistent state. The points below explain the conditions that produce it.

• A driver stalled during sleep or wake. The driver did not signal that it finished entering or leaving a low-power state.
• An incompatible or outdated driver. A driver written for an older Windows build mishandles modern power transitions.
• Aggressive device power management. A setting that powers down a device too soon can leave a driver unable to respond.
• Fast Startup conflicts. The hybrid shutdown feature can leave drivers in a state they cannot resume from cleanly.

Identify the Failing Driver from the Minidump

Identifying the driver named in the crash file points the fix at one device instead of every driver on the system. Windows saves a minidump after the stop error.

1. Open C:\Windows\Minidump in BlueScreenView after the crash.
2. Read the Caused By Driver column to find the responsible .sys file.
3. Open Windows Event Viewer, expand Windows Logs, and check System for the matching BugCheck and any device power errors.
4. For detail, open the dump in WinDbg and run !analyze -v to confirm the failing module.
5. Match the .sys file to its device in Device Manager, often a GPU, Wi-Fi, or chipset driver.

Update or Roll Back the Driver

Updating the named driver, or rolling back a driver that began failing after an update, resolves most DRIVER_POWER_STATE_FAILURE crashes. Graphics, network, and chipset drivers are the usual culprits.

1. Open Device Manager and locate the device that matches the failing .sys file.
2. Right-click it, select Update driver, then Search automatically for drivers.
3. Download the newest driver from the device or PC maker if Windows reports none.
4. If the crashes began after an update, open Properties, select the Driver tab, and click Roll Back Driver.
5. Restart and run a full sleep, hibernate, and wake cycle to confirm the fix.

Disable Fast Startup

Disabling Fast Startup stops the hybrid shutdown that leaves drivers in a power state they cannot resume from, a frequent trigger for this error. The setting sits in the Control Panel power options.

1. Open Control Panel, then Hardware and Sound, then Power Options.
2. Click Choose what the power buttons do.
3. Click Change settings that are currently unavailable.
4. Clear the Turn on fast startup (recommended) checkbox.
5. Save changes, restart, and test sleep and shutdown behavior.

Adjust Power Management for Devices

Stopping Windows from powering down key devices keeps their drivers responsive during sleep transitions. Device power management is set per device in Device Manager.

1. Open Device Manager and expand Network adapters.
2. Right-click the Wi-Fi or Ethernet adapter and open Properties.
3. On the Power Management tab, clear “Allow the computer to turn off this device to save power.”
4. Repeat for USB Root Hub entries under Universal Serial Bus controllers.
5. In Power Options, open the active plan, select Change advanced power settings, and set PCI Express Link State Power Management to Off.

Update the BIOS and Chipset Drivers

Updating the BIOS and chipset drivers corrects power-management firmware and driver faults that cause sleep and wake failures. Both come from the motherboard or PC maker.

1. Identify the motherboard or PC model and current BIOS version from System Information.
2. Download the latest BIOS and chipset drivers from the manufacturer support page.
3. Install the chipset driver package first, then restart.
4. Update the BIOS following the maker instructions, without interrupting power during the flash.
5. Test a full sleep and wake cycle after each update.

Disable the Problem Device to Confirm

Disabling the suspect device confirms it is the cause when the failing driver is uncertain, because the crash stops once the device is offline. The test isolates one device at a time.

1. Open Device Manager and locate the suspected device.
2. Right-click it and select Disable device.
3. Run several sleep and wake cycles to see whether the crash returns.
4. If the crash stops, replace or permanently update that device driver.
5. Re-enable the device and repeat for the next suspect if the crash continues.

When minidumps do not name a driver, the Driver Verifier tool forces a crash that identifies the failing power-management driver.

Check Connected USB and Storage Devices

Removing or updating external USB and storage devices clears power-state faults that come from a peripheral rather than an internal component. External drives, docks, and hubs introduce their own power-management drivers.

1. Unplug all external USB drives, docks, printers, and hubs before a sleep test.
2. Run several suspend and wake cycles with only the keyboard and mouse attached.
3. Reconnect each device one at a time, testing sleep after each, to find the device that returns the crash.
4. Update the firmware and driver of any external drive or dock identified.
5. Replace a hub or cable that causes repeated wake failures.

A USB selective suspend setting can also leave an external device unresponsive. Set USB selective suspend to Disabled under the active power plan advanced settings to test it.

Reinstall the Graphics Driver Cleanly

A clean reinstall of the graphics driver removes leftover power-management files when a GPU driver is named in the minidump. Display drivers are a frequent cause of this stop code.

1. Download the latest graphics driver from the GPU or PC maker before starting.
2. Run Display Driver Uninstaller from Safe Mode to remove every trace of the current driver.
3. Restart into normal Windows.
4. Install the freshly downloaded driver and select a clean installation if offered.
5. Run several sleep and wake cycles to confirm the crash is gone.

Check the Power Plan and Reset Power Settings

Resetting the power plan clears a misconfigured power profile that drives a device into a state its driver cannot resume from. The reset uses the powercfg command.

1. Open Terminal or Command Prompt as administrator.
2. Run powercfg -restoredefaultschemes to reset all power plans to their defaults.
3. Open Power Options and select the Balanced plan.
4. Confirm sleep and hibernate timers are set to standard values.
5. Test a full suspend and wake cycle after the reset.

A corrupt hibernation file also causes resume failures. Run powercfg /h off and then powercfg /h on to rebuild it. The powercfg /energy command generates a report that flags devices and drivers blocking sleep, which names additional culprits to update or disable.

DRIVER_POWER_STATE_FAILURE Symptoms and Causes

Stop Hibernation and Sleep Crashes Long Term

Keeping sleep and hibernation stable long term 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.

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. Reset that plan to defaults.

Key Takeaways

• The error is a power-transition fault. A driver failed to enter or leave a sleep state, named by the bug-check 0x0000009F.
• Find the driver in the minidump. BlueScreenView names the failing .sys file to target the fix.
• Update or roll back first. Most cases resolve by correcting the GPU, Wi-Fi, or chipset driver.
• Disable Fast Startup. The hybrid shutdown often leaves drivers unable to resume cleanly.
• Adjust device power management. Stop Windows from powering down the named device during sleep.

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 the bug-check 0x0000009F always points to a power-state fault. Updating or rolling back the GPU, Wi-Fi, or chipset driver, disabling Fast Startup, and adjusting device power management resolve most cases. The full crash workflow and the meaning of each code are covered in the guides to fixing the Blue Screen of Death and reading BSOD stop codes.

Related stop codes are handled in the steps to fix KERNEL_SECURITY_CHECK_FAILURE and fix SYSTEM_SERVICE_EXCEPTION. Because outdated drivers are the leading cause, the explanation of what drivers are clarifies why keeping them current prevents power-state crashes.