This is a video hardware error, BugCheck 116.
STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card (see Significant Posts section below)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\Downloads\A-Rar\Windows7_BSOD_jcgriff2\082210-21715-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50
Debug session time: Sun Aug 22 20:06:20.872 2010 (GMT-4)
System Uptime: 10 days 21:50:31.682
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80071454e0, fffff88003b8ec80, 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+6c80 )
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: fffffa80071454e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003b8ec80, 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+6c80
fffff880`03b8ec80 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`02e8d988 fffff880`04506ef8 : 00000000`00000116 fffffa80`071454e0 fffff880`03b8ec80 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e8d990 fffff880`04506c02 : fffff880`03b8ec80 fffffa80`071454e0 fffffa80`0903d680 fffffa80`08ad4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02e8d9d0 fffff880`045adf07 : fffffa80`071454e0 00000000`00000000 fffffa80`0903d680 fffffa80`08ad4410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02e8da00 fffff880`045d7b75 : 00000000`ffffffff 00000000`039a0145 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e8dae0 fffff880`045d62bb : 00000000`00000102 00000000`00000002 00000000`039a0145 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02e8db10 fffff880`045a92c6 : ffffffff`ff676980 fffffa80`08ad4410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02e8dbb0 fffff880`045d5e7a : 00000000`00000000 fffffa80`0903d680 00000000`00000080 fffffa80`08ad4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02e8dcc0 fffff800`0311ec06 : 00000000`fffffc32 fffffa80`08adab60 fffffa80`06a05040 fffffa80`08adab60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02e8dd00 fffff800`02e58c26 : fffff800`02ff4e80 fffffa80`08adab60 fffff800`03002c40 fffff880`01262534 : nt!PspSystemThreadStartup+0x5a
fffff880`02e8dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+6c80
fffff880`03b8ec80 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+6c80
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
Read through the thread below for information on this stop error
Video's crashing the display driver (ATI HD5870)
Please update this driver: ASACPI.sys Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
You also have another out of date driver. Win 7 generally does like older drivers. They can and do cause conflicts, memory corruption, and crashes. If you can, update this driver; I do not think an update is available.
L1E62x64.sys Thu Jun 11 02:45:22 2009 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20). Atheros, Wireless LAN, WLAN, 2.4/5-GHz, 802.11a/b/g, 802.11b/g, 802.11n, Radio-on-a-Chip, Overview, Networking, Products and Technology
After you update ASACPI.sys, run your system and see how it does.
Quote