BSOD computer keeps restarting (kernel-power 41 task category 63)

I am having extremely frequent reboots, I built this computer brand new and im trying to figure out which parts are faulty...

Have reformatted multiple times, updated all drivers etc... right now it's at a point where it reboots every time I open my mining software

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2014-01-23T15:34:59.194009900Z" />
<EventRecordID>109839</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Mining-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">278</Data>
<Data Name="BugcheckParameter1">0xfffffa80097af190</Data>
<Data Name="BugcheckParameter2">0xfffff8800400bd7c</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x2</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

I have followed the BSOD instructions and also did a debug with SF_debug tool... I have attached that ZIP

Any help is extremely appreciated

First off, thanks for the really fast reply!

My PSU is Antec 850w

I am using 2x r9 290 gpu

I am using this computer for mining so the gpu load is constantly at 100% when it is mining

Right now when I open my mining software at all it crashes and reboots the computer. Was running fine for close to a month

The link below says I need 608w of power for my system which should be enough since I am using 850w. But I am running both GPU at 100% load when the system is in use... is that a problem?

I will try and install latest drivers

Arc said:

Hi blackrabbit.

It is a stop 0x116, a display related error.

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

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

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the 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: Speccy - Publish Snapshot of your System Specs .

Let us know the results.
________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007781010, fffff88003ab1d7c, 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+bd7c )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007781010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003ab1d7c, 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+bd7c
fffff880`03ab1d7c 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.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`06cac928 fffff880`03d11054 : 00000000`00000116 fffffa80`07781010 fffff880`03ab1d7c 00000000`00000000 : nt!KeBugCheckEx
fffff880`06cac930 fffff880`03d10d5e : fffff880`03ab1d7c fffffa80`07781010 fffffa80`076b9010 fffffa80`08969410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06cac970 fffff880`03db7f13 : fffffa80`07781010 00000000`00000000 fffffa80`076b9010 fffffa80`08969410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06cac9a0 fffff880`03de1cf1 : 00000000`ffffffff 00000000`00001bae 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06caca80 fffff880`03db32e1 : fffffa80`08969410 ffffffff`00000011 00000000`00001bae 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06cacab0 fffff880`03ddfff6 : 00000000`00000000 fffffa80`09618a80 00000000`00000080 fffffa80`08969410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`06cacbc0 fffff800`0316fede : 00000000`020be287 fffffa80`0864bb50 fffffa80`072f0b30 fffffa80`0864bb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06cacc00 fffff800`02ec2906 : fffff880`009eb180 fffffa80`0864bb50 fffff880`009f5fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06cacc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bd7c
fffff880`03ab1d7c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bd7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  528f7074

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
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03aa6000 fffff880`03b45000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Nov 22 20:25:48 2013 (528F7074)
    CheckSum:         000A0E9C
    ImageSize:        0009F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4