Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffd187c5801f1c, 2, fffff80395fbfe38, c}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
Hi,
as you can see from the above dump file the faulting driver could not be read.
File scans
Right click on the Start menu icon and from the revealed list choose 'admin command prompt'. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
I can see STEAM was running at the time of blue screen and it may help if you removed steam and installed a fresh copy. (you did mention that cleaning up game cache helped)
How long did you test the RAM for?
I've known memtest86 to either miss errors or it simply wasn't ran long enough and another way to check that it isn't the ram that's at issue is to run the system using only one stick of RAM.
If you have two or four sticks then remove them all apart from one stick. Now try running a game or something that normally triggers a bsod event.
If the machine bsod's then stop testing and change to another stick making sure you keep note of which sticks have been tried and which haven't.
If you find a stick or sticks which don't bsod when tested then you'll know that they are ok and the others are bad.
Is your RAM all from the same manufacturer?
If that fails to work please run the driver verifier.
This easy to follow guide will show you how to run the verifier:
Using Driver Verifier to fix Blue Screen of Death (BSOD) errors - Troubleshooter On occasion the verifier can cause a boot loop. To stop this you'll need to boot into windows using a recovery drive/disc, enter safe mode and turn off the verifier.
How to Create and Use a Recovery Drive or System Repair Disc in Windows 8 or 10