BSOD playing Neverwinter, error 0x00000116

Hi folks,

As of recently, I keep getting BSODs - B as in "Black", not blue, mind you - playing Neverwinter (The online version developed by Cryptic Studios). The screen randomly turns black all of a sudden and the sound freezes a few seconds afterwards leaving me with no option but to hard reset my computer.

I googled the error "0x00000116" but any suggested steps I found couldn't solve the problem for me. Here's a list of what I already tried. I just came back from a 1 week vacation so this is just what I recall off the top of my head. Anyways, here's what I tried so far:

- MemTest for several hours - no errors occured
- Installed newest as well as legacy graphic drivers with and w/o DDU, with and w/o nVidia Experience - no success
- SSD Tweaks. I got this computer from a friend a while ago and put in an SSD cause they're so awesome . So after a few weeks of using the computer some crashes occured that I could fix with SSD tweaks. I don't remember the details but I could search my browser history and provide more info if needed.

Some more notes:
- This so far only happened while playing this particular game and ONCE while randomly browsing the interwebz (I'm not sure if that particular occasion was the same error, though. Didn't bother to have a look at the event log back then). I play this game on the lowest settings possible in order to have a constant very high framerate. The GPU and CPU load should be pretty low since it also runs smoothly on highest settings. Also the fan noise level is quite low when I run the game on lowest settings which sort of underlines my point.
- Sometimes I can play hours over hours without a crash, sometimes I keep getting crashes a few minutes in. I can't really see a pattern there.
- I played the Metro games for several hours straight without any crashes whatsoever. On very high settings. Boy my machine got loud then! But addmitedly, that was quite a few weeks back and at a time where I didn't play NW and before I had these issues. I'll try to run it for a few hours and see if I get the same BSOD.
- Same with Borderlands 2.

That's all that I can think of for now. If you need more information that is neither provided in this post nor the attached zip file, please let me know.

Thanks in advance, I hope one of you guys has a solution at hand. This is getting really frustrating .
Dave

Hum well the dump files are showing you have some graphics problem

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8010536010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005e742dc, 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`05e742dc 48ff257d97edff  jmp     qword ptr [nvlddmkm+0x675a60 (fffff880`05d4da60)]
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`027d7a48 fffff880`06140134 : 00000000`00000116 fffffa80`10536010 fffff880`05e742dc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`027d7a50 fffff880`06113867 : fffff880`05e742dc fffffa80`0c1a0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`027d7a90 fffff880`0613ff43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`10536010 fffff880`05637f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`027d7b40 fffff880`0563803d : fffffa80`0fc15010 00000000`00000080 00000000`00000000 fffffa80`0c194320 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`027d7bc0 fffff800`03963aba : 00000000`025cc7e0 fffffa80`0c1d3760 fffffa80`09d43380 fffffa80`0c1d3760 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`027d7c00 fffff800`036bb426 : fffff800`03849e80 fffffa80`0c1d3760 fffff800`03857cc0 fffffa80`0bb8b680 : nt!PspSystemThreadStartup+0x5a
fffff880`027d7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+79c2dc
fffff880`05e742dc 48ff257d97edff  jmp     qword ptr [nvlddmkm+0x675a60 (fffff880`05d4da60)]
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
---------

Have you got the latest drivers for your graphics? (some specs would be good mate)
System Info - See Your System Specs

Ok mate looks like one of the GPU's might not be "playing the game'" and suggest - if you haven't already reseating the GPU's and maybe even cleaning the slots - see my little ditty - just be very gentle doing it

GENERAL SLOT CLEANING
Now as for any motherboard slots to clean them use a strip of old credit card (or any card thin enough some are better than others ) 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
(I will send the pic from my other machine later but it isn't difficult to make though)
I would also try using the machine with one card at a time and run that Furmark test on each one - if you like with both in first.


Now for another little tip if you want to know what is inside the machine and it will do it in great detail (handy sometimes) use PART B: of this other ditty of mine it will at least let you know what sound card you have in
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. In my pic the section (Nuvoton) with VBATT is a dead give away you are in the section for the rail voltages. There are other section titles and one that pops up often is ITE
Now the voltage on the different rails have to be within 5% =+/- of what is required or the machine will not work properly if at all.
See this for the rail voltage info
http://www.tomshardware.com/reviews/power-supply-specifications-atx-reference,3061.html (Section 2.)
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.

You can of course check out the PSU too if you so want to takes very little time see my pic for what you are looking for - it isn't ut of the realms of possibilities that the cards are not getting their correct rail volts.

PS The stick cleaner pic - just added

Ok mate and as Gokay says the SLI connections too could be just something real simple.