KERNEL_MODE_HEAP_CORRUPTION is Windows catching a driver red-handed. The kernel allocates memory from “heaps,” and when a driver writes past the end of its allocation or uses memory after freeing it, the heap manager notices the damage and crashes the system rather than let corruption spread silently.

The practical upshot: some third-party driver on your system has a memory bug. Your job is to find which one. This guide goes from the quick driver refresh through the definitive tool — Driver Verifier — that catches the culprit in the act. For the closely related pool corruption variant, see our BAD_POOL_HEADER fix .

Heap corruption is also one of the stop codes where Driver Verifier truly shines — more than most. Because the corruption is a driver writing out of bounds, Verifier’s Special pool option catches it at the exact moment it happens, with the driver’s name attached. If the quick fixes below don’t resolve it, Verifier (Fix 4) is your endgame.

Why this happens

  • Buggy graphics driver: The #1 offender — GPU drivers manage huge amounts of memory and heap bugs surface after major driver or Windows updates.
  • Faulty network driver: Wi-Fi and Ethernet drivers with buffer-management bugs, often after Windows Update swaps in a new version.
  • Antivirus/VPN filter drivers: Kernel-mode security drivers that intercept system operations are frequent heap corruptors.
  • Corrupted driver installation: A half-installed or mismatched driver version behaving badly.
  • Bad RAM: Faulty memory corrupting heap contents, mimicking a driver bug.
  • Overclocking instability: Unstable CPU/RAM causing bit errors that the heap manager interprets as corruption.
  • Sloppy utility drivers: RGB control, fan utilities, and motherboard “gaming” tools with poor memory hygiene.

How to fix it

Work through these in order.

Fix 1: Clean-install the graphics driver

Start with the most likely culprit. GPU drivers allocate enormous heaps for textures, shaders, and buffers — more heap activity means more opportunities for a heap bug to trigger. A truly clean reinstall (not an update-over) matters here.

  1. Download Display Driver Uninstaller (DDU) and the latest stable graphics driver for your GPU (from your laptop maker first, or NVIDIA/AMD/Intel).
  2. Boot into Safe Mode (Shift + Restart > Troubleshoot > Advanced options > Startup Settings).
  3. Run DDU, choose Clean and restart — this removes every trace of the old driver.
  4. Install the fresh driver and restart normally.

Fix 2: Update network and chipset drivers

The second tier of usual suspects.

  1. From your manufacturer’s support site, download the latest Wi-Fi, Ethernet (if present), and chipset drivers for your exact model.
  2. Install them one at a time with restarts between.
  3. If the crashes started after a Windows update, check Device Manager for recently updated drivers and roll those back first (Properties > Driver > Roll Back Driver).

Fix 3: Remove kernel-mode third-party software

Antivirus, VPN, and “system optimizer” drivers are classic heap corruptors.

  1. Uninstall third-party antivirus and VPN clients completely.
  2. Remove any “driver updater,” “PC cleaner,” or game-booster utilities — these often install their own kernel drivers.
  3. Restart and use the system normally for a day. Windows Security covers you in the meantime.

Fix 4: Use Driver Verifier to catch the guilty driver

This is the definitive diagnostic — it makes the bad driver crash immediately instead of corrupting things silently. Plan for it to take a day of normal use; Verifier only catches the driver when the buggy code path actually executes.

  1. Create a System Restore point first (Control Panel > System > System protection > Create).
  2. Press Win + R, type verifier.exe, press Enter.
  3. Choose Create custom settings, click Next, select Standard settings plus Special pool (great for heap corruption), click Next.
  4. Choose Select driver names from a list, sort by Provider, and check all drivers NOT provided by Microsoft.
  5. Click Finish and restart. Use the PC normally — Verifier will BSOD with the guilty driver’s name (often DRIVER_VERIFIER_DETECTED_VIOLATION) when it misbehaves.
  6. After identifying it, boot into Safe Mode and run verifier /reset in an admin terminal to turn Verifier off, then update/remove the guilty driver.

Caution: Verifier can cause boot loops if a boot-critical driver is buggy. Know the Safe Mode path (triple-interrupt boot) before enabling it.

Fix 5: Run SFC and DISM

Rule out corrupted Windows components contributing to the instability.

  1. Open Terminal (Admin) and run sfc /scannow.
  2. Follow with DISM /Online /Cleanup-Image /RestoreHealth if SFC reports unfixable damage.
  3. Restart and test.

Fix 6: Test the RAM

If Verifier finds nothing and fresh drivers don’t help, suspect hardware. For the broader family of memory stop codes, see our memory management stop-code troubleshooting .

  1. Run Windows Memory Diagnostic (mdsched.exe) as a first screen.
  2. Follow with MemTest86 from a bootable USB for one full pass — zero errors is the only acceptable result.
  3. Test sticks individually if errors appear, and reseat modules before replacing.

Fix 7: Disable overclocks and check thermals

  1. Reset BIOS/UEFI to optimized defaults, disabling XMP/EXPO memory profiles and any CPU tuning.
  2. Remove Intel XTU / Ryzen Master / Afterburner overclocks.
  3. Monitor temperatures with HWiNFO64 — clean vents and fans if the system runs hot, since thermal instability can cause heap-like corruption signatures.

Fix 8: Analyze dumps for the repeat offender

If crashes persist after all driver updates:

  1. Install WinDbg Preview from the Microsoft Store.
  2. Open dumps from C:\Windows\Minidump and run !analyze -v.
  3. If the same .sys file appears in every dump, you’ve found it — search the Microsoft Update Catalog for an older stable version, or check the hardware vendor’s site for a fixed release.

Closing

KERNEL_MODE_HEAP_CORRUPTION is Windows doing you a favor — it caught memory corruption before it could silently destroy your data. The fix path is: refresh the graphics and network drivers, strip out third-party kernel software, then let Driver Verifier name the culprit if the obvious steps don’t work. RAM testing is the backstop for when software checks come up empty. In the large majority of cases, one of the first four fixes ends the crashes for good. One caution: if Verifier fingers a driver and the vendor has no fixed version, don’t just disable Verifier and live with it — roll back to the last stable version or replace the hardware/software. Corruption you can’t see is still corruption.

Frequently asked questions

What is KERNEL_MODE_HEAP_CORRUPTION?
The Windows kernel’s heap manager detected that a driver wrote outside its allocated memory — a buffer overflow or use-after-free in kernel mode. Windows crashes deliberately to prevent silent corruption. It’s essentially always a buggy third-party driver, not a Windows bug.
Which drivers usually cause heap corruption?
Graphics drivers (especially after major updates), network/Wi-Fi drivers, storage filter drivers, and antivirus or VPN kernel drivers. Any driver that manages its own memory pools can corrupt the heap if it has a bug.
Can bad RAM cause KERNEL_MODE_HEAP_CORRUPTION?
Yes, though it’s less common than a driver bug. Faulty RAM can corrupt heap contents in ways that look identical to a driver bug. If Driver Verifier and driver updates don’t resolve it, test the RAM with MemTest86.
Is Driver Verifier safe to use?
Yes, when used carefully. It intentionally stresses drivers and will BSOD the system when it catches the guilty driver — that’s the point. Always create a restore point first, only verify third-party drivers, and know how to boot to Safe Mode to run verifier /reset if you get stuck in a crash loop.