Windows 10: BSOD "Critical Process Died"
-
Yes, I did. I can't find any trace of it.
-
-
Remove the entries from your hosts file.
There are no dump files in the zip you uploaded. Please make sure your PC is configured for small dump files:
How to Configure Windows 10 to Create Dump Files on BSOD
See if there is a C:\Windows\MEMORY.DMP file. That's a larger memory dump. If there, zip it then upload to one of the file sharing sites like OneDrive and post the link here/ That will give me something to look at.
Event Viewer has over 60 of these entries:
Code:
Event[15774]:
Log Name: System
Source: EventLog
Date: 2016-12-14T23:20:47.372
Event ID: 6008
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Justin-PC
Description:
The previous system shutdown at 11:16:22 PM on ?12/?14/?2016 was unexpected.
but nothing preceding the entry indicates a problem occurred nor why the shutdown happened.
Need dumps to go any further.
-
Alright, it's been deleted from the hosts file, and I changed the dump settings from "small" to "active". I also downloaded a .reg file to allow active dump files, just in case.
-
-
Great, now we wait and hope is another BSOD occurs we'll get a dump.
Did you check to see if there is a C:\Windows\MEMORY.DMP
-
I don't believe there is.
-
I just experienced a BSOD and had to manually reboot. The error code this time was: "UNEXPECTED STORE EXCEPTION"
And then I ran the log collector. Hopefully my PC created dump files. I'm not sure.
Attachment 114131
-
Unfortunately, no dump again. I don't see anything in the event viewer output other than saying the previous shutdown was unexpected. No indication as to what caused it.
Let's do some testing, memory, then CPU and GPU.
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:
- RAM will accept and keep random patterns of data sent to it
- There are no errors when different parts of memory try to interact
- There are no conflicts between memory addresses
Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.
If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.
Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums
===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums
If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..
If none of those show anything useful then we'll try enabling Driver Verifier and see if that gives any help:
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.
Driver Verifier - Enable and Disable in Windows 10
Pay close attention to
PART TWO 
and make sure the correct boxes are checked.
Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.
Always create a Restore Point prior to enabling Driver Verifier.
What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
-