ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

DRIVER_POWER_STATE_FAILURE

DRIVER_POWER_STATE_FAILURE (0x9F) on Windows: driver power fault

Verified with sources3 sourcesReviewed Oct 4, 2026
Technician coming? See the 2 steps they must show you

Risk level

Medium

Proceed carefully and stop if the check is unclear.

Urgency

High

Quick answer

Windows stopped because a driver was left in an invalid power state, often when sleeping, hibernating or resuming. Temporarily turn off power saving and check the last driver or device you added.

Safety first

Stop and check this first

  • A crash on sleep does not mean the battery or motherboard is faulty: 0x9F points to a driver. Ask for the diagnosis before agreeing to replace parts.

Safe checks you can perform

  • When the crash happens
  • Temporarily turn off power saving
  • Device Manager

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Analyse the dump and the blocked IRP
  • Do not attempt this professional task: Firmware and maker diagnostics

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Analyse the dump and the blocked IRP

    What they doThe technician runs !analyze -v on the dump, reviews the nt!TRIAGE_9F_POWER structure and the blocked IRP with !irp to identify the device stack involved.

    They must show youthe output with parameter 1 and the identified driver.

    In writingwhich device was blocking the request and what was done.

  2. Firmware and maker diagnostics

    What they doThey ask the PC maker for newer ACPI or BIOS firmware and run its hardware diagnostics.

    They must show youfirmware versions before and after and the diagnostic report.

    In writingwhat was updated and whether the hardware passed.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. When the crash happens

    No special tools

    Who:
    you.
    How:
    note whether the blue screen appears when sleeping, hibernating, closing the lid or waking from those states, and photograph the code and driver if shown.
    Result that matters:
    whether the failure is tied to power management.
    If it matches sleep or resume:
    it points to a driver that handles power badly.
    If it happens at any time:
    go on to recent drivers and hardware.
    Evidence to keep:
    photo of the screen and the exact moment of each crash.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

  2. Temporarily turn off power saving

    No special tools

    Who:
    you.
    How:
    in Control Panel, Power Options, temporarily turn off the saving modes (sleep and hibernation) and use the PC for a few days.
    Result that matters:
    whether crashes stop without power saving.
    If they stop:
    a driver fails during power transitions; look for its update.
    If they continue:
    power is not the trigger.
    Evidence to keep:
    test dates and number of crashes.

    This is only a test to isolate the cause: restore your settings when you finish.

    Evidence: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

  3. Device Manager

    No special tools

    Who:
    you.
    How:
    open Device Manager, look for devices with an exclamation mark, review the events in the driver properties and use Update driver.
    Result that matters:
    whether any device shows errors and whether updating fixes it.
    If it fixes it:
    that driver was the cause.
    If there are no errors:
    remove recently added hardware and test again.
    Evidence to keep:
    screenshot of the device and its driver version.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x0000009F
  • 0x9F
  • DRIVER POWER STATE FAILURE
  • STOP 0x0000009F
  • stop code DRIVER_POWER_STATE_FAILURE

What it means

Microsoft defines bug check 0x0000009F as a driver in an inconsistent or invalid power state. Depending on parameter 1, it can be a device freed with a power request still outstanding, a device blocking a request (IRP) for too long, or a power transition timing out while waiting for the Plug and Play subsystem. Microsoft links several cases to hibernation and to suspending and resuming. The code points to a driver and does not prove the device is broken.

Warnings and stop conditions

  • Mediumeditorial warning

    A crash on sleep does not mean the battery or motherboard is faulty: 0x9F points to a driver. Ask for the diagnosis before agreeing to replace parts.

    Evidence: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

Symptoms and causes

Probable causes · in order

  • New or updated driverCommon

    Microsoft asks you to check recently added drivers or services first; suspect them if the failure began after installing them.

    Evidence: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

  • Problem when sleeping, hibernating or resumingPossible

    You can tell because the crash happens when closing the lid, sleeping or waking; turning off power saving helps isolate it.

    Evidence: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

  • Recently added hardwarePossible

    If you added a part or peripheral, Microsoft says to remove it or ask its maker for patches.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

  • Outdated ACPI or BIOS firmwarePossible

    If nothing changed, Microsoft suggests asking the maker for newer ACPI or BIOS firmware.

    Evidence: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

Virtual technician

Does DRIVER_POWER_STATE_FAILURE still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Stop code error or bug check troubleshooting (IT professionals)

    Microsoft · 2026 · official_doc

  2. 2

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

  3. 3

    Bug Check 0x9F DRIVER_POWER_STATE_FAILURE

    Microsoft · 2026 · official_doc

Sources: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x9F DRIVER_POWER_STATE_FAILUREreviewed 2026-10-04 · verified

Was this entry useful?