BSOD 0x00000116 atikmpag.sys when playing games.

Colaran · 18 Mar 2015

I'm having an issue when playing games, i can play a game for about 15 min then the computer gets stuck and as result the 0x00000116 atikmpag.sys blue screen.

My specs are :

Windows 7 x64
Intel i5 4590
Asrock H87 Pro4
Corsair Vengeance CML8GX3M2A1600C9 2x4gb
AMD Radeon R9 200 series
Western Digital Blue WD10EZEX 1TB
Corsair 750m
1 monitor

Done some research on the internet but all solutions didnt help.
Updated AMD drivers + a fresh install of windows 7 x64.. Still the crashes occurs

Sorry for my bad english.

Hopefully someone can help my with this problem.

Cheers

Arc · 18 Mar 2015

Hi Colaran.

Dont use a BETA display driver.

Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

Let us know for any further BSOD after doing it.
___________________________________________

Code:

BugCheck 116, {fffffa800c3de4e0, fffff88007017848, 0, 2}

*** 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+b848 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c3de4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007017848, 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`07017848 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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`02e63888 fffff880`10526134 : 00000000`00000116 fffffa80`0c3de4e0 fffff880`07017848 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e63890 fffff880`10525e3e : fffff880`07017848 fffffa80`0c3de4e0 fffffa80`0b356c80 fffffa80`0a648410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02e638d0 fffff880`070b1f13 : fffffa80`0c3de4e0 00000000`00000000 fffffa80`0b356c80 fffffa80`0a648410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02e63900 fffff880`070dbcf1 : 00000000`ffffffff 00000000`000e9d6f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02e639e0 fffff880`070da437 : 00000000`00000102 00000000`00000000 00000000`000e9d6f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02e63a10 fffff880`070ad2d2 : ffffffff`ff676980 fffffa80`0a648410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02e63ab0 fffff880`070d9ff6 : 00000000`00000000 fffffa80`074cfd50 00000000`00000080 fffffa80`0a648410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02e63bc0 fffff800`03518b8a : 00000000`fffffc32 fffffa80`0acb9b50 fffffa80`066a6740 fffffa80`0acb9b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02e63c00 fffff800`0326b8e6 : fffff880`03165180 fffffa80`0acb9b50 fffff880`0316ffc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
fffff880`02e63c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b848
fffff880`07017848 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
---------

3: kd> lmvm atikmpag
start             end                 module name
fffff880`0700c000 fffff880`070a2000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 21 07:38:54 2014 (546E9EB6)
    CheckSum:         00093077
    ImageSize:        00096000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Colaran · 22 Mar 2015

well re installed windows 7 and used the guru3d driver that you recommended, i can game now for about 1.5 hours, at least better then 15 min :)
Ingame (world of warcraft) many textures flashes, and when that happens the game will crash soon, and as result a blue screen.

attached a new log

tnx for the help

Arc · 24 Mar 2015

No BSOD dump is there in the uploaded zip, so it appears that there is no further BSOD.

Colaran · 25 Mar 2015

sorry wrong one, just had a blue screen while playing wow

Arc · 26 Mar 2015

If any of your hardware parts are overclocked, set them to defaults.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
_______________________________________________

Code:

BugCheck 117, {fffffa800c71b4e0, fffff88004c50dac, 0, 0}

*** 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+bdac )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa800c71b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004c50dac, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+bdac
fffff880`04c50dac ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`044cd350 fffff880`04d4372b : fffffa80`0c71b4e0 fffff8a0`0975b9a4 00000000`00000000 fffff880`04d4346d : watchdog!WdDbgReportRecreate+0xa3
fffff880`044cd870 fffff880`04d441a9 : fffff8a0`098b2ffc fffff8a0`100938e0 fffff8a0`0975b9a4 00000000`00157658 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`044cd8c0 fffff880`04d44e16 : fffffa80`0c71b4e0 fffffa80`0c71b4e0 fffffa80`06c3a7d0 fffffa80`0a4ca010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`044cd960 fffff880`10331f13 : fffffa80`0c71b4e0 00000000`00000000 fffffa80`06c3a7d0 fffffa80`0a4ca010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`044cd990 fffff880`1035fed6 : fffffa80`ffffffff 00000000`00016065 fffff880`044cdaf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`044cda70 fffff880`1032d2aa : fffffa80`0a4ca010 ffffffff`feced300 fffffa80`06c3a7d0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`044cdab0 fffff880`10359ff6 : 00000000`00000000 fffffa80`06c3a7d0 00000000`00000080 fffffa80`0a4ca010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`044cdbc0 fffff800`02d22b8a : 00000000`01a10c6b fffffa80`0ab08a00 fffffa80`066a6890 fffffa80`0ab08a00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`044cdc00 fffff800`02a758e6 : fffff800`02c00e80 fffffa80`0ab08a00 fffff800`02c0ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`044cdc40 00000000`00000000 : fffff880`044ce000 fffff880`044c8000 fffff880`078c0aa0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bdac
fffff880`04c50dac ??              ???

SYMBOL_NAME:  atikmpag+bdac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53507abb

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x117_image_atikmpag.sys

FAILURE_ID_HASH:  {fa4b6286-8c4a-e9c2-c89f-5612619e000e}

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`04c45000 fffff880`04ce8000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Apr 18 06:37:07 2014 (53507ABB)
    CheckSum:         000A6939
    ImageSize:        000A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4