ThisCalculator

Everyday

Driver Power State Failure: Fix & Causes

Updated · Standard formula, shown below

Driver Power State Failure: Fix & Causes

Driver Power State Failure is a Blue Screen of Death (BSOD) error in Windows that occurs when a device driver fails to complete a power state transition within the allotted time, typically when the computer is entering or exiting sleep, hibernate, or a low-power idle state. The fix usually involves updating or rolling back the problematic driver, adjusting power settings, or running hardware diagnostics. This article explains what causes the error, how to identify the offending driver, and the step-by-step methods to resolve it.

What Is Driver Power State Failure?

This stop code (bug check 0x0000009F) is triggered by the Windows Power Manager when a driver does not respond to a power IRP (I/O Request Packet) within a defined timeout. When you put your PC to sleep or wake it up, Windows sends commands to each device (like the GPU, network adapter, or storage controller) to change its power state. If a driver hangs or takes too long, the system assumes a critical failure and crashes to prevent data corruption.

The error is more common on laptops and desktops with hybrid sleep or fast startup enabled, but it can occur on any Windows system. It is rarely caused by a single hardware fault; more often it is a software conflict, an outdated driver, or a misconfigured power plan.

Common Causes

  • Outdated or buggy drivers – especially graphics, chipset, network, or Bluetooth drivers.
  • Incompatible drivers after a Windows feature update.
  • Power management settings that allow the device to turn off to save power, but the driver does not handle the wake correctly.
  • Faulty hardware – a dying SSD or RAM can cause random power state failures.
  • Overclocking or unstable BIOS settings that affect power delivery.
  • Third-party software that interacts with power plans, such as manufacturer utilities or antivirus tools.

How to Identify the Problematic Driver

Windows writes a minidump file when the crash occurs. You can analyze it to see which driver caused the failure. The easiest method is to use the built-in Event Viewer or a free tool like BlueScreenView (but we won’t name tools; you can search for “minidump viewer”). The dump file is usually located at C:\Windows\Minidump.

  1. Open Event Viewer (press Win + R, type eventvwr.msc).
  2. Go to Windows Logs → System and look for errors with source BugCheck shortly before the crash time.
  3. Note the bug check code and any parameters. The fourth parameter often contains the address of the offending driver.
  4. Alternatively, open the minidump with a debugger and run !analyze -v to see the driver name.

If you cannot read the dump, a common trick is to disable fast startup and see if the error stops. If it does, the issue is likely with a driver that does not handle the hybrid shutdown.

Step-by-Step Fixes

1. Update or Roll Back Drivers

Start with the most likely culprits: graphics, network, and chipset drivers. Go to Device Manager (Win + X → Device Manager), expand the category, right-click the device, and select Update driver. If the error started after a recent update, try Roll back driver instead.

2. Disable Fast Startup

Fast startup in Windows 10/11 can cause power state issues because it uses a hybrid shutdown that does not fully close drivers. To disable it:

  1. Open Control Panel → Power Options → Choose what the power buttons do.
  2. Click Change settings that are currently unavailable.
  3. Uncheck Turn on fast startup and save changes.

3. Change Power Plan Settings

Some devices are allowed to turn off to save power, but this can trigger the bug. In Device Manager, right-click a device (e.g., network adapter), select Properties, go to the Power Management tab, and uncheck Allow the computer to turn off this device to save power. Repeat for USB controllers and network adapters.

4. Run Hardware Diagnostics

If the problem persists, test your RAM with Windows Memory Diagnostic (search for it in Start) and check your hard drive with chkdsk in an admin command prompt. A failing component can cause random power state failures.

5. Update BIOS and Chipset Drivers

An outdated BIOS can have power management bugs. Check your motherboard manufacturer’s support page for the latest BIOS. Also update the chipset drivers from the same source.

6. Clean Boot

To rule out third-party software, perform a clean boot (msconfig → Services → hide all Microsoft services → Disable all, then restart). If the error stops, re-enable services one by one to find the culprit.

What to Do If the Error Repeats

If you have tried all the above and the error still occurs, consider these advanced steps:

  • Check for Windows updates – a pending update might fix a known driver conflict.
  • Use System Restore – roll back to a point before the issue started.
  • Reset Windows – keep your files but reinstall the OS to eliminate any system-level corruption.
  • Test with a different power plan – switch from Balanced to High Performance and see if the error stops.

If the error only occurs when you manually put the PC to sleep, you can work around it by disabling sleep entirely and using only the monitor off feature. This is not a fix but a temporary solution.

Prevention Tips

  • Keep your drivers updated, but do not install beta drivers unless you are troubleshooting.
  • Regularly check for Windows updates.
  • Use the manufacturer’s power management tools (e.g., for your GPU) instead of generic Windows settings.
  • If you overclock, revert to stock settings to test.
  • Periodically run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files.

Frequently Asked Questions

Does Driver Power State Failure damage my hardware?

No, the BSOD itself does not damage hardware. It is a protective measure that stops the system to avoid data corruption. However, the underlying cause (e.g., a failing SSD) could eventually damage data, so it is worth fixing.

Why does the error happen only when I close the laptop lid?

Closing the lid triggers a sleep transition. If a driver (often the graphics or network driver) does not respond quickly enough, Windows crashes. Try changing the lid action to “Do nothing” temporarily to confirm.

Can a faulty RAM stick cause this error?

Yes, faulty RAM can cause any BSOD, including Driver Power State Failure, because data corruption can make drivers behave erratically. Run a memory test to rule this out.

Is it safe to disable fast startup?

Yes, it is safe. It may add a few seconds to boot time, but it does not affect functionality. Many users disable it to avoid this exact error.

Should I reinstall Windows if nothing works?

Reinstalling Windows is a last resort, but it can resolve stubborn driver conflicts. Before that, try a system restore to a point before the error started, or reset your PC while keeping files.

Does this error occur on Windows 11 as well?

Yes, it can occur on Windows 11, though it is less common than on older versions. The same troubleshooting steps apply.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.