Critical_Process_Died, Windows 11, no recovery tools work

C

Caballus

New member
Joined
Aug 27, 2022
Posts
3
Hello folks,
I'm about to have a mental breakdown.
PC from son crashed today. It shows a "CRITICAL_PROCESS_DIED" everytime at startup. 2 weeks ago it crashed too.... had to restore the corrupted partition table and got it working again.

What I did so far:
1.) PC gave me an option to start the recovery at the blue screen.
2.) At the recovery options: SAFE BOOT fails, I have no "revert back to day" options
3.) Starting the console, I used the DISM /online /cleanup-image /checkhealth command. Didn't work. Can't Access image. Tried the offline command.
4.) At console: sfc \scannow was stopped by Windows Resource Protection.
5.) At console: chkdsk shows no problems.
I have exhausted every known option and can't believe that I'm sitting at the same bs like I did 20 years ago with nothing of that recovery stuff actually working. fixboot, fixmbr and all this stuff brought no joy.
Regarding BCD: Total identified Windows installations: 0

Rig is this:

IdeaCentre Gaming 5-14IOB6 Desktop - Type 90RE​

I feel so mentally exhausted and tired. Don't know what to do.​

​

Greetings,​

Cabal
 
Last edited:
Disk not tested as of now but tested it weeks ago only with Lenovo Diagnostics and everything was fine.

It’s a M.2 SSD.
 
I would recommend testing the SSD using Seagate Tools Bootable using these instructions. You'll want to run a Long Generic test which may take a few hours to complete. Ultimately, this will not resolve the issue since it appears that file system may possibly be corrupt beyond repair, however, it will help to establish what caused the issue to occur in the first place.
 
Hi BlueRobot,

shortly after my last reply here, another blue screen happened and I contacted Lenovo and sent it for repair. The guy from Lenovo told me I should stay with Windows 10 because of incompatibilities this rig might have with Windows 11. 🤨
I will do the test ASAP and post the results. I still feel that I have a lemon here.

Greetings,
Cabal
 
Hardware incompatibility problems will not cause a Stop 0xEF, most cases it is due to hardware failure and rarely there has been a couple of instances of over-zealous security software terminating critical system processes like svchost.exe.
 
I agree with @x BlueRobot -- the hard drive would be the first thing to test here.

@Caballus - don't let Lenovo run you up against the warranty expiration! I do hope it runs fine on W10, but when you get it back, test the system by using it as much as possible, leaving it on, etc... to hep assure that they did in fact fix it.

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top