Memory related BSOD, mostly when playing League

[A4K]

Hello there.

I've been experiencing frequent crashes, most of them I believe to be related to memory, and seem to happen almost every time I'm playing a game of League (which is the only game I play / have installed on my computer, so were I to play a different game may happen as well).

Suspecting errors with my RAM, I ran a couple passes of Windows Diagnostic Tool (nothing to report) and then a couple passes of Memtest86 (which with the frequency of the crashes I'd suspect a couple passes should be enough -- nothing to report either). I've also tried removing all external devices save for my mouse and keyboard, yet the problem still persists.

I'm rather uneducated in the matter, however my suspicions include:

improper voltage?
driver errors?
computer overheating?

So I've come to this wonderful community for help on my subject. Thanks for all your time!

Attached is my DM Log

 

[A4K]

So I've tried running driver verifier, which has populated a special pool detected memory corruption crash (which I can now tell the computer is about to crash because certain chrome tabs start crashing themselves) and has also made it so I can't start League (which I've tried a couple known fixes for now). I've also tried disabling everything in Startup except for the antivirus. Neither of these have given conclusive results.

I've now tried running a disk check, but the system won't boot when I have one scheduled. Really reaching the ends of my wit, and looking for some good help. Thanks!

 

[A4K]

Turns out the black screen was a result of me having no GUI boot enabled, so I'm running it again. I also read some people recommending against chkdsk, maybe somebody more experted would like to weigh in? Anyway, I ran it again with the /r option because I don't think the last result was recorded anywhere.

Don't wanna bump again so I'll edit this post. Turns out /r doesn't really do what I thought it did, but I found how to view the results of the chkdsk (I was kinda napping hehe) and it turns out it didn't find any errors, so back to the drawing board.