View Single Post
25 Feb 2012  

Windows 7 Home Premium 64 Bit

OS Version:                6.1.7600 N/A Build 7600
Update to Service Pack 1 (SP1)
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]

Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]

Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

Service Pack 1 Download site
Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH

Antivirus Software? Good and Free system security combination.


Loading Dump File [D:\Kingston\BSODDmpFiles\Banecraft\Windows_NT6_BSOD_jcgriff2\022212-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Wed Feb 22 15:38:31.878 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:16.813
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800679e4e0, fffff88010081ae4, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1aeae4 )

Followup: MachineOwner

2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa800679e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010081ae4, 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:

fffff880`10081ae4 4883ec28        sub     rsp,28h






fffff880`043b4988 fffff880`040c0cbc : 00000000`00000116 fffffa80`0679e4e0 fffff880`10081ae4 00000000`00000000 : nt!KeBugCheckEx
fffff880`043b4990 fffff880`040c09c6 : fffff880`10081ae4 fffffa80`0679e4e0 fffffa80`08aafd50 fffffa80`088f4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`043b49d0 fffff880`04167f07 : fffffa80`0679e4e0 00000000`00000000 fffffa80`08aafd50 fffffa80`088f4410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`043b4a00 fffff880`04191b75 : 00000000`ffffffff 00000000`00003f74 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`043b4ae0 fffff880`041902bb : 00000000`00000102 00000000`00000000 00000000`00003f74 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`043b4b10 fffff880`041632c6 : ffffffff`ff676980 fffffa80`088f4410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`043b4bb0 fffff880`0418fe7a : 00000000`00000000 fffffa80`08aafd50 00000000`00000080 fffffa80`088f4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`043b4cc0 fffff800`03160166 : 00000000`fffffc32 fffffa80`08a41060 fffffa80`06720040 fffffa80`08a41060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`043b4d00 fffff800`02e9b486 : fffff800`03035e80 fffffa80`08a41060 fffff800`03043c40 fffff880`01247a90 : nt!PspSystemThreadStartup+0x5a
fffff880`043b4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

fffff880`10081ae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+1aeae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
Quote   Quote: Originally Posted by H2SO4 View Post
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, 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.
My System SpecsSystem Spec