BSOD playing Counterstrike Global Offensive and Payday 2 error 116

[Tribal]

I built my pc about a year and a half ago, and only recently have I run into these BSOD's. They always freeze the game I am playing, and when I go to reboot the game, it blue screens. It is most frustrating with payday, for it tends to happen more quickly when playing it. I have tried a clean install of drivers for my graphics card and that did not work. There was a lull at one point, but now it is almost constant. I would greatly appreciate any help at all.

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[Tribal]

That was quick. Hope this is what you were looking for.

 

[essenbe]

Hello Tribal, I will try to help you with this. When did you build this computer? You have dump files going back to 7/2014. Every one I checked was always the same reason.

BugCheck 116, {fffffa8006948210, fffff88004af9848, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for atikmpag.sys[/COLOR]
Probably caused by : atikmpag.sys ( atikmpag+b848 )

[COLOR=red]VIDEO_TDR_FAILURE (116[/COLOR])
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006948210, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004af9848, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

I'm sure you know that is your graphics driver. A TDR error is extremely difficult usually. TDR stands for Time Delay and Response. In other words your graphics drivers crashed but did not recover in time. Please reinstall your graphics driver, but do it thie way I am going to describe below.

I am going to give you some links that will help you get a good clean install and not have any drivers you don't need that will conflict with other drivers. Download a WHQL driver from http://www.sevenforums.com/graphic-cards/329659-latest-amd-catalyst-video-driver-windows-7-a.html . Once you have them downloaded, uninstall you current driver from control panel. next clean up any left over drivers from following this tutorial http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html and select only ATI Display Drivers. After you have done that and rebooted, install the new driver, only select custom install and install only what you have to. Very few people need most of what they include. You do not need the audio/HDMI drivers as you already have that in your Motherboard drivers. Unless there is some reason you need them, the only thing you really need is the Display Driver.

I would also like you to add to your system specs which PSU you are using and which CPU cooler you are using.

If you don't already have one, please find a graphics card program that will let you monitor your card temps at all times. Most card manufacturers provide those. If you don't already have one, you may try MSI Afterburner (MSI Afterburner). Also a CPU temp monitoring program to monitor your CPU temps.

If you are overclocking anything, please set it back to default levels.

After you have done that, upload the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2 after your next BSOD along with your CPU and GPU temps.

 

[Tribal]

I am still having BSOD's even after doing what you told me and my CPU temp never gets above 45C.

 

[essenbe]

If you are still having BSODs, upload the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2 and I'll have a look tomorrow morning.