iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
KERNEL_MODE_HEAP_CORRUPTION (0x13A) means Windows detected corruption in a kernel-mode heap; it does not identify the faulty component. A driver, hardware device, or software issue may be involved, and the stop code alone does not prove that RAM is defective. Try these seven steps from low-risk checks to advanced crash analysis, stopping when you have identified a likely trigger.
What KERNEL_MODE_HEAP_CORRUPTION (0x13A) means
Microsoft defines bug check 0x0000013A as a case where the kernel-mode heap manager detected corruption in a heap. Its four parameters describe the corruption type, heap address, address where corruption was detected, and a reserved value. The first parameter can provide clues about patterns such as buffer overrun or underrun, use-after-free, double-free, or corrupted lists; it does not name the responsible driver or device. See Microsoft’s 0x13A documentation.
Microsoft’s general stop-code guidance says an unexpected restart might involve a hardware device, its driver, or software. The guidance applies broadly to Windows 10 and Windows 11; it does not rank fixes specifically for 0x13A or guarantee that any one step will resolve it. The actions below are ways to isolate a cause and gather better evidence.
Seven troubleshooting steps, from basic checks to crash analysis
1. Remove recently added hardware and retest
If the crashes started after you connected or installed a device, shut down the PC, remove that device, then use the computer as usual and check whether the same stop code returns. This controlled test can reveal whether the timing is related; it does not by itself prove the device is defective. Follow the computer or device manufacturer’s instructions for safe removal.
#1 Best Overall
2. Use Safe Mode if normal startup is unstable
When Windows cannot stay running long enough to troubleshoot, start in Safe Mode and continue with the checks below. Safe Mode loads a limited set of drivers and services, which can make it easier to investigate a recurring startup crash. Microsoft’s stop-code guidance explains how to use Safe Mode as part of troubleshooting: Troubleshooting Windows unexpected restarts and stop code errors. The exact recovery screens can vary by Windows version and PC.
3. Review Device Manager and recent driver changes
Open Device Manager and look for devices marked with an exclamation point. Also consider whether the crashes began after a driver update or a newly installed device. If a particular device is flagged or its driver changed just before the problem started, try updating that driver. If updating does not help, Microsoft suggests disabling or uninstalling the device as a test. Make one reversible change at a time, and avoid disabling hardware you need to start or operate the PC.
4. Check free space on the Windows system drive
Check available space on the drive containing Windows. Microsoft gives 10% to 15% free space as a practical general guideline because Windows and applications need room for swap files and other functions; the amount needed depends on the system configuration. This is a general stop-code maintenance check, not an established 0x13A-specific cause. Microsoft’s storage guidance is included in its stop-code troubleshooting article.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems5. Install current Windows updates
Check Windows Update and install available updates, then restart if Windows requests it. Use the PC normally afterward and note whether the same stop code recurs. This is a standard Microsoft stop-code troubleshooting step, not a guaranteed repair for heap corruption.
6. Consider Windows recovery if the basic checks fail
If the crashes continue after the earlier checks, Microsoft recommends considering System Restore or another Windows recovery option. Choose an option that fits what changed and how severe the startup problem is. Back up important files first when possible, and review what the selected recovery option will affect before proceeding. Recovery choices and their consequences vary, so use Microsoft’s instructions for the option you select rather than treating every reset or restore as interchangeable.
7. Capture and analyze crash data for recurring failures
For repeated crashes that remain unexplained, record the circumstances and preserve the crash data instead of guessing from the stop-code name. Microsoft documents ways to collect bug-check parameters through Event Viewer, a generated dump, or a kernel debugger. Its 0x13A technical entry identifies the debugger extensions !analyze and !heap as useful for investigating the failure: Bug check 0x13A: KERNEL_MODE_HEAP_CORRUPTION. Dump analysis is an advanced task; a support professional can use the dump and the exact crash circumstances to narrow down what happened.
Driver Verifier is an advanced diagnostic step
Driver Verifier is built into Windows and checks driver behavior, including use of memory resources. It can deliberately raise an exception when it detects driver execution errors, so it may add diagnostic evidence but is not a repair button. Verification adds overhead, and Microsoft’s guidance is to verify the smallest number of drivers possible. It is better suited to an advanced user or support professional investigating repeated crashes than to routine first-line troubleshooting. Read Microsoft’s Driver Verifier documentation before using it.
Recommended Free Tools
How to choose the next step
- A device was added shortly before the crashes: remove it and retest before changing unrelated settings.
- Windows is unstable during startup: use Safe Mode to reach the system and perform basic checks.
- A device is flagged or a driver recently changed: focus on that device, and make reversible changes one at a time.
- Basic checks do not explain a recurring crash: collect dump data and seek help interpreting it; reserve Driver Verifier for a focused, advanced investigation.
Microsoft has estimated that faulting drivers cause about three quarters of stop-code errors overall, but that general estimate is not a rate measured specifically for KERNEL_MODE_HEAP_CORRUPTION. It can justify checking drivers without making a particular driver the presumed culprit.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
