Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8009c5b4e0, fffff88010e30e98, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+ce98 )
Followup: MachineOwner
Hi,
of the dump files sent most are like the one posted above which means that for some reason your graphics driver did not reset within time. These are also known as 'TDR's' ( TDR stands for Timeout Detection and Recovery) and can be caused by many different things. The probable cause relates to your graphics driver and almost every dump file regardless of bugcheck pointed to the gpu driver as a possible issue
.
I checked through your dump file and you do have a few possible culprits although first let's deal with your graphics driver.
atikmdag.sys Fri Dec 04 17:14:28 2015: AMD Graphics driver:
Please remove this version of driver using an application called the Display Driver Uninstaller. This, when used in safe mode, ensures that everything is removed including anything left behind by previous driver installs.
Display Driver Uninstaller Once removed please install the latest version available for your card:
Desktop GVTDrv64.sys Tue Sep 05 08:10:02 2006: Gigabyte Easy Tune 6 driver (known
BSOD issues w/Win7) please remove.
Your main system drivers could also do with updating. You can find drivers for Windows 7 on your motherboard support page:
GIGABYTE - Motherboard - Socket AM3+ - GA-970A-DS3P (rev. 1.0) Check for system corruption by looking in the all programs area of the start menu for command prompt, right click on it, choose properties and then run as admin. Type:
sfc /scannow
Press enter and await results.
Make the above changes and see how you go. If you were overclocking the card please stop until the BSOD is stopped.
Post any new dump files.