Solved BSOD playing any game, randomly, error 0x0000007E

[Cheezebell]

As said suggested in the title, I've been getting BSOD constantly the past few days playing many games (even Terraria) at seemingly random times or just immediately after launching a game. Tried switching drivers but that did nothing, reset the CMOS on my mobo, still getting BSOD. I'm not quite sure what to do but any help would be greatly appreciated and I have the details of my last BSOD in the file attached. (Edit: I also get BSOD from time to time viewing Twitch)

 

[Arc]

Hi Cheezebell.

Dont use a BETA display driver.

Uninstall the installed display driver using DDU. 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.
_____________________________________

BugCheck 116, {fffffa8006db34e0, fffff88003e0b848, 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006db34e0, 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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`03cbf898 fffff880`1305d134 : 00000000`00000116 fffffa80`06db34e0 fffff880`03e0b848 00000000`00000000 : nt!KeBugCheckEx
fffff880`03cbf8a0 fffff880`1305ce3e : fffff880`03e0b848 fffffa80`06db34e0 fffffa80`0f80e110 fffffa80`09bff010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03cbf8e0 fffff880`14392f13 : fffffa80`06db34e0 00000000`00000000 fffffa80`0f80e110 fffffa80`09bff010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03cbf910 fffff880`143c0ed6 : 00000000`ffffffff 00000000`001b57b3 fffff880`03cbfa70 fffffa80`09bff010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03cbf9f0 fffff880`143bc82b : fffffa80`09bff010 ffffffff`feced300 00000000`00000000 00024eae`0000000b : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03cbfa30 fffff880`143bb19f : fffffa80`09bff010 00000000`00000002 fffff880`03cbfb90 fffff880`03cbfb80 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`03cbfb20 fffff880`143bb47a : 00000000`00000000 00000000`00000002 0000000b`000005e4 fffff880`143bcbb9 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`03cbfb50 fffff880`1438e2d2 : ffffffff`ff676980 fffffa80`09bff010 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`03cbfbf0 fffff880`143baff6 : fffffa80`0f80e110 fffffa80`0f80e110 00000000`00000080 fffffa80`09bff010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03cbfd00 fffff800`0375eb8a : 00000000`fffffc32 fffffa80`09c2e610 fffffa80`06a0c040 fffffa80`09c2e610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03cbfd40 fffff800`034b18e6 : fffff800`0363ce80 fffffa80`09c2e610 fffff800`0364acc0 00740073`00790053 : nt!PspSystemThreadStartup+0x5a
fffff880`03cbfd80 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
---------

1: kd> lmvm atikmpag
start             end                 module name
fffff880`03e00000 fffff880`03e96000   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

 

[Cheezebell]

Thank you for the help! I'm getting right on to uninstall the beta drivers and re-install the proper drivers to run that stress test!

 

[Cheezebell]

Okay I'm back after running furmark for over an hour lol (I was gaming on my Wii U so I decided to just keep running it for a while) and I'll attach the screenshot I took of the data. It seemed like it was doing alright throughout the test or so I think.

 

[Arc]

OK, now test some games. Report us how it went.

 

[Cheezebell]

I only had a bit of time as I had to leave for vacation but in my time after the Furmark test I was able to run Dark Souls II just fine, but one single time I got a crash, though I was just on Chrome browsing reddit for a couple minutes. I think that it worked though, thank you so much for lending me a hand here lol, I wasn't sure if it was the drivers causing issues but I think that resolved the issue.