Windows 10: Can someone please explain this dmp file to me. Thank you.

[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\LilJi\Desktop\dump files\032421-9812-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff806`25e00000 PsLoadedModuleList = 0xfffff806`26245e90Debug session time: Wed Mar 24 14:19:29.031 2021 UTC + 8:00System Uptime: 0 days 0:39:46.680Loading Kernel Symbols...........................................................................................................................................................................Loading User SymbolsLoading unloaded module list........For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff806`25fc3ab0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd87`be4296d0=000000000000011d1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************EVENT_TRACING_FATAL_ERROR 11dEvent Tracing subsystem has encountered an unexpected fatal error. First parameter indicatesthe type of failure.Arguments:Arg1: 0000000000000007, Trace buffer corruption.Arg2: ffff8688b42c8000Arg3: 0000000000001000Arg4: 0000000000009000Debugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6905 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 15799 Key : Analysis.Init.CPU.mSec Value: 1984 Key : Analysis.Init.Elapsed.mSec Value: 10434 Key : Analysis.Memory.CommitPeak.Mb Value: 78 Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1BUGCHECK_CODE: 11dBUGCHECK_P1: 7BUGCHECK_P2: ffff8688b42c8000BUGCHECK_P3: 1000BUGCHECK_P4: 9000BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: fffffd87`be4296c8 fffff806`25fe7448 : 00000000`0000011d 00000000`00000007 ffff8688`b42c8000 00000000`00001000 : nt!KeBugCheckExfffffd87`be4296d0 fffff806`25e12c32 : ffff8688`c2764202 00000000`00000000 ffff8688`b40ff000 00000000`00000000 : nt!EtwpDequeueFreeBuffer+0x1d4634fffffd87`be429720 fffff806`25ec654f : ffff8688`c2010f60 ffff8688`b40ff000 00000000`00000fe8 ffffcc00`cd5a0180 : nt!EtwpSwitchBuffer+0x32fffffd87`be429780 fffff806`25ec5ebb : 00000003`01010000 00000000`00000000 00000000`00000000 fffffd87`be429848 : nt!EtwpReserveTraceBuffer+0x1affffffd87`be429810 fffff806`25f12963 : 00000000`00000000 ffff8688`b2fde000 00000000`00000000 00000000`00000002 : nt!EtwpLogKernelEvent+0x1ebfffffd87`be4298c0 fffff806`25ec689b : ffff8688`c2b4d5b0 00000000`00000002 00000000`00000080 ffff8688`b7db4010 : nt!EtwTraceTimedEvent+0xd3fffffd87`be429940 fffff806`25ec5479 : 00000000`0000001e 00000000`00989680 00000000`000163a4 00000000`000000bc : nt!KiProcessExpiredTimerList+0x2ebfffffd87`be429a30 fffff806`25fc75de : ffffffff`00000000 ffffcc00`cd5a0180 ffffcc00`cd5b1140 ffff8688`c2b80080 : nt!KiRetireDpcList+0x4e9fffffd87`be429c60 00000000`00000000 : fffffd87`be42a000 fffffd87`be424000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7eSYMBOL_NAME: nt!EtwpDequeueFreeBuffer+1d4634MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]nt[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.18362.1440STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1d4634FAILURE_BUCKET_ID: 0x11D_nt!EtwpDequeueFreeBufferOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {0e9c61c7-de70-385f-fe47-c57c1696e765}Followup: MachineOwner---------[/COLOR]

:)

 

Help reading mini dmp file

Download BlueScreenView, unpack the ZIP, and run the EXE (no installation necessary). It's an excellent little utility for looking at DMP files and finding the cause of crashes.

 

Help reading mini dmp file

look at post #6 , *Toast :toast:

 

How to view non-Windows .dmp files?

Ah...!
Many thanks. I wasn't aware of that option.
Though, in my case, regretfully it makes no difference: after changing the folder, no dmp file list was displayed.
When selecting a single .dmp file (also in the advanced options), nothing was displayed either.

Not sure... but there is a line in the advanced options reading
"%programfiles%\Debugging Tools for Windows\DumpChk.exe" "%1"

I've searched for the dumpchk.exe, but it is not on my system, so maybe that is the reason..?