Windows 10: Windows 10 BSOD CRITICAL_PROCESS_DIED

I have had an on-going problem with my computer...

Computer Specs:
i7-3770k
Asus Sabertooth Z77
120 GB SSD (OS / A Few Apps / No Page File)
600 WD Raptor (Main Progam Drive / Page File)
Defrag Turned Off
Windows Defender turned off through group policy
16 GB RAM (1600 MHz)
950 Watt PSU
EVGA GTX 970 FTW



The problem I have been having is the computer just slowly starts locking up and explorer windows won't close or open and the computer just generally hangs. Task manager won't open either and after a few seconds it will eventually BSOD with "CRITICAL_PROCESS_DIED". This happens at random. Sometimes it will go several hours and the next time, it happens at boot. Blue screen view gives driver ntoskrnl.exe as the culprit. I really don't know what I am reading here but this has been an on-going problem. I even did a clean install to see if it would fix it. This problem was there before I installed the SSD as well. I have tried sfc /scannow but it returns that there are 1 problems but it can't be fixed. I tried all the solutions to fix the windows store but nothing worked. Something to do with opencl.dll. I've read somewhere that nvidia drivers could the cause of this.



When it self-restarts after it's collected it's information, 9 times out of 10, the SSD will disappear from the BIOS unless I manually shut it off and then turn it back on.

The computer is over-clocked, but it is doing this on stock clocks as well. Besides, the computer has been OC'd for over a year. All temps are well within normal so I know it is not a heating issue. I have very good air cooling.

I have both memory.dmp and mini dump files available for diagnostics. If someone could help me out, I would greatly appreciate it.



Whocrashed defines it as the file ntdll.sys. I have been thinking of doing a in OS upgrade to try to resolved this. Will that work?

:)

 

BSODs since yesterday when using GPU intensive programs.

The BSOD is always: CRITICAL_PROCESS_DIED

 

Your PC ran into a problem and needs to restart.

Boot speed low to you Windows 10 Home not responding

That for Laptop try is CRITICAL_PROCESS_DIED Error is fix

YOUR TO SSD ERROR ON BSOD

How to Restart Install Windows Setup Try in USB BOOTABLE IS SPEED UP NO BSOD IS ERROR TO BLUE SCREEN IS PROBLEM SLOW BOOT PERFORMAMCE

 

If your system is still overclocked, it is recommended to remove any overclock while your system is unstable.

Is the SSD connected with the same cable your previous drive used?

 

Not sure if I used the same cable or not. I noticed that the raptor drive cable slot was "distorted" and I was using a self locking cable but it no longer locks. It just slips in and out. Its almost looks like it "melted" slightly. I think I used a new cable on the SSD.

I still get the BSOD under normal (turbo) clocks (3.9 Ghz/1600 mhz memory) so I figured I would just leave the settings where it is at.

When you talked downclocked, do you mean the stock clocks of 3.5 or the stock MB Bios turbo clock of 3.9?

Have you looked over the file pack I submitted?

 

Is the connection of the motherboard the same?

I mean the max designed frequency of the component.

 

Ah I think I put it on the same one.

Gotcha.

Is this looking like a sata connection issue based off the file pack?

 

No, based on your description, need to rule connection faulty possibility out first *Smile

 

So should I switch them around? I only have two intel sata 6gb slots, 4 intel 3gb and 2 asmedia 6gb slots.

I have them both plugged into the intel 6gb slots.

 

I've done extensive benchmarking on both drives and they both are reported as good and healthy.

 

What test did you run?

 

Please make screenshots of the benchmark and health status.

 

Attachment 62270Attachment 62271Attachment 62272Attachment 62273

 

Just got another BSOD but this time it said "Unexpected_Store_Exception". Like the last one, when it rebooted after collecting data, it said insert boot media (SSD disappeared). I had to manually shut it down and restart it for the SSD to appear.

Turns out WhoCrashed brought it back as Kaspersky driver...

I am going to do a memtest overnight and see what it comes up with...

 

I am currently running a memtest86. It's currently at 15 hours, 5 passes and no errors. Figured I would rule out a memory problem.