Bsod critical_process_died

I used this computer a couple of years with ubuntu. I do not think it crashed once.

I then installed windows 10 pro to a new SSD and the problems started.

BSOD are sporadic, sometimes days between, other times hours.

Most BSOD happens when the computer is unattended. It has happened when I dragged a file over to a network drive and the latest when I was saving a document to a new file.

When it happens the system becomes gradually more unresponsive until the BSOD. The latest were acompanied with deep beeps in a repeating pattern.

I have run
SFC /SCANNOW
chkdsk C: /f
and memtest86+ (Dropbox - memtest.jpg - Simplify your life) for more than 8 passes without problems.

V2 log file is here: Dropbox - HAFX-(2020-02-02_10-19-51).zip - Simplify your life

Windows version: 1909 (OS build 18363.592)

Sincerely,

Send full memory dump (MEMORY.DMP in C:\Windows)

One of the things I did in my tries to get rid of the BSOD were to set the virtual memory to the amount of RAM, 16GB. I have saved the file, but it is difficult to share right now. I will reset virtual memory back the the windows recommended 2 GB or something.

Also, I were in the process of making a system image in order to transfer the OS to another disk when I got a new BSOD. The screensaver came on and as soon as I moved the mouse the screensaver froze and the BSOD happened. This time a SYSTEM_SERVICE_EXCEPTION.

The memory.dmp is from after this crash.

And here is the latest V2 log file: Dropbox - HAFX-(2020-02-02_13-13-30).zip - Simplify your life

I am going to reset the virtual memory size and I will post the memory.dmp when I have the new file.

- - - Updated - - -

So I got a new BSOD. The original CRITICAL_PROCESS_DIED

V2 log: Dropbox - HAFX-(2020-02-03_12-46-02).zip - Simplify your life
memory.dmp: Dropbox - MEMORY.7z - Simplify your life

I am not going to change anything, like a new drive on the computer unless told so BTW.

Virtual memory set to automatic.

PC still running without problems.

What happened: After I got the BSOD I found that the virtual memory were set to "1000Mb, recommended 2400 Mb". So I set it to 16Gb.

If there are no more problems within a week I will mark it as solved.

Ztruker said:

Why not leave it set to automatic and let the system manage it?

I will leave it at automatic. I am just not to good expressing myself. I were just explaining why I messed with the setting in the first place.

But no, a SYSTEM_SERVICE_EXCEPTION this time. But the BSOD feels the same, one window stops responding, then gradually others. I managed to close a couple of windows before the crash.

I also notice that the virtual memory size stays at the same value as I once set it; 17408 MB. But it is on automatic.Attachment 266296

The V2 collector log: Dropbox - HAFX-(2020-02-09_08-51-41).zip - Simplify your life