Windows 10: BSOD error Critical_process_died - repeatedly and frequently

Hi,

If anyone can help I would really appreciated it, just got this machine and can't really get anything done on it as the keep getting 'critical_process_died' error.

It generally happens when streaming or watching media.

I have tried the following media players for watching movies and they all result in the same problem:

Ace Player, MPC, VLC, WMP.

For example I 'tried' to watch a movie yesterday and I had to hard reset 6-7 times using different players.

If I am trying to watch a stream through ace player there is absolutely no chance I will get through a entire game of anything.

I also have the same problem when using Skygo, or BT apps.

Essentially anything visual and the bugger BSODS me to death!

There have been other errors but I can't remember the exact error name, think it was 'memory_management'

If anyone could help me through what to do here I would appreciated it, I just moved back to window OS as starting a t CAD design course and want to have conistent access to programs (Mac UIs are rubbish as not everyone does a decent version). As a result I am a little rusty so any guides and pointers how to make this beast do what it's told would make my life liveable!

If I see that sideways sad face again I may smash my screen.

:)

 

Windows 10 Frequent Blue Screen - Lenovo

Hello Microsoft Community,

I've been getting pretty frequent (5 in an hour) BSOD errors. They seem to come in waves; it will happen frequently for a couple of days and then be fine for a week. Also it seems to be several different errors, cycling through CRITICAL_PROCESS_DIED or SYSTEM_SERVICE_EXCEPTION
among others.

Past 3 Minidump Files: 060517-4109-01.zip

Specs: Lenovo Specs.PNG

MSinfo32: Lenovo Yoga 2 Pro.nfo

Thanks in advance for the assistance.

 

Computer reboots with: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef

The dmp file showed a CRITICAL_PROCESS_DIED (ef) stop error (BSOD).

The Release Notes for the Intel storage driver lists a resolved issue being a CRITICAL_PROCESS_DIED (ef) BSOD.

The S3/S4 would be related to sleep if you notice the error tends to occur more going into or out of sleep.

I believe the new driver would be very beneficial but as a general precaution you could create a System Restore Point beforehand.

 

Hi LeeCandler,

Welcome to the 10forums *Smile

Unfortunately I'm unable to find any logs that tells us a BSOD has occured.
I would want you to run a few tests, to see the status of a few parts.
Please read the instructions carefully!






Diagnostics Test

HDD TEST
*Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums







Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Hi axe0,

thanks for the response mate, will go through those tests.

the lack of logs (i didn't know where to look for them in the zip file to notice) is perhaps down to the fact that the process with the BSOD always hangs on 0% when it is mentions there is supposed to be a report being created. I am usually in the middle of watching something time sensitive so perhaps I am being impatient! haha

how long should it take to make a 'report', it doesn't seem to leave zero in a reasonable ammount of time to me.

I'll do the rest of the tests tomorrow (UK) and post them up as as soon as I can.

 

Here is the HD tune screenshots.

Attachment 102482Attachment 102483Attachment 102484

 

This 'collecting data' process is simply copying the data that is present in the kernel memory of the RAM to the pagefile to temporary store the data until it can be saved to a file. This is because the RAM is volatile, as soon as the system has been shutdown everything in the RAM is lost.
When the system starts up again it 'dumps' the saved information from the pagefile into a .dmp file called 'MEMORY.dmp' located in the system root directory (C:\Windows) and a mini version of the dump version in the minidump location (C:\Windows\Minidump).

The process of collecting data should take less than a few minutes at max, even with very low specs.
Reasons why this process hangs could be following

• Registry settings corrupted,
• RAM faulty,
• Hard drive faulty,

It is possible that more reasons are behind the problem, but these are the onces I have ever seen occuring.

Now you know why I suggested HDD/SSD and RAM tests *Smile

 

Haha you are like a BSOD Prophet!

Will try and be more patient next time!

Will post results in a bit.

 

should I run seatools? It says no point with SSD?

 

SeaTools is focused on HDDs, on SSDs it's never been recommended due to unreliable results.

Don't use SeaTools on SSDs, as alternative use the software the manufacturer of the SSD provides.

 

Here is the ChkDsk Log:

Attachment 102594

 

Please upload the chkdskresult.txt on your desktop.
The screenshot doesn't show what changes Windows has made.

 

Here you go sir:





TimeCreated : 22/09/2016 11:38:18
Message :

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.


A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x1fc96.
280064 file records processed.
File verification completed.
8362 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
366542 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Cleaning up 2431 unused index entries from index $SII of file 0x9.
Cleaning up 2431 unused index entries from index $SDH of file 0x9.
Cleaning up 2431 unused security descriptors.
Security descriptor verification completed.
43240 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Windows has made corrections to the file system.
No further action is required.

487642111 KB total disk space.
127641824 KB in 209540 files.
127984 KB in 43241 indexes.
0 KB in bad sectors.
365263 KB in use by the system.
65536 KB occupied by the log file.
359507040 KB available on disk.

4096 bytes in each allocation unit.
121910527 total allocation units on disk.
89876760 allocation units available on disk.

Internal Info:
00 46 04 00 1b db 03 00 4d 47 07 00 00 00 00 00 .F......MG......
7f 01 00 00 4a 00 00 00 00 00 00 00 00 00 00 00 ....J...........

Windows has finished checking your disk.
Please wait while your computer restarts.

 

I have uploaded the actual txt file to show that is all the info.

I also got BSODed in the face again so ran DM log collector and have uploaded the new zip file.

 

What was the error? Any driver mentioned?