Security Software:
Code:
ccsvchst.exe c:\program files (x86)\norton internet security\engine\19.6.2.10\ccsvchst.exe 1832 8 1024 10240 3/24/2012 3:57 AM 11.2.1.4 134.99 KB (138,232 bytes) 3/23/2012 5:42 AM
ccsvchst.exe c:\program files (x86)\norton internet security\engine\19.6.2.10\ccsvchst.exe 2864 8 1024 10240 3/24/2012 3:57 AM 11.2.1.4 134.99 KB (138,232 bytes) 3/23/2012 5:42 AM
Possible out of date drivers:
Code:
Alpham264 fffff880`04a4a000 fffff880`04a4f500 Tue Mar 20 03:51:03 2007 (45ffae87) 000058cb Alpham264.sys
Alpham164 fffff880`04a3d000 fffff880`04a49f00 Mon Jul 23 01:57:03 2007 (46a45f4f) 000134fc Alpham164.sys
Alpham264.sys
Alpham164.sys
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\hollowcrumlish\Windows_NT6_BSOD_jcgriff2\032412-22058-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a2650
Debug session time: Sat Mar 24 01:42:33.739 2012 (UTC - 6:00)
System Uptime: 0 days 0:08:09.128
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8002922010, fffff8800ff7baa4, ffffffffc000009a, 4}
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+ca1aa4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8002922010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ff7baa4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+ca1aa4
fffff880`0ff7baa4 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`03078b88 fffff880`0431d000 : 00000000`00000116 fffffa80`02922010 fffff880`0ff7baa4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03078b90 fffff880`042f0867 : fffff880`0ff7baa4 fffffa80`05eeb000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03078bd0 fffff880`0431ce0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`02922010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`03078c80 fffff880`0f237ec1 : fffffa80`073abcf0 00000000`00000080 00000000`00000000 fffffa80`05d90010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`03078d00 fffff800`03374f7a : 00000000`03038202 fffffa80`05e2a210 fffffa80`024d1040 fffffa80`05e2a210 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`03078d40 fffff800`030cb9c6 : fffff880`009e6180 fffffa80`05e2a210 fffff880`009f0f40 fffff880`0143c384 : nt!PspSystemThreadStartup+0x5a
fffff880`03078d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+ca1aa4
fffff880`0ff7baa4 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+ca1aa4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f347ad2
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
All your crashes were Video TDR failure errors:
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