Solved BlueScreen while playing newer games

[Vychor]

Hi!

I recently built a new PC and while it's been fine for surfing, I've experienced several crashes and BlueScreens, mostly while playing a couple of games (Dishonored and Shadow Warrior). After playing these games for ~5 min the computer crashes. After rebooting, I get a message of how "Windows has recovered from an unexpected shutdown", the event name (BlueScreen) and the BCCode (116).

It also crashed when it was just installing some stuff (Microsoft DirectX, among other things) when I first started up Dishonored on Steam and it gave me a BSOD when I tried to update my Windows Experience Index. I was able to solve the latter by uninstalling my NVIDIA driver and then letting Windows update install the driver, after which I was able to update the Index.

I've made sure that my drivers are up to date and I've tried doing a whole new clean install of Windows, but that hasnt solved it. I ran MemTest86 for a whole night, like 12 passes, and it found no errors. I also checked the GPU temps while playing, wondering if it was overheating, though I doubted it. 65-75°C while playing, which I'm pretty sure isnt enough to cause a crash.

On the other hand, I've tried a few older games (Portal, Repbulic Commando and Red Faction 1) and they seem to work (by which I mean they pass the 5 min mark without crashing), so that's something.

I'm gonna make a wild guess and say that this is driver or card related? Right now it seems to be confined mostly to newer games but I'm worried that it might eventually spread.

I've attached the zip file. Please tell me if theres anything else.

 

[ICIT2LOL]

Hello and welcome Vychor sorry you have had to wait for so long now inthe dump files there is a problem with the graphics driver. Now I am not afan of the Windows update to be honest and prefer to go to the manufacturessite. What I suggest you do is to download direct from NVidia.

http://www.geforce.com/drivers
Your dump is showing this

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8019bb3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800628dad4, 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+82fad4
fffff880`0628dad4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`0614ccc0)]
DEFAULT_BUCKET_ID:  [COLOR=red]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
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`08bcca48 fffff880`0527d134 : 00000000`00000116 fffffa80`19bb3010 fffff880`0628dad4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`08bcca50 fffff880`05250867 : fffff880`0628dad4 fffffa80`176f9000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`08bcca90 fffff880`0527cf43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`19bb3010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`08bccb40 fffff880`0534d03d : fffffa80`18651960 00000000`00000080 00000000`00000000 fffffa80`176f8410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`08bccbc0 fffff800`0312b456 : 00000000`012b4879 fffffa80`1772ba00 fffffa80`0ca8a5d0 fffffa80`1772ba00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`08bccc00 fffff800`02e832c6 : fffff800`03010e80 fffffa80`1772ba00 fffff800`0301ecc0 fffffa80`0d400da0 : nt!PspSystemThreadStartup+0x5a
fffff880`08bccc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+82fad4
fffff880`0628dad4 48ff25e5f1ebff  jmp     qword ptr [nvlddmkm+0x6eecc0 (fffff880`0614ccc0)]
SYMBOL_NAME:  nvlddmkm+82fad4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5566824f
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x116_IMAGE_nvlddmkm.sys[/COLOR]
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING: [COLOR=red] km:x64_0x116_image_nvlddmkm.sys[/COLOR]
FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
Followup: MachineOwner
---------

 

[Vychor]

Thanks for the reply!

Alright, I just uninstalled my current driver (I tried using a couple of older drivers a few days ago. There was a little difference: I could now play a bit longer before it crashed.) I've rebooted, downloaded and installed the latest driver from Nvidia. I'm gonna reboot again and then see if that solved it.

Another thing though: I downloaded BlueScreenView and ran it yesterday. According to it, almost all of the crashes (two exceptions) were caused by a driver called dxgkrnl.sys Clicking on any of the dmp files reveals the same three files in the red: dxgkrnl.sys, dxgmms1.sys and nvlddmkm.sys. That mean anything to you?

 

[Boozad]

They're all referring to a video error. dxgmms1.sys and dxgkrnl.sys are Windows DirectX system drivers while nvlddmkm.sys is your nVidia driver. 0x116s point solely to a video card problem be it a driver, power to the card, a heat issue or a generally bad card amongst other things. Monitor the situation after installing a different driver version and post up any new logs if you receive more BSODs and we can look into it further.

In your system specs it says you also have Intel graphics, you're using a desktop so could I ask what the Intel graphics are please?

 

[Vychor]

They're all referring to a video error. dxgmms1.sys and dxgkrnl.sys are Windows DirectX system drivers while nvlddmkm.sys is your nVidia driver. 0x116s point solely to a video card problem be it a driver, power to the card, a heat issue or a generally bad card amongst other things. Monitor the situation after installing a different driver version and post up any new logs if you receive more BSODs and we can look into it further.

In your system specs it says you also have Intel graphics, you're using a desktop so could I ask what the Intel graphics are please?

Yeah, I suspected it had something to do with the Nvidia driver. I've already tried a couple of older drivers (they were from all the way back in 2014) and it meant I could play it slightly longer before it crashed. I'll try a couple more recent ones and then report back here.

I'm a bit unsure of what you mean with "Intel graphics". Do you mean the driver version?

 

[Boozad]

In your system specs it says Intel graphics 4600, is that the onboard graphics?

 

[ICIT2LOL]

Yes Gav & Vychor that is the onboard stuff for that CPU I have the same CPU in my new laptop and it does have an adjusting GUI if you click on the desktop and check the set up. If you see my thread it will give you some idea of it http://www.sevenforums.com/graphic-cards/373339-having-use-intel-graphics.html but I think the NVidia card will have to removed before it can be set up.

 

[Boozad]

I don't see any need for Intel graphics being active on a desktop with a GPU installed, that was what confused me.

 

[Vychor]

Alright, I've tried three different drivers downloaded directly from the geforce website (including one that was released TODAY. No effect so far. I checked BlueScreenView and saw that two of todays crashes were crashed by nvlddmkm.sys, whatever that is. I ran dm log collector again and attached it to this post. Can anyone see any difference?

I don't see any need for Intel graphics being active on a desktop with a GPU installed, that was what confused me.

You think I should disable it?

 

[Boozad]

Your latest dump is a partially corrupt 0x1E which is still blaming the nVidia driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

First off before we look at testing the card (replacing drivers obviously isn't working) can you tell me or take a screenshot of where you're seeing Intel graphics on your machine?

 

[Vychor]

Your latest dump is a partially corrupt 0x1E which is still blaming the nVidia driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

First off before we look at testing the card (replacing drivers obviously isn't working) can you tell me or take a screenshot of where you're seeing Intel graphics on your machine?

Well, I'm seeing Intel Graphics in Device Manager (Intel(R) HD Graphics 4600) Is that what you mean or are you referring to something else?

Sorry if I'm missing something obvious here.

 

[Boozad]

Is it showing under display adaptors? If you could post a screenshot that would be good.

 

[Vychor]

Yeah, it's under display adapters.

 

[Boozad]

Can you check in BIOS to see what you have set as Initial Display Output? It should be PCIe Slot 1.

View attachment 363615
​

Also can you check to see if the Intel Processor Graphics option is set to disabled. It should be seeing as you have a discrete GPU installed, if it's set to enabled please disable it.

 

[Vychor]

Okay, I'll check BIOS.


Just so we're clear, by "Intel Processor Graphics option", you mean the one in Device Manager right?

 

[Vychor]

After taking a minute to actually check your picture, I saw which option you meant.

The Initial Display Output was PCIe Slot 1 but the Intel Processor Graphics option was in fact not disabled but I've disable it now.

 

[Boozad]

OK good. That should have removed Intel from Device Manager. Now use the system normally and see how stable it is.

 

[ICIT2LOL]

I'll leave this one to you Gav as I can only see what you have been looking at and I was also wondering why Intel was involved.

 

[Boozad]

I just wanted to rule out a driver conflict John for starters, we'll see what happens now.

 

[ICIT2LOL]

Ok mate