Startup BSOD - Critical Process Died - Repair failed

Hey all,

My friends computer is getting this error on boot. He brought it to me back in October with the same error, and after trying a handful of things to repair, restore, etc., I wound up re-installing Windows 10.

It worked fine for a few months, but now it is back at it again.

I booted the machine this afternoon using Hiren's boot cd, an old trick left over from my days as a computer repair guy in the early 2000's (not what I do these days at all). Anyways, I ran a few hard drive scans which seemed to tell me that there is nothing wrong with the hard drive.

I'm reluctant to just reload windows yet again given he further symptoms. I did manage to grab the event logs and check them out from a working computer, but they are not really telling me that much unfortunately.

Any advice greatly appreciated!!

musiclover7 said:

Hey all,

My friends computer is getting this error on boot. He brought it to me back in October with the same error, and after trying a handful of things to repair, restore, etc., I wound up re-installing Windows 10.

It worked fine for a few months, but now it is back at it again.

I booted the machine this afternoon using Hiren's boot cd, an old trick left over from my days as a computer repair guy in the early 2000's (not what I do these days at all). Anyways, I ran a few hard drive scans which seemed to tell me that there is nothing wrong with the hard drive.

I'm reluctant to just reload windows yet again given he further symptoms. I did manage to grab the event logs and check them out from a working computer, but they are not really telling me that much unfortunately.

Any advice greatly appreciated!!

Attention: XXXXXXX

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 10 Blue Screen Of Death problems in this section.

How do I gather the requested information when I cannot boot into windows either in regular or safe mode? Meaning, the tools seem to require that I run them on a working system, but my system will not boot up at all.

I did manage to pull the hard drive and extract the .dmp file from the C:\Windows directory. Uploading that here.

Let me know if there is something else I can/should do. Thanks!!

axe0 said:

What further symptoms are there?

Well, I reinstalled windows in October, and here I am again, back at the Blue-Screen problem. The further symptoms are that the initial reload of Windows did not fix the problem, or at least not for long.

I found a bios update (This laptop was 4 versions behind) and applied it, then reloaded Windows 10. Applied all the latest drivers from Lenovo for this device. Fingers crossed.

musiclover7 said:

Well, I reinstalled windows in October, and here I am again, back at the Blue-Screen problem. The further symptoms are that the initial reload of Windows did not fix the problem, or at least not for long.

I found a bios update (This laptop was 4 versions behind) and applied it, then reloaded Windows 10. Applied all the latest drivers from Lenovo for this device. Fingers crossed.

Well, looking at the dump file, they are breaking wininit. Output from debugger below:

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tom\Desktop\123021-8921-01\123021-8921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`30400000 PsLoadedModuleList = 0xfffff805`3102a1b0
Debug session time: Thu Dec 30 18:47:38.690 2021 (UTC - 8:00)
System Uptime: 0 days 0:00:08.359
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 14922

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

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

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

Key : CriticalProcessDied.ExceptionCode
Value: 8841d140

Key : CriticalProcessDied.Process
Value: wininit.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


BUGCHECK_CODE: ef

BUGCHECK_P1: ffffaa8988273280

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: wininit.exe

CRITICAL_PROCESS: wininit.exe

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffd203`a3e87878 fffff805`30d07c22 : 00000000`000000ef ffffaa89`88273280 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd203`a3e87880 fffff805`30c0ea17 : ffffaa89`8841d140 ffffaa89`882736b8 00000000`00000000 fffff805`3097d5a7 : nt!PspCatchCriticalBreak+0x10e
ffffd203`a3e87920 fffff805`30ab41cf : 00000000`00000000 00000000`00000000 ffffaa89`88273280 00000000`00000000 : nt!PspTerminateAllThreads+0x15b37b
ffffd203`a3e87990 fffff805`30808ab5 : ffffaa89`88273280 ffffaa89`8841d140 ffffd203`a3e87a80 ffffaa89`00000000 : nt!NtTerminateProcess+0x16f
ffffd203`a3e87a00 00007ff9`e560d2f4 : 00007ff9`e55cd9d4 00000000`000036ff 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c9`7faefcd8 00007ff9`e55cd9d4 : 00000000`000036ff 00000000`00000000 00000000`00000000 00007ff9`e34ecd80 : 0x00007ff9`e560d2f4
000000c9`7faefce0 00000000`000036ff : 00000000`00000000 00000000`00000000 00007ff9`e34ecd80 00000000`000036b1 : 0x00007ff9`e55cd9d4
000000c9`7faefce8 00000000`00000000 : 00000000`00000000 00007ff9`e34ecd80 00000000`000036b1 00007ff9`e390e0ab : 0x36ff


SYMBOL_NAME: nt!PspCatchCriticalBreak+10e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1415

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 10e

FAILURE_BUCKET_ID: 0xEF_wininit.exe_BUGCHECK_CRITICAL_PROCESS_8841d140_nt!PspCatchCriticalBreak

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {13ae584b-661e-3bfd-a7e2-0f3d90e1fde4}

Followup: MachineOwner