Multiple Daily Driver Crash and BSOD

Hello, I've been getting multiple driver crash per day and got a BSOD once.

I've been using the same Nvidia driver since January, but for some reason it started crashing for the past week. I didn't update anything nor change my hardware. No overclock.

You can find my system specs here:
https://www.sevenforums.com/members/birkhoff.html

Hi Birkhoff.

Update the display driver to the latest WHQL from Drivers - Download NVIDIA Drivers.

When done, 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. Also let us for any further BSOD.
____________________________________________

Code:

BugCheck 117, {fffffa80071db4e0, fffff88004f4b81c, 0, 0}

*** 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+13e81c )

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

2: 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: fffffa80071db4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004f4b81c, 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: 
nvlddmkm+13e81c
fffff880`04f4b81c ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`095a34f0 fffff880`0587672b : fffffa80`071db4e0 fffff880`058c30cc fffffa80`071db4e0 fffff880`05844843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`095a3a10 fffff880`058773f0 : fffff8a0`0332d850 fffff8a0`0332d850 00000000`00000080 fffffa80`071db4e0 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`095a3a60 fffff880`0584b6b3 : 00000000`00000001 fffffa80`08b06000 00000000`00000000 fffff880`00000049 : dxgkrnl!TdrCollectDbgInfoStage2+0x220
fffff880`095a3a90 fffff880`05877f43 : fffffa80`08ae4658 ffffffff`fffe7960 fffffa80`071db4e0 fffff880`05947f3c : dxgkrnl!DXGADAPTER::Reset+0xef
fffff880`095a3b40 fffff880`0594803d : fffffa80`09815510 00000000`00000080 00000000`00000000 fffffa80`08ae4010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`095a3bc0 fffff800`03156aba : 00000000`fffffc32 fffffa80`08b2c060 fffffa80`066a55f0 fffffa80`08b2c060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`095a3c00 fffff800`02eae426 : fffff800`0303ce80 fffffa80`08b2c060 fffff800`0304acc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`095a3c40 00000000`00000000 : fffff880`095a4000 fffff880`0959e000 fffff880`0eae5d40 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+13e81c
fffff880`04f4b81c ??              ???

SYMBOL_NAME:  nvlddmkm+13e81c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0548e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x117_image_nvlddmkm.sys

FAILURE_ID_HASH:  {c306f7be-ced2-9b11-9b10-d0239a4fd800}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04e0d000 fffff880`0581b000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Jan 10 03:52:06 2015 (54B0548E)
    CheckSum:         009D73FA
    ImageSize:        00A0E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I am using 350.12 WHQL, and have suggested other users to use it, there is no big issue with that driver itself.

Can you reset the BIOS to the default settings, just as a test?

How To Clear CMOS (Reset BIOS)

   Warning

Before clearing CMOS, boot into the BIOS and check your storage controller mode.

If the PC refuses to boot after resetting CMOS, boot back to BIOS, apply the storage controller mode previously applied before clearing CMOS.

No pay attention to the issue.
First of all, if you havent performed teh suggestin of post #6 yet, do it.

If Clearing CMOS does not change the situation, disable hardware acceleration in Firefox. See how it goes.

If both of them did not help, we will have a very limited options left there.

If you are noticing display artifacts, you may test the situation with any other graphics card.