BlueScreen of Death. Windows 7 (64-bit) Locale ID: 1033

Question

Hello. I keep happening to get errors, when the computer Idles or goes in sleep mode. This isn't the first time, either.
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033
Additional information about the problem:
  BCCode: 116
  BCP1: FFFFFA8003EA34E0
  BCP2: FFFFF8800409EDC0
  BCP3: 0000000000000000
  BCP4: 000000000000000D
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1
Files that help describe the problem:
  C:\Windows\Minidump\042514-19843-01.dmp
  C:\Users\Zach\AppData\Local\Temp\WER-70481-0.sysdata.xml
Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
Minidump: https://onedrive.live.com/?cid=f535c11f3f3b6b66&id=F535C11F3F3B6B66%21134#cid=14F604FB3205F70D&id=14F604FB3205F70D%21105

Answer 1

ZV
Two issues.  The driver verified crash was related to readyboost.  I would turn it off at least to test, the others were called BCC116
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
 Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
 Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog  http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Bugcheck code 00000116
Bugcheck code 00000116
Bugcheck code 00000116
Bugcheck code 0000007F
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
Probably caused by : atikmpag.sys ( atikmpag+bdc0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
SYSTEM UP-TIME
System Uptime: 1 days 11:16:46.716
System Uptime: 2 days 4:48:03.890
System Uptime: 2 days 5:21:56.656
System Uptime: 0 days 0:00:14.976
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Apr 25 04:47:05.280 2014 (UTC - 4:00)
System Uptime: 1 days 11:16:46.716
BugCheck 116, {fffffa8003ea34e0, fffff8800409edc0, 0, d}
*** 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+bdc0 )
BUGCHECK_STR: 0x116
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Wed Apr 23 16:38:38.470 2014 (UTC - 4:00)
System Uptime: 2 days 4:48:03.890
BugCheck 116, {fffffa800597e320, fffff880040f6dc0, 0, d}
*** 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+bdc0 )
BUGCHECK_STR: 0x116
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 21 04:18:13.236 2014 (UTC - 4:00)
System Uptime: 2 days 5:21:56.656
BugCheck 116, {fffffa80047114e0, fffff88003a92dc0, 0, 2}
*** 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+bdc0 )
BUGCHECK_STR: 0x116
PROCESS_NAME: System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Sat Nov 9 07:15:24.664 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:14.976
BugCheck 7F, {8, 80050031, 6f8, fffff88000f9cf9b}
Probably caused by : partmgr.sys ( partmgr!PmReadWriteCompletion+9b )
BUGCHECK_STR: 0x7f_8
PROCESS_NAME: System
Wanikiya and Dyami--Team Zigzag