Critical Process Died BSOD (BugCheck 239/159) + VolmGr 161 error

I've been getting incessant BSODs for the past 2 months. Initially it was a NetBT 4311 error pertaining to NordVPN's interactions with new network drivers, but I've since rolled back the drivers and uninstalled NordVPN completely. The NetBT errors stopped, but BSODs continued. This entire time, the system has failed to create Minidump files (volmgr 161). I finally received a minidump after an abnormal crash (several minutes of hang, no blue screen), but I'm not sure if the NT kernel error it describes is the main cause behind all the other BSODs. Again, I have never seen a minidump for the type of crash that normally happens (freezes for 5-15 seconds, then blue screen).
My OS version is 19042.844 (Windows 10 20H2)

Things I've tried:
SFC, DISM restore health, chkdsk, a repair install (in-place upgrade), Windows Memory Diagnostic, updating drivers, rolling back drivers. I ran Driver Verifier and it succeeded in forcing a BSOD, but it failed to produce dump files just like the rest, so I still don't know which driver/application is causing the issue.
All my drives are healthy as far as I can tell, since I've run several diagnostics that all came up clean.

The recent (and only) minidump file: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
The ZIP from the TenForums V2 log tool: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

I did my usual BSOD dirty fix: re-seating the RAM and boot drive. Turns out my boot drive has one physically defective sector and I should probably replace it ASAP (even though it's only 2 years old). This has been the cause of almost 700 BSODs under different error codes: WHEA hardware, critical_process_died, unexpected_store_exception. I'm still getting crashes from system hang, but at least those give proper minidumps instead of volmgr 161 errors.

Thanks for the feedback.

Have you got the reason? I have the same issue with CRITICAL PROCESS DIED. But can not find the dump file. In Event Manager log it said: Can not create the dump file.
The windows install on M.2 NVMe Samsung 970 EVO (drive install on the top M2 slot of Gigabyte Z370 Gaming 7. I reinstall windows on 2.5 SSD and everything work fine again. Then I buy another M.2 NVMe WD 500GB and install it at the botton M.2 slot and now have the error WHEA _UNCORRECTABLE_ERROR... So confuse now don't know what happen with my PC :"(

SeCrEt BoY said:

Can not create the dump file.
:"(

Have Windows Create a Small Memory Dump (Minidump) on BSOD
Configure Windows 10 to Create Minidump on BSOD

jmatt said:

Have Windows Create a Small Memory Dump (Minidump) on BSOD
Configure Windows 10 to Create Minidump on BSOD

Thanks so much. I will check again this when go back home. Just wonder if WHEA_UNCORRECTABLE_ERROR maybe caused by power supply?

@SeCrEt BoY

Please run again so that the settings are maintained in the primary thread:
Critical_process_died bsod
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

zbook said:

@SeCrEt BoY

Please run again so that the settings are maintained in the primary thread:
Critical_process_died bsod
Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.

Hi, sorry about late. Have come back home from a long bussiness trip. This is the log file saved via Tuneup.bat
My computer have just BSOD with WHEA_UNCORRECTABLE_ERROR.

Dropbox - Tuneup.log - Simplify your life

SeCrEt BoY said:

Hi, sorry about late. Have come back home from a long bussiness trip. This is the log file saved via Tuneup.bat
My computer have just BSOD with WHEA_UNCORRECTABLE_ERROR.

Dropbox - Tuneup.log - Simplify your life

Please open a nee thread.

For any BSOD run the V2 log collector to collect new log files.