Question Critical Process Died ?

Toggle sidebar Toggle sidebar
manolis kokotsakis

manolis kokotsakis

Honorable
Mar 9, 2019
273
7
10,695
Hello,
1 month ago, i got this message on my screen. Since , i wrote the case to a forum in my country, and ask friends, more experienced than me , with out any succes till now, thats why i ask your help now.

I tryed allredy, check ram, nvme, temp, and all hardware.
I tryed all sofware solutions , check from comand prompt all advice the offer me, nothing.

Finaly , 2 days ago, i did for second time format , to win 11. Nothing. 2-3 times a day, i have the same blue screen.

my pc specs

ASRock H610M-H2/M.2 D5​

i31200,
16gb ram ddr5 kingston 4800,
psu, corsair CX430,

I hope for your help..​

 
Sort by date Sort by votes
ex_bubblehead said:
As already stated. You have an old piece of junk power supply. Until you change that to something newer and better quality you will continue to have random problems. The PSU is the heart and soul of the PC and if you continue to use junk you will have no end of problems.
Click to expand...
I agree sir, but as i said, the psu is an old model but only have 2 months of use. It was new in the box in my closet. You think that is the problem ?
 
Upvote 0 Downvote
manolis kokotsakis said:
I tryed allredy, check ram, nvme, temp, and all hardware.
I tryed all sofware solutions , check from comand prompt all advice the offer me, nothing.
ASRock H610M-H2/M.2 D5​
i31200,​
16gb ram ddr5 kingston 4800,​
psu, corsair CX430​
Click to expand...
I'd suspect storage device.
What storage device are you using?

Is it SSD? Diagnose with ssd manufacturer specific SSD tool software.
 
  • Like
Reactions: manolis kokotsakis, Dark Lord of Tech and Colif
Upvote 0 Downvote
Question about "Critical Process Died".

Any error codes, warnings, or informational events being captured by Reliability History/Monitor and/or Event Viewer?

Especially any that were captured just before or at the times the screen message was presented.

Look for such entries and then take a look at the details for those entries. An error code or codes may prove helpful.

Just a thought....
 
  • Like
Reactions: Dark Lord of Tech
Upvote 0 Downvote
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

that will possibly show us exactly what the cause is.
Since its a BSOD after all.
 
  • Like
Reactions: manolis kokotsakis
Upvote 0 Downvote
Colif said:
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

that will possibly show us exactly what the cause is.
Since its a BSOD after all.
Click to expand...
Hi,
thanks for try helping me.
Sorry ir, i cant find where is minidump, and what you tell me. Sorry i am so expert on computers.



Colif said:
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

that will possibly show us exactly what the cause is.
Since its a BSOD after all.
Click to expand...
 
Upvote 0 Downvote
Colif said:
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

that will possibly show us exactly what the cause is.
Since its a BSOD after all.
Click to expand...
How can i enter a pictre here to show you ?
I dont know.
 
Upvote 0 Downvote
You only have a minidump folder after you set it up to make them and AFTER the next BSOD
Otherwise folder doesn't exist yet

Image posting via Imgur

go here - https://imgur.com/ you might need to set up a user. click on New Post which will display next screen where you can select image(s) - hold Ctrl while selecting images in explorer to get multiple Once uploaded, images will show on the next page right clicking an image (once its shown...
forums.tomshardware.com forums.tomshardware.com
 
Upvote 0 Downvote
The 0xEF bugcheck CRITICAL_PROCESS_DIED is almost always caused by bad hardware, though there are a tiny few exceptions. As suggested above, it's wise to check on your hardware first.

It would be useful if you could download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
 
  • Like
Reactions: manolis kokotsakis
Upvote 0 Downvote
Ι return to leave a commned to this discussion only to answer to all of you to what happened to this case. Finally the all problem created from the screen. I impossible to believe but yes.

I return to the old one and all problems stop. I dont understand how posible to have a bluse screen from a screen but this is how it is.
 
Upvote 0 Downvote
ubuysa said:
I don't believe that just changing the monitor fixed the problem either, but without the Sysnative data I asked for we'll never know. I'm glad it seems fixed.
Click to expand...
What you mean sir with the sysnative data ?
I allready work on pc over 10 days now and nothing .
If you think its not the screen what possibly can be ? I dont undertand myself also ?
 
Last edited:
Upvote 0 Downvote
manolis kokotsakis said:
Finally the all problem created from the screen. I impossible to believe but yes.

I return to the old one and all problems stop. I dont understand how posible to have a bluse screen from a screen but this is how it is.
Click to expand...

I only return to say that its unlikely a monitor would cause a BSOD since you don't install any software on the PC to run it, and its more likely the other screen is smaller than one you had and is perhaps not putting as much strain on current PC.

I would do what Ubuysa has asked (I quoted it below) as you haven't fixed it, you are just avoiding it.


ubuysa said:
It would be useful if you could download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.
Click to expand...
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom