How to Fix INTERNAL_POWER_ERROR (0x000000A0) Blue Screen Error in Windows

Quick Answer

INTERNAL_POWER_ERROR (0x000000A0) is a Windows Blue Screen of Death (BSOD) error that occurs when the Windows power policy manager encounters a fatal internal failure. It may happen during sleep, hibernation, resume, shutdown, or other power-management operations.

To troubleshoot this error, check recently installed drivers and Windows updates, investigate hibernation and sleep-related problems, inspect BIOS/UEFI firmware compatibility, and review Windows power settings. If the error continues, analyze the crash dump using WinDbg to identify the specific bug-check parameters and narrow down the failing operation.

What Is INTERNAL_POWER_ERROR (0x000000A0)?

INTERNAL_POWER_ERROR is a Windows kernel bug check identified by hexadecimal code 0x000000A0. It indicates that the Windows power policy manager encountered a fatal error while processing an internal power-management operation.

Windows power management coordinates communication between the operating system, hardware devices, device drivers, and system firmware. It manages operations such as:

• Entering and leaving sleep mode.
• Entering and resuming from hibernation.
• Shutting down and restarting the computer.
• Changing device power states.
• Managing processor idle states.
• Coordinating hardware power consumption.

If an internal operation fails, Windows may stop execution to prevent further system instability and display the INTERNAL_POWER_ERROR blue screen.

The stop code identifies the general failure category. The exact cause depends on the first bug-check parameter and additional diagnostic information.

Common Symptoms

Depending on the underlying failure, the following symptoms may occur:

• Windows displays a blue screen containing INTERNAL_POWER_ERROR.
• The computer crashes while entering sleep or hibernation.
• The system restarts unexpectedly when waking from sleep.
• Windows freezes during shutdown or restart.
• The computer repeatedly crashes during power-state transitions.
• The error appears after installing a device driver or Windows update.
• The system becomes unstable after connecting a docking station or external device.
• The computer fails to complete a power-management operation.

Common Causes of INTERNAL_POWER_ERROR

The following are possible areas to investigate. They are not confirmed causes for every occurrence of this stop code.

Understanding Bug Check Parameters

Windows supplies four parameters when reporting bug check 0xA0. The first parameter identifies the type of violation. The meanings of the remaining parameters depend on the first parameter.

The following table contains selected Parameter 1 values documented by Microsoft. It is not an exhaustive list.

For the complete parameter list and the meanings of Parameters 2, 3, and 4, refer to Microsoft's Bug Check 0xA0: INTERNAL_POWER_ERROR documentation.

How to Fix INTERNAL_POWER_ERROR (0x000000A0)

Follow the troubleshooting procedures in order. Begin with basic checks and recently changed components before attempting advanced system or firmware modifications.

1. Restart Windows and Disconnect External Devices

A temporary device or power-management problem may not recur after restarting Windows.

1. Save your work and restart the computer if Windows is accessible.
2. Disconnect nonessential USB devices, external storage devices, docking stations, and recently connected peripherals.
3. Start Windows without the disconnected devices.
4. Observe whether the error occurs again.
5. Reconnect devices individually if the computer remains stable.

If the error returns after connecting a particular device, investigate its driver, firmware, and compatibility with the computer.

2. Install Available Windows Updates

Windows updates may include operating-system reliability improvements, compatibility updates, and fixes for known system problems.

1. Press Windows + I to open Settings.
2. Navigate to Windows Update.
3. Select Check for updates.
4. Install applicable updates.
5. Restart the computer when requested.

After updating Windows, check whether the blue screen still occurs during the same power-management operation.

3. Update or Roll Back Device Drivers

Device drivers participate in Windows power-management operations. A driver that does not correctly handle a power request may contribute to an INTERNAL_POWER_ERROR crash.

Check Device Drivers

1. Right-click Start and select Device Manager.
2. Expand the relevant hardware categories.
3. Look for devices displaying a warning symbol.
4. Right-click a suspected device and select Properties.
5. Open the Driver tab.
6. Review the driver provider, date, and version.
7. Check the manufacturer's official support website for a compatible driver when an update is justified.

Depending on the diagnostic evidence, relevant drivers may include chipset, graphics, storage controller, USB, network, and other platform-related drivers.

Avoid updating every driver indiscriminately. Prioritize devices that were recently changed or are identified by crash dump analysis.

Roll Back a Recently Updated Driver

If the problem began immediately after installing a driver update, restoring the previous version may help determine whether the change is related.

1. Open Device Manager.
2. Right-click the affected device.
3. Select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver, if available.
6. Follow the instructions and restart Windows.

If the rollback option is unavailable, obtain an appropriate previous compatible driver from the device manufacturer's official support website.

4. Check Whether Hibernation Is Related to the Error

Hibernation is a Windows power-saving feature that stores system state in a file named hiberfil.sys. Windows uses this file to restore the computer when resuming from hibernation.

If the crash occurs during hibernation or resume, temporarily disabling hibernation can help determine whether the problem is associated with hibernation-related operations.

Disable Hibernation

1. Open Start.
2. Search for Command Prompt.
3. Right-click Command Prompt and select Run as administrator.
4. Execute the following command:

powercfg.exe /hibernate off

This command disables Windows hibernation.

Test the operation that previously triggered the blue screen. Remember that hibernation and hybrid sleep will not be available during this test.

Re-enable Hibernation

To restore hibernation, open Command Prompt as administrator and execute:

powercfg.exe /hibernate on

This command enables hibernation again.

If the error stops while hibernation is disabled, investigate hibernation and resume operations further. This observation does not prove that the hibernation file is defective or establish a permanent fix.

Reference: Microsoft: How to disable and re-enable hibernation.

5. Inspect Windows Power Configuration

Windows includes the Power Configuration utility, powercfg, for inspecting and managing power plans and device power settings.

Open Command Prompt or Windows Terminal and execute the following commands to collect diagnostic information.

Display the active power plan:

powercfg /getactivescheme

This command displays the currently active power scheme.

Display available sleep states:

powercfg /a

This command identifies available sleep states and may provide reasons why certain states are unavailable.

Display power settings:

powercfg /query

This command displays configured power settings.

Review the results for unexpected configuration changes, unavailable sleep states, or settings relevant to the operation that triggers the crash.

These commands primarily collect diagnostic information. Avoid randomly changing advanced power settings without identifying a relevant configuration issue.

Reference: Microsoft: Powercfg command-line options.

6. Check BIOS/UEFI and Firmware Compatibility

BIOS/UEFI firmware provides hardware configuration and ACPI information that Windows uses for power management.

Firmware investigation is particularly relevant when the crash dump identifies an ACPI-related failure, such as Parameter 1 equal to 0x680.

1. Identify the exact computer or motherboard model.
2. Visit the manufacturer's official support website.
3. Check for BIOS/UEFI updates applicable to the exact model.
4. Read the firmware release notes for power-management, sleep, resume, or compatibility improvements.
5. Follow the manufacturer's update procedure if an update is appropriate.

A BIOS update is not a universal solution for INTERNAL_POWER_ERROR. Perform it only when justified by diagnostic evidence or manufacturer guidance.

7. Repair Windows System Files

If Windows also displays other stability problems or system-file integrity errors, use DISM and System File Checker (SFC) to check and repair Windows components.

Open Command Prompt or Windows Terminal as administrator.

Step 1: Repair the Windows component store.

DISM.exe /Online /Cleanup-Image /RestoreHealth

This command checks the online Windows image and attempts to repair component-store corruption. A suitable repair source may be required if Windows Update is unavailable.

Step 2: Scan protected Windows system files.

sfc /scannow

This command scans protected system files and attempts to repair integrity violations.

Wait until both operations finish. Review their results and restart Windows if repairs were performed.

These tools address Windows image and system-file corruption. They are general troubleshooting procedures rather than guaranteed fixes for bug check 0xA0.

8. Test Windows in Safe Mode

If the computer crashes during normal Windows operation, Safe Mode can help determine whether the issue is associated with drivers or services that are not loaded in the same way during a normal startup.

1. Open Settings.
2. Navigate to System > Recovery.
3. Under Advanced startup, select Restart now.
4. In Windows Recovery Environment, select Troubleshoot > Advanced options > Startup Settings.
5. Select Restart.
6. Choose the appropriate Safe Mode option.
7. Observe whether Windows remains stable.

If Windows cannot reach Settings, use the available Windows Recovery Environment startup options.

Stability in Safe Mode is a diagnostic clue. It does not independently identify a faulty driver or service.

Advanced Troubleshooting: Analyze the Crash Dump

If the basic troubleshooting procedures do not resolve the issue, analyze the Windows crash dump. This is particularly useful for IT support technicians and system administrators.

A crash dump can contain bug-check parameters, processor context, stack information, and other diagnostic data captured when Windows stopped.

1. Locate the Windows Memory Dump

Windows may store crash dump files in the following default locations:

The actual location depends on Windows configuration. A dump may not be available if dump collection was disabled or the system could not complete the dump-writing operation.

2. Configure Crash Dump Collection

If Windows is not generating useful crash dumps, review the startup and recovery settings.

1. Press Windows + R.
2. Enter sysdm.cpl and press Enter.
3. Open the Advanced tab.
4. Under Startup and Recovery, select Settings.
5. Locate Write debugging information.
6. Select an appropriate dump type, such as Automatic memory dump.
7. Review the dump file location and related settings.
8. Save the changes.

Crash dump collection requires suitable system configuration and disk space. Memory dumps may contain sensitive information from system memory. Do not upload them to public websites or share them without considering privacy and security implications.

Reference: Microsoft: Stop code error or blue screen error troubleshooting.

3. Analyze the Dump Using WinDbg

WinDbg is Microsoft's debugging tool for examining Windows crash dumps. It is useful when bug-check parameters do not provide enough information for basic troubleshooting.

1. Install WinDbg using Microsoft's official distribution.
2. Start WinDbg.
3. Open the relevant memory dump file.
4. Allow WinDbg to load the required debugging symbols.
5. Open the debugger command window.
6. Execute the following command:

!analyze -v

This command performs verbose analysis of the current bug check or exception.

Review the available diagnostic information:

• BugCheck: The bug-check code and associated parameters.
• Arguments: The four arguments supplied to the bug check.
• STACK_TEXT: The available stack trace information.
• MODULE_NAME: A module associated with the debugger's analysis.
• IMAGE_NAME: The associated image name.
• FAILURE_BUCKET_ID: A failure classification that can help compare similar crashes.

A module named in the analysis is not automatically the root cause. It may simply be part of the execution path when another component or operation failed.

Official documentation:

• Microsoft: Analyze a Kernel-Mode Dump File by Using WinDbg
• Microsoft: !analyze (WinDbg)

4. Investigate the First Bug-Check Parameter

Compare Parameter 1 from the crash dump with Microsoft's official bug-check reference.

• Parameter 1 = 0x1: Investigate power I/O request handling and the associated device or driver information.
• Parameter 1 = 0x3 or 0x4: Investigate the hibernation context or hibernation file operation indicated by the checksum information.
• Parameter 1 = 0x9: Investigate the hibernation file preparation failure and associated status information.
• Parameter 1 = 0xD, 0xF, 0xF0, or 0xF1: Investigate the power-state transition, sleep checkpoint, and relevant thread information.
• Parameter 1 = 0x680: Investigate ACPI table availability and firmware compatibility.
• Parameter 1 = 0x701: Investigate the processor idle-state transition and the processor identified in the bug-check parameters.

Some parameters contain pointers to internal kernel structures rather than ordinary error codes. Use the appropriate debugger commands and Microsoft documentation to interpret them. Do not treat pointer values as standalone error identifiers.

When to Suspect Hardware Problems

Hardware investigation may be appropriate when the error continues after relevant software and driver troubleshooting or when crash dump evidence indicates a hardware or firmware-related failure.

Consider the following checks:

• Inspect the battery and power adapter for physical damage or abnormal behavior.
• Run manufacturer-provided hardware diagnostics.
• Investigate storage-related errors if the dump identifies hibernation file read or write failures.
• Check memory stability if other diagnostic evidence indicates memory problems.
• Investigate docking stations and external devices if the crash occurs during connection or disconnection.
• Review motherboard and firmware diagnostics when ACPI or platform power-management problems are indicated.

Do not replace the motherboard, power supply, battery, or other hardware solely because Windows displays INTERNAL_POWER_ERROR. Confirm the suspected hardware problem using appropriate diagnostic evidence.

What to Do If Windows Cannot Start Normally

If the computer repeatedly crashes and cannot start Windows normally, use Windows Recovery Environment (WinRE) to investigate and recover the system.

1. Allow Automatic Repair to start if Windows enters its recovery process.
2. Select Advanced options.
3. Open Troubleshoot > Advanced options.
4. Try Startup Settings and Safe Mode where appropriate.
5. If the problem started after a recent Windows update, consider Uninstall Updates.
6. If a suitable restore point exists and the problem followed a system change, consider System Restore.

Some recovery operations may require a BitLocker recovery key when device encryption is enabled. Keep the recovery key available before attempting operations that require access to an encrypted Windows installation.

Back up important data whenever possible before performing recovery operations that may affect installed applications, settings, or files.

Refer to Microsoft Support: Troubleshooting Windows unexpected restarts and stop code errors.

How to Prevent INTERNAL_POWER_ERROR

Not every power-management failure can be prevented. However, the following practices can reduce avoidable driver, firmware, and configuration problems:

• Install compatible device drivers from Windows Update or official manufacturer websites.
• Keep Windows updated with applicable reliability and security updates.
• Install BIOS/UEFI updates only when appropriate for the exact hardware model.
• Avoid downloading drivers from untrusted third-party websites.
• Investigate repeated sleep, resume, and shutdown failures instead of ignoring them.
• Maintain sufficient disk space for Windows operations and crash dump collection.
• Back up important files regularly.
• Review recently changed power settings and device configurations when power-management problems begin.

Frequently Asked Questions

What does INTERNAL_POWER_ERROR 0x000000A0 mean?

It means the Windows power policy manager encountered a fatal error. The exact failure depends on the first bug-check parameter and may involve power I/O requests, hibernation, device power management, or processor power-state operations.

Is INTERNAL_POWER_ERROR caused by a faulty power supply?

Not necessarily. Although hardware or power-delivery problems may contribute to system instability, this stop code identifies a fatal power policy manager failure. Driver, firmware, hibernation, and device power-management problems are also possible.

Can a device driver cause INTERNAL_POWER_ERROR?

Yes. A driver that incorrectly handles power-management requests may contribute to this bug check. However, the stop code alone does not identify the responsible driver. Crash dump analysis and recent driver-change history are useful for narrowing the cause.

Why does INTERNAL_POWER_ERROR occur when Windows wakes from sleep?

A failure may occur while Windows restores devices and system components to their operational power states. Investigate the bug-check parameters, device drivers, firmware, and crash dump when the failure consistently occurs during resume.

Will disabling hibernation fix INTERNAL_POWER_ERROR?

Disabling hibernation can help determine whether the problem is associated with hibernation-related operations. It is a diagnostic test rather than a guaranteed permanent fix. Disabling hibernation also makes hybrid sleep unavailable.

Where are INTERNAL_POWER_ERROR crash dump files stored?

Small memory dumps are normally stored in C:\Windows\Minidump. Kernel, automatic, and complete memory dumps are normally stored in C:\Windows\MEMORY.DMP. The actual location depends on the configured dump type and system settings.

Can WinDbg identify the cause of INTERNAL_POWER_ERROR?

WinDbg can help investigate the bug-check parameters, stack trace, and other diagnostic information. It can narrow down the failing operation, but interpreting the results may require knowledge of Windows kernel debugging and power management.

Should I reinstall Windows to resolve error 0xA0?

Reinstalling Windows should not be the first troubleshooting step. Investigate drivers, power-management operations, hibernation, firmware, and crash dump evidence first. Consider reinstalling Windows only after less disruptive recovery and diagnostic procedures have been exhausted and the available evidence justifies it.

Sources

• Microsoft Learn: Bug Check 0xA0 – INTERNAL_POWER_ERROR
• Microsoft Learn: Powercfg Command-Line Options
• Microsoft Learn: How to Disable and Re-enable Hibernation
• Microsoft Learn: Analyze a Kernel-Mode Dump File by Using WinDbg
• Microsoft Learn: !analyze (WinDbg)
• Microsoft Learn: Stop Code Error or Blue Screen Error Troubleshooting
• Microsoft Support: Troubleshooting Windows Unexpected Restarts and Stop Code Errors