How to fix event 1801 de TPM-WMI (uploaded the dump file)

Pancho Loewen 0 Reputation points
2025-11-28T21:23:34.5666667+00:00 
************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- 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.29457.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Users\CS-1242\Desktop\SAUL\112825-11890-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 (28 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`b3c00000 PsLoadedModuleList = 0xfffff806`b4af5030
Debug session time: Fri Nov 28 14:42:25.708 2025 (UTC - 6:00)
System Uptime: 1 days 6:23:24.900
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:
fffff806`b40f6880 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe48a`a69af3a0=000000000000013a
10: kd> !analyze -v
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
.............
*******************************************************************************
*                                                                             *
*                        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: ffffe78f91100340, Address of the heap that reported the corruption
Arg3: ffffe78fa4da36e0, Address at which the corruption was detected
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1078

    Key  : Analysis.Elapsed.mSec
    Value: 1079

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29457.1000

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.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: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

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


BUGCHECK_CODE:  13a

BUGCHECK_P1: 17

BUGCHECK_P2: ffffe78f91100340

BUGCHECK_P3: ffffe78fa4da36e0

BUGCHECK_P4: 0

FILE_IN_CAB:  112825-11890-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe78fb4802080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffe48a`a69af398 fffff806`b41e5894     : 00000000`0000013a 00000000`00000017 ffffe78f`91100340 ffffe78f`a4da36e0 : nt!KeBugCheckEx
ffffe48a`a69af3a0 fffff806`b41e58f4     : 00000000`00000017 00000000`0000023a ffffe78f`91100340 00000000`00004000 : nt!RtlpHeapHandleError+0x40
ffffe48a`a69af3e0 fffff806`b3e9ce31     : 00000000`00000217 000ffffe`78fa4d84 00000000`02000103 00000000`00000000 : nt!RtlpHpHeapHandleError+0x58
ffffe48a`a69af410 fffff806`b3fe43de     : ffffe78f`5f1fb3c8 00000000`00000010 00000000`00000002 00000000`00000002 : nt!RtlpLogHeapFailure+0x45
ffffe48a`a69af440 fffff806`b3fe3eab     : 00000000`00000007 00000000`000000f0 00000000`0012021b 000ffffe`78fa4d84 : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x2be
ffffe48a`a69af4c0 fffff806`b3f9f89a     : 00000000`00000007 00000000`0012021b ffffe78f`91100340 ffffe78f`91103cc0 : nt!RtlpHpLfhOwnerRunMaintenance+0x14b
ffffe48a`a69af520 fffff806`b3f9f9b9     : 00000000`00000000 ffffe78f`91103cc0 ffffe78f`91103cc0 ffffe48a`a69af6d0 : nt!RtlpHpLfhOwnerCompact+0xbe
ffffe48a`a69af6a0 fffff806`b3f9faf3     : 00000000`00000000 ffffe78f`911041c0 ffff14b2`292b3446 00000000`00000000 : nt!RtlpHpLfhOwnerCompact+0x1dd
ffffe48a`a69af820 fffff806`b3f9f465     : ffffe78f`91100000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpLfhContextCompact+0xa3
ffffe48a`a69af860 fffff806`b3f9f403     : 00000000`00000001 00000000`00000000 00000000`00000001 ffffe78f`b48021c0 : nt!RtlpHpHeapCompact+0x21
ffffe48a`a69af890 fffff806`b4081875     : 00000000`00000001 00000000`00000001 00000000`00000000 ffffe48a`a69af910 : nt!ExpHpCompactHeapCallback+0x23
ffffe48a`a69af8c0 fffff806`b40817d5     : 00000000`00000001 ffffe48a`a69afa50 ffffe78f`91802ae0 ffffe78f`91802ae0 : nt!ExpHpEnumerateHeaps+0x71
ffffe48a`a69af920 fffff806`b3edb8ac     : ffffe78f`b4802080 ffffe48a`a69afa00 ffffe78f`91802a00 fffff806`b40d8a70 : nt!ExpHpCompactionRoutine+0x15
ffffe48a`a69af950 fffff806`b40815ea     : ffffe78f`b4802080 ffffe78f`b4802080 fffff806`b3edb2c0 ffffe78f`91802ae0 : nt!ExpWorkerThread+0x5ec
ffffe48a`a69afb30 fffff806`b429fd74     : ffff9f01`eb1a0180 ffffe78f`b4802080 fffff806`b4081590 ffffe78f`c0924910 : nt!PspSystemThreadStartup+0x5a
ffffe48a`a69afb80 00000000`00000000     : ffffe48a`a69b0000 ffffe48a`a69a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!RtlpHeapHandleError+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.7171

STACK_COMMAND: .process /r /p 0xffffe78f914c9040; .thread 0xffffe78fb4802080 ; 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
---------
Windows for home | Windows 10 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. JC 8,235 Reputation points Independent Advisor
    2025-11-28T22:02:00.24+00:00

    Hello,

    This error seems to be related to TPM and secureboot, follow this guide on how to enable them both through your bios if it’s available, if you’re using a computer that doesn’t support TPM and secureboot the options won’t be available.

    How to enable TPM 2.0 and Secure Boot for Windows 11

    Hope this helps,

    JC

    Was this answer helpful?

    0 comments

  2. AI answer

    2025-11-28T21:23:44.28+00:00

    The event 1801 related to TPM-WMI typically indicates an issue with the Trusted Platform Module (TPM) on your system. The dump file analysis shows a bugcheck code of KERNEL_MODE_HEAP_CORRUPTION (13a), which suggests that there is corruption in the kernel mode heap. This can be caused by various factors, including faulty drivers, hardware issues, or memory corruption.

    Here are some steps you can take to troubleshoot and potentially fix this issue:

    1. Update Drivers: Ensure all your device drivers, especially for hardware related to TPM, are up to date. You can do this through Device Manager or by visiting the manufacturer's website.
    2. Check for Windows Updates: Make sure your Windows operating system is fully updated, as updates can include fixes for known issues.
    3. Run Memory Diagnostics: Use the Windows Memory Diagnostic tool to check for memory issues that could be causing heap corruption. You can access this by typing mdsched.exe in the Run dialog (Win + R).
    4. Check Disk for Errors: Run a disk check to ensure there are no file system errors. You can do this by running chkdsk /f in an elevated command prompt.
    5. Inspect Event Viewer: Look in the Event Viewer for any additional errors or warnings that could provide more context about the issue. Focus on the System and Application logs.
    6. Disable TPM: If the issue persists and you do not require TPM for your applications, consider disabling it in the BIOS/UEFI settings as a temporary measure to see if it resolves the crashes.
    7. Consult Microsoft Documentation: For more detailed analysis and troubleshooting steps, refer to Microsoft’s documentation on debugging kernel mode crashes and analyzing crash dump files.

    If these steps do not resolve the issue, you may need to consider further hardware diagnostics or consult with a professional technician for a more in-depth analysis.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.