video cuts out

For Great HONOR · 29 Nov 2009

I have a geforce gtx 280 and ever since running windows 7 the video seems to randomly cut out. Sometimes it will go a week without doing anything but other times it will happen after just a few minutes of running time.

the sound stays on as do all the lights on the case and the mouse laser. The monitor just displays no signal detected. Ive tried hitting keyboard keys, the wake button, and moving/clicking the mouse. At first I thought it was a sleep issue, but have completely disabled the feature. All I can do to get the video back is restart the system via case reset buttons.

I have been reading similar problems online and several people immidiately say temperature. I don't think this is my issue however because it will happen while doing anything from idle computing to intense gaming.

Booting up in xp the error never occurs, only 7 seems to have the issue.

smarteyeball · 29 Nov 2009

The fact that it's fine in XP tends to rule out a h/w issue like a faulty PSU etc. However, have you spent any length of time using XP lately, or are you just occasionally booting back into it?

As for temps, have you at least tried monitoring the temps with GPU-Z?

techPowerUp! :: Downloads

At least it will conclusively rule out a temp issue.

torrentg · 29 Nov 2009

Hi. That's a 0x116 error. A TDR timeout.

You could search my user name on here and 0x116 for the numerous posts I've made on it.

Most likely drivers not for the video card and/or heat related.

Post a crash dump for analysis if you'd like. See the top thread in Crashes and Debugging section for how to do that.

For Great HONOR · 29 Nov 2009

Initially I went back to xp for a while and went about a week with no issue. But I like the increased performance I get from running 64 bit in 7, so ive been roughing it with the problem for a little while now and am finaly fed up. So recently I haven't been running xp at all, but the error has only ever happend in 7 and it happend on day 2 of the install.

I located plug and play OS and hit yes. Due to the nature of my problem I cannot say if it is solved yet but thanks for the help.

I'll run the z gpu for a while in case it crashes again to see if there is a temperature error associated with it as well.

torrentg · 29 Nov 2009

Well that was a very good thing to do already. Like I said, if you have further crashes, post a dump and we can look into what drivers can be updated to try to stabilize the system to its fullest potential.

mushroomboy · 30 Nov 2009

I had overclocking issues in windows 7 where I had not had them before. Really, I'm getting RAM errors ever since I upgraded my computer to the new Phenom II and at first thought it was an overclocking error on the CPU but at regular speeds it happened. What did I conclude? I was getting errors due to the fact that my CPU can now push my GFX to it's full. How does this relate? Well if you weren't using x64 before, you might be having RAM issues with your GFX as people tend to know 64bit os's use more computer ram but also more video ram. Now that may seem silly, but the video card still has to store data, and with the bits registering as twice the size.... It's not always twice the RAM used, but it's more taxing on the ram as apposed to 32 bit and that could be a factor in what's going on. =) Just an idea thrown around there, as I didn't add it together until after I played around with everything. No really, it just sort of hit me as to why my card can OC higher before then after. As that might also be why some people get higher overclocks on 32bit as apposed to 64bit I think.

Oh and is your XP 32bit?

For Great HONOR · 30 Nov 2009

Yeah, I run xp with 32 bit.

mushroomboy · 30 Nov 2009

I would go with tpu ram/a defect with the 64bit drivers/the card has a fault. If different drivers don't work, then I'm guessing it's hardware. As you said WinXP works fine.

For Great HONOR · 01 Dec 2009

Had the problem again today so plug and play os didn't fix it. Althought I forgot to run the temperature program when I booted up today. So, I dont have that as a clue here yet.

So right after I posted this it happend again. My gpu temp was last recorded as 58 degrees.

Also, I looked at the thread on crash dumps, but it didn't really explain how to do it for me. I don't know what process is actually crashing, so I can't create the file at the time. I might have read the wrong thread. Could you give me a link to it?

I just got feedback from BFG and they suggested to update my BIOS and chipset drivers. That has been done and I'm waiting to see if it happens again.

smarteyeball · 01 Dec 2009

Windows generate the crash dumps, it's not something a user can generate.
-
So if there aren't any .dmp files in C:\Windows or C:\Windows\minidumps, then there is nothing to view in that regard. It may be freezing before having a chance to generate a crash dump, or technically it's not "Blue Sceening"

You could always check your event viewer logs for possible issues. (Start > 'search bar and type' Event and select 'view event logs' and look in Custom Views>Administrative Events

58 degrees for the card is fine, so I'd say now you can ignore that aspect and concentrate on something else.