KERNEL_MODE_HEAP_CORRUPTION (0x0000013A): Windows Blue Screen Fix

Quick answer

The Windows stop code KERNEL_MODE_HEAP_CORRUPTION (0x0000013A) means: Windows detected corruption in kernel-mode memory (the heap). If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

Before you start: note the stop code shown on the blue screen. If Windows will not start normally, it usually opens Automatic Repair after two failed starts; from there choose Advanced options to reach Safe Mode or System Restore.

Is it serious? Can I keep using my PC?

Severity: Medium

If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

Common causes

Faulty, outdated or incompatible driver
Conflict with antivirus, VPN or system utility software
Graphics card driver problem

How to fix it

Restart the PC. If the blue screen happened only once and does not return, no further action is usually needed
Find the faulting driver: check Event Viewer and the dump files in C:\Windows\Minidump
Update or roll back the driver of the faulting device in Device Manager (look for yellow warning icons)
Install the latest Windows updates
Clean-install the latest graphics driver from the GPU maker (NVIDIA, AMD or Intel)
Uninstall recently installed programs, especially antivirus, VPN or system tools

Frequently asked questions

What does KERNEL_MODE_HEAP_CORRUPTION mean?

The Windows stop code KERNEL_MODE_HEAP_CORRUPTION (0x0000013A) means: Windows detected corruption in kernel-mode memory (the heap).

Is KERNEL_MODE_HEAP_CORRUPTION serious?

Severity: Medium. If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

How do I fix KERNEL_MODE_HEAP_CORRUPTION?

Start with these steps: Restart the PC. If the blue screen happened only once and does not return, no further action is usually needed; Find the faulting driver: check Event Viewer and the dump files in C:\Windows\Minidump; Update or roll back the driver of the faulting device in Device Manager (look for yellow warning icons); Install the latest Windows updates; Clean-install the latest graphics driver from the GPU maker (NVIDIA, AMD or Intel).

Related codes

0x3B SYSTEM_SERVICE_EXCEPTIONAn error occurred while a system service was running, often caused by a driver (frequently graphics) or security software.0xA IRQL_NOT_LESS_OR_EQUALA driver or system process tried to access memory it was not allowed to use, usually because of a faulty driver.0x1E KMODE_EXCEPTION_NOT_HANDLEDA program running in the Windows kernel caused an error that it did not handle.0x3F NO_MORE_SYSTEM_PTESWindows ran out of system page table entries, usually because a driver is not releasing memory.0x50 PAGE_FAULT_IN_NONPAGED_AREAWindows tried to use memory that does not exist or is not available, often due to a driver, security software or faulty RAM.0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDA system thread caused an error that was not handled, usually because of a driver.0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORYA driver tried to write to read-only memory.0xC2 BAD_POOL_CALLERA driver or program made an invalid memory request.0xC5 DRIVER_CORRUPTED_EXPOOLA driver corrupted the system memory pool.