How d i understand what the dmp file says?

Question

Arguments:
Arg1: 0000000000000098, 
Arg2: 00000000006b35a1
Arg3: 000000000040005e
Arg4: 00000000006b35a1

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 875

    Key  : Analysis.Elapsed.mSec
    Value: 3855

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x4e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x4e

    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: 0x4E_98_nt!MiReplenishPageSlist

    Key  : Failure.Hash
    Value: {ea55319d-b4e8-e64e-0a29-51e8e4bbf98d}

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


BUGCHECK_CODE:  4e

BUGCHECK_P1: 98

BUGCHECK_P2: 6b35a1

BUGCHECK_P3: 40005e

BUGCHECK_P4: 6b35a1

FILE_IN_CAB:  020726-14562-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffde89dd8be080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WerFault.exe

STACK_TEXT:  
ffffdc0d`9dad9498 fffff803`bbcf3fba     : 00000000`0000004e 00000000`00000098 00000000`006b35a1 00000000`0040005e : nt!KeBugCheckEx
ffffdc0d`9dad94a0 fffff803`bbaa5349     : ffff920c`00004300 ffff920c`00000000 ffffdc0d`9dad9711 ffffdc0d`9dad95e0 : nt!MiReplenishPageSlist+0x7ea
ffffdc0d`9dad95a0 fffff803`bbaa39c9     : ffffc781`33b00000 00000000`00000005 ffffdc0d`9dad97b0 00000000`000700a1 : nt!MiGetPerfectColorHeadPage+0x579
ffffdc0d`9dad96b0 fffff803`bbaac334     : 00000000`80000004 fffff803`bc637ec0 ffffde89`dc88d080 00000000`00000039 : nt!MiGetPage+0x3f9
ffffdc0d`9dad9800 fffff803`bbaadab1     : 00000000`00000000 00000000`00000000 ffffdc0d`9dad99b0 ffffdc0d`9dad9e60 : nt!MiGetPageChain+0x154
ffffdc0d`9dad98b0 fffff803`bbaabc66     : 05560001`00000009 00000000`00000000 ffffffff`ffffffff fffff803`bc637ec0 : nt!MiResolvePrivateZeroFault+0x621
ffffdc0d`9dad9a70 fffff803`bbb2ae5e     : ffffdc0d`9dad9db0 ffffdc0d`9dad9d10 fffff1e3`c099d808 00000000`00000000 : nt!MiResolveDemandZeroFault+0x246
ffffdc0d`9dad9c10 fffff803`bbb2cf36     : ffffc781`33b0005f ffff8000`00000000 ffffc781`33b01ffa 0000007f`fffffff8 : nt!MiDispatchFault+0x5ee
ffffdc0d`9dad9d80 fffff803`bbeb12cb     : ffffde89`00000000 00000000`00002000 ffffc781`33b00000 ffffde89`5b426760 : nt!MmAccessFault+0x226
ffffdc0d`9dad9ef0 fffff803`bbbab7b9     : 00000000`00000002 fffff803`bbbabd46 00000000`00000000 ffffc781`33b00000 : nt!KiPageFault+0x38b
ffffdc0d`9dada080 fffff803`bbbabb30     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc781`05000140 : nt!RtlpHpSegSegmentInitialize+0x99
ffffdc0d`9dada0d0 fffff803`bbbab883     : 00000000`0005511c ffffdc0d`9dada2c0 00000000`00000056 fffff803`bc638b00 : nt!RtlpHpSegPageRangeAllocate+0x14c
ffffdc0d`9dada120 fffff803`bbbab80d     : 00000000`0005511c fffff803`bc6eeb00 00000000`00000000 ffffc781`33b00000 : nt!RtlpHpSegAlloc+0x67
ffffdc0d`9dada180 fffff803`bba5e011     : 00000000`00000001 00000010`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpAllocateHeapBackend+0x2d
ffffdc0d`9dada1c0 fffff803`bba5d8a2     : ffffde8a`3a3dd300 ffffdc0d`9dadaaa0 00000000`324e6f49 00000000`00000000 : nt!ExAllocateHeapPool+0x701
ffffdc0d`9dada450 fffff803`bc36818d     : 00000000`00000100 ffffdc0d`9dadaaa0 00000000`00000000 fffff803`bc1a9fc7 : nt!ExpAllocatePoolWithTagFromNode+0x52
ffffdc0d`9dada490 fffff803`bc168211     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdc0d`9dada910 : nt!ExAllocatePool2+0x9d
ffffdc0d`9dada540 fffff803`bc169ea6     : ffffde8a`14bc48c0 00000000`00000000 00000000`00000000 0000024d`9763dcd8 : nt!IopQueryNameInternal+0x551
ffffdc0d`9dada630 fffff803`bc16951d     : 00038664`00004550 00000000`68a7f420 202200f0`00000000 00000000`000b020b : nt!IopQueryName+0x26
ffffdc0d`9dada680 fffff803`bc1869e4     : ffffde8a`14bc48c0 0000024d`9763dcd8 00000000`0005511c ffffdc0d`9dada828 : nt!ObQueryNameStringMode+0x15d
ffffdc0d`9dada7e0 fffff803`bc185d95     : ffffde89`dd8be080 00007ffe`f2080080 0000005c`19eef5e0 0000005c`19eef588 : nt!MmQueryVirtualMemory+0xc34
ffffdc0d`9dada960 fffff803`bbeb5755     : 00000000`00000000 0000024d`9763dcc0 ffffdc0d`9dadaaa0 00007ffe`f2080000 : nt!NtQueryVirtualMemory+0x25
ffffdc0d`9dada9b0 00007fff`3f542024     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000005c`19eef708 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`3f542024


SYMBOL_NAME:  nt!MiReplenishPageSlist+7ea

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.7623

STACK_COMMAND: .process /r /p 0xffffde89dc88d080; .thread 0xffffde89dd8be080 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  7ea

FAILURE_BUCKET_ID:  0x4E_98_nt!MiReplenishPageSlist

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ea55319d-b4e8-e64e-0a29-51e8e4bbf98d}

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

Answer 1

Hi Blank ISme,

Welcome to Microsoft Q&A!

Thanks for sharing the dump, and sorry if you’re hitting BSODs.

For file dump analyze, you can try using WinDbg to analyze the dump file. Here are the steps that you can follow to get WinDbg work on this:

• First, install WinDbg
• Open WinDbg as Administrator: Run WinDbg with administrator privileges to analyze system-level dump files.
• Open Dump File: Click on the File menu, select Start debugging, and then Open dump file. Browse to the location of the dump file and open it.
• To analyze the Dump File: Type !analyze -v in the command line and press Enter. This command will analyze the dump file and display verbose information in the Command tab.

Now, I will entangle each piece of data from this so you can better understand what it means. Here are the key details from your dump:

• PROCESS_NAME: WerFault.exe the process triggered the event.
• Calls are in ntkrnlmp.exe, meaning the failure is low-level (memory)
• FAILURE_BUCKET_ID: 0x4E_98_nt!MiReplenishPageSlist: The crash occurred while Windows was trying to manage free physical memory pages.

That pattern usually means RAM corruption or a kernel‑mode driver scribbling over memory; less commonly it’s file‑system/NTFS side effects. Here are some suggestions on what you can do next:

1. Run a full Windows Memory Diagnostic (extended mode)
   1. Press Start > type mdsched > choose Restart now and check for problems.
   2. For a deeper check, try a third-party RAM testing tool (e.g. MemTest86).
2. Check disk and file system health
   1. Press Win + X > Terminal (Admin) > run the commands below.
   2. chkdsk /scan
   3. DISM /online /cleanup-image /restorehealth
   4. sfc /scannow

   Disclaimer: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, do not cancel or interrupt chkdsk, and back up important data. More information please refer to this chkdsk | Microsoft Learn. 

3. If the crashes started after installing something recently, it may be writing bad memory. Consider uninstalling it/them to see if the situation improves.
4. If XMP/EXPO/undervolting is enabled, try running at the default JEDEC frequency to test stability.

If you'd like, you can paste more lines above the bugcheck or/and share when exactly the crash happens (during any specific actions or application uses), and I can narrow it down further. If there's anything you want to understand more, feel free to ask!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.