Geforce 310.90 driver released

[Mustang]

Thought this could be interest for our nvidia users, source from Rage3d (i wised AMD would release stuff like this on weekends too!)

 

"NVIDIA has released its certified 310.90 drivers, which improve performance on the GTX 690, add a security update for the NVIDIA Driver Display service, fix some bugs, and update SLI and 3D Vision profiles.

 

Hit the source to download.

 

Source: Geforce"

[GriffonBR]

So, is there any braveheart here to test it on DCS/FC3?:D

[Wolf Rider]

multicard/ multi gpu users might need to be aware (atop) there is a coldboot bug associated with these drivers

 

 

http://www.evga.com/forums/tm.aspx?m=1830605

Edited January 8, 2013 by Wolf Rider

[Vlerkies]

If you don't mind my Nvidia ignorance, I just bought a GTX680, was on ATI6990, which Nvidia driver should I install?

[GriffonBR]

Well, people say that you must keep your drivers always up to date, but those latest Nvidia drivers are causing so many problems. It´s a lottery.:noexpression:

[Lange_666]

If you don't mind my Nvidia ignorance, I just bought a GTX680, was on ATI6990, which Nvidia driver should I install?

306,97 are fine for me and from what i'm reading the 310,90's should be OK to, didn't test them yet.

[Vlerkies]

Hi Lange, long time, Nero here ;)

 

My card should arrive tomorrow. Looks like its just probs with SLI setups on the latest set from what I can see as well.

[Lange_666]

Offtopic:

 

Hi Lange, long time, Nero here ;)

 

Ha, those SA dudes always surface here and there under other names...LOL.

Still hiding for the cops...:D

[Vlerkies]

:shocking: :police:

 

I cannot confirm or deny the above

 

:music_whistling:

[GriffonBR]

Guys, I´ve tested these drivers on my single GTX 670 and for my surprise and happines, my FC3 are more smoothly now. Give it a try too.

[Amisnaru]

These drivers absolutely killed my performance... went from 35fps to 10.

GT640M

[Lange_666]

No joy here either, went back to 306,97.

 

Somehow with every driver i try higher then 306,97 i get at irregular intervals a "Display Driver stopped working and has recovered" error.

It happens mostly when opening extra software so not in between when doing nothing. Most prone to this problem is TrackIR but not every time. Sometimes i can open it 5 or 6 times in a row without a problem.

Went back to 306,97, problem gone.

[GriffonBR]

That´s sad, but I've read at some other forums that the 310,90 dosen't works great with onboard GPU like the GT640M. Well, I'm really sorry for you guys, but everything is running very fine here.

 

Are you did a clean instalation of these drivers? Clean up the register and so forth?

[Echelon]

Guys dont go to 310.90 as there are allot of bugs in it.

If you have an x64 system the driver wont even load at boot.

On the gforce forums allot of people seems to be affected by this buggy driver.

 

Please wait with the update to 310.90 as Nvidia is trying to fix this bug with there driver.

 

See related topics on:

https://forums.geforce.com/default/topic/527148/geforce-drivers/you-are-not-currently-using-a-display-attached-to-an-nvidia-gpu/

 

and

 

https://forums.geforce.com/default/topic/527036/geforce-drivers/310-90-will-not-load-with-gtx-690/

[Aries]

Why 306.97? Anything awesome about this specific version regarding DCS?

[Vlerkies]

Why 306.97? Anything awesome about this specific version regarding DCS?

 

Yeah thats seems quite a bit older, have most people been running the previous set (310.70) with success?

[Lange_666]

Why 306.97? Anything awesome about this specific version regarding DCS?

 

Because 306,97 are for some reason the latest drivers where i don't have that "display driver stopped responding and has recovered" error. Anything higher i tried all gave the same problem on my system.

 

I'm not the guy who always change drivers whenever a new driver shows up, certainly not when the videocard i have is already a bit older. I've learned over the last 18 years that new drivers on older cards mostly bring the same... nothing... so in general, if my hardware grows older, i'll stop upgrading the drivers because i don't get extra performance out of them and i'll stick to one which works just fine.

 

The reason why i'm on 306,97 and i tried these new drivers has 2 reasons:

- 1: drivers above 300 have the "adaptive VSync at half the refresh rate" option.

- 2: since i went from A-10C stand alone to DCS World i lost quite a bit of performance and "maybe" a new driver could top it up a bit...

 

Reason 2 has all to do with reason 1 and vice versa because the adaptive VSync at half the refreshrate makes the motion of the sim fluid again if your FPS drops under the native refreshrate of the monitor, otherwise it stutters slightly, most noticable closer to the ground and looking sideways at which point you have fast motion of the terrain (lot's of things to find about this problem on various forums).

[Vlerkies]

Thx Lange, will bare that in mind.

Just got my card, installed the 310.70's way better than what I had on the 6990, so chuffed to bits. Haven't had time to fiddle with others yet or try and optimize.

[PoleCat]

Because 306,97 are for some reason the latest drivers where i don't have that "display driver stopped responding and has recovered" error. Anything higher i tried all gave the same problem on my system.

 

 

Have you considered that this error may not be caused by the drivers themselves? Particularly if you have the same problem with several different driver versions. If that is the case then it could be the card itself or a system level problem.

 

Out

[Lange_666]

Yes i did, but...

The first drivers i tried above 306,97 where 310,54. There i had the "display driver stopped responding and has recovered" error almost directly after installation. Computer rebooted, i messed with the profiles a bit (did set them as i had them under 306,97) and started TrackIR (with the idea of running DCS as a test) and bang... error.

I then started to check everything, GPU temps, MB temps, speed of fans, power supply...you name it. Only to find out that on some occations the error would pop up and always on starting or opening a program (so never in DCS self when the GPU was under full load, always outside DCS or whatever game).

I then removed them, did the full cleaning and reinstalled drivers from scratch, same shit.

I then went back to 306,97 and oeps... no more errors.

Did the same with 310,70, same problem.

Did the same with 310,90, same problem.

Back to 306,97... no problem.

 

You tell me what's wrong with 310.xx because i don't know.

 

If you look up the error, you'll find that people have it on various systems with various driver versions, so not only 310,xx. If you look further, you'll see that the same error can occur with both ATI and nVidia cards (in fact, it seems the Win7 work around to a BSOD). You'll also find that there are numerous solutions which won't help and a lot which just don't make sense (in the end you find that there is no real fix solution for the problem). Took me quite some time to read and investigate and re-read all about this error when i first encountered it.

 

It it very likely that something in the 310,xx series triggers the error (310.54, 310.70, 310.90 are all basically the same drivers) on my system and that the next big change in drivers solves it again. Who knows? The only thing i know is that they give a problem on my system and that the 306.97 don't. The real reason i still don't know up until this date.