BSOD while gaming, benchmarking or stressing, code 116

Windows 7 home premium 64bit retail fresh install
ASUS maximus gene-z/gen3 (few days old)
i5 2500K (few days old)
asus eah hd 4850 with zalman vf900 (couple of years old)
DDR3 1333 2x2GB (couple of years old)
kingston SSDNOW V+200 120gb (couple of days old)
NeoHe 430W (6 years old)

Just bought that new motherboard and the processor with it. Put everything together and did a fresh windows install. Installed the newest radeon drivers, but nearly everytime I start any game the system boots straight away giving code 116. Same thing with the windows system benchmark, 3dmark vantage, furmark stress test. Sometimes it will let me run a test or a game for a little while before booting but most of the time it's a boot before I see any action on the screen. Already reinstalled windows twice, tried the previous radeon drivers, ran memtest for around 6 hours without errors.

STOP 0x116: VIDEO_TDR_ERROR troubleshooting Tried to start with the steps in that topic, thinking that it was the same issue, but since the system boots straight away when I even try to run the furmark I decided to make a topic.

Buying a new gfx-card really isn't an issue, but I just want to know that doing so will fix the issue. The requested files are attached.

I really didn't need to take a look at the dumps to answer this based off of the very informative OP you gave, so thanks for that! However, I did anyway.

All dumps are the *116 TDR bugcheck, and as you've stated, you already know what the means and what can cause it. Yours points directly to the AMD video driver every time, and you've already said you've reinstalled Windows multiple times and tried different versions, so it's not just the latest driver.

It's a brand new computer, so I doubt there's a dust issues causing overheating, but I'd go ahead and monitor the temperature of the graphics card and the system just to be sure.

Just a suggestion, try updating your DirectX or repairing it: Download: DirectX End-User Runtime - Microsoft Download Center - Download Details

Ensure that the connection between the GPU and the pci-e slot isn't obstructed, etc, any other basic troubleshooting.

If all else fails, it's the card my friend, most likely the memory on the card. If you put the computer together very recently, you can call who you bought it from (for example Newegg), and they'll replace it. If you've purchased it and it's over the 30 day, but still early, you'll want to contact the manufacturer and explain to them exactly what you told us.

Dump for reference:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\032412-9094-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.20994.amd64fre.win7_ldr.110622-1505
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03082ed0
Debug session time: Sat Mar 24 12:19:04.252 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:19.547
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80087f2230, fffff88001c07840, ffffffffc0000001, 3}

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+7840 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80087f2230, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88001c07840, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+7840
fffff880`01c07840 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`0255d9d8 fffff880`056c8000 : 00000000`00000116 fffffa80`087f2230 fffff880`01c07840 ffffffff`c0000001 : nt!KeBugCheckEx
fffff880`0255d9e0 fffff880`0569b569 : fffff880`01c07840 fffffa80`071e8000 00000000`00000000 fffffa80`07181410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0255da20 fffff880`056c7dad : fffffa80`087f2230 fffffa80`087f2230 fffffa80`087f2230 fffffa80`07181410 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
fffff880`0255da60 fffff880`0576ef07 : fffffa80`087f2230 00000000`00000000 fffffa80`0b31c010 fffffa80`07181410 : dxgkrnl!TdrIsRecoveryRequired+0x245
fffff880`0255da90 fffff880`0579cd5a : 00000000`ffffffff 00000000`000079f7 fffff880`0255dbf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0255db70 fffff880`0576a29e : fffffa80`07181410 ffffffff`feced300 fffffa80`06faad50 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`0255dbb0 fffff880`05796e7a : 00000000`00000000 fffffa80`0b31c010 00000000`00000080 fffffa80`07181410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`0255dcc0 fffff800`03155bba : 00000000`01923378 fffffa80`06ee0b60 fffffa80`039b9890 fffffa80`06ee0b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0255dd00 fffff800`02e91106 : fffff880`03363180 fffffa80`06ee0b60 fffff880`0336dfc0 3265532f`6c72506f : nt!PspSystemThreadStartup+0x5a
fffff880`0255dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7840
fffff880`01c07840 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7840

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ebb331c

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Appreciate the fast answer, just wanted to be sure it was the card causing the crashes.
I updated DirectX like you suggested and while I'm not getting my hopes up just yet, that turned out to be really good advice. Now I was able to do a 15 minute furmark benchmark without a crash with the max temperature of 74 degrees celcius! There's no dust build up and I've checked the pci-e slot.

Even if the directx-update didn't fix the issue at least I now know to go and buy a new gpu. Thank you, will go ahead and marked this one solved.

Best of luck, post back when you receive your new card and let us know if everything's working as intended :)

Yeah, went out and bought a new card and been running the pc with multiple stresses and games non-stop all day!

Great! Glad to hear your issue is solved.