Random BSOD while playing games and idling, monitor display shuts off.

Here lately on my PC I've been getting random BSOD and the monitor display with turn off and back on randomly a few times with one of them showing no signal then it will revert to being back on, all of my temps on my PC are pretty cool when this happens and I cannot figure out what is going on, any tips?

-Attached a report to this thread as well containing a system scan.

-Edit: Another BSOD a few minuted after posting this, here is the report from it.
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: FFFFF88002825008
BCP4: FFFFF88002824860
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052515-27549-01.dmp
C:\Users\Braxton\AppData\Local\Temp\WER-131508-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

-Edit: Booted up a game just now and while in the middle of playing the game and audio randomly freezes multiple times and on the task manager my CPU usage would spike to 100% 2 times then anywhere from 70-90% about 5 times then it would settle back down to normal levels around 10%.

Update the display driver to 352.86 WHQL and see how it goes.

NVIDIA DRIVERS GeForce Game Ready Driver WHQL
_______________________________________________________

Code:

BugCheck 116, {fffffa800d070010, fffff88006059a08, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7aca08 )

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

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


FAULTING_IP: 
nvlddmkm+7aca08
fffff880`06059a08 48ff258126edff  jmp     qword ptr [nvlddmkm+0x67f090 (fffff880`05f2c090)]

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`06806a48 fffff880`06342134 : 00000000`00000116 fffffa80`0d070010 fffff880`06059a08 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06806a50 fffff880`06315867 : fffff880`06059a08 fffffa80`10c42000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06806a90 fffff880`06341f43 : 00000000`ffffd846 ffffffff`fffe7960 fffffa80`0d070010 fffff880`05837f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06806b40 fffff880`0583803d : fffffa80`0cfae0d0 00000000`00000080 00000000`00000000 fffffa80`10c25410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06806bc0 fffff800`0331a456 : 00000000`fffffc32 fffffa80`1091ca00 fffffa80`0c749040 fffffa80`1091ca00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06806c00 fffff800`030722c6 : fffff800`031ffe80 fffffa80`1091ca00 fffff800`0320dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06806c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7aca08
fffff880`06059a08 48ff258126edff  jmp     qword ptr [nvlddmkm+0x67f090 (fffff880`05f2c090)]

SYMBOL_NAME:  nvlddmkm+7aca08

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55259065

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

3: kd> lmvm nvlddmkm
start             end                 module name
fffff880`058ad000 fffff880`062e5000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Apr 09 02:02:37 2015 (55259065)
    CheckSum:         009F7AE7
    ImageSize:        00A38000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Kramos said:

Sorry for the late reply been a little busy. I updated to version 352.86 WHQL and I was still getting the same errors. I turned down the graphic settings in the games I play and now it does not do it anymore. I'm guessing the card is going bad or dying?

You posted about your GPU temps, but an elaboration is needed. 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

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.