How to Fix DRIVER_POWER_STATE_FAILURE Blue Screen on Windows 11

DRIVER_POWER_STATE_FAILURE occurs in Windows 11 when drivers fail to handle power state transitions properly, often causing crashes during sleep or shutdown.

To better understand other Windows crash codes, see our Windows Blue Screen Errors guide.

DRIVER_POWER_STATE_FAILURE is a common Blue Screen of Death (BSOD) error on Windows 11 that usually appears during sleep, shutdown, or resume from standby. In most cases, the problem is caused by a driver that fails to handle power state transitions correctly.

The good news: this error is usually fixable without reinstalling Windows or replacing hardware.

Below is a practical, step-by-step repair guide.

What Does DRIVER_POWER_STATE_FAILURE Mean?

This BSOD happens when a device driver does not respond properly when Windows changes power states - for example:

  • sleep → wake
  • plug/unplug power
  • shutdown → restart
  • GPU power state switch
  • network adapter sleep mode

Windows waits for the driver to respond. If it doesn’t, the system crashes to prevent corruption.

Most Common Causes

  • Outdated or incompatible drivers
  • GPU driver issues
  • Network adapter drivers
  • Storage controller drivers
  • Fast Startup conflicts
  • Broken power plan settings
  • Laptop power management bugs

If you are also seeing GPU timeout or nvlddmkm crashes, see our guide on fixing NVIDIA TDR and driver timeout errors on Windows 11.

If crashes started after a graphics update and include black screens, also review the Windows 11 black screen after driver update fixes.

Step 1 - Check Which Driver Caused the Crash

After reboot:

  • Open Event Viewer
  • Windows Logs → System
  • Look for critical errors near crash time
  • Note any driver file name (.sys)

This often points directly to the faulty device.

Step 2 - Update or Roll Back Drivers

Open Device Manager and check:

  • Display adapters
  • Network adapters
  • Storage controllers
  • Chipset devices

For each major device:

  • Right-click → Update driver
  • If crashes started after an update → Roll Back Driver instead

Avoid random driver updater tools - use manufacturer sources only.

Step 3 - Disable Fast Startup

Fast Startup frequently causes power-state driver conflicts.

Control Panel → Power Options → Choose what power buttons do
Click “Change settings currently unavailable”
Uncheck Turn on fast startup

Reboot.

Step 4 - Reset Power Plan

Broken advanced power settings can trigger this BSOD.

Open Command Prompt as Administrator:

powercfg -restoredefaultschemes

Reboot after running it.

Step 5 - Change Device Power Saving Settings

Device Manager → Network Adapter → Properties → Power Management

Uncheck:

Allow the computer to turn off this device to save power

Do this especially for:

  • Wi-Fi adapters
  • Ethernet adapters
  • USB controllers

Step 6 - Run System File Repair

Open Command Prompt as Administrator and run:

sfc /scannow

Then:

DISM /Online /Cleanup-Image /RestoreHealth

Reboot after both complete.

System corruption can indirectly trigger driver power failures.

You can also review Microsoft’s official System File Checker documentation for deeper repair details.

Step 7 - Check Sleep & Hibernate Behavior

If crashes happen after sleep:

Try disabling hibernation:

powercfg -h off 

Test system stability for a day.

Step 8 - BIOS & Firmware Check (If Repeated)

If crashes continue:

  • Update BIOS (only from manufacturer)
  • Update chipset drivers
  • Update storage controller drivers
  • Check SSD firmware tools

Related Crash Types You Should Check

If your system freezes heavily before crashing, disk or IO stalls may also be involved - see our Windows 11 file transfer freezes and 100% disk usage troubleshooting guide.

If instead you see IRQL blue screens, follow our full IRQL_NOT_LESS_OR_EQUAL repair guide.

Final Thoughts

DRIVER_POWER_STATE_FAILURE looks serious, but it is usually a driver power-handling bug - not hardware failure. Updating or rolling back drivers, disabling Fast Startup, and resetting power settings fix most systems.

If the error started right after a driver or Windows update, start with rollback and power configuration fixes first - they solve the majority of cases.