Fix ACPI_BIOS_ERROR (0x000000A5) in Windows 11

ACPI_BIOS_ERROR, or stop code 0x000000A5, means the firmware on your motherboard is not fully compliant with the Advanced Configuration and Power Interface specification, so Windows cannot manage power and hardware configuration the way it expects. This stop code is unusual: it very often is not a Windows fault or even a driver fault, but a firmware one.

That changes the repair strategy. This guide explains what ACPI does, how parameter 1 narrows the problem down, and why the fixes centre on firmware versions and firmware settings rather than on Windows itself.

PAGE CONTENT

• What ACPI Does and What 0xA5 Means
• Read Parameter 1 to See What Is Missing
• Fix 1: Update or Roll Back the Firmware
• Fix 2: Reset the Firmware Settings That Changed
• Fix 3: If the Error Appears in a Virtual Machine
• Fix 4: Rule Out a Failing CMOS Battery
• Fix 5: Windows-Side Checks Worth Doing
• FAQs About ACPI_BIOS_ERROR
• Back Up and Restore Windows with Qiling Disk Master

What ACPI Does and What 0xA5 Means

ACPI is the standard that lets the operating system control power management and discover how hardware is wired together. Instead of guessing, Windows asks the firmware for a set of tables that describe the machine: which devices exist, how interrupts are routed, how to put the system to sleep, and how to power it off cleanly.

This stop code means those tables are wrong, incomplete, or internally inconsistent. Because Windows depends on them for basic device management, it cannot continue safely once it detects the problem.

Microsoft describes the condition as the computer's ACPI firmware not being fully compliant with the specification. The triggers are narrower than they first appear:

• A firmware update, or a rollback, that introduced or restored a faulty table
• Firmware settings changed in a way the existing firmware release does not handle correctly, such as enabling Secure Boot, a TPM, or virtualization-based security
• A virtual machine whose firmware type does not match the guest, or a hypervisor with an incomplete ACPI implementation
• An older or low-cost motherboard whose firmware was never fully compliant
• A nearly dead CMOS battery, which lets firmware settings drift or reset unpredictably

Read Parameter 1 to See What Is Missing

Parameter 1 identifies the type of incompatibility, and the meaning of the other parameters depends on its value. When the problem relates to plug and play or power management, the values describe a specific missing resource:

• 0x01 — ACPI cannot find the system control interrupt vector in the resources it was given when ACPI started. The second parameter is the ACPI device extension, the third is the ACPI resource list, and the fourth tells you whether no resource list was found at all or whether the list simply contained no interrupt resource.
• 0x02 and higher — these describe other specific table or method problems, such as a device description that contradicts the hardware or a control method that fails when Windows evaluates it.

In practice, whichever value you see, the conclusion is similar. A missing interrupt resource or a contradictory device description is something you cannot rewrite from inside Windows; it comes from the firmware, so the repair is to change the firmware or the settings that feed it.

Fix 1: Update or Roll Back the Firmware

Step 1. Identify the exact model of your motherboard or computer from the system information screen, then visit the maker's support page and compare the installed firmware version with the newest one published.

Step 2. If a newer release exists, install it. Firmware updates frequently correct table problems, memory initialisation bugs, and device description errors, and an ACPI compliance fault is exactly the kind of thing a later release fixes.

Step 3. If the stop code began immediately after a firmware update, install the previous version instead. Most makers keep older releases available for this reason, and a regression is a common story with this stop code.

Step 4. Follow the maker's instructions precisely while updating. Never interrupt the process, and connect a laptop to mains power first, because an interrupted firmware write can leave the board unusable.

Fix 2: Reset the Firmware Settings That Changed

Step 1. Enter BIOS or UEFI setup and load the optimised or default settings. This clears any saved profile that may be feeding the firmware inconsistent data.

Step 2. Test the machine with those defaults. If it starts normally, you have confirmed that a setting rather than the hardware is responsible.

Step 3. Re-apply your required settings one at a time, restarting after each one. Secure Boot, the TPM, virtualization support, and memory profiles are the ones most likely to interact with the ACPI tables.

Step 4. If you need Secure Boot and the certificate work that goes with it, do that deliberately rather than as part of a batch of changes, so you can tell which step caused a new fault. Our guide on the Secure Boot certificate expiry covers the current certificate situation.

Fix 3: If the Error Appears in a Virtual Machine

Step 1. Confirm that the virtual machine's firmware type matches the guest. A virtual machine configured as a legacy BIOS guest while the operating system expects UEFI, or the reverse, is a frequent source of this stop code.

Step 2. Update the hypervisor to its current release. Virtualization products implement their own ACPI tables, and older builds contain known gaps that later versions correct.

Step 3. Set the guest operating system type correctly in the virtual machine's settings. The host software uses that value to decide which virtual hardware, and which tables, to present.

Step 4. If the host already runs Windows with virtualization-based security, review that configuration too, since a nested hypervisor can conflict with the guest. Our guide on HYPERVISOR_ERROR covers the settings involved.

Fix 4: Rule Out a Failing CMOS Battery

Step 1. Check whether the clock is wrong on every boot, or whether firmware settings revert on their own. Both point at the small battery that keeps those settings alive when the machine is unplugged.

Step 2. Replace the battery on a desktop if the machine is several years old. It is inexpensive, and a drifting battery can present firmware with inconsistent configuration data, which is exactly what this stop code reports.

Step 3. On most laptops the equivalent battery is a serviceable part but may require opening the chassis. If the machine is under warranty, use the maker's service rather than opening it yourself.

Fix 5: Windows-Side Checks Worth Doing

Step 1. Repair the system files to exclude corrupted components from the picture. Open Command Prompt as administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Step 2. Install all pending Windows updates, including optional driver updates. Windows updates sometimes carry workarounds for known firmware behaviour, so they are worth having even though they cannot rewrite the tables themselves.

Step 3. Remove third-party power management and overclocking utilities. These tools write to the same power and configuration settings that ACPI manages, and a tool built for a different chipset can produce conflicting instructions.

Step 4. Record the firmware version and the settings you changed. If the stop code returns, that record is what tells you whether it tracks a particular configuration or appears regardless of it.

FAQs About ACPI_BIOS_ERROR

Is 0x000000A5 caused by Windows?

Usually not. The stop code reports that the firmware tables Windows received are not compliant. Windows is the messenger, which is why a reinstall rarely helps.

It appeared right after I updated the BIOS. What now?

Install the previous firmware version and load the optimised defaults. If the machine is stable again, wait for a later release before updating once more, and read the release notes for ACPI or power related fixes.

Can I fix it without a firmware update?

Sometimes. Loading the optimised defaults and removing the setting that was recently changed is often enough. If it happens in a virtual machine, updating the hypervisor and correcting the firmware type usually resolves it.

Does this mean my motherboard is failing?

Not necessarily. A non-compliant table is a firmware fault rather than a hardware failure, and an older board may never have been fully compliant. A failing CMOS battery is the main hardware cause worth checking.

Will a Windows reset or clean install help?

Rarely. The tables come from the motherboard before Windows starts, so a clean installation receives the same data and reports the same error.

Why does it only happen on one of my machines?

Because firmware is per-machine. Even two boards of the same model can ship with different firmware releases, and only one of them may contain the faulty table.

Back Up and Restore Windows with Qiling Disk Master

Firmware updates and low-level setting changes can leave a machine that will not start, and recovering from that is far easier with an image than with a repair attempt. Create a full system backup before you begin. Qiling Disk Master handles both the backup and the restore.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the changes began.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created, with your files and programs intact.

Conclusion

ACPI_BIOS_ERROR means the firmware tables your motherboard hands to Windows are not fully compliant with the ACPI specification, so Windows cannot manage power and hardware configuration reliably. Parameter 1 names the specific gap, such as a missing system control interrupt vector, but the answer almost always lies in the firmware rather than in Windows. Update the firmware if a newer release exists, or roll back if the fault began right after an update, then load the optimised defaults and re-apply your settings one at a time. On a virtual machine, check the firmware type and update the hypervisor, and on an older desktop, consider the CMOS battery.

Protect your PC with Qiling Backup—create a system image before your next troubleshooting step.

Related Articles

• Computer Keeps Booting to BIOS: Why It Happens and How to Fix It
  A frequent companion problem. If firmware settings will not persist, this guide walks through the causes in the same order.
• How to Enter BIOS or UEFI Setup on Any PC
• How to Repair the EFI Bootloader in Windows 11
• Windows 11 Secure Boot Certificate Expired in 2026 (Fix)
  Firmware settings and certificates interact with the ACPI tables. Make these changes deliberately, one at a time.
• Fix HYPERVISOR_ERROR (0x00020001) in Windows 11