BSOD when playing 3D games

The tests passed

Here are the screen shots

I got some IRQL BSODs when I tried to play world of tanks.

Hi andywl94,

Please do NOT post in other threads + do not post in your own thread until somebody has responded. Posting in your own thread while nobody else has yet responded removes your thread from the unanswered threads list and that lessens the chance of a BSOD analyst looking into your thread. The unanswered thread list is where we are looking at first working from oldest threads to newest as the oldest are waiting the longest to ensure everybody gets helped. Please wait some more time until someone gets to you.

Jsnarch, please wait a few more minutes, I'm currently analyzing your logs :)
If you have in %systemroot% a file called memory.dmp, please upload this file to a 3rd party uploader (like dropbox, onedrive, google drive, etc.) and post a share link into your next reply. I believe this crash you're talking about is the last crash, unfortunately I can't open the dump for some reason and because that crash you mention occurs very infrequently I would like to have a look at it.

Please remove the Gigabyte software while troubleshooting, Gigabyte software is known for causing BSODs in the past and that hasn't changed.

Please uninstall AVG and use Microsoft Security Essentials as alternative while troubleshooting.
https://support.avg.com/SupportArtic...-uninstall-AVG

Code:

fffff880`0d884988  fffff880`018a3127Unable to load image avgmfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
 avgmfx64+0x17127

That is odd, it is the 0x24 from 3 days ago, it should've been overwritten (deleted and newly created) a few times.

Code:

Debug session time: Fri May  6 22:44:30.937 2016 (UTC + 2:00)

Possibly, IRQL is basically the priority scheme that Windows uses when processing, most often it is due to a IRQL level 2 which is for dispatching, DPC's and synchronisation, normally a proper IRQL for processing stuff that isn't for Windows is at level 0. A bad CPU could process the IRQL incorrect and thus process the data not at the right IRQL level.
However it more often happens that it is caused by drivers due to pagefaults at IRQL level 2, at that level only nonpaged memory, nonpaged memory is memory that is reserved for the system (used by drivers and Windows), can be accessed at which pagefault do not occur so a pagefault at IRQL level 2 is a violation.

I suggest that you follow the posting instructions for analysis :)

Ps, I'm well aware that I'm talking about things you might not understand, but explaining it all just takes a lot of time.