0XC0140011

BSOD 0xC0140011: ACPI invalid access size fix

You get this BSOD when a driver or system component tries to read/write an ACPI field with the wrong byte size. It's almost always a bad BIOS or a faulty driver.

When you see this error

You're working normally — maybe browsing, maybe compiling code — then the screen freezes and you get a blue screen with STATUS_ACPI_INVALID_ACCESS_SIZE and the stop code 0xC0140011. It often happens on wake-from-sleep or during a driver install that touches power management. I've seen it most on recent Ryzen systems (5000/7000 series) with certain NVMe drives or newer Thunderbolt docks.

What's actually happening here

The ACPI (Advanced Configuration and Power Interface) defines fields in system memory — things like temperature sensors, fan speed controls, battery status. Each field has an expected size: 1 byte, 2 bytes, 4 bytes, etc. When a driver or the kernel tries to read 8 bytes from a field that's only 4 bytes wide, the ACPI interpreter throws 0xC0140011. The core issue is a mismatch between what the driver expects and what the BIOS defined in the DSDT/SSDT tables.

This isn't a random hardware failure. It's a logic bug — either in a third-party driver that's making assumptions about ACPI field sizes, or in the BIOS itself if the tables are malformed. Windows doesn't recover from this because it's an integrity check: letting a driver read past the field boundary could cause memory corruption or give it fake data.

The fix — step by step

  1. Update your BIOS/UEFI firmware. This is the most common fix. BIOS vendors fix ACPI table bugs in newer revisions. Check your motherboard manufacturer's site — ASUS, Gigabyte, MSI, ASRock — download the latest non-beta BIOS. Flash it from the UEFI menu (or use USB Flashback if available). After updating, let the system boot normally once, then restart again for good measure.
  2. Update chipset drivers. Go to AMD or Intel's official chipset driver page — not the motherboard vendor's page. They often have older versions. Download and install the latest chipset driver. This replaces the ACPI-compatible drivers that talk to the hardware. For AMD systems, the chipset driver package from amd.com includes the GPIO and I2C drivers that fix ACPI access issues on sleep/wake.
  3. Disable Fast Startup. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > uncheck "Turn on fast startup." Fast Startup is a hybrid shutdown that hibernates the kernel session, and on systems with buggy ACPI, the resume path triggers the invalid access. I've fixed multiple 0xC0140011 BSODs on Ryzen laptops by just disabling this.
  4. Run a memory test. Open Windows Memory Diagnostic (mdsched.exe from the Run dialog). Let it run extended mode overnight. If it reports errors, you have a hardware memory issue that can manifest as ACPI access failures because the data read from the ACPI region gets corrupted in cache or between the memory controller and CPU. Replace the faulty stick.
  5. Check event logs for the culprit driver. Boot to Safe Mode (hold Shift while clicking Restart, then choose Troubleshoot > Advanced Options > Startup Settings > Enable Safe Mode). Once in Safe Mode, open Event Viewer > Windows Logs > System. Filter by Event ID 1 (BugCheck). Find the 0xC0140011 bug check and look at the parameters — they often show the driver that triggered it. Common offenders: acpi.sys, intelppm.sys, amdfendrv.sys, or a third-party battery/thermal driver.
  6. Use Driver Verifier (advanced). If you still can't pin it down, run verifier.exe from an admin command prompt. Select "Create custom settings" > "Select individual settings" > check everything except "Force IRQL checking" (that one floods false positives for ACPI). Then choose "Select driver names from a list" and pick acpi.sys, pci.sys, and any third-party drivers you suspect. Reboot and reproduce the crash. Verifier will break into a WinDbg session showing exactly which driver made the illegal ACPI access. Only do this if you're comfortable with kernel debugging — Verifier can make your system unresponsive if the driver is truly broken.

If it still fails after all this

You have a hardware defect — maybe a failing ACPI controller on the motherboard, or a BIOS that can't be fixed. Try swapping out devices one by one: unplug all USB devices except keyboard/mouse, remove expansion cards (WiFi, sound, capture cards), test with only one RAM stick in slot A2. On laptops, try running with the battery removed and only the AC adapter. If the error goes away, that last device you removed was causing the ACPI access size error through its driver. Replace that device, not the whole system.

If you've done all that and it still happens, consider flashing an older BIOS version — sometimes a new BIOS introduces ACPI bugs. Check your motherboard vendor's forums for known issues with the specific error code. I've seen cases where rolling back to a 2021-era BIOS fixed 0xC0140011 on Asus X570 boards that newer updates had broken.

Pro tip: Before you do anything else, note the exact timestamp of the crash from the Event Log. Then check if that timestamp lines up with a specific USB device being plugged in or a power state transition. That narrows the search from "everything" to "exactly when it happens."
Related Errors in Windows Errors
0XC00D104B NS_E_WMG_PLUGINUNAVAILABLE (0XC00D104B) fix 0XC0000121 STATUS_CANNOT_DELETE (0XC0000121) – File Won’t Delete 0XC00D14B5 Fix NS_E_EMPTY_PLAYLIST (0XC00D14B5) on Windows Media Player 0XC00D1BB5 NS_E_MULTIPLE_VBR_AUDIENCES (0XC00D1BB5) fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.