Sign in with
Sign up | Sign in
Your question

Windows Blackscreens/ hardware faults while playing some games.

Last response: in Windows 7
Share
September 22, 2012 7:00:06 AM

First of all I appoligize if this is the wrong place to post this. Second here is a dxdiag of my setup dxdiag and sience the text version of dxdiag is a bit log he are a couple screen shots of the main pages. imgur dxdiag pics

Anyways here is the problem I am running into, playing some games namely Torchlight 2 and League of Legends Windows will crash lock up and require me to reboot. This happens at random intervals sometimes 5 or 10 min into a game while other happen at an hour or really anywhere in between seems very random to me. Other games in full screen work fine and I don't experience any problems. I don't get a bluescreen so no dice there it seems like a hardware fault I'm guessing? Just a black screen and a .3 second loop of whatever sound file was playing at the time. Upon reboot I get this imgur error code pics and the spoiler is an edited minidump file.

Spoiler

Probably caused by : nvlddmkm.sys ( nvlddmkm+ad6004 )

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

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800727d2f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb48004, 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:
------------------



ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80003011000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503f8bb8

FAULTING_IP:
nvlddmkm+ad6004
fffff880`0fb48004 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x116

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`057e2b48 fffff880`0733e000 : 00000000`00000116 fffffa80`0727d2f0 fffff880`0fb48004 ffffffff`c000009a : nt+0x7f1c0
fffff880`057e2b50 00000000`00000116 : fffffa80`0727d2f0 fffff880`0fb48004 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d000
fffff880`057e2b58 fffffa80`0727d2f0 : fffff880`0fb48004 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`057e2b60 fffff880`0fb48004 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`0727d2f0 : 0xfffffa80`0727d2f0
fffff880`057e2b68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`0727d2f0 fffff880`07311867 : nvlddmkm+0xad6004
fffff880`057e2b70 00000000`00000004 : 00000000`00000001 fffffa80`0727d2f0 fffff880`07311867 fffff880`0fb48004 : 0xffffffff`c000009a
fffff880`057e2b78 00000000`00000001 : fffffa80`0727d2f0 fffff880`07311867 fffff880`0fb48004 fffffa80`066d8000 : 0x4
fffff880`057e2b80 fffffa80`0727d2f0 : fffff880`07311867 fffff880`0fb48004 fffffa80`066d8000 00000000`00000000 : 0x1
fffff880`057e2b88 fffff880`07311867 : fffff880`0fb48004 fffffa80`066d8000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0727d2f0
fffff880`057e2b90 fffff880`0fb48004 : fffffa80`066d8000 00000000`00000000 ffffffff`c000009a fffffa80`066d4010 : dxgkrnl+0x30867
fffff880`057e2b98 fffffa80`066d8000 : 00000000`00000000 ffffffff`c000009a fffffa80`066d4010 ffffffff`feced300 : nvlddmkm+0xad6004
fffff880`057e2ba0 00000000`00000000 : ffffffff`c000009a fffffa80`066d4010 ffffffff`feced300 fffffa80`06d82630 : 0xfffffa80`066d8000


STACK_COMMAND: kb

FOLLOWUP_IP:
nvlddmkm+ad6004
fffff880`0fb48004 4055 push rbp

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nvlddmkm+ad6004

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

BUCKET_ID: WRONG_SYMBOLS

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


I just posted the acual debug and not the warning/information here is the full log on pastebin if that helps. full minidump

This link is the pastebin of the sysdata.xml file. sysdata

So from those two im thinking its a nvidia driver issue? I honestly have no idea. I cant read these memory dump files very well. The thing is I have the latest drivers so could it be an issue with me using dual monitors or something weird like that? Any help would be greatly appreciated.
September 26, 2012 9:20:16 PM

Congratulations, you successfully achieved the 'squeal of death'.
Let's start with what's bothering me about your post.
First, what's your system configuration, what's in the box ?
Second, how many video cards do you have and why are you showing DxDiag with 2 video adapters and 6 COUNT THEM WITH ME 6 audio adapters ??? Squeal of Death ranges from weak power supply to a dying card to a dying MB, it will not be easy to find. But lets start eliminating the obvious. Run CPU-ID and GPU-Z, if the die speed "technology" of the video card is lower than your cpu, your cpu is crashing as a bottleneck.
m
0
l
September 26, 2012 11:54:38 PM

I'm pretty sure its the graphics card as I borrowed a friends and it worked fine for 5 straight hours so I'm pretty sure that's it, but I do want to see if it was the card or not. What I was really hoping for was a "hey moron you forgot to check this box or enable this setting" and not a hardware problem, but its not looking good for that outcome.

I'm running with a Nvidia 680i LT MoBo, Nvidia 580 graphics card, 4GB DDR2 Ram, 750W Power supply, and an Intel 3.0GHz quad core. As for the 2 displays I'm running with dual monitors. For the audio devices I have no idea I'm just using the standard on board HD audio device, but never installed the drivers for it as I didn't like the utility and sounds works fine without them.

Pretty sure we can rule out the power supply with something like I have. The mobo is slow as hell (not really just me complaing) and a bit old, but it seems to still work fine with other graphics card. I'll check the die speed when I get home as I'm currently at work.

All this computer needs to do is last for another month or so then its time to upgrade anyways, but I do want to see if I can donate it so fixing it would be nice or at least finding out what the problem is.
m
0
l
Related resources
September 27, 2012 1:15:05 AM

AMD used to have a checkmark on AGP to recover on crash.
Ah, problem, when drivers not installed, OS is unstable, I don't care if you don't enable it, but you MUST install drivers. Microsoft picked drivers maybe EXACTLY what is crashing you. Install audio drivers only, ignore the software. Sheesh !!!
m
0
l
a b $ Windows 7
September 27, 2012 1:32:31 PM

Its the GPU: 0x116: VIDEO_TDR_FAILURE indicates the GPU display driver crashed, and could not recover properly. Its *possible* the GPU drivers are really at fault though, but if the problem exists through multiple driver revisions, its probably the GPU itself thats bad.
m
0
l
September 27, 2012 4:54:15 PM

gamerk316 said:
Its the GPU: 0x116: VIDEO_TDR_FAILURE indicates the GPU display driver crashed, and could not recover properly. Its *possible* the GPU drivers are really at fault though, but if the problem exists through multiple driver revisions, its probably the GPU itself thats bad.


The display drivers crashing shouldn't lock my computer up right? I'm pretty sure its the GPU iv tried driver releases from 9 months ago and the latest stable and then even beta drivers to see if it would fix the issue.
m
0
l
September 27, 2012 7:42:32 PM

Install audio drivers or stop asking for my advice.
Microsoft default drivers are known to cause problems.
You don't have to run the software that comes with the drivers, most websites offer bare drivers download.
m
0
l
September 27, 2012 7:44:23 PM

You can also try disabling HD Audio on the video card in control panel, device manager. Which is HDMI audio output of video card, if you're not using it, see if that helps.
m
0
l
a b $ Windows 7
September 28, 2012 12:00:56 PM

Zyrax1 said:
The display drivers crashing shouldn't lock my computer up right? I'm pretty sure its the GPU iv tried driver releases from 9 months ago and the latest stable and then even beta drivers to see if it would fix the issue.


Then the GPU is failing. Happened to my 4890 not too long ago. Best bet is the RMA and get a replacement.

And yes, any hardware driver crashing stands a very good chance of crashing the entire system, especially the GPU driver. The fact its constantly crashing and then not being able to recover is close to conclusive proof the GPU is at fault.
m
0
l
!