Jump to content

Critical process died Win10 error

EvolvedApe
By EvolvedApe
in Troubleshooting
 Share
Posted

hey

 

A few days ago my pc started turning itself off and back on randomly, no blue screen or error or anything.. it would turn back on instantly which led me to think its a psu issue.  

i didnt install or update or change any settings before that either, so whatever caused the issue happened by itself

I took the psu out to check all the connections and looked inside to see if i could see any obvious signs of a problem but couldnt find one. 

afteri reconnected the psu, the PC worked fine for about 3 days

i stress tested for hours just to make sure

Then a few hours ago my pc blue screened and shows the error that a critical process died. The error shows up for less than a second, i had to record it with my phone and watch it back to catch it.

I did some research myself and non of what i found online helped. 

I reinstalled windows and completely erased all of my drives and i still get that message. 

because of covid i cant really get a new psu to check if thats the problem or not

i dont know if the two issues are connected either, but since they are happened within a few days i wanted to mention it

 

If anyone has any ideas on how to troubleshoot let me know please, thank you

 

Specs:

ryzen 5 3600

corsair ax 860

GTX 1080 TI 

GIGABYTE X570 AORUS ULTRA

ADATA XPG SPECTRIX D60G RGB 16GB(2x8GB) DDR4 3600MHz

 

Link to comment
https://linustechtips.com/topic/1239168-critical-process-died-win10-error/
Share on other sites
Link to post
Share on other sites
Posted

With a fresh install, unless your installation media is corrupted it is likely hardware issue, but could also be missing or wrong drivers. You could disable automatic restart after system crash if it even starts anymore... Sharing that BSOD error code with us wouldn't hurt. Unless CRITICAL PROCESS DIED is all there is.

Link to post
Share on other sites
Posted
  • Author
12 minutes ago, RageTester said:

https://windowsreport.com/system-file-checker/

If you can  try running Command Prompt, and type sfc /scannow 

22 minutes ago, RageTester said:

With a fresh install, unless your installation media is corrupted it is a hardware issue. You could disable automatic restart after system crash if it even starts anymore... Sharing that BSOD error code with us wouldn't hurt. Unless CRITICAL PROCESS DIED is all there is.

I ran that command before reinstalling windows a few hours ago, it came back with no problems detected. ill run it again now to see if anything shows up

the only error code that is there is the critical process died.

 on other PCs ive seen it stays on the blue screen until the progress bar reaches 100% so you have time to see the error codes and everything, but in my case when i slow down the video i took of the bsod, it stays at 0% and i feel like the whole PC shuts off before it can display the entire code. (if there is anything more to be shown) 

 

edit: I ran sfc scannow after reinstalling windows and still no problems shown.

 

Link to post
Share on other sites
Posted
  • Author

 

7 minutes ago, RageTester said:

https://windowsreport.com/system-file-checker/

If you can  try running Command Prompt, and type sfc /scannow 

just some further information, the PC will freeze (i can still move my mouse cursor but cant do anything), then it changes to a black screen with just my cursor for 20-30s, and then the blue screen happens for less than a second,  and then the pc restarts. 

 

As i am typing this my pc crashed again but no blue screen this time, all my fans and leds and stuff are on, my monitors are turned on, but nothing is being displayed. 

The only thing i changed was turning off auto restart, 

Link to post
Share on other sites
Posted
  • Author
7 hours ago, RageTester said:

It's weird that nothing crashed during stress test. Have you tried booting into safe mode with networking, I got suspicion it might be the graphics card driver... try reinstalling that just in case.

Im moving around the ram now to check if thats the issue, but a few other blue screen codes have popped up

 

HAL INITIALIZATION FAILED

WHEA Uncorrectable Error

 

same things as before, just crashes a few minutes after starting the pc. I used DDU to reinstall graphics driver, and updated all other driver and windows. nothing worked yet

Link to post
Share on other sites
Posted

Uh I see some of these errors for a first time, if it was RAM error code would be pretty straight forward.

Are you booting from a hard drive or SSD? Any chance that boot drive is dying?

You might not have enough time to run a check... but In the Command Prompt, type chkdsk /f

 

Stick to safe mode, does it crash in safe mode?

Link to post
Share on other sites
Posted
  • Author

 

45 minutes ago, RageTester said:

 

Could be in fact CPU not getting enough voltage, then power supply is the problem as you thought at start.

 

51 minutes ago, RageTester said:

Uh I see some of these errors for a first time, if it was RAM error code would be pretty straight forward.

Are you booting from a hard drive or SSD? Any chance that boot drive is dying?

You might not have enough time to run a check... but In the Command Prompt, type chkdsk /f

 

Stick to safe mode, does it crash in safe mode?

the boot drive is less than a 2 months old WD nvme ssd so i doubt it that. unless there is a known issue i dont know about

 

i moved around the ram, and it seems to be crashing with 1 of the sticks in and not the other.

So far it seems to be that 1 of the ram stick causes the crash, but i dont know if thats the only issue. I checked each ram stick in 2 different slots. 1 ram stick works in both, and 1 doesnt work in either.

 

I ran the microsoft memory diagnostic and it did not find an issue when i had both ram sticks in, i will try to run a different ram test with each ram stick to see if it detects anything.

 

do you have any ram tests to recommend?

 

----------------------
Nevermind, it crashed after 30 minutes even with the good ram stick. it just takes alot longer to crash with that one. i think i might just take it to a pc repair shop

 

 

Link to post
Share on other sites
  • 9 months later...
Posted
On 8/28/2020 at 4:44 AM, EvolvedApe said:

 

 

the boot drive is less than a 2 months old WD nvme ssd so i doubt it that. unless there is a known issue i dont know about

 

i moved around the ram, and it seems to be crashing with 1 of the sticks in and not the other.

So far it seems to be that 1 of the ram stick causes the crash, but i dont know if thats the only issue. I checked each ram stick in 2 different slots. 1 ram stick works in both, and 1 doesnt work in either.

 

I ran the microsoft memory diagnostic and it did not find an issue when i had both ram sticks in, i will try to run a different ram test with each ram stick to see if it detects anything.

 

do you have any ram tests to recommend?

 

----------------------
Nevermind, it crashed after 30 minutes even with the good ram stick. it just takes alot longer to crash with that one. i think i might just take it to a pc repair shop

 

 

Hey, Ik this thread is very old but did you manage to fix this error, I am getting the exact some problems as you are

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×