How to interpret ntkrnlmp.exe crash report results after BSOD

Question

Hello, I get somewhat frequent BSOD crashes, this has happened since I built this PC and installed Windows 11. These sometimes happen on startup, before the login screen. The most recent results I have using WinDbg point to a CRITICAL PROCESS DIED error with NT / ntkrnlmp.exe. See below for results.

Is there any way to determine what is causing this error? I searched online, it can be related to RAM or the power supply etc, is there a way to narrow down the results?

Thank you.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff95081d9c10c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffff95081d9c10c0, The process object that initiated the termination.
Arg4: 0000000000000000, Additional triage data.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1890

    Key  : Analysis.Elapsed.mSec
    Value: 1902

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key  : Bugcheck.Code.TargetModel
    Value: 0xef

    Key  : CriticalProcessDied.ExceptionCode
    Value: 0x38a57080

    Key  : CriticalProcessDied.Process
    Value: svchost.exe

    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: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_38a57080_nt!PspCatchCriticalBreak

    Key  : Failure.Hash
    Value: {7c014cb4-0a97-cef3-7d7d-d2620e89c9cf}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

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


BUGCHECK_CODE:  ef

BUGCHECK_P1: ffff95081d9c10c0

BUGCHECK_P2: 0

BUGCHECK_P3: ffff95081d9c10c0

BUGCHECK_P4: 0

FILE_IN_CAB:  111125-7953-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff950838a57080

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

ERROR_CODE: (NTSTATUS) 0x38a57080 - <Unable to get error code text>

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

STACK_TEXT:  
ffffb600`4f96f8b8 fffff806`b0b67340     : 00000000`000000ef ffff9508`1d9c10c0 00000000`00000000 ffff9508`1d9c10c0 : nt!KeBugCheckEx
ffffb600`4f96f8c0 fffff806`b0cc94ff     : ffff9508`1d9c10c0 00000000`00000000 00000000`00000000 fffff806`b0885ce1 : nt!PspCatchCriticalBreak+0x128
ffffb600`4f96f960 fffff806`b0d0364f     : ffff9508`1d9c10c0 ffff9508`1d9c1288 ffff9508`1d9c10c0 00000000`00000000 : nt!PspTerminateAllThreads+0x27b
ffffb600`4f96f9e0 fffff806`b0e6866a     : ffff9508`1d9c10c0 00000000`00000001 ffff9508`38a57080 ffff9508`1d9c10c0 : nt!PspTerminateProcess+0xf7
ffffb600`4f96fa20 fffff806`b0ab1455     : ffff9508`1d9c10c0 ffff9508`38a57080 01dc4ebf`a5caeea1 000f0000`0000004f : nt!NtTerminateProcess+0xca
ffffb600`4f96faa0 00007ffa`8d882174     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000002c`c337cb98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`8d882174


SYMBOL_NAME:  nt!PspCatchCriticalBreak+128

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.6899

STACK_COMMAND: .process /r /p 0xffff95081d9c10c0; .thread 0xffff950838a57080 ; kb

BUCKET_ID_FUNC_OFFSET:  128

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_38a57080_nt!PspCatchCriticalBreak

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7c014cb4-0a97-cef3-7d7d-d2620e89c9cf}

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

Answer 1

The error you're encountering, CRITICAL_PROCESS_DIED (ef), indicates that a critical system process has unexpectedly terminated. In your case, the crash report points to svchost.exe, which is a generic host process name for services that run from dynamic-link libraries (DLLs). Here are some steps you can take to narrow down the cause of this error:

1. Check for Recent Changes: If you have recently installed new hardware or software, consider removing or updating them to see if the issue persists.
2. Driver Updates: Ensure that all your device drivers are up to date. Outdated or incompatible drivers can often lead to system crashes.
3. Memory Check: Since you mentioned RAM, run the Windows Memory Diagnostics tool to check for memory issues. Faulty RAM can cause critical process failures.
4. Power Supply: If your power supply is insufficient or failing, it can lead to system instability. Ensure that your power supply meets the requirements for your hardware.
5. Event Viewer: Use the Event Viewer to check for any critical errors or warnings that occurred around the time of the crash. This can provide additional context on what might be causing the issue.
6. System File Checker: Run the System File Checker tool (sfc /scannow) to repair any corrupted system files that might be contributing to the problem.
7. Analyze Crash Dumps: If you are comfortable with it, you can analyze the crash dump files using debugging tools like WinDbg to get more insights into the crash.
8. Check for Malware: Run a full system scan with a reputable antivirus program to rule out malware as a potential cause of the crashes.

By following these steps, you should be able to narrow down the potential causes of the CRITICAL_PROCESS_DIED error and take appropriate actions to resolve it.

Answer 2

Hi, I'm Bernard, a fellow Windows user. I'm happy to help!

As per checking the logs you have, it is only displaying a general error on the PC. In this case, can you please upload and share all the Minidump files on the affected device so I can further examine the root cause of the issue?

 

Press Windows key + E (To open File Explorer)

 

Click "This PC" > then follow the file path:

 

C:\Windows\Minidump

 

Copy the Minidump files and save them to another location, like the Desktop or Documents.

 

Then please upload it to Cloud storage like OneDrive or any cloud storage you are using, and please share the shareable link here.

To upload and share the link using OneDrive:

Go to this link: https://onedrive.live.com/, then upload the file.

Then, provide the shareable link by following the steps from this link: https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07