Im certainly not going to argue with
@x BlueRobot, he's way more advanced at this that I, but from the earlier dumps this looks very much like a RAM problem to me, that or a CPU issue. I don't recognise that Memtest86 output you posted?
My reasoning is that, although you have Driver Verifier enabled (with just the standard tests rather than
those recommended here), none of these BSODs are Driver Verifier generated and that in itself is a good indication of a hardware cause. In addition, I don't see any third-party drivers referenced in these dumps, another good indicator of a hardware issue.
Two of the dumps are 0x3B bugchecks with non-canonical (garbage) memory address references and hence 0xC0000005 exceptions (invalid memory access), one of these also has a misaligned instruction pointer flagged. One dump is a 0x50 with an invalid memory reference, another is a 0x139 for a corrupted memory data structure, neither showing any third-party driver references - another good indication of a probable hardware cause. The fifth dump is a 0x101, which we can only fully debug with a kernel dump, but sadly that's already been overwritten. This bugcheck indicates a CPU hang and that's generally a CPU problem, which is why I mentioned CPU above.
In addition, in your System log, I can see the crashes with no indication of any error that might have caused them - another indicator of a probably hardware cause. In your Application log there are a number of application error messages with either 0xC0000005 exception codes (invalid memory reference) or 0x0000374 exception codes (heap corruption) - these point at a potential RAM issue.
I do know that AMD processors like fast RAM and you seem to have your 3200MHz RAM clocked at the stock frequency of 2133MHz. I don't hold out much hope but you could try running your RAM at the 3200MHz design speed?
You have two 8GB RAM sticks so you could also try removing one stick at a time and see whether it's BSODing on only one.
I've also seen a few AMD CPUs that were a tad unstable at low power C-States, so if you can, try disabling C-States in the BIOS and see whether that stops the BSODs.
