Share via

Frequent Kernel Model Heap Corruption BSOD

Anonymous
2025-02-23T05:26:39+00:00

Hi everyone,

I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing the issue since December, though.

Most times when I'm playing video games, a really low number of times just regular browsing, (YouTube, mostly streaming sites, etc.) using Edge.

Have tried a few things that people have suggested to users experiencing the same issue, but nothing seems to work.

Things I've tried (which didn't work):

  1. Switched from single-channel RAM, switching slots as well, to isolate possibly faulty RAM.
  2. Ran MemTest86, but no issues found.
  3. Ran /sfc scannow and DISM.exe /Online /Cleanup-Image /Restorehealth
  4. Reinstalled GPU drivers
  5. Reverted BIOS config to default
  6. Turned Hypervisor off, but changed it back again (since no effects)
  7. Performed Clean Boot

Minidump Analysis (WinDbg)

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000017, Type of corruption detected
Arg2: ffff890968100380, Address of the heap that reported the corruption
Arg3: ffff89098e7fca00, Address at which the corruption was detected
Arg4: 0000000000000000

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1859

    Key  : Analysis.Elapsed.mSec
    Value: 7832

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 421

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3199

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 88

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x13a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x13a

    Key  : Failure.Bucket
    Value: 0x13a_17_nt!RtlpHeapHandleError

    Key  : Failure.Hash
    Value: {b1500314-0083-90bd-d812-716f3060523d}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 24a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

BUGCHECK_CODE:  13a

BUGCHECK_P1: 17

BUGCHECK_P2: ffff890968100380

BUGCHECK_P3: ffff89098e7fca00

BUGCHECK_P4: 0

FILE_IN_CAB:  022325-8984-01.dmp

FAULTING_THREAD:  ffff89097e5cf080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbb84`64407408 fffff802`8cdb2358     : 00000000`0000013a 00000000`00000017 ffff8909`68100380 ffff8909`8e7fca00 : nt!KeBugCheckEx
ffffbb84`64407410 fffff802`8cdb23b8     : 00000000`00000017 00000000`000002c9 ffff8909`68100380 00000000`00000000 : nt!RtlpHeapHandleError+0x40
ffffbb84`64407450 fffff802`8ca85451     : ffff8909`8e7f7000 ffff8909`68100380 00000000`00000000 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffffbb84`64407480 fffff802`8cc69535     : fffff802`8ca86de0 ffffbb84`644073b0 00000000`00000040 00000000`0000c000 : nt!RtlpLogHeapFailure+0x45
ffffbb84`644074b0 fffff802`8cc04ca9     : ffff8909`8e7f7000 00000000`000002fb ffff8909`68100380 ffff8909`00000001 : nt!RtlpHpLfhReportError+0x21
ffffbb84`644074f0 fffff802`8cc04878     : ffff8909`8e7f7000 ffff8909`00000020 00000000`006a0309 000ffff8`9098e7f7 : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x255
ffffbb84`64407570 fffff802`8cc2d372     : 00000000`00000007 00000000`006a0309 ffff8909`68100380 ffff8909`68798e40 : nt!RtlpHpLfhOwnerRunMaintenance+0x174
ffffbb84`644075d0 fffff802`8cc2d44f     : 00000000`00000000 fffff802`8cb8e020 ffff8909`681002c0 ffffbb84`64407780 : nt!RtlpHpLfhOwnerCompact+0xc2
ffffbb84`64407750 fffff802`8cc2d11f     : ffff8909`68100000 fffff802`8cc2d4d6 00010000`00000000 00000000`00000000 : nt!RtlpHpLfhOwnerCompact+0x19f
ffffbb84`644078d0 fffff802`8cc2d055     : ffff8909`68100000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpLfhContextCompact+0xa3
ffffbb84`64407910 fffff802`8cc2cff3     : 00000000`00000000 ffff8909`8674a000 00000000`00000001 ffff8909`7e5cf0c0 : nt!RtlpHpHeapCompact+0x21
ffffbb84`64407940 fffff802`8cc71165     : 00000000`00000001 00000000`00000001 00000000`00000000 fffff802`8cb70b56 : nt!ExpHpCompactHeapCallback+0x23
ffffbb84`64407970 fffff802`8cc710c5     : 00000000`00000001 ffffbb84`64407b00 ffff8909`68856ae0 ffff8909`68856ae0 : nt!ExpHpEnumerateHeaps+0x71
ffffbb84`644079d0 fffff802`8cb704b2     : ffff8909`7e5cf080 ffff8909`68856a00 fffff802`00000000 fffff802`00000000 : nt!ExpHpCompactionRoutine+0x15
ffffbb84`64407a00 fffff802`8cc5594a     : ffff8909`7e5cf080 ffff8909`7e5cf080 fffff802`8cb70300 ffff8909`68856ae0 : nt!ExpWorkerThread+0x1b2
ffffbb84`64407bb0 fffff802`8ce7a004     : ffffe381`f5dd7180 ffff8909`7e5cf080 fffff802`8cc558f0 df326831`b39b9ef1 : nt!PspSystemThreadStartup+0x5a
ffffbb84`64407c00 00000000`00000000     : ffffbb84`64408000 ffffbb84`64401000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nt!RtlpHeapHandleError+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.3194

STACK_COMMAND:  .process /r /p 0xffff8909686bb040; .thread 0xffff89097e5cf080 ; kb

BUCKET_ID_FUNC_OFFSET:  40

FAILURE_BUCKET_ID:  0x13a_17_nt!RtlpHeapHandleError

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

BSODs before were auto- restarting but the recent two or more BSODs has stopped auto-restarting so have resorted to force-restart. Not sure if that would help in the diagnosis, though.

System Information:

MB: ASUS Prime B550M-A Wifi II

RAM: T-Force Delta R 2x16Gb 3600Mhz

GPU: Sapphire Radeon 7600XT

CPU: AMD Ryzen 7 5700X3D

SSD: Samsung 990 EVO 1TB

PSU: MSI MAG A750GL PCIE5 750W

OS ver: Windows 11 24H2 (KB5051987)

Any advice would be helpful. Thanks a lot!

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 868K Reputation points Independent Advisor
    2025-02-23T12:35:22+00:00

    Your new minidump file indicates a driver usually associated to the Armory Crate utility caused your system to crash.

    Please ensure Driver Verifier is now disabled and do not re-enable it.

    If oyu have Armory Crate installed on your PC, uninstall that, restart your PC for testing purposes and wait to see if your system is stable.

    0 comments
  2. Anonymous
    2025-02-23T12:19:26+00:00

    Have run driver verifier. Uploaded the files here:

    022325-4734-02.zip

    0 comments
  3. DaveM121 868K Reputation points Independent Advisor
    2025-02-23T08:40:21+00:00

    Your one minidump file just indicate generic memory (RAM) corruption no specific cause of that crash is listed

    To try to force Windows to show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...

    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    0 comments
  4. Anonymous
    2025-02-23T08:37:38+00:00
    0 comments
  5. DaveM121 868K Reputation points Independent Advisor
    2025-02-23T07:58:49+00:00

    Hi, I am Dave, I will help you with this.

    Please upload any minidump files you may have for analysis, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    0 comments