PC Freezing And Blue Screening

[Max I Guess]

Hello,

 

I'm having issues with my PC blue screening, freezing, games crashing, and sometimes even red screening. I ran MemTest64 and it found a few errors then blue screened with the error code MEMORY_MANAGMENT. I changed some XMP settings and ran MemTest64 again, which found no errors. A few days later I got another crash, ran MemTest64, and it found errors again. Changed some XMP settings, MemTest64 found no errors until next crash. My RAM has always been set to the recommended settings, sometimes maybe a bit lower. My BSOD error codes vary alot. After MemTest finds an error or two, my PC suddenly blue screens with the error code MEMORY_MANAGMENT. I ran WhoCrashed and it said This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateThread+0x14) Bugcheck code: 0x1A (0x41790, 0xFFFF908007E8B530, 0x20, 0x21) Error: MEMORY_MANAGEMENT. It's also worth mentioning that I mainly get the crashes when the PC is under some sort of load. I've run GPU and CPU benchmarks and haven't had any crashing issues. Here's my PCPartPicker list. I'm not really sure what to do, so any help would be greatly appreciated.

 

Thanks!

 

 

UPDATE

 

I was playing Getting Over It With Bennet Foddy, and all of a sudden I heard the sound that Windows 10 makes when you disconnect something from the I/O, then I heard the reconnect sound. The game froze for a second, then minimized. I also got a crash report from the same game which reads: 

Getting Over It [version: Unity 2017.4.9f1 (6d84dfc57ccf)]

UnityPlayer.dll caused an Access Violation (0xc0000005)
  in module UnityPlayer.dll at 0023:0fdae6dd.

Error occurred at 2019-01-29_165906.
C:\Program Files (x86)\Steam\steamapps\common\Getting Over It\GettingOverIt.exe, run by maxis.
26% memory in use.
0 MB physical memory [0 MB free].
0 MB paging file [0 MB free].
0 MB user address space [3129 MB free].
Write to location e0000019 caused an access violation.

[suchamoneypit]

Seems like you answered your own question. Everything here says its a RAM issue.