Fix ACPI Error 0XC0140014: Subsystem Not Initialized

That ACPI 0XC0140014 error is annoying — pops up right at boot or when your laptop tries to sleep, and it makes no sense. Let's cut through the noise and get it fixed.

The Quick Fix: Reinstall the ACPI Driver

This error shows up because Windows loaded a stale or corrupted ACPI driver. The fix is to force a clean reinstall. Here's exactly what to do:

Press Windows Key + X and select Device Manager.
Expand the System devices category. You'll see a long list — look for Microsoft ACPI-Compliant System. There might be more than one entry. You want the one with the yellow exclamation mark or the one that's grayed out. Sometimes there's no warning icon at all — just right-click each one until you find the one that shows 'This device is not working properly' in its Properties.
Right-click that entry and choose Uninstall device.
A warning pops up: 'Are you sure you want to uninstall this device?' Check the box that says Delete the driver software for this device. This is important — if you skip this, Windows will just reinstall the same broken driver.
Click Uninstall. Wait for it to finish — you'll see the device disappear from the list.
Now restart your computer. Don't skip this step — a reboot is mandatory here.

After the restart, Windows will automatically detect the missing ACPI device and install a fresh copy of the driver. You should see the error stop appearing. If it doesn't, proceed to the next step.

If That Didn't Work: Run the System File Checker

Sometimes the ACPI.sys file itself gets corrupted. This file is a core Windows system file, so you can't just download a replacement. Instead, run the built-in repair tool:

Open Command Prompt as administrator. Hit Windows Key + X, then choose Windows Terminal (Admin) or Command Prompt (Admin), depending on your Windows version.
Type this command and press Enter:
```
sfc /scannow
```
Wait for the scan to finish. It takes about 15 minutes on most machines. You'll see a progress bar — let it run.
When it's done, it'll tell you either 'Windows Resource Protection did not find any integrity violations' or 'Found corrupt files and successfully repaired them.' If it found and fixed files, restart your PC.

I've seen this fix work on Windows 11 version 22H2 and 23H2, and on Windows 10 21H2 as well. If the SFC scan finds nothing, move to the next fix.

Still Seeing the Error? Check Your BIOS Settings

This error can sometimes be triggered by a BIOS setting that's out of whack — especially if you've recently updated your motherboard firmware or swapped out RAM. Here's what to look for:

Restart your PC and enter BIOS/UEFI setup. This is usually done by pressing F2, Del, or F10 right after you turn the machine on. Look at the screen during boot — it'll say 'Press [key] to enter setup'.
Find the Power Management or ACPI section. On Dell machines, it's under 'Power Management Setup'. On ASUS boards, look for 'ACPI Settings'.
Look for a setting called ACPI 3.0 Support or ACPI 5.0 Support. Set this to Enabled. If it's already enabled, disable it and see if the error goes away. I've seen both directions work depending on the hardware.
Also check Wake on LAN and Wake on USB — disable both temporarily. These can cause initialization conflicts with the ACPI subsystem.
Save changes and exit. Reboot normally.

If you're on a laptop, also check for a BIOS setting called Power On By PCIe — turn that off. Lenovo ThinkPads from 2020 onward (X1 Carbon Gen 8, T14 Gen 1) are notorious for this error with PCIe wake enabled.

Why This Error Happens

The error code 0XC0140014 translates to STATUS_NOT_INITIALIZED. The ACPI subsystem in Windows is responsible for power management — handling sleep states, wake events, and device power-on sequences. When Windows boots, it tries to initialize the ACPI driver (acpi.sys). If that driver loads with corrupted registry data, or if the BIOS reports a device state that Windows can't understand, the subsystem fails to start.

This shows up most often after a Windows update that changes power policies, after a BIOS update that changes ACPI tables, or after installing a new driver for a PCIe device (like a graphics card or NVMe SSD). The real trigger is mismatched power state information — Windows thinks the subsystem is already running when it's not, or vice versa.

Less Common Variations

I've seen this error appear in a few other scenarios:

On dual-boot systems: If you're running Windows alongside Linux, the ACPI tables can get confused after a kernel update. The fix is to disable Fast Startup in Windows: go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > uncheck 'Turn on fast startup'. Reboot.
After a major Windows version upgrade: Going from Windows 10 to 11, or from 11 22H2 to 23H2, can leave stale ACPI driver cache. Run dism /online /cleanup-image /restorehealth from admin command prompt, then run SFC again.
On virtual machines: If you're running a VM in Hyper-V or VMware, the ACPI error often means the VM's firmware doesn't match the host. Set the VM to use UEFI instead of BIOS, or vice versa — try both.
With third-party power management software: Tools like ThrottleStop, QuickCPU, or ASUS Armoury Crate can interfere with ACPI initialization. Uninstall them temporarily and see if the error stops.

Preventing It From Coming Back

Once you've fixed it, do these three things to stop it from returning:

Keep Windows updated. Microsoft has patched ACPI-related bugs in cumulative updates — especially KB5032190 and KB5032281 for Windows 11. Go to Settings > Windows Update and make sure you're on the latest build.
Stick with stable BIOS versions. Don't install beta BIOS updates. Stick to the 'Recommended' or 'Stable' versions from your motherboard vendor. Beta BIOSes sometimes introduce ACPI table changes that break Windows.
Don't mix power plans manually. If you've tweaked your power plan settings (like disabling sleep or changing PCIe power management), revert to the Balanced plan. Custom power plans are the number one cause of ACPI state mismatches.

If you've gone through all these steps and the error still appears, you might have a hardware issue — specifically a failing CMOS battery on older desktops (motherboards from 2015-2018 are common culprits). Replace the CR2032 battery on the motherboard. That forces the BIOS to reset its ACPI tables on next boot, and it often clears this error for good.