CRITICAL_PROCESS_DIED

Question

So basically, while i was just browsing around internet, my pc froze.

I cant do anything and the only way to use it is to restart it again.

And i tried looking at the minidump file, analyzed it with Windbg, this is the result;

CRITICAL_PROCESS_DIED (ef) A critical system process died Arguments: Arg1: ffffb50d8bc92080, 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: 5093

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 27818

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

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

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

Key  : CriticalProcessDied.ExceptionCode
Value: 8f69f080

Key  : CriticalProcessDied.Process
Value: svchost.exe

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: 051722-32593-01.dmp

BUGCHECK_CODE: ef

BUGCHECK_P1: ffffb50d8bc92080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: svchost.exe

CRITICAL_PROCESS: svchost.exe

EXCEPTION_RECORD: 0000000000001000 -- (.exr 0x1000) Cannot read Exception record @ 0000000000001000

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

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffff980afb20cd88 fffff8015f3085d2 : 00000000000000ef ffffb50d8bc92080 0000000000000000 0000000000000000 : nt!KeBugCheckEx ffff980afb20cd90 fffff8015f1edeb9 : 0000000000000001 fffff8015ed591c1 0000000000000002 fffff8015ed590eb : nt!PspCatchCriticalBreak+0x10e ffff980afb20ce30 fffff8015f0f6320 : ffffb50d00000000 0000000000000000 ffffb50d8bc92080 ffffb50d8bc924b8 : nt!PspTerminateAllThreads+0x20df2d ffff980afb20cea0 fffff8015f0f611c : ffffb50d8bc92080 0000000000000001 ffffffffffffffff 0000000000000000 : nt!PspTerminateProcess+0xe0 ffff980afb20cee0 fffff8015ee096b8 : ffffb50d8bc92080 ffffb50d8f69f080 ffff980afb20cfd0 fffff8015f121b92 : nt!NtTerminateProcess+0x9c ffff980afb20cf50 fffff8015edfbbc0 : fffff8015ee586c1 ffff980afb20da58 ffff980afb20da58 ffffffffffffffff : nt!KiSystemServiceCopyEnd+0x28 ffff980afb20d0e8 fffff8015ee586c1 : ffff980afb20da58 ffff980afb20da58 ffffffffffffffff 00007ffe8c3b3228 : nt!KiServiceLinkage ffff980afb20d0f0 fffff8015ee09dac : 0000000000001000 ffff980afb20db00 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x17c491 ffff980afb20d920 fffff8015ee05f43 : 00007ffe8d8e13a8 ffffb50d00000000 ffff980afb20db80 ffffb50d00000000 : nt!KiExceptionDispatch+0x12c ffff980afb20db00 00007ffe8d8e124e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x443 0000009ae8780e70 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`8d8e124e

SYMBOL_NAME: nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1706

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_8f69f080_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dda8430b-c01c-0022-2cfe-833f51d7fa64}

Followup: MachineOwner

What should i do?

Answer 1

Hi Ushier

Okay, please wait for your system to crash a couple more times, then upload any newly created minidump files, and I will analyze those for you.

Answer 2

This is a recurring problem, since last year i believe. It comes to the point where i cant boot into windows anymore, so i had to reinstall it. After that i replaced my motherboard because i thought i had bad ports. And after 2 weeks of replacing it, i then got a blue screen again, and reinstalled it. Since windows reinstallation, this freezing happened couple of times but i only had 1 minidump.

Answer 3

Hi Ushier

Your minidump files just indicate memory (RAM) corruption no specific driver is listed

Was this a one-time crash, or is this a recurring issue?

1

If this was a one-time crash, most likely, Windows was updating drivers in the background, and that caused a temporary incompatibility, there is nothing further you need to do

2

If this is a recurring problem, do you have any more minidump files you can upload for analysis?

Answer 4

Hello, thank you for the reply. This is the Minidump zipped up.

https://drive.google.com/file/d/1_6PE8KlMDTvvS8Ckw2tjp3M3K99Ea9Lo/view?usp=sharing

Answer 5

Hi Ushier,

I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.