PDA

View Full Version : NVIDIA Forceware 185.85 WHQL - May 6


Pages : 1 [2] 3

walterman
05-08-09, 02:58 PM
The AOC DX10 Test still does not work. Also, i still have the same problems with the hardware deinterlacing in powerDVD.

LitHiuM
05-08-09, 03:12 PM
Everything fine for me so far; dual-monitors running fine, all games I play looking good with AO, no other problems as yet. :)

Tikimotel
05-09-09, 05:48 AM
hmm is the nvidia service running? or have you disabled any of the startup files for nvidia?... also try removing the old physx drivers before installing

I found it! (woohoo) :captnkill:
It turns out the driver was not at fault.

I have Directory Opus 9 installed (on all 3 machines), it had added itself to the right-click menu on desktop.
I disabled this option in Directory Opus and now everything runs without crashing "explorer.exe".

So maybe it is a conflict between Directory Opus and the Nvidia control panel integration or this bug occurs with other programs that add some option to the right-click menu of the desktop (and nvidia control panel integration simply doesn't like any other program adding stuff to that particular menu).

shilk
05-09-09, 02:08 PM
Yeah, Really annoying that I have to constantly switch back and forth between idle to fix it.

I had that bug before and hit the Steam forums for a solution a while back. It happens to source engine based games more often, seems like.

It's CSAA. I had mine set to 8xCSAA and when I installed an older driver. What I did was disable AA in the NVIDIA control panel completely and used the in-game CSAA option. If I changed it to MSAA, then it was fine. After it fixed itself, I switched back to 8xCSAA from in the game, and everything went back to normal.

Seems to happen to only a select few drivers though. :(

NarcissistZero
05-09-09, 07:01 PM
Started playing Fallout 3 again for Broken Steel and it crashed everytime I tried to confirm VATS with these drivers.

Reverting to 182.5 fixed it.

|MaguS|
05-09-09, 08:18 PM
I had that bug before and hit the Steam forums for a solution a while back. It happens to source engine based games more often, seems like.

It's CSAA. I had mine set to 8xCSAA and when I installed an older driver. What I did was disable AA in the NVIDIA control panel completely and used the in-game CSAA option. If I changed it to MSAA, then it was fine. After it fixed itself, I switched back to 8xCSAA from in the game, and everything went back to normal.

Seems to happen to only a select few drivers though. :(

So I have to disable AA in CP and set the AA ingame?

nekrosoft13
05-09-09, 08:21 PM
Started playing Fallout 3 again for Broken Steel and it crashed everytime I tried to confirm VATS with these drivers.

Reverting to 182.5 fixed it.

f3 seems to work fine over here.

NarcissistZero
05-09-09, 08:45 PM
f3 seems to work fine over here.

Well I didn't change anything other than drivers and suddenly VATS works again.

BelligerentBill
05-09-09, 09:20 PM
I found it! (woohoo) :captnkill:
It turns out the driver was not at fault.

I have Directory Opus 9 installed (on all 3 machines), it had added itself to the right-click menu on desktop.
I disabled this option in Directory Opus and now everything runs without crashing "explorer.exe".

So maybe it is a conflict between Directory Opus and the Nvidia control panel integration or this bug occurs with other programs that add some option to the right-click menu of the desktop (and nvidia control panel integration simply doesn't like any other program adding stuff to that particular menu).

I had this problem under Windows 7 with the 185.68's

I too have Directory Opus installed, as everyone should :p It's the greatest thing since sliced bread and I'll not give up any of IT's features for some generally broken Nvidia drivers. The 185.xx series has ALWAYS had something major busted, like they hired some retards to code them in another studio/office just for the tax breaks provided by hiring said retards.

Blacklash
05-10-09, 09:23 AM
For SLi users, on Vista I suggest 182.50. For SLi users on Windows 7 I suggest 181.71.

You can get them below by searching BETA and archived drivers-

http://www.nvidia.com/Download/index.aspx?lang=en-us

With any 185.xx driver and SLi the nVidia CP opens very slowly for me, and I get flashing icons in my inventory in AoC. With the first mentioned drivers I do not and the CP opens snappy. It also applies settings quickly.

slaWter
05-10-09, 09:50 AM
I agree, 182.50 is one of the best drivers :)

mullet
05-10-09, 09:56 AM
I agree, 182.50 is one of the best drivers :)

+1 I put them on both rigs and everything is running great now.

ATOJAR
05-10-09, 01:45 PM
185.85's seem fine here, COD 4 & 5, ToCa race driver 3, BF2/2142 & all expantions, Age of Conan, Unreal Tournament III, Counter Strike Source & Day of Defeat Source all run fine :)

AdamK47
05-10-09, 02:35 PM
I've been using 182.52 with eVGA SLI enhancement. Good drivers. At least I can use vsync in DX10 titles. nVidia seems to be oblivious to the fact that it's broken in the 185.xx series.

Dirthead
05-11-09, 12:37 AM
Yea i tried the 182.50 drivers and all my games now works and hate to say it even better then the 185.85 drivers.........

So until i have to im going to use these till i have to change.... or when they fix the problems with the 185.xx drivers...

methimpikehoses
05-11-09, 02:00 AM
I went back to 182.5 also. Better nao.

shilk
05-11-09, 02:38 AM
So I have to disable AA in CP and set the AA ingame?

Yep. That's how I set it, and it's not dark anymore. :)

Ever since the 18x.xx series drivers, it's been an issue judging from the Steam forums.

Blacklash
05-12-09, 06:27 AM
I did fix the AoC flickering icons in the inventory issue with 185.85 when using SLi. Forcing AFR2 fixed it for whatever the reason.

Raptorman
05-12-09, 11:13 AM
I have weird graphical anomalies in Empire: Total War. All the characters are purple rectangles until I zoom in then they are fine. Time to ditch these drivers.

nekrosoft13
05-12-09, 02:18 PM
all fine here

http://img100.imageshack.us/img100/8334/clipboard01ose.th.jpg (http://img100.imageshack.us/my.php?image=clipboard01ose.jpg)

185.85 so far been good to me

Sgt_Pitt
05-12-09, 11:06 PM
With these drivers if i force 8xAA and 4x AF my screen goes fuzzy with snow and distorted textutres and NVKLMD(whatever) stops responding.

It could be my card on the way out, but i've never had this problem before.

Edit: sorry wrong drivers i was talking about 185.81 windows 7 x64

alfredog1976
05-13-09, 04:30 AM
Flickering came back in Mirror's Edge with these, but I'm sure it's an SLi setting (as I'm still new to this). I did turn on Ambient Occlusion and the framerate stayed constant in Left 4 Dead, also. Keeping these for now. :)

I also get flickering with Mirror's Edge (main character's hands flicker). Anyone know how to fix this? I didn't get this with the 182.50 drivers...

saturnotaku
05-13-09, 06:57 AM
Anyone know how to fix this? I didn't get this with the 182.50 drivers...

You just answered your own question.

shilk
05-13-09, 01:15 PM
I also get flickering with Mirror's Edge (main character's hands flicker). Anyone know how to fix this? I didn't get this with the 182.50 drivers...
I'm using SLi, so it may be a bit different in your case. It seems to go away when I pick different SLi modes or something.

jcossin
05-13-09, 07:54 PM
These won't load on my 9800m based machine... :(

181.81 load fine, these claim that no compatible hardware was found even though nvidia's site claims these fully support 9800m...