BSOD watching video in Firefox.

My PC just BSOD watching a video in Firefox. Its done it a couple of times in the past but always when in Firefox watching videos. I have also suffered a BSOD when playing a game but that game is known for crashing (Kenshi).

The last BSOD was a 0x116 (video driver) stop.
Temp are all perfect for CPU and GPU.
I've never had issues with this machine before so I'm suspecting perhaps PSU or memory.

http://palmergames.com/libs/ELGARL-P..._140039_56.zip

- - - Updated - - -

Well its definitely something to do with the Video card or driver

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa802338b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880100e5eac, 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:
nvlddmkm+c96eac
fffff880`100e5eac 48ff25edd2c5ff jmp qword ptr [nvlddmkm+0x8f41a0 (fffff880`0fd431a0)]

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`025a8888 fffff880`0405d134 : 00000000`00000116 fffffa80`2338b4e0 fffff880`100e5eac 00000000`00000000 : nt!KeBugCheckEx
fffff880`025a8890 fffff880`0405ce3e : fffff880`100e5eac fffffa80`2338b4e0 fffffa80`231bd3b0 fffffa80`1c1f5010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`025a88d0 fffff880`0f40ff13 : fffffa80`2338b4e0 00000000`00000000 fffffa80`231bd3b0 fffffa80`1c1f5010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`025a8900 fffff880`0f439cf1 : 00000000`ffffffff 00000000`000bf34a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`025a89e0 fffff880`0f438437 : 00000000`00000102 00000000`00000003 00000000`000bf34a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`025a8a10 fffff880`0f40b2d2 : ffffffff`ff676980 fffffa80`1c1f5010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`025a8ab0 fffff880`0f437ff6 : 00000000`00000000 fffffa80`1ec71700 00000000`00000080 fffffa80`1c1f5010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`025a8bc0 fffff800`037531a0 : 00000000`07b1249e fffff800`035f6180 00000000`00000001 fffffa80`1c2304c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`025a8c00 fffff800`034abba6 : fffff800`035f6180 fffffa80`1c2304c0 fffff800`036061c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`025a8c40 00000000`00000000 : fffff880`025a9000 fffff880`025a3000 fffff880`0d281db0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+c96eac
fffff880`100e5eac 48ff25edd2c5ff jmp qword ptr [nvlddmkm+0x8f41a0 (fffff880`0fd431a0)]

SYMBOL_NAME: nvlddmkm+c96eac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 600b20e4

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
---------