GeForce 314.14 Beta Driver Download

Videocards - NVIDIA GeForce Windows 10 | 11 683 Updated by Hilbert Hagedoorn

Click here to post a comment for GeForce 314.14 Beta Driver Download on our message forum
data/avatar/default/avatar11.webp
can't install on 540m. "This graphics driver could not find compatible graphics hardware"
https://forums.guru3d.com/data/avatars/m/223/223076.jpg
tomb rider hair killing our overclocks
https://forums.guru3d.com/data/avatars/m/239/239932.jpg
Blops2, skyrim and SC2 WoL all working great on my 460 sli. Can't wait for the expansion 😀
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
Hi Tj, what do you mean, more fps ? Versus 314.07 ? You don't have any crash in BO2 with your GTX570@930MHz ? I am gealous ! Mine GTX580 doesn't allow any overclocking in BO2 without any crashes (Even with 310.90 WHQL). i play now GTX580@stock at BO2. Only since one day. I hope I won't any crashes at stock frequencies !! All my other games (COD's) seem to run perfectly with my GTX580@910MHz (I have to try more hours because I mainly play BO2...). Crazy...:3eyes:
Fps was pretty much at ~ 120-125fps all the time (maybe few dips to ~ 90ish fps) and camera felt even smoother compared to early 313.96, more fluid. I played at 900mhz OC - 4-5 rounds (DM) and I didnt crash yet.. Also no high pitch sound freeze. Metro2033 played ok too. Im installing TomRaider now, I will see if i have any issues with tessellation, etc. EDIT: I benchmarked tombraider and it didnt crash, but TressFX takes a big hit. And sometimes it leaks memory?/direct compute if i turn it on /off and test again.. FPS drops to 10fps, quitting the game fixes it. Also Ambient Occlusion has some micro glitches around her face, tiny particles of garbage.
https://forums.guru3d.com/data/avatars/m/87/87487.jpg
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...
https://forums.guru3d.com/data/avatars/m/87/87487.jpg
so we just disable Tesellation in game ? not a driver related problem ? how you found that ? thanks ! Sergio
I'm been reading that the v310.xx drivers work fine with Tomb Raider and tessellation so it points very much to it being a driver issue in the latest v314.xx ones.
https://forums.guru3d.com/data/avatars/m/245/245409.jpg
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...
I can agree, I only just got Far Cry 3 couple of weeks ago.Love the fact that patches get installed right after initial installation.Runs pretty well for the cpu that I got.If I had gotten it at release I don't think I would've been a happy camper.
data/avatar/default/avatar27.webp
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.
https://forums.guru3d.com/data/avatars/m/231/231366.jpg
but is it really a DRIVER problem with TESSELLATION or a GAME ENGINE problem ???
https://forums.guru3d.com/data/avatars/m/87/87487.jpg
but is it really a DRIVER problem with TESSELLATION or a GAME ENGINE problem ???
Could be both. The earlier v310.xx and recently released v311.06 drivers apparently work with Tomb Raider and tessellation so there is a problem with the newer v314.xx driver code, possibly caused by the changes NVIDIA have made between the v31x.xx and v314.xx code and optimizations made in the game for AMD graphics hardware (since it is an AMD 'Gaming Evolved' branded title). Looks like NVIDIA have been a bit slack with the testing on this game or perhaps the developers made late changes unknown to NVIDIA. Whatever, it is yet another buggy launch release to join all the others. Ain't PC gaming just fun!
https://forums.guru3d.com/data/avatars/m/231/231366.jpg
Could be both. The earlier v310.xx and recently released v311.06 drivers apparently work with Tomb Raider and tessellation so there is a problem with the newer v314.xx driver code, possibly caused by the changes NVIDIA have made between the v31x.xx and v314.xx code and optimizations made in the game for AMD graphics hardware (since it is an AMD 'Gaming Evolved' branded title). Looks like NVIDIA have been a bit slack with the testing on this game or perhaps the developers made late changes unknown to NVIDIA. Whatever, it is yet another buggy launch release to join all the others. Ain't PC gaming just fun!
jeeze Darren...thx for your quick reply !!! someone say that 314. earlier also work can anyone confirm this ???
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
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.
https://forums.guru3d.com/data/avatars/m/90/90667.jpg
i heard there was a 1GB patch to the game, made any difference? any notes?
https://forums.guru3d.com/data/avatars/m/180/180832.jpg
Moderator
Isnt that the launch patch ? you are forced to use it
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
^ IDK, Could be.. Steam downoladed something, retail DVD stopped at ~ 7.2GB then it downloaded another 1.6gb or so.
https://forums.guru3d.com/data/avatars/m/115/115710.jpg
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...
Yeah, got BSOD in Tomb Rider (STOP: 0x00000119).
https://forums.guru3d.com/data/avatars/m/87/87487.jpg
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.
https://forums.guru3d.com/data/avatars/m/79/79740.jpg
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.
https://forums.guru3d.com/data/avatars/m/223/223076.jpg
so anoning play my love game with crashes
https://forums.guru3d.com/data/avatars/m/242/242471.jpg
Yeah, got BSOD in Tomb Rider (STOP: 0x00000119).
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 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
Problem signature Problem Event Name: BEX Application Name: TombRaider.exe Application Version: 1.0.716.5 Application Timestamp: 5131eb70 Fault Module Name: StackHash_5861 Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: PCH_15_FROM_ntdll+0x00041318 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.2.9200.2.0.0.256.103 Locale ID: 1060 Additional Information 1: 5861 Additional Information 2: 5861822e1919d7c014bbb064c64908b2 Additional Information 3: f3d5 Additional Information 4: f3d5be0cad2787556264647dc02181c3