Blue Screen of Death: CRITICAL_PROCESS_DIED on Windows 10

I really need some help here. Every time I try to boot up my laptop, I just get hit with this "critical_process_died" error message. Does anyone know how I can fix this? If you could walk me through the steps, I would truly appreciate it. Thanks!

You gotta get into Safe Mode first. Not sure if you're running on BIOS or those newer settings, though... try spamming F8 right when that black screen pops up after the initial boot image. Hit it about every half second. Once you're in, fire up CMD as an admin and run sfc /scannow
Let it finish, then try a regular reboot.

William Richardson12 said:You really need to boot into Safe Mode, though I'm guessing you might not know if your system is running on BIOS or UEFI settings. Try tapping the F8 key repeatedly—just a quick tap about every half second—right when that first splash screen pops up and before the black screen hits. Once you're in Safe Mode, fire up the Command Prompt as an administrator and run sfc /scannow
Just let that process run its course, then try restarting the computer normally.

As soon as I hit the power button, I'm just met with a black screen, and then it immediately jumps straight into AUTOMATIC REPAIR 🙂

Here's a photo of what I'm seeing

Image :

Just pop open the advanced options and hunt for some kind of command line or whatever...

William Richardson12 said:Try heading into the advanced options menu and see if you can find a command line interface or something similar there.

Okay, so I went into the advanced options and pulled up the command prompt. Now I'm staring at this black window that says ADMINISTRATOR: X:/WINDOWS /SYSTEM32/CMD.EXE

X:/WINDOWS/SYSTEM32> So, do I just type that specific command right here after the prompt?

Update: I actually typed it in and something finally popped up on the screen. I'm attaching a screenshot here so you guys can see what I mean.

Image

Does it say 100% or "success" or something else? If it does, you're good... try booting it up now.

It doesn't say anywhere that it's a hundred percent guaranteed.

You typed that command in wrong.

rowdybadger18 said:It looks like you typed that command in all wrong.

Well then, what's the right way to do it?

You need to type sfc /scannow exactly as shown. You might have missed the space between the slash and sfc.