Random CRITICAL_PROCESS_DIED BSOD Windows 10

Warysaur

Reputable
Sep 10, 2016
11
0
4,510
So, for a few weeks I've been having trouble keeping my computer running without getting a "CRITICAL PROCESS DIED" BSOD at random intervals. I've ran memtest86 and my memory seems to be fine, no errors, and checked the HDD using Linux Mint with positive results. (Pics available for both.) I've tried sfc and I'm just at a loss for ideas right now. Sometimes, upon restart, it asks me to "select the proper boot drive" or something along the lines, and no minidump file is created, despite having it set to create one upon BSOD. I've also deleted everything on my HDD and reinstalled Windows 10, and the problem persists. Any ideas or help to fix this problem? It's very annoying.

AMD FX-4350
ASUS M59A7 R2.0
EVGA GTX 750 Ti FTW
WD Caviar Blue 1TB
 
Solution
Solution: Replace the harddrive. Buy an other brand!
Small explanation: As I upgraded to Win10, I renewed my harddrive. Win7=Seagate, Win10=WDC. Begin of second week of August I got problems with Critical Process Died.
For testing, I have prepared my old Seagate with the Win10 image from the WDC.
Since then I had never a BOSD.
Detailed explanation: First of all I had fear my might be new HD break down. Never problems with WDC and the price was good I ordered the same model, but different firmware. The BOSD was still happen. The problem is, the OS doesn't do anything after the event. Unable to write a MiniDump or an ProcessExplorer file when this happen. The Eventviewer has no usable entries. Huge problem to figure out...
Solution: Replace the harddrive. Buy an other brand!
Small explanation: As I upgraded to Win10, I renewed my harddrive. Win7=Seagate, Win10=WDC. Begin of second week of August I got problems with Critical Process Died.
For testing, I have prepared my old Seagate with the Win10 image from the WDC.
Since then I had never a BOSD.
Detailed explanation: First of all I had fear my might be new HD break down. Never problems with WDC and the price was good I ordered the same model, but different firmware. The BOSD was still happen. The problem is, the OS doesn't do anything after the event. Unable to write a MiniDump or an ProcessExplorer file when this happen. The Eventviewer has no usable entries. Huge problem to figure out what is going on. Until today.

My theory: One of Win10 Updates make problems in combination with WDC harddrives.

My hardware:
MEDIONPC MS-7713
AMD Athlon II X4 640
ATI AMD Radeon HD 5450
8,00GB Dual Kanal DDR3 @ 666MHz (New)
WDC WD10EZEX-00WN4A0 OS (New) Same HD like Warysaur !!
WDC WD10EZEX-08M2NA0 Data
Windows 10 Home 64-bit
 
Solution