353.30 game ready

not installing these, will wait until the drivers are stable again on Keplar

 

Oh boy.

Looks like it's time for some restructuring of the nVidia driver teams.

4 pages full of complaints already, doesn't look good.

 

then u gonna wait longer... there are report that kepler optimization didn't not carry to this drivers.

 

I'm on Windows 10 build 10147 with 353.30 and for me Tri-SLI working, although I did get two PCI to PCI Bridge errors in device manager that lost two of my cards when I installed it. Uninstalling them in device manager and rebooting to let the system find them again fixed it.

 

Still too early but tried these for 6 hours now and no problems running Win7 x64. Did have problems with previous drivers (beyond ver. 347.88) and the "driver stopped responding" error, but these are good so far. Only thing different is I uninstalled using control panel (no 3rd party uninstaller) and let computer reboot twice, then installed these. Game optimizations in these are pretty nice compared to 347.88.

 

Eee say what? "...kepler optimization didn't not carry to this drivers" - 45-50-60fps in The Witcher 3 here - for me it's the same drivers like 353.06 was but + Batman Arkham Knight profile and IMO drivers performance is also good...

 

Sorry, I'm late to the party.. So what's this BS with Kepler cards not receiving optimization in the drivers? There was a release driver focused on Kepler cards called 353.06? Is this the only current driver we have? Why is Nvidia not making drivers with all cards in mind anymore? Are Kepler cards only receiving attention every so often now? WTH

 

nvidia downgraded kepler performance on purpose to promote the 900 series even more, 353.06 "address" this issues.

Some users received improved performance mainly in the witcher, some other don't, same thing with this driver.

this driver aims for batman.

 

yep, honestly i would prefer my system to be stable, 353.06 seem ok if i dont use AB or anything that polls the api but i havnt spent any length of time in Witcher 3 yet( finished GTAV on 353.06 ) mainly due to lack of time atm.

 

This is true.

Going up Crow's Perch in the Witcher 3, minimum I saw:

353.30: 27fps
353.06: 34fps

Nvidia, seriously :3eyes:

I'm so going AMD next time...

Skip these drivers if you have a Kepler card.

 

On purpose... Seriously, you don't have to say that in every post. I don't think they did any downgrading on purpose.

 

wow... i thought these random crashes i had with tw3 were oc related, although they were really random. now with these playing fc4 i found out that the crashes even occur on stock clocks for me too. even when setting clock speeds to absolute ref (1076mhz on boost). i never had those crashes with chrome some others are reporting about so i really thought it was due to ocing. but ok... so which driver is the one to go? 347.88??? or is it related to afterburner?

 

Same dude, I almost RMA'd my GPU because I couldnt oc memory at all. I'm using 350.12 but I do get here and there drivers stopped working in Witcher 3. Apparently 347.xx are most stable.

From what we've seen even 9xx and Titan owners should skip this. Performance boost in Batman will probably be like 3-5fps as always. And stability over that small fps gain will always be better.

 

Anyone tried this driver with GTX 5xx and win 10?

I may try it tomorrow if i am not tired.

 

hm... ok so i think i will finally go with 347.88. thx mate

 

I have the same videocard did u test after use DDU? I'm thinking to give it a try, because I'm going to play Batman

 

If you dont mind report back if its stable with overclock for you I'm thinking about rolling back my 350.12 drivers back to those. Thanks in advance.

 

WOW! Talk about cheap. Jeeeezz

 

Received first "driver stopped responding" error while browsing (IE) after 7 hours normal usage. Prior to this had no problems browsing or playing TW3. If error persists will go back to 347.88

 

Random white screen flashes. Thought it was the game "The Witcher 3". it was with every 35x.xx driver. Random TDR's in event viewer matched the time stamps when the screen flashed. So the drivers were causing random TDR's in game.

Went back to the 347.88's and not a single TDR since.

The new drivers for me are trash.