Partition Commander Now it's easy for anyone to safely partition their hard drive! You can reclaim waste disk space, organize files, even add new OSes.
Double Anti-Spy Fast Double Anti-Spyware protection handles thousands of threats.
Driver Genius Improve system stability by getting new drivers! Also makes it easy to backup, restore, and remove drivers.
INTERNAL_POWER_ERROR
STOP: 0x000000A0
Description
The System Power Policy (SPP) component had a fatal problem. The SPP is used to watch system activity and set the correct power state in different modes, such as AC power, or running from a battery or UPS. This is used to balance speed, battery duration and other factors.
This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
Sample Screen
A problem has been detected and Windows has been shut down to prevent damage to your computer.
INTERNAL_POWER_ERROR
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x000000A0
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance.
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
Microsoft has issued a hot fix (a special update) to fix this issue:
For Windows Vista first release, view this possible fix. This fix is included in SP1.
FaultWire Staff Posted: 5-Oct-2008
Get the Latest Updates
7
Install the latest Windows software updates. Don't forget to check for non-critical updates too!
To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).
For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.
For IE 7 and older: Click on Tools, then Windows Update. Follow the instructions.
FaultWire Staff Posted: 5-Oct-2008
Uninstall the Last Install
6
If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.
For removal of an application (Windows 7 & Vista):
Click on Start, Control Panel, then Programs and Features.
Select the software to uninstall and select Uninstall.
For removal of an application (Windows XP):
Click on Start, Control Panel, then Add or Remove Programs.
Select the software to uninstall and select Remove.
To disable a driver:
Bring up the system information dialog:
On the keyboard, press the Windows key + Pause/Break.
or
Select Start, right click Computer and on the drop-down, select Properties.
Click on the left side option Advanced system settings(7/Vista only).
In System Properties, select the Hardware tab, then click on Device Manager button.
Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
Click OK to exit, then close the Device Manager and other previously opened dialogs.
The power policy manager experienced a fatal error.
After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameters 1 and 2 specify the cause of the issue.
Parameter 1
Parameter 2
Cause
0x00000001
1
An error occurred during the handling of the power I/O request packet (IRP). A device has overrun its maximum number of reference counts.
2, 3, or 4
An error occurred during the handling of the power I/O request packet (IRP). Too many inrush power IRPs have been queued (Server 2003 and older only).
5
An error occurred during the handling of the power I/O request packet (IRP). The power IRP has been sent to a passive level device object (Server 2003 and older only).
0x00000002
undefined
An internal failure has occurred while attempting to process a power event.
0x00000003
checksum
The checksum for a hibernation context page does not match its expected checksum.
0x00000004
checksum
The checksum for a page about to be written to the hibernation file does not match its expected checksum.
0x00000005
undefined
An unknown shutdown code has been sent to the system shutdown handler.
0x00000007
undefined
An unhandled exception has occurred.
0x00000008
0x100
An unknown device type is being processed.
0x101
An unhandled exception occurred.
0x102
The hibernation working buffer size is not page-aligned.
0x103
Some working pages were not accounted for during the hibernation process.
0x104
An attempt was made to map internal hibernation memory while the internal memory structures were locked.
0x105
An attempt was made to map internal hibernation memory with an unsupported memory type flag.
0x106
A memory descriptor list (MDL) was created during the hibernation process that describes memory that is not paged-aligned.
0x107
A data mismatch occurred in the internal hibernation data structures.
0x108
The disk subsystem failed to properly write part of the hibernation file.
0x109
The checksum for the processor state data does not match its expected checksum.
0x10A
The disk subsystem failed to properly write part of the hibernation file.
0x200
An unknown device type is being checked for an idle state.
0x300
An unknown status was returned from a battery power IRP.
0x301
The battery has entered an unknown state
0x400
A device has overrun its maximum number of reference counts.
0x401-403
Too many inrush power IRPs have been queued (Server 2003 and older only).
0x404
A power IRP has been sent to a passive level device object (Server 2003 and older only).
0x500
An unknown status was returned from a thermal power IRP.
Parameter 3 depends on the value of Parameter 1 and 2.
Parameter 4 depends on the value of Parameter 1 and 2.
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues.
Research this Issue
Getting search results...
Notes
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it.