[SOLVED] CRITICAL_PROCESS_DIED

Mar 31, 2022
7
0
10
Full dump https://www.mediafire.com/file/kcqhwv49bp5o46h/critical.rar/file

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2733

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 9343

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

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

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

    Key  : CriticalProcessDied.ExceptionCode
    Value: ca644080

    Key  : CriticalProcessDied.ImageName
    Value: ntdll.dll

    Key  : CriticalProcessDied.ImageOffset
    Value: ff249

    Key  : CriticalProcessDied.ImageSize
    Value: 1f5000

    Key  : CriticalProcessDied.ImageTimestamp
    Value: 1be73aa8

    Key  : CriticalProcessDied.Process
    Value: svchost.exe

    Key  : CriticalProcessDied.Symbol
    Value: ntdll.dll!RtlReportFatalFailure

    Key  : CriticalProcessDied.WERReportId
    Value: db062956-75de-4ce3-b7fe-a91f4867e564

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  033122-7078-01.dmp

BUGCHECK_CODE:  ef

BUGCHECK_P1: ffff818ec7e06280

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

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

CRITICAL_PROCESS_REPORTGUID:  {db062956-75de-4ce3-b7fe-a91f4867e564}

IMAGE_NAME:  ntdll.dll

MODULE_NAME: ntdll

FAULTING_MODULE: 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
fffff68f`04b5d938 fffff803`33d086d2     : 00000000`000000ef ffff818e`c7e06280 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff68f`04b5d940 fffff803`33c0fceb     : 00000000`00000000 fffff803`336fd8ad 00000000`00000002 fffff803`336fcec7 : nt!PspCatchCriticalBreak+0x10e
fffff68f`04b5d9e0 fffff803`33ab58b4     : ffff818e`00000000 00000000`00000000 ffff818e`c7e06280 ffff818e`c7e066b8 : nt!PspTerminateAllThreads+0x15ab6f
fffff68f`04b5da50 fffff803`33ab5bdc     : ffff818e`c7e06280 00000000`00000000 00000000`00000000 fffff68f`04b5dae8 : nt!PspTerminateProcess+0xe0
fffff68f`04b5da90 fffff803`33808fb8     : ffff818e`c7e06280 ffff818e`ca644080 fffff68f`04b5db80 ffffffff`f70f2e80 : nt!NtTerminateProcess+0x9c
fffff68f`04b5db00 00007ff8`9c50d2f4     : 00007ff8`9c56f290 00007ff8`9c5bffd4 000000cc`01b7eeb0 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000cc`01b7ded8 00007ff8`9c56f290     : 00007ff8`9c5bffd4 000000cc`01b7eeb0 00000000`00000000 00000000`00000000 : 0x00007ff8`9c50d2f4
000000cc`01b7dee0 00007ff8`9c5bffd4     : 000000cc`01b7eeb0 00000000`00000000 00000000`00000000 00000000`000ff249 : 0x00007ff8`9c56f290
000000cc`01b7dee8 000000cc`01b7eeb0     : 00000000`00000000 00000000`00000000 00000000`000ff249 00007ff8`9c4fc766 : 0x00007ff8`9c5bffd4
000000cc`01b7def0 00000000`00000000     : 00000000`00000000 00000000`000ff249 00007ff8`9c4fc766 00007ff8`9c5ed200 : 0x000000cc`01b7eeb0


STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_ca644080_ntdll.dll!RtlReportFatalFailure_IMAGE_ntdll.dll

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4695ea8e-07f0-249c-e856-854ae2ff0099}

Followup:     MachineOwner
---------
 
Solution
right click start button
choose powershell (admin)
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth and press enter
Then type SFC /scannow and press enter

First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

critical process died is a System file specific error, can only happen to Microsoft files. Doesn't mean they are the cause
nt.dll appears to be what caused the crash. Microsoft files don't normally cause crashes.

what are specs of the PC?
right click start button
choose powershell (admin)
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth and press enter
Then type SFC /scannow and press enter

First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

critical process died is a System file specific error, can only happen to Microsoft files. Doesn't mean they are the cause
nt.dll appears to be what caused the crash. Microsoft files don't normally cause crashes.

what are specs of the PC?
 
  • Like
Reactions: Niydayoltu
Solution
Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/z3st6frp/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:033122-7078-01.dmp (Mar 31 2022 - 07:01:55)
Bugcheck:CRITICAL_PROCESS_DIED (EF)
Probably caused by:memory_corruption (Process running at time of crash: svchost.exe)
Uptime:1 Day(s), 17 Hour(s), 25 Min(s), and 40 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/B450-TOMAHAWK-MAX
You are using the latest stable BIOS available. I recommend avoiding BETAs.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
  • Like
Reactions: Niydayoltu