INTERNAL_POWER_ERROR Blue Screen? Check the First Value

INTERNAL_POWER_ERROR, stop code 0xA0, means the Windows power manager (the code that handles sleep, hibernation and device power) hit an error it couldn't recover from.

On laptops with both Intel and AMD graphics, the AMD display driver is the first thing to suspect, especially if the crashes showed up after a Windows upgrade.

A crash just as the PC goes into hibernation points to the other common cause instead: a hibernation file too small for your memory. The first value Windows saves with the crash tells you which one you've got.

Read the first value saved with the crash

Windows writes the full code to its System log when it starts back up after the crash. Right-click Start, open Event Viewer, go to Windows Logs > System and look for a BugCheck entry from around that time.

The entry starts with The computer has rebooted from a bugcheck, followed by 0x000000a0 and four values in brackets. Only the first one matters here. Drop the leading zeros, so 0x000000000000000b reads as 0xB.

Diagram of the first value in an INTERNAL_POWER_ERROR record and what it means: 0xB is a hibernation file that's too small, 0x108, 0x10A or 0x10E is the drive, and most other values point to a driver

The bug check 0xA0 reference has a long table of these values, but three groups cover what you'll see on a home PC:

  • 0xB means the hibernation file is too small. Start with fix 1.
  • 0x108, 0x10A or 0x10E means the drive failed to write or read the hibernation file, or handed back corrupt data from it. Go to fix 3.
  • Most other values mean a power change went wrong in Windows or a driver. 0x613, for example, means a driver tried to finish a request that Windows wasn't waiting on. Go to fix 2.

Timing helps too. In owners' reports, laptops that crashed within minutes of every startup after a Windows upgrade led back to the AMD graphics driver again and again.

1. Make the hibernation file bigger (first value 0xB)

The hibernation file, hiberfil.sys, holds a copy of your memory while the PC hibernates. When what's in memory doesn't fit, Windows crashes with this code. One command resizes it.

Right-click Start and choose Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) on Windows 10. Approve the prompt, then run:

powercfg /hibernate /size 100

That sets the file to 100 percent of your installed memory, and the same command turns hibernation on if it was off.

Restart, then run shutdown /h once to test it. The PC should hibernate, then resume cleanly when you press the power button.

If the file was already at 100 percent, size isn't your problem. One owner whose PC was set that way from the start deleted and recreated the file and still crashed on every hibernate, so move on to the driver in fix 2.

If you never use hibernation, powercfg /hibernate off avoids the crash by turning the feature off. Fast Startup goes with it, because it starts Windows from that same file.

2. Roll back, replace or disable the graphics driver

This is the fix owners confirmed most often. Most of their laptops paired an Intel chip with an AMD Radeon (the R9 M200X, R9 M265X and HD 7600M all came up), and the crashes started with a Windows upgrade.

If the PC crashes before you can do anything, start it in Safe Mode, which loads only basic drivers. On the sign-in screen, select Power, hold Shift and select Restart.

On the recovery screen, choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 when the list of startup options appears.

Right-click Start, open Device Manager and expand Display adapters. On a two-chip laptop, right-click the AMD entry and leave the Intel one alone.

Choose Properties > Driver > Roll Back Driver, pick a reason, confirm and restart.

Drawing of Device Manager with Display adapters expanded, showing an Intel and an AMD Radeon entry and the right-click menu with Update driver, Disable device, Uninstall device and Properties

Rolling back makes sense when a driver update started the crashes. The Device Manager driver steps need an administrator account. If the button is gray, Windows didn't keep an older driver.

In that case, download the newest graphics driver listed under your laptop's model number on the maker's website. I'd take the maker's driver over a generic one on these two-chip laptops.

One owner with a Toshiba P70-B got rid of the crash by updating the AMD graphics and Intel Wi-Fi drivers from Device Manager in Safe Mode.

As a stopgap, right-click the AMD entry and choose Disable device. Several owners stopped the crashes that way. Games and video then run on the slower Intel chip until you install a working AMD driver.

Don't just uninstall the AMD driver. Windows Update put the same one back for owners who tried, and the crashes returned. One of them put it this way: "This worked, until window updates put the problem drivers back."

3. Check the drive, then the other drivers

A first value of 0x108, 0x10A or 0x10E means the drive itself failed while handling the hibernation file. Copy off anything you can't lose before you do anything else.

Then run powercfg /hibernate off so Windows stops using that file, and have the drive tested with its maker's tool or by a repair shop.

For any other value, work through Microsoft's blue screen checklist. Remove hardware you added just before the crashes began, update any device that shows a warning mark in Device Manager, and install any Windows updates that are waiting.

A value like 0x613 points to a misbehaving driver. After the graphics driver, get the current chipset driver (the one for the motherboard's own chips) from your PC or motherboard maker's support page.

If the crashes keep coming

Each crash like this saves a memory dump (a snapshot of memory at the moment of the crash), usually C:\Windows\MEMORY.DMP. A repair shop or your PC maker's support team can open it in a debugger and read off the exact driver behind it.

If the crashes started with a Windows upgrade and you have a restore point from before it, System Restore rolls back the drivers that came with the upgrade.

On a laptop still under warranty, give the maker the stop code, the first value and the model, and ask for a driver that matches your Windows version.

As a last resort, Reset this PC in Settings > System > Recovery (Update & Security > Recovery on Windows 10) reinstalls Windows. It can keep your personal files, but it removes your apps, so plan on installing them again.

The Short Version

Find the BugCheck entry in Event Viewer and read the first value after 0x000000a0. For 0xB, run powercfg /hibernate /size 100.

For most other values, roll back, replace or disable the AMD graphics driver. For 0x108, 0x10A or 0x10E, back up your files and get the drive tested.

Checked November 19, 2026.

If you have any business, I can build it online

Hi, I’m Hamza. I’ve been building websites and online shops for business owners since 2019, and I also built this site you’re reading.

Tell me what business you have or what you’re working on. I’ll look into how much it can grow online, and then we talk. You don’t have to buy anything or hire me first.

Chat with me on my site and I’ll show you proof of businesses I’ve helped and how they’ve grown.

Written by Isaac Smith

Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.

More from Isaac Smith

Leave a Comment