Geforce/Ion Driver Release 195.55 - Page 4

Memorian · 11-17-2009, 23:17 | posts: 1,201 | Location: Beyond the coast

PES10 is working great

ZeBeeDY · 11-17-2009, 23:20 | posts: 35 | Location: Ankara/Turkey

Quote:

Originally Posted by Memorian

PES10 is working great

then it must be a problem with my hw. maybe reinstalling will solve the problem...

Year · 11-17-2009, 23:56 | posts: 11,657 | Location: ♫

finished testing them on W7 Professional X64 , they're the best drivers to date, gained 3fps in ResidentEvil5, 2 fps in FC2, and games seem smoother too on my GTX260.

the Fallout3 "hitching" problem when turning around with the mouse remains though, only way to fix it is to go back to 186.xx but since i dont play FO3 anymore, i can live with that.

card downclocks fine after gaming and temps seem fine too.

a word about PES2010, i had no problem with earlier drivers and the new ones work just as well (played a full 15 min match) perfectly.

really liking this set.

aly_mohy1 · 11-18-2009, 00:06 | posts: 5

pes 2010 stop running

aly_mohy1 · 11-18-2009, 00:21 | posts: 5

Faulting application name: pes2010.exe, version: 1.0.0.0, time stamp: 0x4aa0787f
Faulting module name: nvd3dum.dll, version: 8.17.11.9555, time stamp: 0x4afe50de
Exception code: 0xc0000005
Fault offset: 0x0041bed1
Faulting process id: 0x8d4
Faulting application start time: 0x01ca67d5f5006a70
Faulting application path: E:\games\PES 10\pes2010.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 361c92ec-d3c9-11de-9a1d-001d7d9f0e8b

aly_mohy1 · 11-18-2009, 00:31 | posts: 5

run when shift to 195.50

g60force · 11-18-2009, 00:47 | posts: 573 | Location: Netherlands

Once again this driver is utter brilliance for my mobile gpu *WOOT*

brunoheitor · 11-18-2009, 00:50 | posts: 4 | Location: Brazil / Rio de Janeiro

Quote:

Originally Posted by aly_mohy1

Faulting application name: pes2010.exe, version: 1.0.0.0, time stamp: 0x4aa0787f
Faulting module name: nvd3dum.dll, version: 8.17.11.9555, time stamp: 0x4afe50de
Exception code: 0xc0000005
Fault offset: 0x0041bed1
Faulting process id: 0x8d4
Faulting application start time: 0x01ca67d5f5006a70
Faulting application path: E:\games\PES 10\pes2010.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 361c92ec-d3c9-11de-9a1d-001d7d9f0e8b

My problem in OFP dragon Rising is the same

DerSchniffles · 11-18-2009, 00:51 | posts: 757 | Location: Washington

I got alot of stuttering on shattered horizons with these...i guess what you would call microstuttering? like its smooth and then ill get a little blimp every 5 seconds or so, just makes it annoying. which sucks because i was getting about 4 fps more in that game with these drivers. back to 191.07

Darren Hodgson · 11-18-2009, 00:55 | posts: 9,654 | Location: England

Quote:

Originally Posted by richard.eid

There is no 59Hz bug in Windows 7.

Regarding 59hz Bug.

What you're seeing is expected beahvior.

It doesn't matter whether it's classed as a bug, expected behaviour or a feature, the fact remains that at least one game has issues with Windows reporting the desktop as 59 Hz. That game is Pro Evo Soccer 2010 which doesn't allow you to set v-sync through the Settings executable if the desktop is 59 Hz (the option is greyed out), not that that is a big deal as it can be forced via the control panel or D3DOverrider.

What is an issue though is that at 59 Hz, the replays and cut scenes are capped at 30 fps. Create a custom resolution at 60 Hz and those same replays and cutscenes run at 60 fps when v-synced and, yes, v-sync is selectable too. So the framerate is halved all because of this 59/60 Hz thing. At 59 Hz the game also stutters intermitently too but at 60 Hz it doesn't at all.

If one game has problems with the desktop at 59 Hz (even though the monitor's OSD shows it is actually 60 Hz) then there's a good chance that future games may have issues too.

Darren Hodgson · 11-18-2009, 00:59 | posts: 9,654 | Location: England

Quote:

Originally Posted by aly_mohy1

Faulting application name: pes2010.exe, version: 1.0.0.0, time stamp: 0x4aa0787f
Faulting module name: nvd3dum.dll, version: 8.17.11.9555, time stamp: 0x4afe50de
Exception code: 0xc0000005
Fault offset: 0x0041bed1
Faulting process id: 0x8d4
Faulting application start time: 0x01ca67d5f5006a70
Faulting application path: E:\games\PES 10\pes2010.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 361c92ec-d3c9-11de-9a1d-001d7d9f0e8b

I've just tried PES 2010 now and I'm getting the same error albeit I'm running the patched v1.1 version.

Looks like I'll be restoring my PC back to the previous drivers tomorrow then...

Darren Hodgson · 11-18-2009, 01:02 | posts: 9,654 | Location: England

And Operation Flashpoint: D.R. crashes too, like the poster above.

Yuck... it's looking like these really are beta drivers after all. I've never had games crashing like this before, usually the beta drivers work fine with games. Going to rollback to the 191.07 WHQL drivers for definite.

plexdude · 11-18-2009, 02:06 | posts: 38

OpenGL apps are still broken in this release. I'm back to 190.62. In particular, SOF2 still fails to load. How can they keep releasing drivers that are so bad an old game can't even launch? Absolute garbage. I have a feeling it's going to be forever until Nvidia's driver developers are even aware that this is an issue. Come on Nvidia... give us something that actually works!!!

sava700 · 11-18-2009, 02:17 | posts: 4,834 | Location: In a game world

too many negatives with this release.. i'll pass and not waste the time on them.

mapel110 · 11-18-2009, 02:18 | posts: 91 | Location: Germany

Quote:

Originally Posted by plexdude

OpenGL apps are still broken in this release. I'm back to 190.62. In particular, SOF2 still fails to load. How can they keep releasing drivers that are so bad an old game can't even launch? Absolute garbage. I have a feeling it's going to be forever until Nvidia's driver developers are even aware that this is an issue. Come on Nvidia... give us something that actually works!!!

This Opengl-Problem is only a profile problem.
When you use nHancer, you have to set "driver extension limit" to "11a8" in the profile of SOF2.
Works for all broken Quake3-Engine-Games like RTCW e.g..

guderiancol · 11-18-2009, 02:35 | posts: 28 | Location: Colombia

Yea mapel110, i think that the new drivers have to be "fixed" with nhancer, i got problems runing heaven benchmark (ungine), plz just use nhancer in everygame that u want to play and im sure that many of issues can be solved... try it.,, and thanks with "driver extension limit" to "11a8" my rtcw now is runing again the texture vertex arrays because they were broken since i get my 295 gtx...i love u.

Squall Leonhart · 11-18-2009, 02:42 | posts: 1,331 | Location: Australia

use 4844 rather than 11a8....

v4npro · 11-18-2009, 02:44 | posts: 730 | Location: Maryland

One minute GTA4 works, the next it crashes right after loading. Going back to 191.66

TheHunter · 11-18-2009, 02:51 | posts: 13,439 | Location: √╥²

Quote:

Originally Posted by Darren Hodgson

It doesn't matter whether it's classed as a bug, expected behaviour or a feature, the fact remains that at least one game has issues with Windows reporting the desktop as 59 Hz. That game is Pro Evo Soccer 2010 which doesn't allow you to set v-sync through the Settings executable if the desktop is 59 Hz (the option is greyed out), not that that is a big deal as it can be forced via the control panel or D3DOverrider.

What is an issue though is that at 59 Hz, the replays and cut scenes are capped at 30 fps. Create a custom resolution at 60 Hz and those same replays and cutscenes run at 60 fps when v-synced and, yes, v-sync is selectable too. So the framerate is halved all because of this 59/60 Hz thing. At 59 Hz the game also stutters intermitently too but at 60 Hz it doesn't at all.

If one game has problems with the desktop at 59 Hz (even though the monitor's OSD shows it is actually 60 Hz) then there's a good chance that future games may have issues too.

Windows 7 Issues
• When switching the refresh rate from 59 Hz to 60Hz, the refresh rate remains at 59
Hz..
See the Microsoft KB article KB2006076 at http://support.microsoft.com/kb/2006076.

this is from release notes.. page 20

and one member had problems with WOW its a issue with the driver too..

• World of Warcraft – there is a 60% drop in performance when running the game in
windowed mode with SLI or multi‐GPU mode enabled. [289427]
This is due to a limitation of the Windows Vista operating system and affects all multi‐GPU
systems. NVIDIA is investigating a workaround for this performance problem.

Shataan · 11-18-2009, 03:05 | posts: 737 | Location: CoolIT Systems Freezone

Runs MW2 nicely at 120 hz on Win 7 Ultimate..... maxed settings at 1680x1050 Keepers. Sli and multi gpu mode enabled. Ambient Occl. etc. Nice to finally have a MW 2 profile.

milktree · 11-18-2009, 03:17 | posts: 134

i got terrible stuttering in crysis with the last drivers. it made it completely unplayable. do these drivers fix that?

mapel110 · 11-18-2009, 03:38 | posts: 91 | Location: Germany

Quote:

Originally Posted by Squall Leonhart

use 4844 rather than 11a8....

Yes, saw that numbers too. But do you know the difference?

DeusEXMachina · 11-18-2009, 03:39 | posts: 39 | Location: Cartagena - Colombia

New drivers!!!!!!!!
Well, My mobo is death, When I receive new one I checked up...
sorry my english, is very bad!!!!

gbinfukdover · 11-18-2009, 04:10 | posts: 13 | Location: cumbria

Doesnt return to 2d clocks for me in dragon age or codmw2 and no gpu2 temp wtf all these 19x.xx drivers have been pap for me back to 186.18 again ffs nvidia come on

KillerC · 11-18-2009, 04:16 | posts: 399 | Location: U.S.A. Florida "The shoot me state"

I have been playing through Crysis again on hard and am about half way through , I changed the driver from 191.07 to 195.55 today and went in to play some more because I was getting some "slight" texture flashing issues. After installing I 195.55 noticed that Ambient Occlusion was no longer available for this game , it says "Not supported for this application" (see image below)...which is strange because I was using through half the game with the 191.07. Is this just a fluke or did maybe my driver not install correctly.

(note: I set some settings in the NV CP to try to make Crysis run better and these settings seem to help)

Also it has some strange performance issues with crysis , pauses and stuttering both in video type playable scenes and in the sp game itself that were not there in 191.07 , however they are not constant.

I just finished the COD MW2 SP game and it seemed to play very well on all high settings , but Crysis has some serious issues with this driver for some reason.