how can i fix my bsod problem i keep getting the kernel mode heap corruption error code

Anonymous
2025-06-05T21:03:26+00:00

here is the mini dump file if anyone can help me figure out what my problem is

StartFragment 

8: 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, Type of corruption detected
Arg2: ffffb78449100380, Address of the heap that reported the corruption
Arg3: ffffb7845968dec0, Address at which the corruption was detected
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1531

    Key  : Analysis.Elapsed.mSec
    Value: 4621

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.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_17_nt!RtlpHeapHandleError

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

BUGCHECK_CODE:  13a

BUGCHECK_P1: 17

BUGCHECK_P2: ffffb78449100380

BUGCHECK_P3: ffffb7845968dec0

BUGCHECK_P4: 0

FILE_IN_CAB:  060525-7484-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb78450f46080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8083`b6c92408 fffff807`aa5ad528     : 00000000`0000013a 00000000`00000017 ffffb784`49100380 ffffb784`5968dec0 : nt!KeBugCheckEx
ffff8083`b6c92410 fffff807`aa5ad588     : 00000000`00000017 00000000`000002ef ffffb784`49100380 00000000`00000000 : nt!RtlpHeapHandleError+0x40
ffff8083`b6c92450 fffff807`aa2389e1     : ffffb784`59688000 ffffb784`49100380 00000000`00000000 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffff8083`b6c92480 fffff807`aa46c735     : fffff807`00000001 00000000`00000001 00000000`00000000 00000020`00000000 : nt!RtlpLogHeapFailure+0x45
ffff8083`b6c924b0 fffff807`aa328bf5     : ffffb784`59688000 00000000`000002c8 ffffb784`49100380 fffff807`aa2e69dd : nt!RtlpHpLfhReportError+0x21
ffff8083`b6c924f0 fffff807`aa328e88     : ffffb784`59688000 00000000`00000020 00000000`001002f5 000ffffb`78459688 : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x255
ffff8083`b6c92570 fffff807`aa433b42     : 00000000`00000007 00000000`001002f5 ffffb784`49100380 ffffb784`49102a80 : nt!RtlpHpLfhOwnerRunMaintenance+0x174
ffff8083`b6c925d0 fffff807`aa433c1f     : 00000000`00000000 fffff807`aa3a2be0 ffffb784`491002c0 ffff8083`b6c9278c : nt!RtlpHpLfhOwnerCompact+0xc2
ffff8083`b6c92750 fffff807`aa4338ef     : ffffb784`49100000 fffff807`aa433ca6 00010000`00000000 00000000`00000000 : nt!RtlpHpLfhOwnerCompact+0x19f
ffff8083`b6c928d0 fffff807`aa433825     : ffffb784`49100000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpLfhContextCompact+0xa3
ffff8083`b6c92910 fffff807`aa4337c3     : 00000000`00000001 00000000`00000000 00000000`00000001 ffffb784`50f460c0 : nt!RtlpHpHeapCompact+0x21
ffff8083`b6c92940 fffff807`aa473655     : 00000000`00000001 00000000`00000001 00000000`00000000 fffff807`aa30a4d8 : nt!ExpHpCompactHeapCallback+0x23
ffff8083`b6c92970 fffff807`aa4735b5     : 00000000`00000001 ffff8083`b6c92b00 ffffb784`49823ae0 ffffb784`49823ae0 : nt!ExpHpEnumerateHeaps+0x71
ffff8083`b6c929d0 fffff807`aa309e32     : ffffb784`50f46080 ffffb784`49823a00 00000000`00000000 ffffb784`00000000 : nt!ExpHpCompactionRoutine+0x15
ffff8083`b6c92a00 fffff807`aa45904a     : ffffb784`50f46080 ffffb784`50f46080 fffff807`aa309c80 ffffb784`49823ae0 : nt!ExpWorkerThread+0x1b2
ffff8083`b6c92bb0 fffff807`aa6741c4     : ffffa581`7a781180 ffffb784`50f46080 fffff807`aa458ff0 00000000`00030d40 : nt!PspSystemThreadStartup+0x5a
ffff8083`b6c92c00 00000000`00000000     : ffff8083`b6c93000 ffff8083`b6c8c000 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 0xffffb784496a6040; .thread 0xffffb78450f46080 ; 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
---------

EndFragment

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

47 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-06-05T22:35:18+00:00

    Hello my name is Jonathan, I'm here to help you with this problem.

    See if your computer is creating minidump files.

    To find these files, this is the path "C:\Windows\Minidump".

    First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud OneDrive.

    Choose to share or right click and get the share link.

    Please post the link to the ZIP file here so it can be reviewed.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2025-06-05T22:55:02+00:00

    060525-6640-01.zip

    there you go take a look at this for me

    Was this answer helpful?

    0 comments
  4. Jonathan Deives 81,795 Reputation points Independent Advisor
    2025-06-05T23:20:17+00:00

    The minidump files do not indicate any driver or hardware causes, only memory corruption.

    Test your RAM using memtest86 tool and see if any problem is found.

    This link has a tutorial on how to use and perform the test;

    https://www.tenforums.com/tutorials/14201-memte...

    ___________________________________________________________

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    ___________________________________________________________

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-06-05T23:41:38+00:00

    What does mem test do because no matter what I do I can’t seem to get rid of this bluescreen I’ve even reinstalled windows 3 times and still didn’t fix the problem I’ve also gone through troubleshooting about 4 times and the problem still persists

    Was this answer helpful?

    0 comments