KERNEL_MODE_HEAP_CORRUPTION — stop code 0x00000013A — means the Windows kernel found its own heap memory corrupted and crashed before the damage could spread. The heap is where the kernel stores working data, so corruption there is serious — but the cause is usually mundane: a buggy driver writing where it should not, or a RAM stick flipping bits.

ASUS laptops deserve special attention here because they ship with an unusually large stack of bundled utilities — Armoury Crate, MyASUS background services, Sonic Studio audio drivers — and those kernel-level components show up in crash dumps for this stop code more often than you would expect. Here is how to find the real culprit.

Why this happens

  • A driver corrupts kernel heap memory. The classic cause — a driver writes past its buffer or frees memory twice, poisoning the heap.
  • ASUS bundled software drivers. Armoury Crate, MyASUS services, and ASUS audio enhancements install kernel drivers that have triggered this stop code in real crash reports.
  • Faulty RAM. Bad memory cells corrupt heap data in transit; the kernel notices and crashes.
  • Graphics driver bugs. NVIDIA and AMD graphics drivers are frequent heap-corruption offenders, especially beta releases.
  • Corrupted system files. A damaged kernel or driver binary on disk can corrupt the heap at load time.
  • Overclocking or XMP instability. Aggressive memory timings corrupt heap contents under load.
  • Failing SSD. Bad sectors in the page file or driver storage corrupt data the kernel reads back.

How to fix it

Work through these in order, from least to most invasive. The minidump analysis tells you whether to chase drivers or memory first.

Fix 1: Read the minidump to identify the pattern

Before changing anything, look at what the crashes have in common.

  1. Press Win + R, type %SystemRoot%\Minidump, and press Enter.
  2. Install WinDbg Preview from the Microsoft Store and open the two or three newest dumps.
  3. In each, run !analyze -v and note the MODULE_NAME.
  4. If the same .sys file appears every time, you have a driver culprit — skip to the fix targeting it.
  5. If every dump names a different driver, or they all point at ntoskrnl.exe, suspect RAM and jump to Fix 5 first.
  6. Our DRIVER_VERIFIER_DETECTED_VIOLATION guide explains dump reading in more detail if you are new to WinDbg.

Fix 2: Update or reinstall ASUS bundled software

On ASUS machines, start with the vendor’s own software stack before touching anything else.

  1. Open MyASUS and check for updates to all ASUS components, or update Armoury Crate from the Microsoft Store.
  2. If crashes started right after an Armoury Crate update, uninstall it from Settings > Apps > Installed apps, restart, and test for a few days.
  3. Reinstall the latest version only after confirming the crashes stopped without it.
  4. Do the same for Sonic Studio or Realtek audio console if the dump names an audio driver — ASUS audio drivers are a known heap-corruption source.
  5. Keep only the ASUS utilities you actually use; every kernel driver you remove is one fewer suspect.

Fix 3: Clean-install the graphics driver

Graphics drivers are the most common third-party cause of heap corruption across all brands.

  1. Download Display Driver Uninstaller (DDU) and the latest stable driver from NVIDIA or AMD — use the NVIDIA driver download page or the AMD driver support page for your exact GPU.
  2. Boot into Safe Mode and run DDU to fully remove the old graphics driver.
  3. Install the fresh stable driver (skip beta/optional releases) and restart normally.
  4. Test with the workloads that used to crash — gaming, video editing, or external monitors.

Fix 4: Update remaining drivers from ASUS support

Do not let Windows Update guess at ASUS-specific drivers.

  1. Find your exact model on the sticker under the laptop.
  2. Download the latest chipset, Wi-Fi/Bluetooth, and storage drivers from ASUS support for that model.
  3. Install chipset first, then the rest, restarting between major installs.
  4. Avoid third-party driver updater tools — they are a common source of the mismatched drivers that cause heap corruption.

Fix 5: Test the RAM thoroughly

If dumps are inconsistent or memory was never tested, do it now — properly.

  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Choose Restart now and check for problems, press F1, and select the Extended test.
  3. For a definitive answer, run MemTest86 from a USB drive overnight.
  4. If errors appear, test sticks individually and replace the bad one.
  5. Also disable XMP/DOCP memory profiles in the BIOS while testing — unstable overclocked RAM is a classic heap-corruption source. The RAM-testing approach in our MEMORY_MANAGEMENT stop code guide applies equally here.

Fix 6: Repair system files and check the drive

Rule out on-disk corruption feeding bad data to the kernel.

  1. Open an elevated Command Prompt and run sfc /scannow.
  2. Follow with DISM /Online /Cleanup-Image /RestoreHealth.
  3. Run chkdsk C: /f /r (type Y and restart) to scan for bad sectors.
  4. Check SMART health with CrystalDiskInfo — a failing SSD plus heap corruption means replace the drive, not the drivers.

Fix 7: Reset Windows as a last resort

When the dumps implicate Windows components themselves and repairs do not help, start fresh.

  1. Go to Settings > System > Recovery > Reset PC.
  2. Choose Keep my files first.
  3. After the reset, install ASUS drivers from ASUS support before running Windows Update.
  4. If heap corruption persists on a clean install with tested RAM, the fault is hardware — usually the motherboard or a soldered RAM chip — and needs a repair shop.

Closing

KERNEL_MODE_HEAP_CORRUPTION on an ASUS laptop usually traces back to one of three things: an ASUS utility driver, the graphics driver, or the RAM. Read a few dumps to see which story yours tells, fix that layer, and work outward. It is a scary-sounding stop code with a very fixable set of causes.

Frequently asked questions

What does KERNEL_MODE_HEAP_CORRUPTION mean?
It is a blue screen stop code (0x00000013A) meaning the Windows kernel detected corruption in its heap memory. A driver wrote invalid data into kernel memory, or failing RAM corrupted it — either way, Windows crashed to prevent further damage.
Is it always a driver problem on ASUS laptops?
Most of the time, yes. ASUS laptops ship with a lot of bundled software — Armoury Crate, MyASUS services, audio enhancements — whose kernel drivers are frequent offenders. But bad RAM is the second most common cause, so test memory too.
Can ASUS Armoury Crate cause this blue screen?
It has been implicated in crash reports more than once. Armoury Crate installs several kernel-level drivers for fan control and lighting. If crashes started after an Armoury Crate update, updating or reinstalling it is worth trying.
How do I know if it is the RAM or a driver?
The minidump usually names a driver when one is at fault. If dumps point at different drivers each time, or at ntoskrnl.exe itself, suspect RAM. Run Windows Memory Diagnostic — it is the fastest way to tell the two apart.