BSOD/crash playing games, memory error on shutdown

I recently bought and built myself a new gaming PC and have had a few issues with it. The first is that any time I shut down my computer after it was in sleep mode, it shows a memory error. The second is that with games, if I play long enough my computer either blue screens or the application crashes and I'm unable to relaunch it without restarting my computer.

With the first issue, the error message that pops up is: 'The instruction at 0x0000000000000000 referenced memory at 0x0000000000000000. The memory could not be read.' The memory addresses are sometimes random, but 0x0 is very common. I've searched online to see if anyone has solved this and it seems to be a bug in Explorer that Microsoft knows about, but is like 'meh, doesn't hurt anything...it's shutting down anyways'. My previous computer used to do the same thing as well. An interesting thing I've noticed, which I don't think has been pointed out elsewhere, is that it only seems to happen after I have had my computer in sleep mode, or the second issue I've been having happened.

With the second issue, I'm able to play games for varying amounts of time. I was able to play Shadow of War for 5 hours yesterday without the issue happening, but happened again today after 1 hour. With Shadow of War, I have noticed that it starts to get jumpy/audio is messed up just before the crash. This happens even worse with Divinity: Original Sin 2. My computer has BSOD'd 3 times now playing Divinity, each time a different stop message, and it has crashed even more often. I've also had it happen on FFXIV. With Shadow of War and FFXIV, I'm not able to relaunch the game until I restart my computer. Divinity is usually able to be restarted if it didn't BSOD, but I did have one instance where I had to reboot for it to start again.

I've already tried the Windows memory check tool, and did a sfc /scannow (but it ran way too short to have actually scanned anything, so I'm going to try it again). Any other suggestions of where to check next?

Updated info, although I'm not sure what info you were looking for that I didn't already have in there...

So it's been about 5 days now and I'm still having the problem, just less often. I had it set up so that my C: drive (ssd) had my OS and important programs, D: (Hitachi) had other installed programs and E: (WD) had documents. I moved it so that D: now held both installed programs and documents, meaning E: isn't used (I don't really need 5TB of storage, 3TB will be more than enough), and the rate of crash has gone down. I also noticed that I forgot to install my motherboard drivers when setting up this computer, which is now only weeks old, so that was probably a factor as well.
I haven't had time to go through the diagnostics steps on all of my drives, but since it's the weekend I decided to do it on my E: drive since it isn't really in use anymore and the error rate went down as soon as I took it mostly out of the loop. The tests yielded the attached results, but in the process I noticed that both D: and E: were hovering somewhere around 55C. HD Tune even warns me about this temperature when I have the drive selected. Could that be part of the problem?

Please use the information in this link to find the chkdsk /r results in the event.vwr and post the report into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

Code:

{Registry Hive Recovered} Registry hive (file): '\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SYSTEM' was corrupted and it has been recovered. Some data might have been lost.

Code:

{Registry Hive Recovered} Registry hive (file): '\??\Volume{53333955-4c95-4087-934c-8614c99ea610}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{E6212BB8-AC1C-4D62-A56A-CF9921CD9FD1}' was corrupted and it has been recovered. Some data might have been lost.

Code:

Volume E: (\Device\HarddiskVolume4) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

Void Concept said:

I also noticed that I forgot to install my motherboard drivers when setting up this computer, which is now only weeks old, so that was probably a factor as well.

Reevaluate after a period of time now that the chipset drivers are installed.

If the problem still continues, post back.

@zbook I ran chkdsk /r on E: and it came back with nothing. Unfortunately forgot to screenshot, but I did read through and there was nothing out of the ordinary printed out. I also can't find any logs of any of the chkdsk runs I've done in the event viewer. Attached is what was printed out from method 2 of the post you linked.

@SmartEyeball I haven't had a crash in the last few days, although I've barely played the games that caused the crashes most often. I am still getting the memory error on shut down fairly often, but again, from my research it seems like a known bug in Explorer that only affects shutdown. I'll report back in a few days again if things crash again or not.

Windows has made corrections to the file system.
Recovering orphaned file psmsrv.dll.mui (355AF) into directory file 24B7C.
1 unindexed files recovered to original directory.

Please turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

Code:

Event[522]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-09-30T16:01:18.695  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Kyle-Desktop  Description: Windows failed fast startup with error status 0xC00000D4.