Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\pboong\Windows_NT6_BSOD_jcgriff2\042712-25428-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`0309f650
Debug session time: Fri Apr 27 09:34:29.341 2012 (UTC - 6:00)
System Uptime: 0 days 0:52:08.152
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 119, {1, cae77, cb31b, cb31a}
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 : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000cae77
Arg3: 00000000000cb31b
Arg4: 00000000000cb31a
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 9
LAST_CONTROL_TRANSFER: from fffff8800154122f to fffff80002ed7c80
STACK_TEXT:
fffff880`0311b398 fffff880`0154122f : 00000000`00000119 00000000`00000001 00000000`000cae77 00000000`000cb31b : nt!KeBugCheckEx
fffff880`0311b3a0 fffff880`077bdeb9 : fffffa80`065568d0 00000000`000cae77 00000000`00000000 00000000`000cb31b : watchdog!WdLogEvent5+0x11b
fffff880`0311b3f0 fffff880`077be125 : fffffa80`06f62000 fffff880`0311b520 00000000`000011ac 0000057f`faf827a8 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`0311b420 fffff880`077bdf76 : 00000000`000cae77 fffff880`0768e3ae fffffa80`06f52000 00000000`00000001 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`0311b470 fffff880`076c513f : fffffa80`064a7480 0000057f`faf827a8 fffffa80`0507d850 fffffa80`06556c80 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0311b4a0 fffff880`07592362 : fffffa80`06556c80 00000000`00000000 00000000`00000000 fffff880`08212605 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0311b4d0 fffffa80`06556c80 : 00000000`00000000 00000000`00000000 fffff880`08212605 0000057f`faf827a8 : atikmpag+0x5362
fffff880`0311b4d8 00000000`00000000 : 00000000`00000000 fffff880`08212605 0000057f`faf827a8 0000057f`f9aa9728 : 0xfffffa80`06556c80
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`077bdeb9 c744244053eeffff mov dword ptr [rsp+40h],0FFFFEE53h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
Followup: MachineOwner
---------
The above crash appears to be related to your graphics card. You also have some 0x116 VIDEO_TDR_FAILURE crashes.
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