Windows BSOD 0x0000011A — EM_CHECK_FAILED — What It Means & How to Fix It

What Does This Error Mean?

Windows BSOD 0x0000011A — also called EM_CHECK_FAILED — means a hardware or firmware check for Execution Mode consistency failed. This indicates that the processor or a system component is behaving in an unexpected way that violates Windows' fundamental expectations about how the CPU operates. This is a serious low-level error often related to CPU issues, firmware inconsistencies, or deep system corruption. It is less common than most BSODs and usually points to hardware or firmware problems.

Affected Models

Windows 10 version 1903 and newer
Windows 11 all versions
Systems with recent Intel or AMD processors
Systems after a BIOS/UEFI firmware update
Virtualized environments on Hyper-V or VMware

Common Causes

BIOS or UEFI firmware is outdated or has a bug that creates CPU execution mode inconsistencies
A recent BIOS update changed processor settings in a way that conflicts with Windows
CPU virtualization extensions (Hyper-V, Intel VT-x, AMD-V) are misconfigured
Hardware issue with the CPU or motherboard causing mode-check failures
Corrupted Windows system files affecting core kernel execution verification

How to Fix It

Check your BIOS/UEFI version and look for updates from your motherboard manufacturer. Go to the manufacturer's website, find your motherboard model, and download the latest BIOS firmware. Follow the update instructions carefully.

BIOS updates fix bugs in CPU initialization and execution mode setup. An outdated BIOS is a common trigger for 0x0000011A on newer processors.
Run System File Checker. Open Command Prompt as Administrator and type: sfc /scannow and press Enter. Let it complete. Then run: DISM /Online /Cleanup-Image /RestoreHealth for deeper repair.

Corrupted Windows system files that affect kernel execution can trigger EM_CHECK_FAILED. SFC and DISM replace corrupted files with verified copies.
Check virtualization settings in BIOS. If you use Hyper-V or another hypervisor, ensure that Intel VT-x or AMD-V is enabled in BIOS. Mismatched virtualization settings cause execution mode conflicts.

Enter BIOS on startup (usually by pressing Del, F2, or F12). Look under CPU settings for virtualization options.
If a BIOS update was recently installed and 0x0000011A began appearing afterward, consider rolling back the BIOS to the previous stable version if your motherboard supports it.

Some BIOS updates introduce bugs that affect CPU mode handling. Your motherboard's BIOS update history notes will indicate if other users have reported similar issues.
Run Windows Startup Repair. Boot from a Windows installation USB, select Repair your computer, and choose Startup Repair. This fixes boot-critical file inconsistencies that can cause this BSOD.

A Windows installation USB can be created using Microsoft's Media Creation Tool, available for free at microsoft.com.

When to Call a Professional

0x0000011A is a complex error that often requires technical diagnosis. If BIOS updates and system file repairs do not resolve it, the motherboard or CPU may need professional testing. A computer repair shop can run diagnostics and test components. Expect $75 to $150 for diagnosis.

Frequently Asked Questions

Is 0x0000011A related to virtualization software like VMware or VirtualBox?

It can be. Virtualization software modifies how the CPU handles execution modes. Conflicts between Hyper-V, VMware, VirtualBox, and Windows security features like VBS (Virtualization Based Security) can trigger 0x0000011A. Disabling Hyper-V temporarily and testing is a useful diagnostic step.

Could overclocking the CPU cause 0x0000011A?

Yes. An overclocked CPU that is not fully stable can cause execution mode check failures. Return the CPU to default clock speeds in BIOS and test for stability. If the BSOD stops after removing the overclock, the CPU was unstable at that clock speed.

How do I read the BSOD dump file to get more information about 0x0000011A?

Windows saves crash dump files in C:\Windows\Minidump. You can open these files with WinDbg Preview (free from the Microsoft Store) or a third-party tool like WhoCrashed. The dump file contains the exact call stack and module that caused the failure, which helps identify the root cause.