BSOD while mining

I built a new computer a day ago, and haven't really had any problems with it until tonight. I was running cgminer mining some crypto, I wasn't watching my computer when I heard the windows startup sound. I logged in and sure enough there was the Windows has recovered from an unexpected shutdown message. Luckily I had already configured it to create dump files. I followed the instructions on the BSOD sticky post and created my file. Thanks for any help in advance!

System Specs:
ASUS Z87-A
Intel i5 4670k
ASUS R9 270x TOP
8GB GSkill ram
Corsair 600 watt PSU

Hi kadrek.

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 .

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
____________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8006bad010, fffff880040dbd7c, 0, d}

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

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: fffffa8006bad010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880040dbd7c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+bd7c
fffff880`040dbd7c 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04bcb758 fffff880`02d16140 : 00000000`00000116 fffffa80`06bad010 fffff880`040dbd7c 00000000`00000000 : nt!KeBugCheckEx
fffff880`04bcb760 fffff880`02d15ec7 : fffff880`040dbd7c fffffa80`06bad010 fffffa80`06987b00 fffffa80`07ac1010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04bcb7a0 fffff880`02dbcf13 : fffffa80`06bad010 00000000`00000000 fffffa80`06987b00 fffffa80`07ac1010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`04bcb7d0 fffff880`02deaed6 : 00000000`ffffffff 00000000`0000cf6a fffff880`04bcb930 fffffa80`07ac1010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04bcb8b0 fffff880`02de682b : fffffa80`07ac1010 ffffffff`feced300 00000000`00000002 000018eb`00000001 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`04bcb8f0 fffff880`02de519f : fffffa80`07ac1010 00000000`00000002 fffff880`02de4f3c 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`04bcb9e0 fffff880`02de547a : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`04bcba10 fffff880`02db82d2 : ffffffff`ff676980 fffffa80`07ac1010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`04bcbab0 fffff880`02de4ff6 : 00000000`00000000 fffffa80`06987b00 00000000`00000080 fffffa80`07ac1010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04bcbbc0 fffff800`02d2f2ea : 00000000`fffffc32 fffffa80`07b704c0 fffffa80`066f0ae0 fffffa80`07b704c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04bcbc00 fffff800`02a838e6 : fffff800`02c0de80 fffffa80`07b704c0 fffff800`02c1bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`04bcbc40 00000000`00000000 : fffff880`04bcc000 fffff880`04bc6000 fffff880`05a53d70 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bd7c
fffff880`040dbd7c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bd7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5298baf8

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

1: kd> lmvm atikmpag
start             end                 module name
fffff880`040d0000 fffff880`0416f000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 29 21:34:08 2013 (5298BAF8)
    CheckSum:         000A54B8
    ImageSize:        0009F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

For the display driver, you have to use the latest WHQL only, not any BETA.

Any glitches during furmark is unhealthy sign for the GPU.

All your latest BSODs are stop 0x116 obviously display issue and nothing else.

If you are overclocking, set all the hardware to default and see how it goes.

If you have the latest WHQL of the display driver installed, If you havent overclocked the hardware, and as the system is not overheating, then you may have a scope to blame the GPU. If furmark shows anyhow artifacts, your blame is justified.

In that case, you may plan to RMA the GPU.