KERNEL_MODE_HEAP_CORRUPTION is a Windows Blue Screen of Death (BSOD) error that normally uses the bug check value:

0x0000013A

or simply:

0x13A

Microsoft defines bug check 0x13A as a condition in which the kernel-mode heap manager detects corruption in a heap.

In simple terms, Windows detected that memory being used by the operating-system kernel or a kernel-mode component no longer contained the data or structure Windows expected.

Because kernel-mode components operate with very high privileges, Windows cannot safely continue once this type of corruption is detected. It therefore stops the system and displays a blue screen to protect the operating system and data from further corruption.

The BSOD may display:

Stop code: KERNEL_MODE_HEAP_CORRUPTION

This problem is frequently associated with faulty or incompatible device drivers, although unstable RAM, overclocking, firmware problems, hardware faults and other low-level software can also contribute.

What Does "Heap Corruption" Mean?

Windows uses areas of memory called heaps for dynamic memory allocation.

Drivers and other kernel-mode components can request memory, use it and release it when it is no longer required.

Problems occur when software incorrectly handles this memory.

Examples include:

• Writing beyond the allocated memory area
• Reading or writing before an allocated buffer
• Accessing memory after it has already been freed
• Freeing the same allocation more than once
• Passing an invalid memory block to the heap manager
• Corrupting heap metadata
• Using an incorrect heap
• Supplying an invalid pointer
• Corrupting an adjacent memory block

Windows may not crash at the exact instant the corruption occurs.

A driver can corrupt memory first, and Windows may discover the damage later when another operation accesses or validates that heap. This is one reason the component appearing in a crash dump is not necessarily the component that originally caused the corruption.

KERNEL_MODE_HEAP_CORRUPTION Bug Check Parameters

Bug check 0x13A contains four parameters.

According to Microsoft's documentation:

Parameter 1: Type of heap corruption detected
Parameter 2: Address of the heap reporting the corruption
Parameter 3: Address where corruption was detected
Parameter 4: Reserved

Parameter 1 can provide particularly useful diagnostic information.

Some important values include:

Parameter 1	Meaning
0x3	Corrupt entry header detected
0x4	Multiple corrupt entry headers
0x5	Corrupt header in a large allocation
0x6	Corruption consistent with a buffer overrun
0x7	Corruption consistent with a buffer underrun
0x8	A free block was supplied to an operation intended for a busy block
0x9	Invalid argument supplied
0xA	Internal heap allocation error
0xB	Possible use-after-free condition
0xC	Wrong heap supplied
0xD	Corrupted free list
0xE	Heap list corruption
0xF	Illegal operation on a free block
0x10	Invalid heap state, potentially caused by a buffer overflow
0x11	Invalid heap state potentially related to double-free or heap corruption
0x12	Invalid state potentially related to use-after-free or adjacent buffer overflow
0x13	NULL heap handle
0x14	Requested allocation exceeds the current allocation limit
0x15	Commit request would exceed the current commit limit
0x16	Internal heap error potentially related to an invalid address or memory corruption
0x17	Corruption detected in a delay-free list

These values are especially useful when investigating a crash dump using WinDbg.

Common Symptoms

A computer experiencing KERNEL_MODE_HEAP_CORRUPTION may show one or more of the following symptoms:

• Sudden blue screen
• Automatic restart
• Crashes while gaming
• Crash when launching a graphics-intensive application
• BSOD during video rendering
• Crash after updating a GPU driver
• BSOD after installing Windows updates
• Random system freezes
• Black screen followed by restart
• Applications crashing before the BSOD
• Crashes when waking from sleep
• BSOD during shutdown or startup
• Crashes under heavy CPU or GPU load
• Repeated crashes after installing new hardware
• BSOD after enabling XMP/EXPO or overclocking

If the crash consistently occurs while performing the same activity, that pattern can help identify the problematic driver or hardware component.

Common Causes of KERNEL_MODE_HEAP_CORRUPTION

1. Faulty or Incompatible Device Drivers

Drivers are one of the first areas to investigate.

A kernel-mode driver that incorrectly accesses memory can corrupt the kernel heap.

Potentially involved drivers include:

• Graphics drivers
• Chipset drivers
• Storage/NVMe drivers
• Network adapters
• Wi-Fi drivers
• Bluetooth drivers
• USB drivers
• Audio drivers
• Printer drivers
• VPN drivers
• Virtualization drivers
• Security software drivers
• Hardware monitoring utilities

Pay particular attention to drivers that were installed or updated shortly before the BSOD started.

2. Graphics Driver Problems

Graphics drivers deserve special attention when the BSOD occurs during:

• Gaming
• Video editing
• 3D rendering
• GPU benchmarks
• Browser hardware acceleration
• Multiple-monitor use
• Sleep/resume
• Graphics-intensive applications

Systems containing NVIDIA, AMD or Intel GPUs should use drivers appropriate for their exact hardware and Windows version.

3. Faulty or Unstable RAM

Heap corruption can also result from actual memory errors.

Possible RAM-related causes include:

• Defective RAM
• Improperly seated memory modules
• Incompatible DIMMs
• Aggressive memory timings
• XMP/EXPO instability
• Memory-controller instability
• Overclocking
• Incorrect BIOS memory settings

This possibility becomes more significant when crashes occur with different stop codes or apparently unrelated drivers.

4. CPU, GPU or RAM Overclocking

An unstable overclock can cause memory corruption even if the computer appears stable during ordinary desktop use.

This includes:

• CPU overclocking
• GPU overclocking
• GPU undervolting
• RAM overclocking
• XMP
• EXPO
• Modified memory timings
• Automatic motherboard performance profiles

For troubleshooting, return the system to stock/default settings.

5. Corrupted Windows System Files

Damaged Windows components can contribute to instability.

Windows includes built-in tools such as:

• System File Checker (SFC)
• Deployment Image Servicing and Management (DISM)

These should be checked when BSODs began after failed updates, unexpected shutdowns, storage problems or system-file corruption.

6. BIOS or Firmware Problems

Outdated or unstable BIOS/UEFI firmware may cause compatibility problems involving:

• RAM
• CPU microcode
• PCIe devices
• Graphics cards
• NVMe SSDs
• Power management
• Sleep/resume

Check your computer or motherboard manufacturer's support page for BIOS and firmware updates.

Do not interrupt a BIOS update once it has started.

7. Third-Party Kernel-Level Software

Some applications install drivers that operate in kernel mode.

Examples include:

• Antivirus products
• Endpoint security software
• VPN software
• Virtual-machine software
• Hardware monitoring tools
• RGB control utilities
• Fan-control applications
• Motherboard tuning utilities
• Disk-management software
• Backup applications
• Anti-cheat systems

If the BSOD started immediately after installing one of these applications, temporarily removing it can be an important diagnostic step.

How to Fix KERNEL_MODE_HEAP_CORRUPTION

The following troubleshooting sequence is recommended because it starts with safer and more common fixes before moving to advanced diagnostics.

Step 1: Restart the Computer

If the BSOD occurred only once, restart Windows and monitor the system.

A single crash does not automatically mean that hardware has failed.

If the BSOD repeats, continue troubleshooting.

Step 2: Identify Recent Changes

Think about what changed immediately before the crashes started.

Examples:

• New graphics driver
• Windows update
• New RAM
• New GPU
• New SSD
• Antivirus installation
• VPN installation
• BIOS update
• Driver update
• New USB device
• New system-tuning software
• Overclocking changes

Reversing the most recent change can sometimes identify the cause quickly.

Step 3: Update Windows

Open:

Settings → Windows Update

Select:

Check for updates

Install applicable Windows updates and restart the computer.

Also check Advanced options → Optional updates when appropriate, but do not install every optional driver blindly when troubleshooting. Drivers from the PC, motherboard or component manufacturer may be preferable for certain hardware.

Step 4: Check Device Manager

Press:

Windows + X

Select:

Device Manager

Check for devices showing a warning symbol.

Pay particular attention to:

• Display adapters
• Storage controllers
• Network adapters
• Sound devices
• USB controllers
• System devices

Open the affected device's properties and examine its driver information and device status.

Step 5: Update the Graphics Driver

If crashes happen while gaming, rendering or playing video, investigate the graphics driver early.

Identify your GPU under:

Device Manager → Display adapters

Then obtain the appropriate driver from the computer manufacturer or GPU manufacturer.

After installation, restart Windows and test again.

Step 6: Roll Back a Recently Updated Driver

If KERNEL_MODE_HEAP_CORRUPTION started immediately after a driver update:

Open:

Device Manager

Right-click the affected device and select:

Properties → Driver → Roll Back Driver

If Roll Back Driver is unavailable, obtain and install the previously stable driver manually.

Step 7: Perform a Clean GPU Driver Installation

Simply installing a new graphics driver over an existing installation may not always remove problematic configuration or components.

For persistent graphics-related crashes:

1. Download the correct graphics driver.
2. Disconnect unnecessary peripherals.
3. Remove the existing graphics driver if appropriate.
4. Restart Windows.
5. Install the known-good driver.
6. Restart again.
7. Test system stability.

Avoid downloading drivers from random third-party driver websites.

Step 8: Run System File Checker

Open Command Prompt or Windows Terminal as Administrator.

Run:

sfc /scannow

Allow the scan to reach 100%.

SFC checks protected Windows system files and attempts to repair damaged copies.

Restart Windows after repairs are completed.

Step 9: Repair the Windows Component Store Using DISM

Open an elevated Command Prompt and run:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

again.

Restart Windows.

Step 10: Check the File System

You can initially perform an online scan using:

chkdsk C: /scan

If file-system errors requiring offline repair are found, an administrator may use an appropriate CHKDSK repair operation and restart the machine when prompted.

Always maintain a current backup before performing extensive disk troubleshooting, especially if storage failure is suspected.

Step 11: Test Windows Memory

Press:

Windows + R

Enter:

mdsched.exe

Choose:

Restart now and check for problems

Windows will restart and perform a memory test.

If errors are detected, investigate the RAM configuration.

Possible actions include:

• Reseat RAM
• Test individual modules
• Disable XMP/EXPO
• Restore default memory timings
• Test known-good RAM
• Replace a defective module

For intermittent memory problems, a longer dedicated memory test may provide better coverage than a short built-in diagnostic.

Step 12: Disable Overclocking

Enter BIOS/UEFI and restore CPU, GPU and RAM settings to manufacturer defaults.

Also temporarily disable:

• XMP
• EXPO
• Manual RAM timings
• CPU overclocking
• GPU overclocking
• Undervolting
• Performance-enhancement profiles

Then test the machine again.

If the BSOD disappears, instability rather than Windows itself may have been responsible.

Step 13: Perform a Clean Boot

A clean boot can help determine whether third-party services or startup software are contributing to the problem.

Press:

Windows + R

Type:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

Then disable the remaining non-Microsoft services for diagnostic testing.

Also disable unnecessary startup applications through Task Manager.

Restart the computer.

If the crashes stop, re-enable items systematically until the problematic software is identified.

Step 14: Check Minidump Files

Windows commonly stores small crash dumps in:

C:\Windows\Minidump

You may see files such as:

082926-12345-01.dmp

For repeated KERNEL_MODE_HEAP_CORRUPTION crashes, dump analysis is far more useful than repeatedly trying random fixes.

Step 15: Analyze the Crash with WinDbg

Microsoft WinDbg can analyze Windows crash dumps.

After opening the dump, a common starting command is:

!analyze -v

Microsoft specifically recommends the !analyze debugger extension for investigating bug check 0x13A. The !heap extension can also provide heap information useful to advanced debugging.

Look for information such as:

BUGCHECK_CODE
MODULE_NAME
IMAGE_NAME
FAILURE_BUCKET_ID
STACK_TEXT
PROCESS_NAME

Also examine the four 0x13A arguments.

For example:

KERNEL_MODE_HEAP_CORRUPTION (13a)

followed by:

Arg1
Arg2
Arg3
Arg4

Arg1 identifies the type of corruption Windows detected.

Important: ntoskrnl.exe May Not Be the Actual Cause

Users frequently analyze a BSOD and find references to:

ntoskrnl.exe

or other Windows kernel components.

This does not automatically mean the Windows kernel itself is defective.

The kernel may simply be the component that discovered the corrupted memory.

A third-party driver could have corrupted the memory earlier.

Therefore, do not replace Windows or blame ntoskrnl.exe solely because it appears in the stack.

Step 16: Use Driver Verifier – Advanced Users Only

Windows includes Driver Verifier, which can stress drivers and expose incorrect driver behavior.

Run:

verifier

However, Driver Verifier should be used carefully.

It intentionally places additional checks on drivers and can make a problematic machine crash more frequently. In some cases, it can contribute to a boot loop until it is disabled.

Before using it:

• Back up important data.
• Create a restore point or recovery plan.
• Know how to access Safe Mode or Windows Recovery.
• Prefer testing suspected third-party drivers rather than indiscriminately stressing everything.

If Driver Verifier causes startup problems, boot into Safe Mode or Windows Recovery Command Prompt and run:

verifier /reset

Then restart the computer.

Recent Microsoft guidance for 0x13A cases also recommends Driver Verifier as a way to expose a faulty kernel driver when an ordinary dump only shows generic heap corruption.

Step 17: Check BIOS and Firmware

Visit the official support page for your:

• Laptop
• Desktop
• Motherboard
• SSD
• GPU

Check for applicable:

• BIOS/UEFI updates
• Chipset drivers
• Intel ME/AMD chipset components
• Storage firmware
• Thunderbolt firmware
• Device firmware

Read the manufacturer's update instructions carefully before updating firmware.

Step 18: Remove Recently Installed Hardware

If the BSOD began after adding hardware such as:

• RAM
• GPU
• NVMe SSD
• PCIe card
• Wi-Fi adapter
• USB device

temporarily remove the new hardware where practical.

If stability returns, investigate compatibility, drivers, firmware, power requirements and the hardware itself.

Step 19: Check RAM Modules Individually

If multiple RAM modules are installed, advanced troubleshooting can involve testing one module at a time.

For example, with two DIMMs:

1. Shut down the computer.
2. Disconnect power.
3. Follow ESD precautions.
4. Remove one RAM module.
5. Test the system.
6. Swap modules.
7. Test again.

If crashes occur only with one particular module, that DIMM becomes a strong suspect.

If both modules work separately but fail together, investigate:

• Memory timings
• XMP/EXPO
• Motherboard compatibility
• Memory-controller stability
• BIOS configuration

Step 20: Check Temperatures and Power Stability

Heap corruption is primarily a memory/software symptom, but unstable hardware can produce apparently random memory corruption.

Check:

• CPU temperatures
• GPU temperatures
• Motherboard temperatures
• PSU stability
• GPU power connectors
• RAM seating
• Motherboard power connections

If crashes happen only under heavy gaming or rendering loads, hardware stability deserves additional investigation.

When KERNEL_MODE_HEAP_CORRUPTION Happens During Gaming

If the BSOD occurs primarily during gaming, prioritize:

1. GPU driver
2. GPU overclock/undervolt
3. RAM/XMP/EXPO stability
4. GPU temperature
5. PSU capacity/stability
6. Game anti-cheat drivers
7. Overlay and monitoring utilities
8. BIOS/chipset updates
9. Crash dump analysis

Do not assume that the game itself is necessarily defective.

A demanding game may simply expose an unstable driver or hardware condition that normal desktop use does not trigger.

When the Error Started After a Windows Update

If the BSOD began immediately after Windows Update:

1. Check whether Windows also installed a device driver.
2. Update drivers from the hardware manufacturer.
3. Roll back a recently changed driver where appropriate.
4. Install newer cumulative updates if Microsoft has released a fix.
5. Run DISM and SFC.
6. Review minidumps.
7. Remove the recent update only when there is strong evidence that it caused the problem and other remediation has failed.

When the Error Started After Installing a New GPU

Check:

• Correct GPU driver
• Old driver remnants
• PSU wattage
• PCIe power connections
• GPU seating
• BIOS compatibility
• Motherboard BIOS version
• GPU overclocking
• Resizable BAR-related configuration if applicable
• RAM stability

If possible, temporarily reinstall the previous GPU and compare stability.

Recommended Troubleshooting Order

For most users, this is an efficient sequence:

1. Restart Windows

↓

2. Check what changed before the problem started

↓

3. Update or roll back the suspected driver

↓

4. Pay special attention to the GPU driver

↓

5. Install Windows updates

↓

6. Run SFC and DISM

↓

7. Test RAM

↓

8. Disable overclocking/XMP/EXPO

↓

9. Perform a clean boot

↓

10. Update BIOS/chipset/firmware where appropriate

↓

11. Analyze minidumps with WinDbg

↓

12. Use Driver Verifier only if deeper driver diagnosis is required

↓

13. Investigate hardware if software troubleshooting does not identify the problem

Commands Quick Reference

Check Windows system files

sfc /scannow

Scan Windows component store

DISM /Online /Cleanup-Image /ScanHealth

Repair Windows component store

DISM /Online /Cleanup-Image /RestoreHealth

Online file-system scan

chkdsk C: /scan

Open Windows Memory Diagnostic

mdsched.exe

Open Driver Verifier

verifier

Disable Driver Verifier

verifier /reset

Basic WinDbg crash analysis

!analyze -v

Prevention Tips

To reduce the possibility of future KERNEL_MODE_HEAP_CORRUPTION errors:

• Keep Windows updated.
• Use drivers from reputable hardware manufacturers.
• Avoid random third-party driver-update utilities.
• Keep graphics and chipset drivers stable and current.
• Avoid unnecessary kernel-level tuning software.
• Do not aggressively overclock RAM, CPU or GPU.
• Test XMP/EXPO configurations for stability.
• Keep BIOS/UEFI reasonably current when updates address relevant stability issues.
• Monitor hardware temperatures.
• Maintain adequate system cooling.
• Use a reliable PSU appropriate for the installed hardware.
• Investigate repeated BSODs rather than ignoring them.
• Keep backups of important data.

Frequently Asked Questions (FAQ)

1. What is KERNEL_MODE_HEAP_CORRUPTION?

KERNEL_MODE_HEAP_CORRUPTION is a Windows BSOD indicating that the kernel-mode heap manager detected corruption in a heap. Its bug check code is 0x0000013A.

2. What is error code 0x13A?

0x13A is the hexadecimal bug check value associated with KERNEL_MODE_HEAP_CORRUPTION.

3. Is KERNEL_MODE_HEAP_CORRUPTION usually a driver problem?

A faulty or incompatible kernel-mode driver is an important possibility and should be investigated early, particularly when the issue starts after a driver or hardware change. Hardware instability can also corrupt memory.

4. Can a graphics driver cause KERNEL_MODE_HEAP_CORRUPTION?

Yes. Graphics drivers operate at a low level and can contribute to kernel memory corruption if they malfunction.

GPU drivers should be investigated especially when crashes occur during gaming, rendering or other GPU-intensive operations.

5. Can faulty RAM cause this BSOD?

Yes. Defective or unstable RAM can corrupt memory and produce BSODs.

Run memory diagnostics and disable XMP/EXPO while troubleshooting.

6. Can XMP cause KERNEL_MODE_HEAP_CORRUPTION?

Potentially. XMP runs memory using a configured performance profile that may be unstable on a particular CPU/motherboard/RAM combination.

Temporarily disable XMP and test the system.

7. Can overclocking cause heap corruption?

Yes. An unstable CPU, GPU or memory overclock can cause incorrect calculations or memory corruption and ultimately produce BSODs.

Return the system to stock settings during diagnosis.

8. Why does the BSOD happen only while gaming?

Gaming places substantial load on the GPU, graphics driver, CPU, RAM and power supply. A stability issue that remains hidden during ordinary desktop use may become apparent under gaming load.

9. Should I reinstall Windows immediately?

Usually not.

First investigate drivers, RAM, overclocking, system files, BIOS/firmware and crash dumps. Reinstalling Windows should generally come later unless there is strong evidence of widespread operating-system corruption.

10. What if the dump points to ntoskrnl.exe?

Do not automatically assume ntoskrnl.exe is defective.

The Windows kernel may simply have detected corruption originally caused by another driver or hardware problem.

11. Where are Windows BSOD minidumps stored?

Usually:

C:\Windows\Minidump

A larger system dump may also exist as:

C:\Windows\MEMORY.DMP

depending on the configured crash-dump settings.

12. How do I analyze KERNEL_MODE_HEAP_CORRUPTION?

Use Microsoft WinDbg and begin with:

!analyze -v

For bug check 0x13A, Microsoft also identifies !heap as a useful debugger extension for heap investigation.

13. Is Driver Verifier safe?

Driver Verifier is a legitimate Windows diagnostic tool, but it intentionally stresses drivers and can cause additional BSODs.

Use it only when necessary and know how to disable it.

14. How do I disable Driver Verifier?

Open an elevated Command Prompt and run:

verifier /reset

Then restart Windows.

If normal Windows will not boot, perform the reset from Safe Mode or Windows Recovery where possible.

15. Can antivirus software cause KERNEL_MODE_HEAP_CORRUPTION?

Potentially. Some security products install kernel-level drivers. A faulty, outdated or incompatible driver from such software can contribute to BSODs.

16. Can VPN software cause this BSOD?

Potentially. VPN clients frequently install virtual network adapters and filtering drivers. If crashes began immediately after installing or updating a VPN, test after updating or temporarily uninstalling it.

17. Can an SSD cause KERNEL_MODE_HEAP_CORRUPTION?

An SSD is not the first suspect for heap corruption, but storage hardware, firmware or storage-controller drivers can contribute to system instability. Check drive health and storage-related drivers when symptoms point in that direction.

18. Should I update BIOS?

Consider a BIOS update when the manufacturer specifically provides compatibility, memory, CPU or stability fixes relevant to your system.

BIOS updates must be performed carefully according to the manufacturer's instructions.

19. Why does KERNEL_MODE_HEAP_CORRUPTION keep returning?

Recurring crashes usually mean the underlying cause has not been corrected.

Instead of repeatedly running generic repair commands, analyze multiple crash dumps and look for consistent drivers, modules, activities or hardware conditions.

20. What should I do if nothing fixes the error?

If normal troubleshooting fails:

• Collect multiple minidumps.
• Analyze them using WinDbg.
• Test RAM extensively.
• Test without overclocking/XMP/EXPO.
• Remove recently added hardware.
• Test the GPU if possible.
• Update BIOS and chipset drivers.
• Check SSD health.
• Check power and temperatures.
• Consider professional hardware diagnostics.

The most valuable next step in a persistent 0x13A case is often determining what actually corrupted the heap, rather than continuing to apply generic Windows repairs.

Technical Summary

Error: KERNEL_MODE_HEAP_CORRUPTION
Bug Check: 0x0000013A
Category: Windows Blue Screen of Death / Kernel memory corruption
Meaning: Windows kernel-mode heap manager detected corruption in a heap.
Common suspects: Faulty drivers, graphics drivers, unstable RAM, overclocking, kernel-level third-party software, firmware or hardware instability
Important diagnostic files: C:\Windows\Minidump\*.dmp and potentially C:\Windows\MEMORY.DMP
Primary debugging tool: WinDbg
Useful WinDbg command: !analyze -v
Advanced diagnostic tool: Driver Verifier
Operating systems: Windows 10, Windows 11 and relevant Windows/Windows Server versions where bug check 0x13A occurs

#tags

#KERNEL_MODE_HEAP_CORRUPTION #KernelModeHeapCorruption #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsTroubleshooting #WindowsError #WindowsRepair #StopCode #BugCheck #BugCheck13A #0x13A #0x0000013A #KernelError #HeapCorruption #MemoryCorruption #DriverError #DriverCrash #FaultyDriver #GraphicsDriver #GPUDriver #NVIDIA #AMD #IntelGraphics #GamingBSOD #WindowsCrash #PCRepair #ComputerRepair #RAMError #MemoryDiagnostic #WindowsMemoryDiagnostic #SFC #DISM #CHKDSK #WinDbg #Minidump #CrashDump #DriverVerifier #DeviceManager #SystemRepair #WindowsUpdate #BIOSUpdate #Overclocking #XMP #HardwareTroubleshooting #SoftwareTroubleshooting #BlueScreenFix #BSODFix