BSOD x116

[iball]

I have cfire 5770 and whenever I play Oblivion I get BSOD's. Strangely I have not experienced the problem with other games like BF2, Portal 2, DA2, Civ 5 etc.

I get a x116 error which when I read around means a video driver error, but I am using the latest drivers 11.5, I had this problem (or similar BSOD's) with 11.4 and 11.3.

Here are my dumps.

 

[zigzag3143]

I have cfire 5770 and whenever I play Oblivion I get BSOD's. Strangely I have not experienced the problem with other games like BF2, Portal 2, DA2, Civ 5 etc.

I get a x116 error which when I read around means a video driver error, but I am using the latest drivers 11.5, I had this problem (or similar BSOD's) with 11.4 and 11.3.

Here are my dumps.

Classic video timeout. The system attempted to reset the video card but it took too long. Causes include driver, card itself, power, heat, etc.

I would start by re-installing your video driver this way (I know you already have)

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\051611-28548-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0341a000 PsLoadedModuleList = 0xfffff800`03657e50
Debug session time: Mon May 16 13:59:44.696 2011 (GMT-4)
System Uptime: 0 days 15:35:54.491
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005385010, fffff88003f2a45c, 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+745c )

Followup: MachineOwner
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005385010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f2a45c, 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+745c
fffff880`03f2a45c 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`06fad9c8 fffff880`040c1ef8 : 00000000`00000116 fffffa80`05385010 fffff880`03f2a45c 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fad9d0 fffff880`040c1c02 : fffff880`03f2a45c fffffa80`05385010 fffffa80`0545a010 fffffa80`03d06410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06fada10 fffff880`04168f07 : fffffa80`05385010 00000000`00000000 fffffa80`0545a010 fffffa80`03d06410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06fada40 fffff880`04192b75 : 00000000`ffffffff 00000000`0036ebf3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06fadb20 fffff880`041912bb : 00000000`00000102 00000000`00000003 00000000`0036ebf3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06fadb50 fffff880`041642c6 : ffffffff`ff676980 fffffa80`03d06410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06fadbf0 fffff880`04190e7a : 00000000`00000000 fffffa80`07bc31b0 00000000`00000080 fffffa80`03d06410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06fadd00 fffff800`0372ec06 : 00000000`fffffc32 fffffa80`05f0bb60 fffffa80`03cce040 fffffa80`05f0bb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06fadd40 fffff800`03468c26 : fffff880`02f63180 fffffa80`05f0bb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06fadd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+745c
fffff880`03f2a45c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+745c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3558

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8005385010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f2a45c, 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+745c
fffff880`03f2a45c 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`06fad9c8 fffff880`040c1ef8 : 00000000`00000116 fffffa80`05385010 fffff880`03f2a45c 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fad9d0 fffff880`040c1c02 : fffff880`03f2a45c fffffa80`05385010 fffffa80`0545a010 fffffa80`03d06410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06fada10 fffff880`04168f07 : fffffa80`05385010 00000000`00000000 fffffa80`0545a010 fffffa80`03d06410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06fada40 fffff880`04192b75 : 00000000`ffffffff 00000000`0036ebf3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06fadb20 fffff880`041912bb : 00000000`00000102 00000000`00000003 00000000`0036ebf3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06fadb50 fffff880`041642c6 : ffffffff`ff676980 fffffa80`03d06410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06fadbf0 fffff880`04190e7a : 00000000`00000000 fffffa80`07bc31b0 00000000`00000080 fffffa80`03d06410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06fadd00 fffff800`0372ec06 : 00000000`fffffc32 fffffa80`05f0bb60 fffffa80`03cce040 fffffa80`05f0bb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06fadd40 fffff800`03468c26 : fffff880`02f63180 fffffa80`05f0bb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06fadd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+745c
fffff880`03f2a45c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+745c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3558

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

2: kd>

 

[fimble]

FYI. There were issues with the v11.4 for some people.

 

[iball]

So I used Phyxion's driver sweeper because Guru3d doesn't update theirs. I cleaned then entire amdness and then installed 11.5 version of the drivers. CCC says my idle clocks are 157/300. I remember that when I had set to default last time that my cards would keep failing and crashing...but I will not change it to 200/400 (settings that worked last time) until I see some errors.

Also, I cannot say whether or not this solution has worked because I usually have to play Oblivion for hour or more to notice (Last BSOD was 16+ hours of play, I left it on overnight).