Skip to content
PCDecoder
0x000000A0INTERNAL_POWER_ERRORStop codeWidely reported

INTERNAL_POWER_ERROR (0xA0): what it means and how to fix it

Updated Oct 22, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This blue screen indicates that the Windows power policy manager encountered an unrecoverable failure during a power state transition. It most frequently occurs when entering or resuming from hibernation, often due to an undersized hibernation file or a failing disk operation. Resizing or resetting the hibernation file is the first step to take.

What it means

INTERNAL_POWER_ERROR (bug check value 0x000000A0) occurs when the Windows power policy manager runs into a fatal error while trying to manage system power states. Windows continuously controls power delivery to different hardware components, coordinating actions like putting the system to sleep, entering hibernation, shutting down, and waking up.

Why the power manager crashes

When Windows transitions between running, sleep, or hibernate, the kernel coordinates with hardware drivers using power I/O request packets (IRPs) and the Power Runtime Framework. If an underlying device driver fails to complete a power transition in a timely manner, corrupts power data, or passes invalid parameters to the power manager, Windows halts the system to prevent data loss.

Hibernation and disk errors

A large number of 0xA0 crashes occur around the hibernation process. When Windows prepares to hibernate, it saves the contents of your active system memory to a dedicated disk file named hiberfil.sys. If the hibernation file is too small to hold the current memory ranges, the power manager triggers this stop code. Similarly, if the storage drive fails to read or write part of the hibernation file, or if the checksum of the saved data does not match what was expected upon resume, Windows stops execution. Corrupt data returned from the disk during resume will also trigger this bug check.

Driver and plugin timeouts

Besides hibernation, this error happens when hardware drivers fail to process power transitions properly. For example, a driver may queue too many inrush power requests, register duplicates with the Power Runtime Framework, or block a power worker thread for too long. If a device fails to wake up or suspend before the kernel's power checkpoint deadline expires, Windows generates the 0xA0 crash.

Common causes

  • The system hibernation file is too small to accommodate the active memory data.
  • The storage disk failed to properly read, write, or verify the hibernation file data.
  • A device driver failed to complete a power transition (suspend or resume) in a timely manner.
  • A Power Engine Plugin or device driver passed invalid parameters to the Power Runtime Framework.
  • Battery or thermal power request packets returned an unknown or corrupt status.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Reset and enlarge the hibernation file

    Use this as the first fix, especially if the crash occurs when putting your PC into hibernation or turning it back on.

    1. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
    2. Type powercfg /hibernate off and press Enter to disable hibernation and remove the existing file.
    3. Restart your computer.
    4. Open Command Prompt as administrator again.
    5. Type powercfg /hibernate on and press Enter to recreate the hibernation file.
    6. Type powercfg /hibernate /size 100 and press Enter to ensure the hibernation file has full capacity for system memory.
    Did this fix it?

  2. Update or reinstall device drivers

    Use this if the crash happens while waking the PC from sleep or during general power state changes.

    1. Right-click the Start menu button and select Device Manager.
    2. Expand sections for major hardware, particularly Display adapters, Network adapters, and Batteries.
    3. Right-click a device and select Update driver.
    4. Choose Search automatically for drivers.
    5. If recent driver updates caused the problem, right-click the device, select Properties, open the Driver tab, and click Roll Back Driver if available.
    Did this fix it?

  3. Run Check Disk to repair storage errors

    Use this if disk subsystem read or write failures are corrupting the power state files.

    1. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
    2. Type chkdsk C: /f /r and press Enter.
    3. Type Y when prompted to schedule the volume check on the next system restart.
    4. Restart your computer and allow the disk scan to complete.
    Did this fix it?

  4. Disable fast startup

    Use this if the error persists during normal shutdowns and boot sequences.

    1. Press Windows Key + R, type control, and press Enter to open Control Panel.
    2. Click Power Options.
    3. Select Choose what the power buttons do from the left pane.
    4. Click Change settings that are currently unavailable.
    5. Uncheck the box next to Turn on fast startup (recommended).
    6. Click Save changes and restart your PC.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 22, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does bug check 0x000000A0 mean?

It is an INTERNAL_POWER_ERROR stop code, meaning the Windows power policy manager suffered a fatal crash while handling system power states like sleep, hibernate, or resume.

Why does INTERNAL_POWER_ERROR happen when waking my PC?

The error happens when a device driver fails to wake up within the required time or when the system reads corrupted data from the hibernation file on your disk.

Can a full hard drive cause an internal power error?

Yes. If your system drive does not have enough free space to expand the hibernation file to match active memory needs, Windows will trigger a 0xA0 crash.

More stop codes decoded