Continuous BSOD 0x116 when starting PC for the first time of the day

hiilopi · 03 Mar 2015

Hello,

I've been having this issue (BSOD 0x00000116 & ATIkmpag.sys) for about half a year now, trying to solve the problem with the help of my father. Sadly we could not find the core problem.

Detailed description of what has been happening:
I start the Computer for the first time of the day (after about ~6-8 hours of beeing turned off) what follows is a blackscreen and then the "HDMI1 - No Signal" text on my monitor. I hear the windows startup sound in the background (I can log in and shut down again with my keyboard: windows button -> left arrow key -> Enter).
After 20-30 minutes I try again. My Monitor now gets a Signal and I can see everything but then it freezes and I get those continuous BSODs for about another half an hour. Sometimes I dont get the Bluescreens or only 1-2, but the blackscreen is always there (this is another mystery...).

What is to note is that the computer runs totally fine after one hour. I can open as many programs and games as I want its not crashing, I can leave it turned on for 2 days and it will not crash. Its only this single hour each day that I get those BSOD.
Attached should be the dump files (CROSSFIRE PC)

Thanks in advance for taking your time to help me :)

Arc · 05 Mar 2015

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. Further steps will be needed depending on the result.
_____________________________________

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009fc4010, fffff8800420b848, 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+b848 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009fc4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800420b848, 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`0420b848 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`04194888 fffff880`04321134 : 00000000`00000116 fffffa80`09fc4010 fffff880`0420b848 00000000`00000000 : nt!KeBugCheckEx
fffff880`04194890 fffff880`04320e3e : fffff880`0420b848 fffffa80`09fc4010 fffffa80`09009c00 fffffa80`08d2f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`041948d0 fffff880`043c8f13 : fffffa80`09fc4010 00000000`00000000 fffffa80`09009c00 fffffa80`08d2f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04194900 fffff880`043f2cf1 : 00000000`ffffffff 00000000`0000222a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`041949e0 fffff880`043f1437 : 00000000`00000102 00000000`00000004 00000000`0000222a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04194a10 fffff880`043c42d2 : ffffffff`ff676980 fffffa80`08d2f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04194ab0 fffff880`043f0ff6 : 00000000`00000000 fffffa80`093bf010 00000000`00000080 fffffa80`08d2f010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04194bc0 fffff800`02f24b8a : 00000000`fffffc32 fffffa80`08ae6b50 fffffa80`066f6b30 fffffa80`08ae6b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04194c00 fffff800`02c778e6 : fffff880`009ef180 fffffa80`08ae6b50 fffff880`009fa0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04194c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

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

7: kd> lmvm atikmpag
start             end                 module name
fffff880`04200000 fffff880`04296000   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

hiilopi · 06 Mar 2015

Okey thanks :) I wasnt even aware that I was using a BETA driver.
I have uninstalled every previous drivers using DDU now and installed the new 14.4 WHQL driver.
I hope this fixed the problem. I'm going to update this thread if the problem still occurs.

Arc · 06 Mar 2015

That was the first step to be taken to troubleshoot a stop 0x116. If the issue is a deeper one, some more actions may be needed there.

hiilopi · 08 Mar 2015

Okay so I didnt use my PC for 2 days and today I turned it on and it was the same as usual at first.
Waiting 30 minutes while watching the "No Signal" screen. Then restart it and suddenly it freezes at the desktop, restart it again and it happens again. After the next restart it works but when I tried opening chrome I get the same bluescreen again (0x116 and atikmpag). The computer only works at Safe Mode or if I go through many restarts, freezes and bluescreens.

So I tried a BIOS-reset by taking out the battery, waiting 3 minutes and putting it in again.
I have no idea how to fix those issues, maybe the graphics card is not compatible with the motherboard?

Thanks :)

Arc · 08 Mar 2015

JVHokiloki said:

After the next restart it works but when I tried opening chrome I get the same bluescreen again (0x116 and atikmpag).

Blue Screen of Death (BSOD) Posting Instructions

hiilopi · 08 Mar 2015

here you go nice sir :)

Arc · 08 Mar 2015

It is BSODing with 14.4 WHQL too.

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.

hiilopi · 08 Mar 2015

Ok so I ran the test for 20 minutes. I had NO crashes/BSOD, no artifacts (maybe the latter is an artifact), but at minute 10 and counting my fps began dropping from the standard 22 to 11 and at that moment the GPU-usage went from 99% (i had 99% all the time, except during those fps drops) to 64%. Those fps drops happened about ~30-50 times in ~30 second intervals.

The attachment is a screenshot at nearly the end when one of those fps drops happened. I tried doing one at the end with the F9 option within Furmark but this made the program crash... (just the program not the graphics card or whatsoever)

Arc · 08 Mar 2015

F9 crashes furmark sometimes. Sniping tool works better. :) At that high GPU usage,framerate may drop, that is usual.
The heat is remarkably low, too.

Anyway, apparently the card is working fine. But the BSODs should not be there, unless it is a very random failure from the part of the card which is not caught by the stress test.

If the BSODs continue to happen, it would be the best that you apply any other card and see how it goes.

I recently had a cold boot issue with a new motherboard. No troubleshooting lead to anything. Then I did RMA the board, all is fine now. Sometimes hardware fail to work that is too random to be pointed out by a test.