W10 BSOD Errors 1101, 161, 6008  

netjack said:

So I bought a new NVME and boom I never received an error again. So I had the game installed on this new NVME (again in NVME slot 2) - could it have been acting up again that caused this BSOD issue?

I'm not sure if I understand what you say because it depends on whether the game was installed on secondary drive or on the same drive where Windows is installed?

games (or any other programs that are installable with an installer) should always be installed on same drive as Windows, and always into either ProgramFiles or ProgramFiles(x86) depending on software "bitnes".

netjack said:

If that is the case, how do I test for a faulty nvme slot?

First you need to test M.2 drive in one slot, if it fails test it in another slot and if that fails again, take another SSD and test it again in first slot and again if it fails test it in 2nd slot.

Once you're certain you have SSD that 100% works in either of the 2 slots, you then use that SSD to test slots, if it fails at least twice in one slot but never in another slot then you know there is some issue with the slot.

Are you saying COD takes 250gb of space??

I would optimize my drive such that in addition to Windows only games that I currently play are installed on main drive.
Anything that is not installable ex. rar files, pictures etc are on secondary drive.

You don't need to have 10+ games installed on main drive if you don't play them, just one or 2 you play.
And then uninstall game and install another one that you play.

I have 500gb SSD and some 7 games installed right now, including a lot of other programs, a bunch of virtual disks and other stuff that could be removed, and never got issues with lack of space, all non installable files are on 1TB secondary drive.

You know if you install games or program to secondary drive then you do need to reinstall them after fresh Windows install?
Secondary problem with installing to another drive is security related.

what do you recommend as a good nvme testing software/program?

I don't know, usually drive manufactures may provide such tools but don't be surprised if you don't find it.

Just use the method of isolating problem I gave you in previous post.

netjack said:

In any case I’m going to run it on the boot. If it doesn’t crash today, I’ve deduced the problem.

Correct, because otherwise you'll be implicitly testing both drives (and slots) which would never give you a clear picture of the problem.

It would not be bad idea to have only 1 drive connected to PC, to be 100% sure you're testing just one drive/slot.

good news figuring out the cause, bad news for your mainboard