BSOD - Continous. Culprit may be: ntdll.dll - csrss.exe - cng.sys

Asger 1 Reputation point
2021-04-29T11:24:19.027+00:00

Hi everyone,

I have recently started getting BSOD when starting up my pc. It only happens when I startup the pc after several hours of having it shut off - then it restarts and then there is no problem at all.

I get 2 kinds of BSOD:
CRITICAL_PROCESS_DIED
KERNEL_DATA_INPAGE_ERROR

I have tried alot of different kinds of solutions to no avail. System restore. Reinstalled windwos. Update windows. Cheching individual drivers if they needed update. sfc/scannow. CHKDSK. I also ran a memtest86 a couple of days ago with 0 errors reported.
sfc/scannow reported that there were corrupted files but they were fixed - but I still get BSOD.

I have saved 4 of my latest MINIDUMP files and attached them here: https://we.tl/t-A5jHgKuIfQ

Here is the latest minidump:

8: kd> !analyze -v


  • *
  • Bugcheck Analysis *
  • *

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

Debugging Details:


KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2124

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2130

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

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

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

Key  : CriticalProcessDied.ExceptionCode
Value: 5f8c1080

Key  : CriticalProcessDied.ImageName
Value: ntdll.dll

Key  : CriticalProcessDied.ImageOffset
Value: 1e312

Key  : CriticalProcessDied.ImageSize
Value: 1f0000

Key  : CriticalProcessDied.ImageTimestamp
Value: 48069cf7

Key  : CriticalProcessDied.Process
Value: csrss.exe

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

Key  : CriticalProcessDied.WERReportId
Value: 10dfb473-939b-4568-8fc0-5879f016851a

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffb4836ffda4c0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: csrss.exe

CRITICAL_PROCESS: csrss.exe

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

CRITICAL_PROCESS_REPORTGUID: {10dfb473-939b-4568-8fc0-5879f016851a}

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:
ffff84040377f838 fffff80025ac9f49 : 00000000000000ef ffffb4836ffda4c0 0000000000000000 0000000000000000 : nt!KeBugCheckEx
ffff84040377f840 fffff800259a1bcb : ffffb4836ffda4c0 fffff80025315635 ffffb4836ffda4c0 fffff800252ec288 : nt!PspCatchCriticalBreak+0x115
ffff84040377f8e0 fffff800257b7a0c : ffffb48300000000 0000000000000000 ffffb4836ffda4c0 ffffb4836ffda4c0 : nt!PspTerminateAllThreads+0x1e7f6f
ffff84040377f950 fffff800258ce4c9 : ffffffffffffffff ffff84040377fa80 ffffb4836ffda4c0 ffff84040377f901 : nt!PspTerminateProcess+0xe0
ffff84040377f990 fffff800253d5455 : ffffb48300000f08 ffffb4835f8c1080 ffffb4836ffda4c0 0000000000000000 : nt!NtTerminateProcess+0xa9
ffff84040377fa00 00007ffe5d95d424 : 00007ffe5a758301 0000000000000000 0000000000000000 ffffffffee1e5d00 : nt!KiSystemServiceCopyEnd+0x25
00000026fb73c128 00007ffe5a758301 : 0000000000000000 0000000000000000 ffffffffee1e5d00 000000000000036c : 0x00007ffe5d95d424 00000026fb73c130 0000000000000000 : 0000000000000000 ffffffffee1e5d00 000000000000036c 0000000000000000 : 0x00007ffe5a758301

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_5f8c1080_ntdll.dll!RtlLookupFunctionEntry_IMAGE_ntdll.dll

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3f218d25-c7d0-038a-d7c9-ff3db378ecb6}

Followup: MachineOwner


Thank you in advance!

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,844 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Carl Fan 6,861 Reputation points
    2021-04-30T09:16:35.41+00:00

    Hi,
    What's your system version and OS build? Type "winver" in Search Bar to check. The latest version is April 22, 2021—KB5001396 (OS Build 18363.1533). Try to update to check.
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died
    Also I see you have tried to reinstall system. If this is a brand new system and no other software was installed, did it also be blue screen?
    Type "msconfig" in Search Bar. Select "service" option, hide all microsoft service, then disable no microsoft service to check.
    Please understand due to security policy, we could not provide dump/log analysis. In addition, if this problem is more urgent for you I still recommend that you open a case to Microsoft for further professional help.
    https://support.microsoft.com/en-us/help/4341255/support-for-busines
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    0 comments No comments

  2. Igor Gaellean 0 Reputation points
    2024-12-15T22:07:44.6633333+00:00

    Hello! Had the same problem (CRITICAL_PROCESS_DIED) since 21st November 2024, solved today. If the solutions with sfc /scannow and DISM did not work for your case, try running CPU stress tests with OCCT. There really may be a hardware problem. Mine apparently was a dead CPU cooler fan leading to overheating and unstable behavior of physical core #0.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.