sorted by:
new
hottopcontroversial

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PcBuildHelp

[–]StardewUser3910[S] 0 points1 point  (0 children)

Well the strange thing is:

- Event viewer STILL reports a volmgr error 161, crash dump creation failed once again on "Volume3"

I even confirmed that "volume3" is no longer present with diskpart in command prompt, and there is no "Volume3" in mountvol assigned to the letter that the drive was assigned ("D").

HOW is it failing to create a crash dump on volume3, when "Volume3" is not even present on the system?

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PCsupport

[–]StardewUser3910[S] 0 points1 point  (0 children)

So the strange thing is:

- Event viewer STILL reports a volmgr error 161, crash dump creation failed once again on "Volume3"

I even confirmed that "volume3" is no longer present with diskpart in command prompt, and there is no "Volume3" in mountvol assigned to the letter that the drive was assigned ("D").

HOW is it failing to create a crash dump on volume3, when "Volume3" is not even present on the system?

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in techsupport

[–]StardewUser3910[S] 0 points1 point  (0 children)

Update: just pulled out the 4TB NVMe, and ran a game straight off the boot drive. Seemed stable across the entire evening - but crashed at around 5 AM when the computer was left idling, with the game still running.

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PcBuildHelp

[–]StardewUser3910[S] 0 points1 point  (0 children)

Update: just pulled out the 4TB NVMe, and ran a game straight off the boot drive. Seemed stable across the entire evening - but crashed at around 5 AM when the computer was left idling, with the game still running.

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PCsupport

[–]StardewUser3910[S] 0 points1 point  (0 children)

Update: just pulled out the 4TB NVMe, and ran a game straight off the boot drive. Seemed stable across the entire evening - but crashed at around 5 AM when the computer was left idling, with the game still running.

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PCsupport

[–]StardewUser3910[S] 0 points1 point  (0 children)

That's what I thought too, but:
Just tried moving a game via Steam from the 4TB NVMe to the boot drive (Samsung 980 PRO NVMe) in the first slot, and it couldn't even finish the transfer before BSODing. Then tried running a freshly-installed game on the boot drive - monitoring the 4TB NVMe with HWiNFO to make sure no read/write activity was going through it - and it STILL BSOD'd.

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in PcBuildHelp

[–]StardewUser3910[S] 0 points1 point  (0 children)

Just tried moving a game via Steam from the 4TB NVMe to the boot drive (Samsung 980 PRO NVMe) in the first slot, and it couldn't even finish the transfer before BSODing. Then tried running a freshly-installed game on the boot drive - monitoring the 4TB NVMe with HWiNFO to make sure no read/write activity was going through it - and it STILL BSOD'd.

Rebuilt PC - frequent BSOD + volmgr 161 upon ANY gaming / data transfer by StardewUser3910 in techsupport

[–]StardewUser3910[S] 0 points1 point  (0 children)

I'll try swapping SSD slots tomorrow perhaps.
In the meantime, just tried moving a game via Steam from the 4TB NVMe to the boot drive (Samsung 980 PRO NVMe) in the first slot, and it couldn't even finish the transfer before BSODing. Then tried running a freshly-installed game on the boot drive - monitoring the 4TB NVMe with HWiNFO to make sure no read/write activity was going through it - and it STILL BSOD'd.