What DRIVER_POWER_STATE_FAILURE means
When Windows changes power state, every driver must cooperate. If one fails to respond in time or ends up in an inconsistent state, Windows stops. Network, graphics, USB and storage drivers are common culprits, and settings such as Fast Startup can make the problem more likely.
Common causes
- An outdated or faulty driver that mishandles sleep, wake or shutdown
- Aggressive power-saving settings on network or USB devices
- Fast Startup combined with problem drivers
- Old BIOS or chipset firmware
How to fix DRIVER_POWER_STATE_FAILURE
Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.
- Work out when it happens. Note whether the crash occurs when going to sleep, waking, restarting or shutting down. That tells you which transition the faulty driver fails on, and whether it happens on a laptop only on battery.
- Update chipset, graphics, network and USB drivers. Get them from the PC or motherboard maker, not only Windows Update. Restart afterwards and test the transition that crashed.
- Turn off Fast Startup. Open Control Panel, Power Options, Choose what the power buttons do, Change settings that are currently unavailable, then untick Turn on fast startup. Restart and test again.
- Loosen device power saving. In Device Manager, open the properties of network adapters and USB hubs, and where a Power Management tab exists, untick Allow the computer to turn off this device to save power.
- Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
If crashes only happen on wake from sleep and every driver is current, check for a BIOS update, which often contains power-management fixes.
Not sure this is your code?
The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.
