BSOD playing League of Legends

Hello and welcome Eric mate some system specs please cannot do mush with seeing them - add them to the System specs at lower left corner of your posts but filling in them in the profile - so much easier than ploughing through reams of other readouts.
Or System Info - See Your System Specs

Now looking at the dump it looks to be a graphics failure (driver most likely)

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800d77c2e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004fb92dc, 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+79c2dc
fffff880`04fb92dc 48ff257d97edff  jmp     qword ptr [nvlddmkm+0x675a60 (fffff880`04e92a60)]
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.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`021d5b48 fffff880`05284cbc : 00000000`00000116 fffffa80`0d77c2e0 fffff880`04fb92dc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`021d5b50 fffff880`05258867 : fffff880`04fb92dc fffffa80`10122000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`021d5b90 fffff880`05284acb : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`0d77c2e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`021d5c40 fffff880`05353ec1 : fffffa80`1057ed50 00000000`00000080 00000000`00000000 fffffa80`100ee010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`021d5cc0 fffff800`03573166 : 00000000`02c7addf fffffa80`101588c0 fffffa80`0cd61b30 fffffa80`101588c0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`021d5d00 fffff800`032ae486 : fffff880`03088180 fffffa80`101588c0 fffff880`030930c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`021d5d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+79c2dc
fffff880`04fb92dc 48ff257d97edff  jmp     qword ptr [nvlddmkm+0x675a60 (fffff880`04e92a60)]
SYMBOL_NAME:  nvlddmkm+79c2dc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  550304cc
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
---------

Will await return post.

Sorry late reply mate haven't been well. Not your problem though if you haven't done any driver updates then try those first http://www.geforce.com/drivers it that doesn't work then yu may try backdating them to see if it makes any difference because the latets are not always the ones to have.

Now just one thing the GPU's are tethered I am assumig and that you have tried reseating them and even cleaning the slots see my little ditty
SLOT CLEANING
Now as for the slots to clean them use a strip of old credit card about 1/2 inch wide nip the corners off one end - preferably round them offhold a piece of thin lint free cloth over the end dab on some form of alcohol - isopropyl alcohol (what we swab the skin with before an injection) is good and GENTLY swipe along the slots.
This can also be done for the GPU slot/s and also the contacts of the sticks or cards - not the stick but some lint free cloth of course. See my pic for the sick but please be very gentle doing it if you are in any doubt - please ask before doing it but I use this all the time and have yet to damage anything.
Plus are you overclocking too??

The next thing which I personally look for is a problems with the PSU see this other ditty
Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic.
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in and then click on the individual component/s (it will highlight in blue) - in the right hand side will appear all sorts of details including brands speeds and other essential info that particular device. See pic for example.
The section in the Sensors readout I am interested in is the voltage rails and a dead give away it that it normally mentions VBATT in that section see the pic of my Ivy Bridge Asus board it ahs Nuvoton and another common title is ITE.

For a really good idea on what they should be see this
Power Supply 101: A Reference Of Specifications - Power Supplies the volts MUST be within 5% +/- of the required value.
Again sorry late reply.