Nvidia GeForce 314.22 WHQL - Download & Discussion

Update your profile! Just to prevent people from being tards, and going... "You don't have a TITAN, your profile says GTX 460!". That was...an example by the way.

 

@GhostXL

okay

 

What's weird in there? Newer drivers allowed your cards to open their potential. GPU usage increased, so did temps and fan speed. And you rolled back.

Also, try to overclock your CPU more, because in some games even for one Titan it is not enough sometimes.

 

No need to overclock etc. All my games are running perfectly with my configuration right now. I get the same performance with the 314.21 beta drivers,as I do with the 314.22,but with less noise and less heat.

 

There was an Nvidia driver i forget which one it was i think it was the 175.** it caused some peoples cards but not everybodys to actually fail due to excessive heat.

I remember testing in on the 280's and it was ok for me but for some people there cards popped!
No joke!

 

196.25 I think.

 

Same for my 580. Nice increase in pretty much everything and where it counts ! Min frames per second ! Not only that but for the heck of it I pushed the clock up to 955 from 945 and no problems. Tomb Raider still beats a 580 to death unless you drop some settings but if I have to compare screen shots to see the difference what does it matter. Smooth 60 fps is all I want.

 

It was the 196.75

Link: http://www.zdnet.com/blog/hardware/warning-nvidia-196-75-drivers-can-kill-your-graphics-card/7551

Seems when some computers came out of sleep, the fans would not turn back on. You can Imagine what happened if you played a video game after just coming out of sleep and your fan didn't come on.

It had mainly to do with the type of fan control the card had so not all cards were effected.

 

Yeah thats the one, remember now.
I knew there was a 75 in it somewhere.

 

For some reason now with 314.22 if I pull a lot of mobs in WoW my gpu usage on each 680 goes down to ~5% and my fps in turn drops to about ~5 as well.

This never happened before... reverting to older driver until fixed but is anyone else experiencing this issue?

 

I reported BSODs earlier, but it turns out it was because of Opera. PC has been running fine every since I uninstalled that.

 

I've put the OSD rendering to Vector 2D for MSI Afterburner and so far everything seems to be good. No crashes for BF3, for now. Been playing Bioshock infinite for about 2 hours and im loving how well it runs with SLI.

ps; For those with crashes/stutter try the newest beta for MSI Afterburner without installing the OSD server or Vector 2D if you use it like me all the time.

 

Any solution for CRYSIS 3 stuttering?

 

I just had a "driver stopped responding" error while using firefox, watching some flash movie? I havent had any issues until this one with these drivers, but almost everytime Ive had the same error in the past, its almost, almost everytime been a flash/browser combination? So something in flash is buggy, or the drivers get buggy with flash? I havent had any issues with this driver until today, and it did recover from the driver crash, so no big deal. But still, it worries me, because I dont like these "drivers stopped" errors, as they often end up in (some cases) a BSOD?! These drivers have been rock solid so far, so im not very worried, but still it gets youre attention for sure!?

 

Yup wait for patch or new drivers

 

The solution is better hardware.
I went from 3x gtx 680 2gb to 2x GTX Titan, then the stuttering was gone

There is just not enough juice in GTX 680

 

I agree one 680 didn't cut it for Crysis 3.

 

Who would spend that much money to play Crysis 3 lol, boring game. What stuttering though? As long as you don't go overboard with the settings, it should be fine. Game runs fine on my end.

 

better drivers are the least of crysis 3' problems at the momment! the 1.3 patch completely broke performance. mainly a MP issue, but now im reading that alot of people are having issues with SP aswell since the 1.3 patch....

 

Nope. I play WoW daily and I have never experienced this issue. Then again, I leave my settings at "Let the 3D application decide". Maybe try that?