It seems the BSODs are back. Here is the new crash dump, same error as the old crash dumps. Again in Skyrim, only in Skyrim.
It seems that everything stabilizes for a while after a driver reinstallation, but then things start to go downhill from there.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\040313-38891-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*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
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329f670
Debug session time: Wed Apr 3 02:28:02.526 2013 (UTC - 4:00)
System Uptime: 0 days 0:38:36.258
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8005aaf4e0, fffff88004cdd410, 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+9410 )
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: fffffa8005aaf4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004cdd410, 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+9410
fffff880`04cdd410 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0233ba18 fffff880`050ec000 : 00000000`00000116 fffffa80`05aaf4e0 fffff880`04cdd410 00000000`00000000 : nt!KeBugCheckEx
fffff880`0233ba20 fffff880`050ebd0a : fffff880`04cdd410 fffffa80`05aaf4e0 fffffa80`0566bd50 fffffa80`061f1410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0233ba60 fffff880`05192f07 : fffffa80`05aaf4e0 00000000`00000000 fffffa80`0566bd50 fffffa80`061f1410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0233ba90 fffff880`051c0d5a : 00000000`ffffffff 00000000`000240c7 fffff880`0233bbf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0233bb70 fffff880`0518e29e : fffffa80`061f1410 ffffffff`feced300 fffffa80`06caf910 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0233bbb0 fffff880`051bae7a : 00000000`00000000 fffffa80`061d3c20 00000000`00000080 fffffa80`061f1410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`0233bcc0 fffff800`0337134a : 00000000`fffffc32 fffffa80`06e9bb50 fffffa80`03cec890 fffffa80`06e9bb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0233bd00 fffff800`030c1946 : fffff880`009e6180 fffffa80`06e9bb50 fffffa80`06ccbb50 fffffa80`061f9050 : nt!PspSystemThreadStartup+0x5a
fffff880`0233bd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+9410
fffff880`04cdd410 4055 push rbp
SYMBOL_NAME: atikmpag+9410
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50d21667
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------It seems that everything stabilizes for a while after a driver reinstallation, but then things start to go downhill from there.
