Hi, please help. After 1–2 hours of the computer running, regardless of its load, a blue screen and a kernel mode heap corruption error appear.

SteenH 0 Reputation points
2026-09-04T09:13:51.37+00:00
: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_HEAP_CORRUPTION (13a)
The kernel mode heap manager has detected corruption in a heap.
Arguments:
Arg1: 0000000000000011, The heap detected invalid internal state during the current operation. This can be the result of a double-free or heap corruption.
Arg2: ffff938957000140, Address of the heap that reported the corruption
Arg3: ffff93896703b800, Address at which the corruption was detected
Arg4: 0000000000000000

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

fffff807dcdc34b0: Unable to get MiVisibleState
fffff807dcdc34b0: Unable to get MiVisibleState

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1796

    Key  : Analysis.Elapsed.mSec
    Value: 1779

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

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

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

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

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

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

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

    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_11_PsTi_nt!RtlpHeapHandleError

    Key  : Failure.Hash
    Value: {88182a6f-2323-c78d-a6c9-5912074916bc}

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  13a

BUGCHECK_P1: 11

BUGCHECK_P2: ffff938957000140

BUGCHECK_P3: ffff93896703b800

BUGCHECK_P4: 0

FILE_IN_CAB:  090426-16734-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffbe827608c040

POOL_ADDRESS: fffff807dcdc34b0: Unable to get MiVisibleState
 ffff93896703b800 

FREED_POOL_TAG:  PsTi

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff581`66830448 fffff807`dc3ad528     : 00000000`0000013a 00000000`00000011 ffff9389`57000140 ffff9389`6703b800 : nt!KeBugCheckEx
fffff581`66830450 fffff807`dc3ad588     : 00000000`00000011 00000000`00000225 ffff9389`57000140 00000000`00000000 : nt!RtlpHeapHandleError+0x40
fffff581`66830490 fffff807`dc0389e1     : ffff9389`67035000 ffff9389`57000380 00000000`00000000 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
fffff581`668304c0 fffff807`dc26c735     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpLogHeapFailure+0x45
fffff581`668304f0 fffff807`dc128c1c     : ffff9389`67035000 00000000`00000225 ffff9389`57000380 00000000`00000000 : nt!RtlpHpLfhReportError+0x21
fffff581`66830530 fffff807`dc128e88     : ffff9389`67035000 00000000`00000030 00000000`000701d7 000ffff9`38967035 : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x27c
fffff581`668305b0 fffff807`dc233b42     : 00000000`00000007 00000000`000701d7 ffff9389`57000380 ffff9389`57002a80 : nt!RtlpHpLfhOwnerRunMaintenance+0x174
fffff581`66830610 fffff807`dc233c1f     : 00000000`00000000 ffff9389`57002a80 ffff9389`57002a80 fffff581`668307c0 : nt!RtlpHpLfhOwnerCompact+0xc2
fffff581`66830790 fffff807`dc2338ef     : 00000000`00000000 fffff807`dc233ca6 00010000`00000000 00000000`00000000 : nt!RtlpHpLfhOwnerCompact+0x19f
fffff581`66830910 fffff807`dc233825     : ffff9389`57000000 00000000`00000002 00000000`00000000 fffff807`70e056cb : nt!RtlpHpLfhContextCompact+0xa3
fffff581`66830950 fffff807`dc2337c3     : 00000000`00000000 ffff9389`6c20f590 00000000`00000003 ffffbe82`7608c080 : nt!RtlpHpHeapCompact+0x21
fffff581`66830980 fffff807`dc273655     : 00000000`00000002 00000000`00000003 00000000`00000000 fffff807`dc10a4d8 : nt!ExpHpCompactHeapCallback+0x23
fffff581`668309b0 fffff807`dc2735b5     : 00000000`00000000 fffff581`66830b40 ffffbe82`69747ca0 ffffbe82`69747ca0 : nt!ExpHpEnumerateHeaps+0x71
fffff581`66830a10 fffff807`dc109e32     : ffffbe82`7608c040 fffff581`66830b00 ffffbe82`69747c00 fffff807`00000000 : nt!ExpHpCompactionRoutine+0x15
fffff581`66830a40 fffff807`dc25904a     : ffffbe82`7608c040 ffffbe82`7608c040 fffff807`dc109c80 ffffbe82`69747ca0 : nt!ExpWorkerThread+0x1b2
fffff581`66830bf0 fffff807`dc4741c4     : ffffa800`4ff05180 ffffbe82`7608c040 fffff807`dc258ff0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff581`66830c40 00000000`00000000     : fffff581`66831000 fffff581`6682b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!RtlpHeapHandleError+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.1742

STACK_COMMAND: .process /r /p 0xffffbe8269695040; .thread /r /p 0xffffbe827608c040 ; kb

BUCKET_ID_FUNC_OFFSET:  40

FAILURE_BUCKET_ID:  0x13a_11_PsTi_nt!RtlpHeapHandleError

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88182a6f-2323-c78d-a6c9-5912074916bc}

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

Windows for home | Windows 11 | Devices and drivers
0 comments No comments

1 answer

Sort by: Newest
  1. DaveM121 928.6K Reputation points Independent Advisor
    2026-09-04T09:47:06.1333333+00:00

    That WinDBG trace does not indicate the cause of the system crashes.

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

    Please do not upload a very large Memory.dmp file.

    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... etc.), then choose to share those and get a share link.

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

    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.