Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\EmpNaval\Windows_NT6_BSOD_jcgriff2\032812-32900-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03419000 PsLoadedModuleList = 0xfffff800`0365d650
Debug session time: Wed Mar 28 02:36:13.476 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:52.959
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80074054e0, fffff88006a079e0, 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+79e0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80074054e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006a079e0, 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.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+79e0
fffff880`06a079e0 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0872a9c8 fffff880`06d1f000 : 00000000`00000116 fffffa80`074054e0 fffff880`06a079e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0872a9d0 fffff880`06d1ed0a : fffff880`06a079e0 fffffa80`074054e0 fffffa80`05f06d50 fffffa80`06aa9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0872aa10 fffff880`06dc5f07 : fffffa80`074054e0 00000000`00000000 fffffa80`05f06d50 fffffa80`06aa9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0872aa40 fffff880`06defb75 : 00000000`ffffffff 00000000`00001934 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0872ab20 fffff880`06dee2bb : 00000000`00000102 00000000`00000000 00000000`00001934 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0872ab50 fffff880`06dc12c6 : ffffffff`ff676980 fffffa80`06aa9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0872abf0 fffff880`06dede7a : 00000000`00000000 fffffa80`05f06d50 00000000`00000080 fffffa80`06aa9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0872ad00 fffff800`0372ff7a : 00000000`fffffc32 fffffa80`06aa1b60 fffffa80`03b66040 fffffa80`06aa1b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0872ad40 fffff800`034869c6 : fffff800`0360ae80 fffffa80`06aa1b60 fffff800`03618cc0 fffff880`01250384 : nt!PspSystemThreadStartup+0x5a
fffff880`0872ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+79e0
fffff880`06a079e0 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+79e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f3b14b8
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
You had a TDR stop error:
These are all stop 0x116 VIDEO_TDR_FAILURE conditions.
It's not a true crash, in the sense that the bluescreen 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 OSs 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.
The above quote was taken from https://www.sevenforums.com/crashes-d...tml#post280172, which is linked to in usasma's thread about this error. Closely follow the first three posts of usasma's thread outlining STOP 0x116: VIDEO_TDR_ERROR troubleshooting and proceed through each step. Let us know if you need further help.
Quote