BSOD random GPU, error 0x00000116

[alex837]

Hi everyone! My pc has been crashing since 4 days due to this BSOD. I found it's a GPU error using some softwares, but i don't understand how to fix it. I have already installed the last drivers.
I don't know if it's related to this problem, but everyday when i left my pc in idle i find it stuck on a black screen and nothing works, so i have to restart. Can you please help me? Thank you

 

[Arc]

Hi alex837.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

How To Clear CMOS (Reset BIOS)
​

Uninstall the installed display driver using Display Driver Uninstaller. Then install the CCC 14.4 WHQL only.

When done, 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.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts
​

Also let us know the wattage of the installed PSU.

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: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .
_______________________________________________

BugCheck 116, {fffffa800a1614e0, fffff88007290848, 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a1614e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007290848, 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`07290848 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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`020cd928 fffff880`074e3134 : 00000000`00000116 fffffa80`0a1614e0 fffff880`07290848 00000000`00000000 : nt!KeBugCheckEx
fffff880`020cd930 fffff880`074e2e3e : fffff880`07290848 fffffa80`0a1614e0 fffffa80`078807c0 fffffa80`089b7410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`020cd970 fffff880`0758af13 : fffffa80`0a1614e0 00000000`00000000 fffffa80`078807c0 fffffa80`089b7410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`020cd9a0 fffff880`075b4cf1 : fffff8a0`ffffffff 00000000`000762fa 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`020cda80 fffff880`075862e1 : fffffa80`089b7410 fffffa80`0000000d 00000000`000762fa 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`020cdab0 fffff880`075b2ff6 : 00000000`00000000 fffffa80`0abc5d50 00000000`00000080 fffffa80`089b7410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`020cdbc0 fffff800`03379b8a : 00000000`fffffc32 fffffa80`08ffcb50 fffffa80`06b5bb30 fffffa80`08ffcb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`020cdc00 fffff800`030cc8e6 : fffff880`030a5180 fffffa80`08ffcb50 fffff880`030b0040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`020cdc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`07285000 fffff880`0731b000   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