Forceware 190.** are broken

[Keysplayr]

For those having trouble with AA? Can I show you something and tell me if this does not pertain to your situations?

Windows 7 64 bit
ForceWare 190.62's

CrysisWH 1680x1050 Gamer 0xAA in game

CrysisWH 1680x1050 Gamer 4xAA in game

Each screeny is about 5MB in size so give it a few secs to load. Original, umcompressed files. Taken with FRAPS.

Does anyone notice any difference in the screenshots?

 

[EliteSentinel]

Originally posted by: Keysplayr
So anyway, using 192.62's in Win7 64.

GTX295

Played Crysis Warhead for about an hour. Exited game.

Launched RivaTuner and GPUz to observe current core clock, shaders and mem frequencies.

Core0: 300.86MHz Shader: 601.71MHz Memory: 100 MHz
Core1: 300.86MHz Shader: 601.71MHz Memory: 100MHz

So I thought I was supposed to be stuck at 3D clocks when exiting a game?
No reboot necessary here.

Like I told you in the other thread, you need to do a fresh re-install of your OS on another hard drive to test your theory. When you do, please come back and report your results.

Not everyone owns a 295, it's the other cards that has this the driver problem.

Everybody should just spend hours re-installing their OS just to test/fix broken drivers :roll: , come on Keys you can do better than trollo.




Your trolling and taunting of Keys is over. Take a week off to figure out if you want to continue posting here. If you decide you do then clean up your act.


esquared
Anandtech Senior Moderator

 

[EliteSentinel]

Originally posted by: Keysplayr
For those having trouble with AA? Can I show you something and tell me if this does not pertain to your situations?

Windows 7 64 bit
ForceWare 190.62's

CrysisWH 1680x1050 Gamer 0xAA in game

CrysisWH 1680x1050 Gamer 4xAA in game

Each screeny is about 5MB in size so give it a few secs to load. Original, umcompressed files. Taken with FRAPS.

Does anyone notice any difference in the screenshots?

Your screenshot still don't fix the broken driver enforcment AA in the 190
And Crysis AA can only be enabled with in game settings in Win7.

 

[nitromullet]

Originally posted by: Keysplayr
For those having trouble with AA? Can I show you something and tell me if this does not pertain to your situations?

Windows 7 64 bit
ForceWare 190.62's

CrysisWH 1680x1050 Gamer 0xAA in game

CrysisWH 1680x1050 Gamer 4xAA in game

Each screeny is about 5MB in size so give it a few secs to load. Original, umcompressed files. Taken with FRAPS.

Does anyone notice any difference in the screenshots?

IIRC, the AA issue on 190.xx isn't an issue with the driver's actual ability to do AA, but a profile issue. One can still enable AA via the driver globally and in game, but applying different AA settings in the game profile via the NVCP or nHancer doesn't have any affect.

According to BFG, this has not been fixed in the latest WHQL drivers: http://forums.anandtech.com/me..._key=y&keyword1=aa+190

 

[Keysplayr]

Originally posted by: EliteSentinel

Originally posted by: Keysplayr
So anyway, using 192.62's in Win7 64.

GTX295

Played Crysis Warhead for about an hour. Exited game.

Launched RivaTuner and GPUz to observe current core clock, shaders and mem frequencies.

Core0: 300.86MHz Shader: 601.71MHz Memory: 100 MHz
Core1: 300.86MHz Shader: 601.71MHz Memory: 100MHz

So I thought I was supposed to be stuck at 3D clocks when exiting a game?
No reboot necessary here.

Like I told you in the other thread, you need to do a fresh re-install of your OS on another hard drive to test your theory. When you do, please come back and report your results.

Not everyone owns a 295, it's the other cards that has this the driver problem.

Everybody should just spend hours re-installing their OS just to test/fix broken drivers :roll: , come on Keys you can do better than trollo.

You waste countless hours to game. You can't spare a few to get it to run right? Or at the very least, determine if it is in fact the driver, the driver and your particular card, or the condition of your OS?

 

[Keysplayr]

Originally posted by: nitromullet

Originally posted by: Keysplayr
For those having trouble with AA? Can I show you something and tell me if this does not pertain to your situations?

Windows 7 64 bit
ForceWare 190.62's

CrysisWH 1680x1050 Gamer 0xAA in game

CrysisWH 1680x1050 Gamer 4xAA in game

Each screeny is about 5MB in size so give it a few secs to load. Original, umcompressed files. Taken with FRAPS.

Does anyone notice any difference in the screenshots?

IIRC, the AA issue on 190.xx isn't an issue with the driver's actual ability to do AA, but a profile issue. One can still enable AA via the driver globally and in game, but applying different AA settings in the game profile via the NVCP or nHancer doesn't have any affect.

According to BFG, this has not been fixed in the latest WHQL drivers: http://forums.anandtech.com/me..._key=y&keyword1=aa+190

Ok, so AA is working, but not exactly the way it should with different settings. It's either AA on or AA off. Do I have this right?

 

[Keysplayr]

Originally posted by: EliteSentinel

Originally posted by: Keysplayr
For those having trouble with AA? Can I show you something and tell me if this does not pertain to your situations?

Windows 7 64 bit
ForceWare 190.62's

CrysisWH 1680x1050 Gamer 0xAA in game

CrysisWH 1680x1050 Gamer 4xAA in game

Each screeny is about 5MB in size so give it a few secs to load. Original, umcompressed files. Taken with FRAPS.

Does anyone notice any difference in the screenshots?

Your screenshot still don't fix the broken driver enforcment AA in the 190
And Crysis AA can only be enabled with in game settings in Win7.

Ah, you guys had me under the impression that AA wasn't working at all. So when I tried AA, I was like, "WTF?". I'll ask NV what they have planned for a fix for this.

 

[cmdrdredd]

When I use 186.18 and 3D game in a window with Aero on in Vista it works fine. 190.xx is another story. It's a stutterfest unless I turn aero off.

So I haven't used 190.xx

 

[nitromullet]

Originally posted by: Keysplayr
Ok, so AA is working, but not exactly the way it should with different settings. It's either AA on or AA off. Do I have this right?

Sort of... All the settings work fine on a global level. It's the profiles that don't work.

Apparently this applies to other settings as well, not just AA.

from: http://forums.anandtech.com/me..._key=y&keyword1=aa+190

Originally posted by: TC91

Originally posted by: nitromullet
Has anyone checked to see if this is only affecting AA, or is it an issue with profiles in general? I can confirm the AA issue on Win 7, but I only have a single card so I have no idea if SLI profiles are affected.

It's every setting as ambient occlusion, AF, and transparency AA do not work on my GTX 285 when using the profiles in 190.38. Have since gone back to 186.18 without any issues.

Apparently using the global settings works but I never tried it since I have too many games and that would be too much of a hassle (would just be like using ati catalyst all over again, ugh. :disgust

I haven't touched the 190's in a while, since they introduced some horrible stuttering issues in Fallout 3 for me. I'm running 186.24 without any issues right now.

 

[terentenet]

I can confirm I had some problems with the 190.62 as well. Some of my games stopped working correctly. I can remember clearly that Burnout Paradise crashed to desktop several times. I left the computer on at night to download some stuff, found it rebooted in the morning; I've checked the Event viewer and I saw that the display driver has crashed several times within 1 minute and all that was followed by a BSOD 1 minute later. That was on a fresh Windows 7 64bit install.
Went back to 190.38, no problems. It seems that 190.62 doesn't like my system.

 

[imaheadcase]

Originally posted by: EliteSentinel

Originally posted by: Keysplayr
So anyway, using 192.62's in Win7 64.

GTX295

Played Crysis Warhead for about an hour. Exited game.

Launched RivaTuner and GPUz to observe current core clock, shaders and mem frequencies.

Core0: 300.86MHz Shader: 601.71MHz Memory: 100 MHz
Core1: 300.86MHz Shader: 601.71MHz Memory: 100MHz

So I thought I was supposed to be stuck at 3D clocks when exiting a game?
No reboot necessary here.

Like I told you in the other thread, you need to do a fresh re-install of your OS on another hard drive to test your theory. When you do, please come back and report your results.

Not everyone owns a 295, it's the other cards that has this the driver problem.

Everybody should just spend hours re-installing their OS just to test/fix broken drivers :roll: , come on Keys you can do better than trollo.




Your trolling and taunting of Keys is over. Take a week off to figure out if you want to continue posting here. If you decide you do then clean up your act.


esquared
Anandtech Senior Moderator

Hours to reinstall a OS? You still using windows 95? Win7 takes like 15min to install..

 

[cmdrdredd]

I don't mean to sound negative and off topic but does anyone else feel like Nvidia has dropped behind ATI with regard to having good drivers? I had a look around the various forums and see a lot of questions about Nvidia cards and which driver works best, but for AMD it seems like you can just grab the latest one and generally be ok.

I still like my GTX295 and the ability to run Physx on a separate GPU (9600GT for me). At the same time though I would like to use the newer drivers because they do introduce speed improvements, unfortunately I play a game that is stutterfest unless I turn off aero and I honestly hate the look of the windows when aero is off so I really prefer it on. That game also doesn't have an update so it functions on Win7 so I am waiting until then to give that a try. Thus, I'm stuck with 186.xx for now. I do try every new release to see if the problem persists.

 

[mejobloggs]

I couldn't even get AA through global. In all my games

Gone back to 180 something and it's fine

 

[terentenet]

Originally posted by: cmdrdredd
I don't mean to sound negative and off topic but does anyone else feel like Nvidia has dropped behind ATI with regard to having good drivers? I had a look around the various forums and see a lot of questions about Nvidia cards and which driver works best, but for AMD it seems like you can just grab the latest one and generally be ok.

I don't think drivers support is the issue with nVidia, I just think it has a wider user base, therefore more problems show up. I rarely have problems with nVidia drivers and most of the time I update the drivers to the latest version because I am getting bored and have nothing better to do.
It happens once in a while that a driver doesn't work very well, but it's not such a big deal since most of the recent drivers support the latest games anyway. I just revert back to the older driver that I was using and be done with it.

 

[TurtleCrusher]

Considering Win7 is still in RC stage, don't whine about it. Why are you expecting nVidia to even support your free operating system? They have much bigger and better things to focus on than your freeloading person.

I would feel happy that someone even attempted to make drivers for an OS that isn't even retail. Cry a river about it somewhere else.

 

[jimhsu]

I report real stuttering (0.25 second pauses every 5 seconds) in Fallout under 190.62 with Windows 7 x64. Installing 186 fixes the problem. The problem is reproducible with identical saves.

I will try tweaking the "maximum pre-rendered frames" setting in the ini to further clarify this.

 

[jimhsu]

I think the issue is solved - need to playtest later when I have time.

Reinstalled 190.62
Set maximum pre-rendered frames = 0 (nvidia control panel) - seems to reduce frequency of stuttering
Set iFPSClamp = 60 (Fallout ini setting) - seems to eliminate it completely

Anyone who has similar stuttering under Win 7, try that.

 

[imaheadcase]

Originally posted by: Scholzpdx
Considering Win7 is still in RC stage, don't whine about it. Why are you expecting nVidia to even support your free operating system? They have much bigger and better things to focus on than your freeloading person.

I would feel happy that someone even attempted to make drivers for an OS that isn't even retail. Cry a river about it somewhere else.

Its not in RC stage for lots of people, I would 10s of thousands are already installed on students PC since they get it free. I got Win 7 final.

 

[CP5670]

I briefly tried 190.62 (XP) but went back to 186.18 right away after seeing the profile bug. That issue alone makes the drivers useless.

 

[solofly]

The official driver 190.xx (whatever it is) off nv's site, froze while being installed onto my 8800GT/Vista...(funny thing is shit like that used to happen to ATI drivers and now it's nvidia)

 

[nitromullet]

Originally posted by: Scholzpdx
Considering Win7 is still in RC stage, don't whine about it. Why are you expecting nVidia to even support your free operating system? They have much bigger and better things to focus on than your freeloading person.

I would feel happy that someone even attempted to make drivers for an OS that isn't even retail. Cry a river about it somewhere else.

I'm sure that Win 7 drivers are actually a pretty high priority for NVIDIA.

Not sure if you remember the time between RTM and retail for Vista, but people were going nuts over NVIDIA not having a Vista driver for the 8-series. Although, I do agree that by running an pre-release version of Win 7 you should expect some driver issues.

 

[BFG10K]

Originally posted by: Scholzpdx

Considering Win7 is still in RC stage, don't whine about it. Why are you expecting nVidia to even support your free operating system? They have much bigger and better things to focus on than your freeloading person.

I would feel happy that someone even attempted to make drivers for an OS that isn't even retail. Cry a river about it somewhere else.

Uh, the profile bug affects XP/Vista/7, and probably 2000 too. :roll:

 

[Dribble]

Originally posted by: Scholzpdx
Considering Win7 is still in RC stage, don't whine about it. Why are you expecting nVidia to even support your free operating system? They have much bigger and better things to focus on than your freeloading person.

I would feel happy that someone even attempted to make drivers for an OS that isn't even retail. Cry a river about it somewhere else.

Been using the final release for over a month now. Anyone with a paid up MSDN subscription has access to it. Been pretty stable - other then lacking slider to o/c shaders nvidia drivers work fine for me - crysis, L4D and TF2 tested although I haven't bothered with profiles so haven't seen that problem. Using 190.62 & GTX 260.

 

[secretanchitman]

190.62/GTX 260 and no problems here. of course i got rid of my 7 install and went back to xp...

 

[pcslookout]

Originally posted by: secretanchitman
190.62/GTX 260 and no problems here. of course i got rid of my 7 install and went back to xp...

Which version of windows xp out of curiousity?