DRIVER_POWER_STATE_FAILURE, the blue screen, explained and fixed

This stop code (0x0000009F) means a driver failed to complete a power request within the time allowed: a device did not go to sleep, wake up, or shut down when Windows told it to. The signature pattern is a PC that hangs for minutes when closing the lid, sleeping, or shutting down, then restarts with this blue screen. Microsoft documents it plainly: a driver has failed to complete a power IRP within a specific time.

The fix, in order

  1. Update the drivers that handle sleep. Graphics, Wi-Fi, Bluetooth, chipset, and USB drivers from the PC or motherboard manufacturer. Power bugs are driver bugs, and these are the ones that most often stall.
  2. Stop Windows from powering down suspect devices. Device Manager → the device (start with Wi-Fi and Bluetooth adapters) → Properties → Power Management tab → uncheck “Allow the computer to turn off this device to save power.” Repeat for USB hubs if the crash follows using a dock or hub.
  3. Disconnect USB devices and docks to isolate. If sleep works with everything unplugged, reconnect one device at a time. External drives, audio interfaces, and older USB peripherals are frequent stall sources.
  4. Turn off Fast Startup. Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup.” Fast Startup saves a partial hibernation image, and drivers that mishandle it cause this crash at shutdown and boot.
  5. Update the BIOS/UEFI. Sleep states are negotiated with the firmware; makers ship fixes for exactly this class of bug. Get the update only from the PC or motherboard maker and follow its instructions exactly.
  6. Repair system files. Admin Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then check for Windows updates, Microsoft ships driver-framework fixes through them.

If it still happens

If one device reliably triggers the stall, replace its driver with the version from the component maker rather than the PC brand, or leave the device disconnected and replace it if it is old. A crash that happens on a clean install with current drivers and BIOS can point at a failing motherboard power circuit, but that is the last stop, not the first.

Common questions

Why does it happen when I close the lid or shut down? Because that is when the power request goes out. Sleeping, waking, hibernating, and shutting down all require every driver to change state on command. A driver that ignores or mishandles the request stalls the whole transition until Windows gives up and shows this code.

Is DRIVER_POWER_STATE_FAILURE a hardware failure? Occasionally a dying device causes it, but the large majority are driver software problems fixed by updates or by stopping Windows from power-managing the device. Suspect hardware only when the same device stalls across clean drivers on a fresh install.

Related errors

Kernel-Power 41 unexpected shutdowns · WIN32K_POWER_WATCHDOG_TIMEOUT · DPC_WATCHDOG_VIOLATION · CRITICAL_PROCESS_DIED