Windows 10: BSOD while gamind 161 volmgr

Hello, I recently changed HDDs 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 looks fine.Any help will be appreciated. Thanks in advance.

:)

 

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.

 

Volmgr 161, kernel power 41 constant BSODs

Constant BSOD - Volmgr 161 followed by Kernel-Power 41.

Laptop is an Asus GL703VD.

Volmgr error (from event viewer) always comes from the same volume area according to the report.

The first time this BSOD occured was a few days ago.

\Device\HarddiskVolume4

000000000100000000000000A10004C000000400010000C000000000000000000000000000000000

Kinda running at my wits' end here. The error went from happening once, to multiple times today, to literally every 5 minutes now. No idea what could be causing

this. Thank you for any help.

Addendum: Laptop has been a good bit slower since this issue has been in full swing.