![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 1%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGR%3C/text%3E%3C/svg%3E)
0x13A means the kernel heap manager detected heap corruption. In the dump, Arg1: 0x17 specifically means a block was corrupted in a delay free list, which is commonly associated with a use-after-free error or a buffer overflow of an adjacent block.
Since sfc, DISM, GPU driver reinstall, and a memory test were already tried, the next useful path is to focus on drivers and recent hardware/software changes rather than repeating those same steps.
Recommended steps:
- Check for recent driver or device changes
- In Device Manager, look for any device with a warning icon.
- Open the properties of recently updated or newly installed devices and review the device events.
- Update or remove recently added drivers or system services.
- This is especially important for storage, chipset, and other low-level device drivers.
- Check Event Viewer for related errors
- Open Event Viewer and review the System log.
- Look for critical or error events in the same time window as the blue screen.
- The goal is to identify the device or driver active just before the crash.
- If hardware was recently changed, test that path
- If any hardware was added or replaced, remove or reseat it if possible.
- Check with the device manufacturer for updated firmware, BIOS, or driver packages.
- For heap corruption after hardware changes, faulty or poorly seated hardware can be a trigger.
- Use Driver Verifier to expose a faulty driver
- One accepted resolution for
0x13Acases that only show memory corruption is to enable Driver Verifier so Windows can force a more specific crash that identifies the bad driver. - Warning: Driver Verifier can make the system unstable or cause boot loops until it is disabled.
- Before enabling it, create a restore point.
- If Windows cannot boot afterward:
- Force shutdown during startup two or three times to enter Recovery.
- Go to Troubleshoot > Advanced Option > Startup Settings > Restart.
- Press 4 for Safe Mode.
- Open an elevated Command Prompt and run:
verifier /reset verifier /bootmode resetonbootfail
- One accepted resolution for
- Run general stop-error checks that can still help
- Run a virus scan.
- Check disk/file-system health from File Explorer > drive Properties > Tools > Check.
- If storage corruption is suspected,
Chkdsk /f /rcan detect and resolve structural file-system corruption. Warning: this requires a restart on the system partition.
- If the issue started after a specific driver update, roll back that driver
- The dump shown does not identify a specific third-party driver.
- In this situation, rolling back recently changed drivers is more useful than reinstalling random components.
- If another dump can be captured after Driver Verifier, compare multiple dumps
- Microsoft guidance for corruption-style bug checks is to examine multiple dump files and look for the same code path or driver repeatedly.
The key point from the dump is that this is a heap corruption symptom, not proof that ntkrnlmp.exe itself is the root cause. The most likely next target is a faulty or incompatible driver, and Driver Verifier is the most direct next step when the dump only shows generic heap corruption.
References:
- Bug check 0x13A: KERNEL_MODE_HEAP_CORRUPTION
- Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE
- Bug check 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
- KERNEL_MODE_HEAP_CORRUPTION (13a) - getting crashes after changing a few pc parts, done by a technician - Microsoft Q&A Just posted to r/techsupport, figured i'd post here too for the support
- my pc got black screen when playing game - Microsoft Q&A my pc keep getting blackscreen when playing MHW and here is the dump file
