DRIVER_POWER_STATE_FAILURE is a Windows Blue Screen of Death (BSOD) associated with bug check code:

0x0000009F

Microsoft defines bug check 0x9F as a condition in which a device driver is in an inconsistent or invalid power state. One common form occurs when a device object blocks a power-related I/O Request Packet (IRP) for too long.

The error frequently appears while Windows is changing power states, such as:

• Starting or shutting down
• Restarting Windows
• Entering Sleep
• Waking from Sleep
• Entering or leaving Hibernate
• Turning individual hardware devices on or off
• Switching between AC power and battery operation
• Applying device power-saving settings

In simple terms, Windows asks a hardware device and its driver to change power state, but the driver does not respond correctly or within the required time. Windows eventually stops the system to prevent it from remaining in an unstable kernel state.

A typical blue screen displays:

Stop code: DRIVER_POWER_STATE_FAILURE

The underlying bug check is normally:

0x0000009F

Why Does DRIVER_POWER_STATE_FAILURE Occur?

The problem is primarily associated with drivers and device power management rather than ordinary application software.

For example, Windows may tell a Wi-Fi adapter to enter a low-power state when the computer goes to sleep. If its driver does not correctly complete the request, Windows may wait for the operation and eventually generate bug check 0x9F.

Microsoft documents several variants of the error, including a device blocking an IRP for too long and a power-state transition timing out while Windows waits for the Plug-and-Play subsystem.

Common Causes

Typical causes include:

1. Outdated device drivers

An older driver may not work correctly with a newer Windows build or firmware version.

2. Corrupted drivers

Driver files or their configuration may become corrupted after an update, interrupted installation, storage problem, or improper shutdown.

3. Incompatible drivers

A driver designed for another Windows version or hardware revision may mishandle power-state transitions.

4. Graphics drivers

Intel, NVIDIA, and AMD display drivers participate heavily in power management, especially on laptops with hybrid graphics.

5. Network drivers

Wi-Fi, Ethernet and Bluetooth adapters frequently enter low-power states and therefore deserve attention when the crash happens during Sleep or Resume.

6. Storage and controller drivers

SATA, AHCI, RAID and NVMe controllers can also contribute to power-transition problems.

7. Chipset or ACPI-related problems

Chipset drivers, system firmware and ACPI components coordinate Windows power management with motherboard hardware.

8. BIOS/UEFI firmware issues

Older firmware may contain ACPI or device-management bugs that become visible after Windows or driver updates.

9. Recently installed hardware

A new USB device, PCIe card, docking station, storage device or network adapter may introduce a problematic driver.

10. Aggressive power-saving settings

PCI Express, USB, wireless adapters and other hardware may behave incorrectly when Windows repeatedly switches them into low-power states.

When Does DRIVER_POWER_STATE_FAILURE Usually Appear?

The timing of the BSOD is extremely useful for diagnosis.

BSOD while shutting down

Check:

• Network drivers
• Bluetooth drivers
• USB devices
• Storage drivers
• Graphics drivers
• Recently installed hardware

BSOD after waking from Sleep

Concentrate on:

• Wi-Fi
• Bluetooth
• GPU
• Chipset
• USB controllers
• ACPI/BIOS
• PCI Express power management

BSOD while restarting

Investigate drivers that may not correctly unload or complete pending I/O operations.

BSOD after installing a driver

The recently installed or updated driver becomes the primary suspect.

BSOD after a Windows update

A previously installed OEM driver may no longer interact correctly with the newer Windows build.

Solution 1: Restart the Computer and Observe the Trigger

If DRIVER_POWER_STATE_FAILURE happened only once, restart Windows and monitor the computer.

A single crash does not automatically indicate hardware failure.

Try to determine what the computer was doing immediately before the BSOD:

• Going to Sleep?
• Waking from Sleep?
• Shutting down?
• Restarting?
• Connecting to Wi-Fi?
• Connecting a USB device?
• Switching graphics mode?
• Docking or undocking a laptop?

Repeated crashes occurring during the same operation provide an important clue.

Solution 2: Disconnect Unnecessary External Devices

Shut down the computer and temporarily disconnect non-essential devices such as:

• USB hard drives
• USB Wi-Fi adapters
• Bluetooth adapters
• USB hubs
• Docking stations
• Printers
• Scanners
• Webcams
• External sound devices
• Card readers
• USB-to-Ethernet adapters

Restart Windows and test again.

If the BSOD disappears, reconnect devices one at a time until the problematic device or driver can be identified.

Solution 3: Check Device Manager

Press:

Windows + X → Device Manager

Inspect the hardware categories carefully.

Pay particular attention to:

• Display adapters
• Network adapters
• Bluetooth
• Storage controllers
• IDE ATA/ATAPI controllers
• Universal Serial Bus controllers
• System devices
• Sound, video and game controllers

Look for devices showing:

• Yellow warning icons
• Unknown Device
• Device cannot start
• Driver errors

Microsoft specifically recommends checking Device Manager for devices marked with an exclamation point and reviewing driver-related events when troubleshooting bug check 0x9F.

Solution 4: Update Important Device Drivers

Do not concentrate only on the graphics driver.

For DRIVER_POWER_STATE_FAILURE, update these driver categories where applicable:

1. Chipset
2. Graphics
3. Wi-Fi
4. Ethernet
5. Bluetooth
6. Storage/NVMe
7. SATA/AHCI/RAID
8. USB controller
9. Thunderbolt/USB4
10. Card reader
11. Audio
12. Laptop power-management components

For branded systems, drivers from the PC manufacturer's support page are often preferable because OEM packages may contain system-specific power-management customizations.

Examples include systems from Dell, HP, Lenovo, ASUS, Acer and other manufacturers.

For custom-built desktops, check the motherboard and component manufacturers.

Solution 5: Roll Back a Recently Updated Driver

If the problem started immediately after updating a driver:

Device Manager → Device → Properties → Driver → Roll Back Driver

Restart the computer afterward.

A newer driver is not necessarily better for every hardware and firmware combination.

If Roll Back Driver is unavailable, download the previous known-working version from the hardware or computer manufacturer.

Solution 6: Reinstall the Suspected Driver

If updating does not help:

1. Open Device Manager.
2. Locate the suspected device.
3. Right-click it.
4. Select Uninstall device.
5. Restart Windows.
6. Install the correct driver supplied by the OEM or hardware manufacturer.

Before uninstalling critical network or storage drivers, make sure you already have the correct replacement driver available.

Solution 7: Install Windows Updates

Open:

Settings → Windows Update

Install applicable Windows updates.

Also inspect:

Windows Update → Advanced options → Optional updates

Driver updates may sometimes appear there.

However, if the problem started immediately after a particular driver update, rolling back that driver may be more appropriate than installing additional versions blindly.

Solution 8: Temporarily Disable Sleep and Hibernate for Testing

Because bug check 0x9F is closely associated with power transitions, temporarily disabling automatic Sleep can help determine whether the crash occurs specifically during a power-state change.

Open:

Control Panel → Power Options → Change plan settings

Temporarily configure:

Put the computer to sleep → Never

Test the system.

You can also temporarily disable hibernation from an elevated Command Prompt:

powercfg /h off

To enable it again:

powercfg /h on

This is primarily a diagnostic measure. If disabling Sleep/Hibernate prevents the BSOD, the underlying driver or firmware problem should still be identified.

Solution 9: Test PCI Express Link State Power Management

Open:

Control Panel → Power Options → Change plan settings → Change advanced power settings

Expand:

PCI Express → Link State Power Management

Temporarily select:

Off

Restart the system and test.

If the crashes disappear, investigate PCIe devices and their drivers, especially:

• Graphics adapters
• Wi-Fi cards
• NVMe devices
• PCIe expansion cards

Do not treat disabling power management permanently as a substitute for fixing a defective driver unless necessary.

Solution 10: Check Network Adapter Power Management

Open:

Device Manager → Network adapters

Open the properties of your Wi-Fi or Ethernet adapter.

If the Power Management tab is available, temporarily clear:

Allow the computer to turn off this device to save power

Click OK and restart Windows.

This test is particularly useful if the BSOD happens after Sleep, Hibernate or Resume.

Solution 11: Update Chipset Drivers

Chipset drivers are especially important because they help Windows communicate correctly with motherboard components and power-management functions.

Obtain the chipset package from:

• Computer manufacturer for OEM laptops/desktops
• Motherboard manufacturer for custom PCs
• Intel or AMD where appropriate

Restart Windows after installation.

Laptop users should generally check the laptop manufacturer's support page first.

Solution 12: Update BIOS/UEFI Firmware

BIOS/UEFI updates may contain fixes related to:

• ACPI
• Sleep states
• CPU power management
• PCIe devices
• USB
• NVMe
• Compatibility
• Resume from Sleep

Microsoft also recommends checking with the system manufacturer for updated ACPI/BIOS or other firmware when diagnosing bug check 0x9F.

Important: BIOS updates must be performed carefully. Use the manufacturer's instructions, ensure stable power, and do not interrupt the firmware-update process.

Solution 13: Run DISM and System File Checker

Although DRIVER_POWER_STATE_FAILURE usually points toward a driver or device, Windows system-file corruption should also be eliminated.

Open Command Prompt or Terminal as Administrator.

Run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Restart Windows afterward.

Microsoft recommends DISM followed by System File Checker when repairing Windows component or protected system-file corruption.

Solution 14: Boot Windows in Safe Mode

If Windows crashes repeatedly during normal startup, use Safe Mode.

Go to:

Windows Recovery Environment → Troubleshoot → Advanced options → Startup Settings → Restart

Then choose:

Safe Mode

or

Safe Mode with Networking

Safe Mode loads Windows with a limited set of drivers and services. If the problem disappears there, this provides useful evidence that a third-party driver, service or configuration may be involved.

From Safe Mode you can:

• Remove a recently installed driver
• Roll back a driver
• Uninstall problematic software
• Remove recently installed hardware utilities
• Run SFC/DISM
• Perform additional diagnostics

Solution 15: Check Event Viewer

Press:

Windows + R

Enter:

eventvwr.msc

Navigate to:

Windows Logs → System

Check events around the exact time of the BSOD.

Look for errors involving:

• Kernel-Power
• BugCheck
• ACPI
• Disk
• StorPort
• Display
• NDIS/network drivers
• Device initialization
• Plug-and-Play

Microsoft recommends reviewing the System log for critical errors occurring around the time of a DRIVER_POWER_STATE_FAILURE crash.

Do not assume that every error immediately before the BSOD caused it; use Event Viewer as supporting evidence.

Solution 16: Check Windows Reliability Monitor

Search Windows for:

View reliability history

Reliability Monitor presents system failures chronologically.

Check the date and time corresponding to the BSOD.

Look for:

• Windows failures
• Hardware errors
• Driver installation
• Application installation
• Windows updates

This can help answer an important troubleshooting question:

What changed immediately before the crashes started?

Solution 17: Analyze the Windows Minidump

For recurring DRIVER_POWER_STATE_FAILURE errors, crash-dump analysis is one of the most reliable diagnostic approaches.

Windows commonly stores small crash dumps in:

C:\Windows\Minidump\

A dump file may look like:

082926-15468-01.dmp

Larger dumps may be stored as:

C:\Windows\MEMORY.DMP

Analyzing DRIVER_POWER_STATE_FAILURE with WinDbg

Install Microsoft's WinDbg and open the crash dump.

Run:

!analyze -v

Microsoft specifically recommends this command for analyzing bug check 0x9F.

The report may reveal:

• Bugcheck code
• Bugcheck parameters
• Device stack
• Blocked IRP
• Suspected driver
• Failure bucket
• Stack trace

You may see:

DRIVER_POWER_STATE_FAILURE (9f)

and, commonly:

Arg1: 0000000000000003

Parameter 1 value 0x3 means that a device object has been blocking an IRP for too long.

Understanding Important 0x9F Parameters

Microsoft documents several forms of DRIVER_POWER_STATE_FAILURE.

Some particularly useful ones are:

Arg1 = 0x3

A device object has blocked an IRP for too long.

This is one of the most useful cases for identifying the device stack associated with the timeout.

Arg1 = 0x4

The power-state transition timed out while waiting for synchronization with the Plug-and-Play subsystem.

Arg1 = 0x5 or 0x6

These cases relate to directed power transitions that a device failed to complete correctly.

The exact interpretation of all four arguments depends on the value of the first parameter.

Important: Do Not Automatically Blame ntoskrnl.exe, pci.sys or ACPI.sys

BSOD-analysis utilities sometimes highlight files such as:

ntoskrnl.exe
pci.sys
ACPI.sys

These are core Windows components and may simply be present in the crash path.

For example, seeing pci.sys in a dump does not automatically prove that pci.sys itself is defective. A third-party device driver lower or higher in the device stack may have failed to complete the requested operation.

Always inspect the complete dump analysis.

Solution 18: Examine the Blocked IRP in WinDbg

For advanced troubleshooting, particularly when Arg1 is 0x3, the fourth bugcheck argument points to the blocked IRP.

Microsoft documents debugger techniques such as inspecting the IRP and associated device stack to determine which driver is holding the power request.

This is especially useful for IT professionals troubleshooting recurring BSODs where basic driver updates do not identify the culprit.

Solution 19: Use Driver Verifier Carefully

Windows Driver Verifier can stress selected drivers and detect improper driver behavior.

Run:

verifier

However, Driver Verifier is an advanced diagnostic utility and can deliberately trigger additional crashes when it detects driver violations.

It should therefore not be enabled casually on production systems.

Before using it:

• Back up important data.
• Make sure Windows Recovery Environment is accessible.
• Know how to enter Safe Mode.
• Prefer testing suspected third-party drivers rather than blindly stressing everything.

If Driver Verifier makes Windows unstable, it can normally be disabled from an elevated command prompt using:

verifier /reset

Then restart the computer.

Solution 20: Perform a Clean Boot

If the problem may involve third-party software or services:

Press:

Windows + R

Enter:

msconfig

Under Services:

1. Select Hide all Microsoft services.
2. Disable remaining third-party services for testing.

Also disable unnecessary startup applications using Task Manager.

Restart Windows.

If the BSOD disappears, re-enable items gradually until the problematic component is identified.

Solution 21: Check Recently Installed Software

Software capable of installing kernel drivers deserves special attention, including:

• Antivirus products
• VPN clients
• Backup software
• Disk encryption utilities
• Hardware monitoring software
• RGB/control utilities
• Virtualization software
• Network filtering software
• Storage utilities
• Motherboard management software
• Third-party firewall software

Temporarily updating or uninstalling a recently added product may help isolate the responsible driver.

Solution 22: Check Hardware

Although 0x9F usually indicates a driver/power-transition problem, hardware should not be ignored if driver troubleshooting fails.

Test:

RAM

Run:

mdsched.exe

For intermittent memory problems, extended memory diagnostics may be required.

Storage

Check SMART/diagnostic information for SSDs and hard drives using the manufacturer's diagnostic utility where available.

External hardware

Remove non-essential hardware and test.

Laptop docking station

Update the docking-station firmware and drivers.

PCIe cards

Reseat or temporarily remove recently installed expansion cards.

Recommended Troubleshooting Order

For most computers, use this sequence:

1. Restart and identify when the crash happens.
2. Disconnect unnecessary USB/external hardware.
3. Check Device Manager.
4. Update chipset drivers.
5. Update graphics drivers.
6. Update Wi-Fi/Ethernet/Bluetooth drivers.
7. Update storage/NVMe drivers.
8. Roll back any driver updated immediately before the problem.
9. Install appropriate Windows updates.
10. Temporarily disable Sleep/Hibernate.
11. Test PCIe/network power-saving settings.
12. Update BIOS/UEFI if an appropriate update is available.
13. Run DISM and SFC.
14. Check Event Viewer and Reliability Monitor.
15. Analyze the minidump with WinDbg.
16. Use Driver Verifier only if advanced diagnosis is necessary.
17. Test hardware if driver troubleshooting does not resolve the problem.

Special Case: DRIVER_POWER_STATE_FAILURE After Sleep

If the BSOD occurs almost exclusively after waking the PC, concentrate first on:

Wi-Fi → Bluetooth → Graphics → Chipset → BIOS/UEFI → USB → PCIe devices

Temporarily disable Sleep and test.

If the system remains stable when Sleep is disabled, this strongly suggests that a power-transition-sensitive driver or device requires further investigation.

Special Case: DRIVER_POWER_STATE_FAILURE During Shutdown

When shutdown hangs for a long time and eventually produces 0x9F, a driver may be failing to complete its shutdown/power request.

Check:

• USB devices
• Network adapters
• Bluetooth
• Storage controllers
• GPU drivers
• VPN/filter drivers
• Recently installed hardware utilities

Dump analysis is particularly valuable in this situation.

Special Case: DRIVER_POWER_STATE_FAILURE After Windows Update

If the crashes began immediately after Windows Update:

1. Check Update History.
2. Identify driver updates installed around the same time.
3. Roll back the suspected driver if possible.
4. Download the OEM-recommended driver.
5. Update chipset and firmware if appropriate.
6. Analyze the latest minidump if the crash continues.

How to Prevent DRIVER_POWER_STATE_FAILURE

To reduce the possibility of future 0x9F crashes:

• Keep Windows updated.
• Use appropriate OEM drivers.
• Keep chipset drivers current.
• Maintain current BIOS/UEFI firmware where updates are relevant.
• Avoid random third-party driver-download websites.
• Remove unused hardware-management utilities.
• Do not install drivers intended for different hardware revisions.
• Investigate repeated Sleep/Resume problems rather than permanently ignoring them.
• Create restore points before major driver changes.
• Keep important data backed up.

Frequently Asked Questions (FAQ)

1. What does DRIVER_POWER_STATE_FAILURE mean?

It means Windows detected a driver or device that failed to correctly handle a power-state operation. The corresponding Windows bug check is 0x0000009F.

2. Is DRIVER_POWER_STATE_FAILURE a hardware problem?

Not necessarily. Driver and firmware problems are common causes, although malfunctioning hardware can also contribute.

3. Why does the BSOD occur when my laptop wakes from Sleep?

Sleep and Resume require Windows to change the power states of many devices. A Wi-Fi, graphics, Bluetooth, USB, storage or chipset-related driver may fail during that transition.

4. Can an NVIDIA or AMD graphics driver cause DRIVER_POWER_STATE_FAILURE?

Yes. Graphics adapters have complex power-management states, so display drivers should be investigated when the crash is associated with Sleep, Resume, shutdown or graphics switching.

5. Can a Wi-Fi driver cause 0x9F?

Yes. Network adapters frequently change power states and can be involved in Sleep/Resume-related crashes.

6. Should I disable Sleep permanently?

Usually not as the first solution. Disabling Sleep is useful diagnostically. The preferred approach is to identify and correct the faulty driver, device or firmware.

7. Where are Windows BSOD dump files stored?

Small dumps are commonly found at:

C:\Windows\Minidump\

A larger system dump may be stored at:

C:\Windows\MEMORY.DMP

8. Which tool should I use to analyze DRIVER_POWER_STATE_FAILURE?

Microsoft WinDbg is the appropriate advanced debugging tool.

A common initial command is:

!analyze -v

Microsoft specifically documents this command for 0x9F debugging.

9. What does 0x9F parameter 1 = 0x3 mean?

It indicates that a device object has been blocking a power IRP for too long.

10. Is ntoskrnl.exe necessarily responsible?

No. ntoskrnl.exe is the Windows kernel and commonly appears in crash dumps. Its presence alone does not establish it as the root cause.

11. Can BIOS cause DRIVER_POWER_STATE_FAILURE?

Firmware/ACPI compatibility problems can contribute to power-state failures. Microsoft recommends checking for applicable BIOS/ACPI/firmware updates during 0x9F troubleshooting.

12. Will SFC fix DRIVER_POWER_STATE_FAILURE?

Only if Windows system-file corruption contributes to the problem. Since 0x9F commonly involves device drivers and power transitions, SFC should be considered one troubleshooting step rather than a guaranteed fix.

13. Can antivirus software cause this BSOD?

Potentially. Security products can install kernel-level filter drivers. If crashes started after installing or updating security software, its drivers should be considered during diagnosis.

14. Can USB devices cause DRIVER_POWER_STATE_FAILURE?

Yes. USB devices, hubs, adapters and their drivers participate in power management and can potentially cause Sleep, Resume or shutdown problems.

15. Is Driver Verifier safe?

Driver Verifier is a legitimate Windows diagnostic feature, but it is intended for advanced troubleshooting and may intentionally cause crashes when it detects driver violations. It should be used cautiously.

16. What should I update first?

For recurring 0x9F crashes, prioritize:

Chipset → GPU → Wi-Fi/Ethernet → Bluetooth → Storage/NVMe → USB/Thunderbolt → BIOS/UEFI

The exact priority should also reflect when the BSOD occurs.

17. Why does my PC take several minutes to shut down before showing DRIVER_POWER_STATE_FAILURE?

A driver may be holding a power or Plug-and-Play operation until Windows reaches its timeout threshold. Dump analysis can help identify the associated device stack.

18. Does reinstalling Windows always fix this problem?

No. If the underlying problem is defective hardware, firmware or an OEM driver that gets reinstalled afterward, the error can return. Driver and dump analysis should normally be attempted first.

19. Should I download drivers from third-party driver websites?

It is generally safer to obtain drivers from Windows Update, the computer manufacturer, motherboard manufacturer or hardware vendor.

20. What is the best way to identify the exact driver?

Analyze the crash dump using WinDbg. Microsoft recommends !analyze -v as the initial analysis command and documents additional techniques for examining blocked IRPs and device stacks.

Conclusion

DRIVER_POWER_STATE_FAILURE (0x0000009F) is primarily a driver and device power-management BSOD. It commonly occurs when Windows is entering or leaving Sleep, Hibernate, shutdown or another device power state and a driver fails to complete the required operation correctly.

Rather than immediately reinstalling Windows, troubleshoot systematically.

Start with recently changed drivers and external hardware, then check chipset, graphics, networking, Bluetooth and storage drivers. Test power-management settings, update appropriate firmware, examine Event Viewer, and analyze crash dumps when the problem persists.

For recurring cases, the most useful evidence is usually the actual .dmp crash file. WinDbg can reveal the bugcheck parameters, blocked IRP and associated device stack, allowing the investigation to move from general troubleshooting to identifying the specific driver or hardware component involved.

#tags

#DRIVER_POWER_STATE_FAILURE #DriverPowerStateFailure #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsError #WindowsTroubleshooting #BSODFix #Error0x9F #0x0000009F #BugCheck0x9F #WindowsDrivers #DriverError #DriverFailure #DeviceDriver #DriverUpdate #DriverRollback #PowerManagement #WindowsPowerManagement #SleepProblem #HibernateProblem #WakeFromSleep #ShutdownProblem #WindowsRestart #LaptopBSOD #DesktopBSOD #GraphicsDriver #NVIDIADriver #AMDDriver #IntelGraphics #WiFiDriver #NetworkDriver #BluetoothDriver #ChipsetDriver #StorageDriver #NVMeDriver #USBDriver #ACPI #BIOSUpdate #UEFI #WinDbg #CrashDump #Minidump #DriverVerifier #DeviceManager #EventViewer #WindowsRepair #WindowsSupport