Windows 10: BSOD while gaming 161 volmgr

Hello, I recently changed HDD because the old one died.After a clean install and all the Windows updates and drivers from Windows Update, I'm getting a BSOD with CRITICAL_PROCESS_DIED while gaming.I´ve tried everything, including a clean GPU install. The verifier says all drivers are fine.After checking the event log, it looks like this HDD is faulty. At this point, it looks like that is the problem because I've run out of ideas because everything else looks fine.Any help will be appreciated. Thanks in advance.Computer Specs:- Windows 10 Home 64b-I7 4790 3.60GHz-16gb ram -Nvidia Geforce GTX 16

:)

 

PC and Games keeps crashing (Volmgr 161)

PC keeps crashing into an unreadable and glitchy BSOD and restarts normally. Event Viewer shows Volmgr 161 followed by Kernal-Power 41 for the last crash but for the older crashes, only Kernal-Power 41 is shown. All the games I play also crash when under Load.

Link to my minidump and the memory dump.

Logs – Google Drive

 

Volmgr 161 + WHEA  

Awesome! Hopefully that works and we take a big leap toward the answer *Smile

- - - Updated - - -

The results are in- just experienced the same BSOD. Was only using Chrome this time…

DumpFiles folder I made and pointed it toward is still empty. No dmp file created as the BSOD continued to stay on 0%

 

Volmgr 161 + WHEA  

I'll list out here what works on my system.

I first uncheck "Automatically manage paging file size for all drives" to enable the controls on the dialog.
I select C: in the drive list and change the settings to match what is shown in this screenshot:



It should look like that after hitting the Set button. Hit OK until the dialog closes and restart the computer.

Go back into the dialog and select D: in the drive list and change the settings to match this screenshot:



Hit the Set button and OK out until the dialog closes. Then restart the computer.

That should set the pagefile for drive D: and it shows that in my msinfo32 information as well the D:\pagefile.sys showing up when I run "dir d: /ah" in a command prompt.