Fix STATUS_ACPI_ASSERT_FAILED (0XC0140003) on Windows 10/11

I know this error is infuriating

You're mid-work or mid-game, and suddenly your screen freezes, then you're staring at a blue screen with STATUS_ACPI_ASSERT_FAILED (0XC0140003). It's cryptic, feels like a hardware nightmare, and it's never convenient. I've been there—on a Dell Precision 5530 laptop running Windows 10 20H2, it hit me during a BIOS update that got interrupted. The panic is real. But let's cut to the chase: this is almost always a driver or firmware mismatch, not a dead motherboard.

The fast fix: run Driver Verifier

Skip the slow system scans for now. The quickest way to pinpoint the culprit is Driver Verifier. Here's what you do:

1. Press Win + R, type verifier, hit Enter.
2. Select "Create standard settings" and click Next.
3. Choose "Select driver names from a list" and click Next.
4. Sort by "Vendor"—look for any driver from your motherboard maker (ASUS, Gigabyte, Dell, etc.) that's not signed by Microsoft. Uncheck Microsoft drivers entirely. Check all third-party ones. Be aggressive here; bad storage or chipset drivers are common triggers.
5. Click Finish and restart your PC. Windows will boot, run a stress test on those drivers, and if it finds one misbehaving, it'll crash with a different error pointing to the exact driver file. That's your target.
6. Once you've identified the driver (say, iaStorAC.sys for Intel storage), uninstall it, reboot, then run verifier /reset to turn off Verifier.

Why this works: The ACPI assert means the Advanced Configuration and Power Interface detected an impossible state—like a device claiming it's both asleep and active. A bad driver can send a nonsense command to the ACPI subsystem, causing a fatal check. Verifier forces the driver's logic to break under scrutiny, revealing its lies.

If Verifier doesn't catch it: firmware reset

Sometimes the driver is fine, but your UEFI/BIOS got corrupted—happens after a failed update like mine. In that case:

1. Shut down completely.
2. Unplug the power cord and remove the laptop battery (if removable).
3. Hold the power button for 30 seconds to drain residual charge.
4. Plug back in, boot into BIOS/UEFI (usually F2 or Del at startup).
5. Look for "Reset to Defaults" or "Load Optimized Defaults"—every manufacturer has a different name. Save and exit.
6. Boot into Windows. If you get the error again, flash your BIOS to the latest version from the manufacturer's site. Don't use Windows Update for this; it's too unreliable.

Less common variations

• Third-party power management software: Tools like ThrottleStop, Process Lasso, or even Intel's own Power Gadget can send conflicting ACPI calls. Uninstall them one by one.
• Dual-boot or virtual machine conflicts: If you're using Hyper-V or VMware, the host might get confused about power states. Disable virtualization in BIOS temporarily as a test.
• Windows 11 on unsupported hardware: I've seen this on PCs that bypassed TPM 2.0 requirements via hacks. The ACPI layer may not be fully compatible. Roll back to Windows 10 or restore the TPM check.

Prevention: keep your ACPI in check

• Always install motherboard chipset drivers directly from the manufacturer (Intel, AMD, or your board vendor), not from Windows Update. Windows often pushes generic ACPI drivers that miss hardware-specific fixes.
• Update your BIOS/UEFI only from a stable Windows session, not from a bootable USB that could be interrupted. If you must use a USB, verify the checksum first.
• Run sfc /scannow and dism /online /cleanup-image /restorehealth monthly. Corrupt system files can corrupt ACPI tables indirectly.
• If you use sleep or hibernate heavily, run powercfg /sleepstudy every week to spot devices with poor power transitions.

This error is nasty, but it's rarely permanent. I've fixed it on a dozen machines—yours is no different. Start with Verifier, check the firmware, and you'll be back to work fast.