BSOD - Computer freezes with black screen

Hi guys,

I have a PC with a AMD 7790 graphics card. The system competely freezes, the music or games stops and the mouse and keyboard are stuck. You have to hard reset the PC to fix it. Mostly after crashing, there is no BSOD dump or something so it's not easy to fit it. I installed all the newest drivers and updated all software.

Specs:
- AMD FX-6300
- ASRock 970 Pro3 R2.0
- ASUS HD7790-DC2OC-1GD5
- Be quiet! Pure Power L8 430W CM
- Kingston ValueRam 8 GB DDR3-1600 CL11
- Seagate Barracuda 7200.14 1 TB
- Windows 7 Ultimate x64

You can find the BSOD report here:
https://onedrive.live.com/?cid=868f...814&ithint=file,.zip&authkey=!AD5I3JXmOIC9z6M

What I did:
- Updated all drivers
- Updated all software
- Did a Memtest
- Did a chkdsk
- ...

At the beginning, the problems where a lot worser. The AMD OverDrive software overclocked the card automatically which was crashing the PC. With the new driver, it looks like that problem is fixed. The PC crashed after 15 minutes playing or something. I also uninstalled AMD Fuel. The PC now crashes after 2/3 hours of playing iRacing or listening to music, so it's a big improvement.

I think it's the graphics card. What do you think?

Regards,

WindowsPro

The dumpfile is a BugCheck 117 Probably caused by : atikmpag.sys with VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.

This is related to your graphic Card.

Possible reasons are overclocking, overheating, driverversion sometimes going back to earlier versions helps, changing the TDR, faulty hardware.
Troubleshooting steps for this kind of error are located here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums.
Also this windows KB can help you "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista .

lifetec said:

The dumpfile is a BugCheck 117 Probably caused by : atikmpag.sys with VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.

This is related to your graphic Card.

Possible reasons are overclocking, overheating, driverversion sometimes going back to earlier versions helps, changing the TDR, faulty hardware.
Troubleshooting steps for this kind of error are located here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums.
Also this windows KB can help you "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista .

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 117, {fffffa800761c4e0, fffff8800480ae80, 0, 0}
Unable to load image 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+ae80 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: fffffa800761c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800480ae80, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------

FAULTING_IP: 
atikmpag+ae80
fffff880`0480ae80 ??              ???
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x117
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:  
fffff880`064b1050 fffff880`02d30737 : fffffa80`0761c4e0 00000000`00000024 fffffa80`098dfd50 fffff880`02d303d8 : watchdog!WdDbgReportRecreate+0xa3
fffff880`064b1570 fffff880`02d30b6e : 00000000`00001000 fffff8a0`035af7a0 00000000`00000008 00000000`00004000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`064b15c0 fffff880`02d31e22 : fffffa80`0761c4e0 fffffa80`0761c4e0 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
fffff880`064b1660 fffff880`02c0ff13 : fffffa80`0761c4e0 00000000`00000000 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`064b1690 fffff880`02c3ded6 : fffff8a0`ffffffff 00000000`000219ad fffff880`064b17f0 fffffa80`094f2410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`064b1770 fffff880`02c39e21 : fffffa80`095e3000 ffffffff`feced300 fffffa80`0999d010 fffff880`111e8eb1 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`064b17b0 fffff880`02c39fd9 : fffffa80`095e3000 fffffa80`094f2410 000000ff`02440000 fffff880`05b50000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`064b18a0 fffff880`02c38eb8 : 00000000`00000040 00000000`00007c0a fffffa80`0999d010 fffffa80`094f2410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`064b19a0 fffff880`02c38514 : fffff880`0308df00 fffff880`02c37f00 fffffa80`00000000 fffffa80`00000120 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`064b1b90 fffff880`02c38012 : 00000000`00000000 fffffa80`098dfd50 00000000`00000080 fffffa80`094f2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`064b1bc0 fffff800`0316c2ea : 00000000`034521ce fffffa80`091d9a00 fffffa80`06cde6f0 fffffa80`091d9a00 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`064b1c00 fffff800`02ec08e6 : fffff880`03089180 fffffa80`091d9a00 fffff880`03094040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`064b1c40 00000000`00000000 : fffff880`064b2000 fffff880`064ac000 fffff880`064afc50 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+ae80
fffff880`0480ae80 ??              ???
SYMBOL_NAME:  atikmpag+ae80
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5253fa42
FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x117_image_atikmpag.sys
FAILURE_ID_HASH:  {fa4b6286-8c4a-e9c2-c89f-5612619e000e}
Followup: MachineOwner
---------

Click to expand...

Hi Lifetec,

Thank you for your response. I will try to install the driver without all the Catalyst software. When that's still not working, I'm going to RMA the card.