BSOD after "No HDMI signal"

Hello, first of all i ask you sorry for my bad english. I got a problem while I was gaming and listening some music: monitor got "No HDMI signals" (music keep listening). So I did reset and after some minutes i got a bluescreen (i didn't read it because it disappeared very quickly), then i restarted and got this message from windows:


Here all the logs needed, hope you'll find THE cause and a solution!
Attachment 351160

Perhaps you uploaded a wrong file? All the contents of the zip seems to be of 2011.

Delete that zip from your desktop if it is still there. Then click on button below ....

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums

Lol, dont be sorry. Mistakes happen. :)

A stop 0x116 is a display/graphics failure. Let us install 347.09 WHQL. NVIDIA DRIVERS GeForce Game Ready Driver WHQL

Then, 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 inform us if you experience any crash or artifacts during the test.

Uninstall the installed display driver using DDU and then install CCC 14.4 WHQL.

When done, stress test the Graphics Card using Furmark one more time.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also inform us if you experience any crash or artifacts during the test.
_______________________________________________

Code:

BugCheck 116, {fffffa8009a70440, fffff8800680b848, 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
---------

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009a70440, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800680b848, 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`0680b848 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`027df888 fffff880`06b0d134 : 00000000`00000116 fffffa80`09a70440 fffff880`0680b848 00000000`00000000 : nt!KeBugCheckEx
fffff880`027df890 fffff880`06b0ce3e : fffff880`0680b848 fffffa80`09a70440 fffffa80`07cbad50 fffffa80`07caa010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`027df8d0 fffff880`06bb4f13 : fffffa80`09a70440 00000000`00000000 fffffa80`07cbad50 fffffa80`07caa010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`027df900 fffff880`06bdecf1 : 00000000`ffffffff 00000000`001a7245 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`027df9e0 fffff880`06bdd437 : 00000000`00000102 00000000`00000004 00000000`001a7245 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`027dfa10 fffff880`06bb02d2 : ffffffff`ff676980 fffffa80`07caa010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`027dfab0 fffff880`06bdcff6 : 00000000`00000000 fffffa80`07f25d50 00000000`00000080 fffffa80`07caa010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`027dfbc0 fffff800`0312a73a : 00000000`fffffc32 fffffa80`07cad200 fffffa80`066a59e0 fffffa80`07cad200 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`027dfc00 fffff800`02e7f8e6 : fffff800`03009e80 fffffa80`07cad200 fffff800`03017cc0 732d7265`792e2e6d : nt!PspSystemThreadStartup+0x5a
fffff880`027dfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+b848
fffff880`0680b848 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
---------

2: kd> lmvm atikmpag
start             end                 module name
fffff880`06800000 fffff880`06896000   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