ATI driver has stopped responding and recovered then BSOD

Gowry · 04 Jun 2015

I have been getting a display driver crash and recover followed by a BSOD when trying to restart a game, it happens intermittently with pretty much any game but most frequently World of Tanks. The issue started 2-3 months ago as described, went away for a month then returned. I upgraded pretty much my entire computer as it was nearly 8 years old anyways, and got the same error i was getting with my old setup....the only hardware i havent changed is my PSU which is a corsair GS800 and my hard drives. Any help or thoughts are appreciated.

ICIT2LOL · 06 Jun 2015

Hello and welcome Gowry mate there are issues a=with the graphics still

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e602010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e0b848, 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+b848
fffff880`03e0b848 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`04972858 fffff880`04117cbc : 00000000`00000116 fffffa80`0e602010 fffff880`03e0b848 00000000`00000000 : nt!KeBugCheckEx
fffff880`04972860 fffff880`041179c6 : fffff880`03e0b848 fffffa80`0e602010 fffffa80`13af7010 fffffa80`0eefa410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`049728a0 fffff880`041bef07 : fffffa80`0e602010 00000000`00000000 fffffa80`13af7010 fffffa80`0eefa410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`049728d0 fffff880`041ecd7e : 00000000`ffffffff 00000000`0003bd11 fffff880`04972a30 fffffa80`0eefa410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`049729b0 fffff880`041e86af : fffffa80`0eefa410 ffffffff`feced300 00000000`00000000 fffff880`041bb2f2 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`049729f0 fffff880`041e7023 : fffffa80`0eefa410 00000000`00000002 fffff880`041e6dc0 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`04972ae0 fffff880`041e72fe : 00000000`00000000 00000000`00000002 00000000`00000002 fffff880`041e8a3d : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`04972b10 fffff880`041ba2c6 : ffffffff`ff676980 fffffa80`0eefa410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`04972bb0 fffff880`041e6e7a : 00000000`00000000 fffffa80`137f2230 00000000`00000080 fffffa80`0eefa410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04972cc0 fffff800`02d69bc6 : 00000000`fffffc32 fffffa80`0eeff060 fffffa80`0cd49b30 fffffa80`0eeff060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04972d00 fffff800`02aa4bc6 : fffff800`02c40e80 fffffa80`0eeff060 fffff800`02c4ec40 d0325277`446f536e : nt!PspSystemThreadStartup+0x5a
fffff880`04972d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+b848
fffff880`03e0b848 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+b848
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
Followup: MachineOwner

Now if you have the Catalyst Control Centre installed uninstall it and see if that makes any difference because that is what the bug check is suggesting to do.
I am guessing you have the updated driver installed if not then redo that too but get rid of CCC if you have it.

Gowry · 06 Jun 2015

K will do and thanks for the help, here is crossing my fingers....will reply in a few days and mark solved if all is well

Gowry · 16 Jul 2015

Alright final update.
Uninstalling CCC didnt help, it seems to be, after some testing, most likely a world of tanks mod, not sure which one, that would time out my driver. After uninstalling the mods i have had no problems. I have played several other games since this issue without problem, world of tanks included.
Thanks

ICIT2LOL · 17 Jul 2015

No problems mate glad it got sorted - well done!