BSOD, Watch Dog Violation 0x133

Since building my new PC around August 2019 I have been getting random reboots and the occasional BSOD, each of these result in my 2nd Samsung 970 Evo Plus (2TB) disappearing from Windows. Originally the PC would instantly restart, more recently I'm getting the BSOD's, so now have MEMORY.dmp files available.

Initially I was getting several lock ups a day, but I later tracked this down to a conflict between Kaspersky and Malwarebytes, originally resolved by removing Malwarebytes and later with a fix issued by Malwarebytes. (I've added this, but it maybe a red herring)

Around the same time I was having the issues with Kaspersky/Malwarebytes I also installed the latest Samsung NVMe drivers (3.2 at the time, now 3.3), with the Samsung drivers installed I'm still getting BSOD's but they seem to be further apart, 1 month to 1.5 months.

Since building my PC I've done several fresh installs of Windows, originally 1909 and now 2004, each installation has been done with the latest drivers for my various devices and I have current firmware's installed for the motherboard and NVMe drives. I've also done several MemTest runs with zero faults.

I've also been in contact with Samsung thinking that maybe the controller is locking and causing the reboot, but after sending them some diagnostic logs and SMART readouts they have said that they don't believe the drive is at fault and it must be down to something else.

I haven't yet contact Asus to see if it's possibly an issue with the X570 chipset. But otherwise I'm at a lose as to what else it could be, I'm hoping someone here who is more knowledgably might be able to clean something from the DMP files?

OS; Windows 10 Pro x64 (2004, with all updates installed)
MB; Asus Crosshair VIII Hero (BIOS; 2206)

OS/Apps are installed on a 1TB Samsung 970 Evo Plus.
Games are installed on the 2TB Samsung 970 Evo Plus (this is the drive that drops out).

See - BSOD - Posting Instructions

I can't seem to edit my original post, V2 Log link; W10-PRO-XXXXXX-(2020-09-27_14-51-26).zip - Google Drive

Unfortunately I don't have the MiniDump files, but I can provide the full Memory.dmp file, although I'd prefer to share that privately.

OK so send MEMORY.DMP file for me

Just tried to send you a private message, but seems I don't have permission presently.

Because the full memory.dmp may contain private data such as a username/password or an encryption key or anything else that was in memory at the time of the crash.

I'm more comfortable controlling who I'm sharing it with especially when posting a publicly available link on a public form.

Please indicate how you get passwords or an encryption key from the memory dump.