Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {31, fffffa800a372540, fffff8800bdb6000, fffff8a004f7025c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7171 )
Followup: MachineOwner
Hi,
the above Bugcheck 1A means a severe memory management issue occurred and the parameter which shows what type of Bugcheck 1A it is, is 31:
0x31
The image relocation fix-up table or code stream has been corrupted. This is probably a hardware error.
ref:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx
However I would consider any third party software your running as suspect as I see your running system information apps, anti-cheat apps as well as Rivatuner or at least a version of Rivatuner which itself is well known for causing bsod issues with Windows 7.
Test by removing each one in turn and see if the bsod stops.
Some of your drivers are also in need of updating.
Rt64win7.sys Wed Dec 26 17:17:50 2012: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet
Link Removed
RTKVHD64.sys Wed Aug 21 05:48:22 2013: Realtek High Definition Audio Function Driver
Link Removed
If after making the above changes the bsod still occurs then you need to go back and test the RAM. Sometimes it can be that Memtest86 may not find any errors within the 12hrs, that doesn't automatically mean the RAM is good. It could be that Memtest86 just didn't find the bug within that time frame. Each test memtest86 runs is different so it's a case of waiting to see if the memory will fail and usually 12hrs is long enough but sometimes it isn't as could be in your case. Now if you have a good idea of what will usually trip a bsod then you could test by running the machine on one stick of RAM at a time. Try to trip the bsod and see if it does it with one stick and not another. Obviously the stick which bsod's is the bad one.
Lastly I may already asked you but just check your Vram is ok too:
Link Removed