• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Does the display driver failures can damage a card?

C

Chapapa07

n00b
Joined
Mar 20, 2012
Messages
62
could you tell me if the display driver failures can damage a video card? because I had a ton of them while I was looking for a stable overclock (oveclocking the core clock. memory and voltage) for my msi gtx 550 ti cyclone II OC editon.

P.S.: While overclocking and getting display driver failures I never got artifacts.
 
I don't know if they can damage the card , i would like to know also cause i have the same problem all the time. Simply quite annoying isn't it.
 
I assume OCing your GPU is similar to OC your cpu. Since you should only be tuning it in once or twice it really shouldnt hurt the hardware. For examples: When I OCed my CPU I must of "froze" my computer 20+ times but onces I found that sweet spot it runs boss. When I OCed my GPU I had a systems freeze as well in a similar fashion.

Now if you are doing it every day of every week you might have a problem.

Edit: Most hardware has failsafes that prevent damage and your driver failure message might be that failsafe kicking in.
 
The display driver failures you saw where most surely part of the windows 7 issues with Timeout Detection and Recovery, so no, they won't damage your card.

What Windows 7 does when it notices what it thinks to be a strangely long time to process a draw call is that it stops the offending driver and reloads it in order to avoid what it thinks will be a full system crash. So, again, nope, that won't damage your card, it can get annoying tho, specially on the cases where Win7 becomes too finicky and misreads everything as a driver crash.
 
I'd say yes a driver can damage a card... If I remember right, nvidia managed to turn off their gpu fans with a bad, very bad, driver release and more than a few people fried their cards...
 
Last edited:
Yakk said:
I'd say yes a driver can damage a card... If I remember right, nvidia managed to turn off their gpu fans with a bad, very bad, driver release and more than a free people fried their cards...
Click to expand...
YUUUP.jpg
 
Heh, that was a nice stint of dead 6000 series cards in my shop because of that.

Also, Dave Hester is a fucking douche bag.
 
jrrandell said:
I assume OCing your GPU is similar to OC your cpu. Since you should only be tuning it in once or twice it really shouldnt hurt the hardware. For examples: When I OCed my CPU I must of "froze" my computer 20+ times but onces I found that sweet spot it runs boss. When I OCed my GPU I had a systems freeze as well in a similar fashion.

Now if you are doing it every day of every week you might have a problem.

Edit: Most hardware has failsafes that prevent damage and your driver failure message might be that failsafe kicking in.
Click to expand...

I had tons of driver display failure while overclocking (just 4 days of overclock, I havent oc my card after those days) and while doing nothing with the clocks (it has happened so few times that I dont pay it attention).
 
Driver issues where it causes the fan/voltage/whatever to go crazy, I would say yes, that can damage the card for sure.

Driver issues where you get a TDR or some random software crash, no.
 
MavericK96 said:
Driver issues where it causes the fan/voltage/whatever to go crazy, I would say yes, that can damage the card for sure.

Driver issues where you get a TDR or some random software crash, no.
Click to expand...

Of course, a faulty driver can really damage a card, but what Im talking about is when you want to find a stable overclock and you get many display driver failure, does that can damage a card? .

By the way what does TDR mean?
 
Trying to find a stable overclock, I wouldn't worry too much about it as long as you are running acceptable voltage levels. As long as you are not running it with constant failure for a long period I would say it's probably fine. Otherwise, how would you find a max overclock in the first place?

And TDR means "Timeout Detection and Recovery". It's what Windows Vista/7 does when the driver/display hangs for whatever reason.
 
Yeah pushing a too high a voltage won't make your card feel good in short order... the heat outout sky rockets...
 
Thanks everybody for your responses, I thought I damaged my card while I was trying to find a max overclock.

This thread: http://hardforum.com/showthread.php?t=1679572&page=3 (the post number 52) was one of the reasons I create this thread.
The user sleepyxtreme said :" Completely unstable for my gtx 280. constant crashing caused my card to eventually burn out. Reverted back to 275 with no avail ."

I thought it could happen to my card too, and the fact that with those drivers was the first time I got artifacts (while watching videos on youtube).
 
It's not the driver crashes that will burn out your card, but putting too much voltage into it might if I understand this stuff right.
 
yea i dont think the driver crashing hurts it, however if ur voltage is too high, that will for sure.
 
well, Once I set the voltage to 1.15 (from 1.025) and the core clock to 1050 (from 950) but the overclock was unstable because the core clock limit was 1030 regardless if the voltage was higher than 1.1.

I found out that when I set the core clock to 1030 and the voltage to 1.1 the OC was stable, was this a good overclock?, and..... is it safe so I can use it 24/7?

P.S.: I used the MSI Afterbunner 2.1.0 and the highest voltage I could set was 1.15 .
 
Last edited:
only if your card is an Nidia card can your driver potentially damage a card. Not once but twice they have released cards where the driver has cooked cards due to failure to properly regulate the fan.
 
Thanks so much whatever-your-name-is. But nobody was asking about that particular issue, the question was whether driver CRASHES can cause a problem, and that's never been seen to my knowledge. Why the hell must AMD fans troll *constantly*?
 
devil22 said:
Thanks so much whatever-your-name-is. But nobody was asking about that particular issue, the question was whether driver CRASHES can cause a problem, and that's never been seen to my knowledge. Why the hell must AMD fans troll *constantly*?
Click to expand...



I answered properly but now that you are bitching and aren't the OP i must ask of any instance of AMD drivers doing the same.


BTW, if interested it isn't to troll consistently, if you would see the ammount of time that people still claims that Nvidia has better drivers on situations which isn't true (single card gaming), you would remind them gladly something that is true, which is that they indeed got out 2 revisions of card killing drivers.
 
You answered what properly? I can't even make sense of this rambling troll bait. Those isolated incidences of *overclocked* card fans failing have nothing at all to do with a driver crash causing hardware problems which is specifically what the OP asked and ALL he asked. Could you please go back to the AMD subforum with this drivel.
 
devil22 said:
Thanks so much whatever-your-name-is. But nobody was asking about that particular issue, the question was whether driver CRASHES can cause a problem, and that's never been seen to my knowledge. Why the hell must AMD fans troll *constantly*?
Click to expand...


lol okay.......he asked a question and I answered it

the original question was:
"could you tell me if the display driver failures can damage a video card? "

Yes as the display driver FAILED to regulate the fan, next question please.
 
Chapapa07 said:
could you tell me if the display driver failures can damage a video card? because I had a ton of them while I was looking for a stable overclock (oveclocking the core clock. memory and voltage) for my msi gtx 550 ti cyclone II OC editon.

P.S.: While overclocking and getting display driver failures I never got artifacts.
Click to expand...



no, BUT if you turn off the auto restart on BSOD and it gets stuck on a BSOD then you can end up damaging the chipset since the board basically locks in full load, had this happen to me a few times with different motherboards. but as far as damaging the card no since the card will lock in 2D clock mode and it can basically run passively at that point if need be. so as far as the guy saying it could damage them based on a bogus thing from a driver version thats now 2 years old, no that crap can't happen and yes i know this for a fact since i used those pos drivers with my 8800GS's which would randomly turn my fans off in the middle of playing BFBC2 and both cards would hit 130C+. only way i ever noticed it was the fact that my frame rate dropped to 15fps because the cards locked in 2D mode. the cards still work to this day after having that happen 9 - 10 times before i figured out what was actually causing it.
 
sirmonkey1985 said:
no, BUT if you turn off the auto restart on BSOD and it gets stuck on a BSOD then you can end up damaging the chipset since the board basically locks in full load, had this happen to me a few times with different motherboards. but as far as damaging the card no since the card will lock in 2D clock mode and it can basically run passively at that point if need be. so as far as the guy saying it could damage them based on a bogus thing from a driver version thats now 2 years old, no that crap can't happen and yes i know this for a fact since i used those pos drivers with my 8800GS's which would randomly turn my fans off in the middle of playing BFBC2 and both cards would hit 130C+. only way i ever noticed it was the fact that my frame rate dropped to 15fps because the cards locked in 2D mode. the cards still work to this day after having that happen 9 - 10 times before i figured out what was actually causing it.
Click to expand...

lol at that comment of "that crap can't happen" after it already did twice......

talk about a lack of common sense.....
 
So my last question is if is it safe to set the core clock to 1030 and the voltage to 1.1 so I can use it 24/7 forever?

P.S.: the OC was stable.
Sorry for my late response.......
 
You must log in or register to reply here.
Back
Top