Can someone please help me trace what caused of my KERNEL HEAP MODE CORRUPTION. It's getting worse 3x a day. please

kids youtube 20 Reputation points
2026-07-29T23:45:05.1666667+00:00
ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29617.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\073026-12031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff805`97c00000 PsLoadedModuleList = 0xfffff805`98af51d0
Debug session time: Thu Jul 30 07:22:05.841 2026 (UTC + 8:00)
System Uptime: 0 days 7:02:56.620
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
........................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`980f8250 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffdc88`3c53f450=000000000000013a
6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................
Loading User Symbols

Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000017, The heap detected that a block was corrupted in a delay free list. This is likely a use-after-free error or a buffer overflow of an adjacent block.
Arg2: ffff828256100340, Address of the heap that reported the corruption
Arg3: ffff82827cdfe6e0, Address at which the corruption was detected
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1578

    Key  : Analysis.Elapsed.mSec
    Value: 5453

    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: 531

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x13a

    Key  : Bugcheck.Code.TargetModel
    Value: 0x13a

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x13a_17_nt!RtlpHeapHandleError

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

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    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: 0x24a10ef

    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: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 1.52.0.0


BUGCHECK_CODE:  13a

BUGCHECK_P1: 17

BUGCHECK_P2: ffff828256100340

BUGCHECK_P3: ffff82827cdfe6e0

BUGCHECK_P4: 0

FILE_IN_CAB:  073026-12031-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff828282c96040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffdc88`3c53f448 fffff805`981efaac     : 00000000`0000013a 00000000`00000017 ffff8282`56100340 ffff8282`7cdfe6e0 : nt!KeBugCheckEx
ffffdc88`3c53f450 fffff805`981efb0c     : 00000000`00000017 000ffff8`2827cdfc ffff8282`56100340 00000000`00001000 : nt!RtlpHeapHandleError+0x40
ffffdc88`3c53f490 fffff805`97f4ebe9     : 00000000`00000132 00000000`00000000 00000000`02000103 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffffdc88`3c53f4c0 fffff805`97fe19db     : ffff8281`5a84fb88 00000000`00000010 00000000`00000001 00000000`00000001 : nt!RtlpLogHeapFailure+0x45
ffffdc88`3c53f4f0 fffff805`97fe150c     : ffff8282`561043d8 fffff805`00000020 00000000`002b0132 000ffff8`2827cdfc : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x2bb
ffffdc88`3c53f570 fffff805`98032f9f     : ffff8282`561043c0 00000000`002b0132 ffff8282`56101b00 00000000`00000001 : nt!RtlpHpLfhOwnerRunMaintenance+0x14c
ffffdc88`3c53f5d0 fffff805`980330da     : ffff8282`56101b00 ffffdc88`3c53f770 ffffdc88`3c53f760 ffff8282`56101b00 : nt!RtlpHpLfhOwnerCompact+0xbf
ffffdc88`3c53f750 fffff805`98032ddf     : ffff8282`56100000 ffff8282`56101b00 ffff8c6d`a29bcc81 00000000`00000000 : nt!RtlpHpLfhOwnerCompact+0x1fa
ffffdc88`3c53f8d0 fffff805`97f4fd35     : ffff8282`56100000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpLfhContextCompact+0xbf
ffffdc88`3c53f910 fffff805`97f4fcd3     : 00000000`00000001 ffff8282`56508d00 00000000`00000001 ffff8282`82c96180 : nt!RtlpHpHeapCompact+0x21
ffffdc88`3c53f940 fffff805`98080665     : 00000000`00000001 00000000`00000001 00000000`00000000 ffffdc88`3c53f9c0 : nt!ExpHpCompactHeapCallback+0x23
ffffdc88`3c53f970 fffff805`980805c5     : 00000000`00000001 ffffdc88`3c53fb00 ffff8282`56553aa0 ffff8282`56553aa0 : nt!ExpHpEnumerateHeaps+0x71
ffffdc88`3c53f9d0 fffff805`97eea57b     : ffff8282`82c96040 ffff8282`82c96000 ffff8282`56553a00 ffff8282`56553aa0 : nt!ExpHpCompactionRoutine+0x15
ffffdc88`3c53fa00 fffff805`9808173a     : ffff8282`82c96040 ffff8282`82c96040 fffff805`97eea0c0 ffff8282`56553aa0 : nt!ExpWorkerThread+0x4bb
ffffdc88`3c53fbb0 fffff805`982aa594     : fffff805`27e8c180 ffff8282`82c96040 fffff805`980816e0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
ffffdc88`3c53fc00 00000000`00000000     : ffffdc88`3c540000 ffffdc88`3c539000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!RtlpHeapHandleError+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8655

STACK_COMMAND: .process /r /p 0xffff82825650d040; .thread /r /p 0xffff828282c96040 ; kb

BUCKET_ID_FUNC_OFFSET:  40

FAILURE_BUCKET_ID:  0x13a_17_nt!RtlpHeapHandleError

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b1500314-0083-90bd-d812-716f3060523d}

Followup:     MachineOwner
---------


already run test

Uninstall your graphics card drivers

Update your device drivers

Resolve any software conflicts

Resolve any hardware issues

Repair corrupted system files

Reinstall your Windows system

still encounter the kernel heap mode error. thank you

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

Answer accepted by question author
Ivan B 120.2K Reputation points Independent Advisor
2026-07-30T00:18:35.3+00:00

Hi ,

Search for msinfo32.exe in the search bar, take a screenshot, and post it here so we can see the correct laptop model or desktop configuration.

Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

Thanks

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Khairy Zhafran H. Kastella 80 Reputation points
    2026-07-29T23:48:15.84+00:00

    The Foundry Model Playground is intended for testing prompts and comparing model behavior, but it doesn't provide a way to save or export prompts directly.

    If you want to reuse your prompts, consider these options:

    Copy the prompt manually into a text file or source control repository. Use the Azure AI Foundry SDK or REST API to store prompts as part of your application code or configuration. If you're using Prompt Flow or another prompt management workflow, keep your prompts in version control (such as Git) so they can be tracked and reused.

    Currently, there isn't a built-in feature in the Model Playground to export prompts directly from the interface. If this functionality would improve your workflow, consider submitting it as feedback through the Azure AI Foundry feedback channels.

    Hopefully Microsoft may add prompt export capabilities in a future update.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.