GeForce 314.14 Beta Driver Download
Click here to post a comment for GeForce 314.14 Beta Driver Download on our message forum
ZeBeeDY
can't install on 540m.
"This graphics driver could not find compatible graphics hardware"
yosef019
tomb rider hair killing our overclocks
lucidus
Blops2, skyrim and SC2 WoL all working great on my 460 sli. Can't wait for the expansion 😀
-Tj-
Darren Hodgson
These drivers and the v314.07 WHQL ones seem to be very, very, very bad for the recently released Tomb Raider on my system as they cause a total system freeze, anywhere within a minute to ten minutes of playing it. The only fix I've found is to disable tessellation which allowed me to play for almost two hours into the early hours of this morning before I decided to go to bed. What am I complaining about then? Well for one I bought two GTX 680s to play all my games on maximum settings so having to disable features because of silly bugs/bad drivers is just insulting really.
Have these drivers been tested with Tomb Raider at all because I'm seeing lots of reports from other NVIDIA card owners , mostly from the Kepler family, experiencing similar freezes and crashes to the desktop?
I have to say that I'm extremely disappointed that this is yet another major release to join Crysis 3 which has performance issues on NVIDIA hardware. Makes me wonder why on earth I continue to buy games at launch. Seems it is best to wait several months for patches and driver updates then buy the game when it is also cheaper. I just never learn. At this point the next-gen consoles are looking more and more appealing...
Darren Hodgson
Dragondale13
NeoandGeo
Starting to wonder why Nvidia even released these drivers a day before Tomb Raider. Should have waited a couple more days and had one game ready driver ready for us.
andressergio
but is it really a DRIVER problem with TESSELLATION or a GAME ENGINE problem ???
Darren Hodgson
andressergio
-Tj-
Well TomRaider works ok here with this driver, i mean no crashes because of Tessellation.
But there are some memory leaks, usually it stalls for a split second right before cinematic camera sequence or new area. Memory goes down 100-200mb (from 1240mb) then back up ~ 100mb (1100mb).. fps also drops in that moment.
Most noticeable was right at the beginning of the game - when you try to get out of that cave., its not so much now in the jungle.
I also dont have any Tessellation issues because of water, it looks normal.
http://www.abload.de/thumb/tombraider_2013_03_05rysct.jpg http://www.abload.de/thumb/tombraider_2013_03_05b2sut.jpg http://www.abload.de/thumb/tombraider_2013_03_056fs6b.jpg
I play it like so
http://www.abload.de/thumb/tombraider_2013_03_05wzp8v.jpg
But again performance is all over the place - im suspecting that DirectCompute issue with TressFX, gpu usage 99% all the time @ 930mhz/2170mhz.. Memory usually ~ 1100mb.
moab600
i heard there was a 1GB patch to the game, made any difference? any notes?
WhiteLightning
Moderator
Isnt that the launch patch ? you are forced to use it
-Tj-
^
IDK, Could be.. Steam downoladed something, retail DVD stopped at ~ 7.2GB then it downloaded another 1.6gb or so.
Anarion
Darren Hodgson
When I had tessellation enabled I was even getting intermittent stuttering during the pre-rendered FMV sequences such as the intro sequence (yeah, crazy, right?) and 1-2 second freezes during the real-time cutscenes in Tomb Raider. Once I disabled tessellation the game and movies played fine without any hitching at all. I'd suggest that anyone with a Kepler (600 series) card either turn tessellation off or use the earlier v310.xx or v311.xx driver for now until the game has been patched and the drivers updated.
I'm a bit annoyed to be honest as I was looking forward to playing the PC version with all the eye candy enabled but I'm not reverting to an older driver simply because I'm playing other games too such as Crysis 3 which the newer v314.xx drivers have been optimized for. I hope this issue is fixed quickly but I've a feeling it might takes a week or more, especially if it requires a new driver to fix it.
alanm
I'll just wait a few weeks until all the issues sorted out. While looking forward to it, what makes me cringe are the QTE's characteristic of past TR games. I like thinking games, not reflex action ones that require finger ballets across several buttons that must be done in micro-second precision.
yosef019
so anoning play my love game with crashes
-Tj-
http://www.overclock.net/t/940091/bsod-codes-when-ocing-must-have-info
Speaking of game crash I didnt have any issues, only in MP after I picked up a machine gun
What triggered this code, nv... or something else?
Few possible codes, its not 100% the same but maybe its worth checking, that's if you OC.
0X109 = add DDR3 voltage
0x19 = memory voltage