NVIDIA Geforce 332.21 WHQL - Download & Discussion

I played TombRaider MP yesterday and after 45-50min or so I got one nasty lag spike, fps dropped from ~ 75-80gfps to a 2-3sec freeze and then back (I almost thought it was a TDR), it didnt do that again.. Dunno but looked weird, never had that before with older 331.xx driver.


@ Darren
yeah its weird, I just tried 64bit version and it shows the same lower 188-191. Doesn't matter gpu transcode on or off, its the same by both..

 

Hi, actually I played it after a good 1-2 months, every time I checked it was always empty.. Especially after I bought those DLC maps.

I guess I got lucky, found 5 people playing and all of them had DLC. And I finally saw new maps after 5-6 months owning them :infinity:

 

I get worse performance in ac4 with these, basically the only demanding game i'm playing currently, what you say rings true on my side too.
I thought they had fully enabled the driver AO or something ..

 

Hoping for a new set of beta's to try soon. These WHQL's seem...well bad tbh.

Ive been troubleshooting a memory leak - that see's my non-paged pool memory reach 8GB usage + under some circumstances.

Using poolmon I've narrowed it down to a few tags (none of which I've managed to find what for definite they are) - but, If I were a betting man I'd point towards these drivers (seeing as 1) That's all I've changed recently and 2) The tags start with NV)

We'll find out when I switch back to the old beta's (which I'll do if no new ones appear this week).

 

when I was on win 8.1 preview ac4 had input lag, now i'm on the full 8.1 pro version I notice the lag is gone, and indeed it's a little more demanding on gpu now which makes sense. before it felt like max pre-rendered at 3, now it feels like my preferred 1 preset, which I've always had it set to.

 

Well there are definitely some performance issues with this driver, it cripples raw cpu performance, not good...

Just tested 331.82 again and I got Rage gpu cuda transcode score 356, still not ~ 392-398 like by older 32x.xx though, but a lot better then 332.21 with only 188.

edit:
In all cases seta jobs_numThreads "8", 332.21 acts like I use seta jobs_numThreads "4" and cuda transcode off.







Also this

Lp2 dx9 fixed test 2 - cpu intense benchmark @ 720p, noaa, no shadows, no blur, rest at high..

with 332.21 108fps


with 331.82 like usual 129fps


I will stick with 331.82. imho this 332.21 is still more like beta :-\


Please, just give us 334 already

 

i'm 200 points lower in the firestrike cpu benchy.
I put it down to my new OS install which I installed these on.
for me ac4 is more demanding than before but I now have no input lag (probably OS related) and now the game seems better looking (probably driver related).

 

Has anyone done any 331.93 vs 332.21 tests?

 

someone done one with tomb raider and these were better, but there's something new going on with these drivers imo.

 

there isnt much difference vs 331.93- apparently only better AC4 support (new sli flag) and fix for GF104/114 with browsers.


I will keep this 331.82 for now, not a single hickup in Tombraider MP anymore, Bf4 runs smoother too..


edit:
both 331.93 and 332.21 are from different r331 branch r331_82-xxx, 331.82 and older are from r331_00-xxx and its this r331_82 that's weird for GF110 idk about others, but I saw GK110 had the same lower gpu transcode score in Rage with this r331_82 branch. Overall im not impressed by it, I've seen better drivers before.

 

Well that's a relief ! This was driving me bat-sh!t crazy, my Firestrike CPU score went from 84xx to 80xx, and i couldn't determine what was up. I also had random TDR at startup after installing these. Gonna uninstall these drivers ASAP and go back to 331.93 i think.

 

I cant get any drivers above 327.xx to work well. When I boot up after Windows logo I usually get a Displayport No Signal. zzz.

So annoying. I have tried every single ones after 327.xx

 

Not directly related to this driver but since this includes PhysX I thought I'd post here rather than create a new thread.

Basically, I installed the PhysX v9.13.0927 System Software a while ago because it was newer but after reading reports that it was slower I reverted to the version included with this driver (v9.13.0725). I just uninstalled the newer one and installed the older one, apparently without issue.

However, when I came to try and play Dragon Age Origins I got a PhysX initialisation error during loading which stated that Cudart32_60.dll was missing. I tried Google-ing this file but found nothing which surprised me. So I tried reinstalling PhysX again and it installed fine, no errors. Sadly, I got the same error, no matter how many times I tried to uninstall/reinstall the version of PhysX included with this driver. I even reinstalled the Legacy driver (v9.12.1031) out of desperation. But, nope, still didn't work.

In the end I had to reinstall the newer v9.13.0927 PhysX driver in order to play the game as it includes the Cudart32_60.dll file. Seems that uninstalling the newer PhysX leaves traces of the newer one in the registry causing it to break some older games that use PhysX.

I just thought I'd post the warning here in case anyone else has issues with PhysX.

 

Same issue with Overlord II (I know its an old game), but the way PhysX is installed in the latest few drivers, the game refuses to run. You have to manually reinstall PhysX, and then it will work.

 

I just experienced the 'blah blah driver geforce whatever.dll crashed and recovered' while watching youtube.

 

Try 331.82, from my experience nv messed up more when they "fixed" GF104/114 browser TDR bug and it affected the rest in its own way.. Useless fix is useless.

 

I corrupted my drivers again, done it after installing latest PhysX, it's ok now after I reinstalled driver on top.
the corrupted driver made ac4 crash.

edit: damn corrupted it again, its my cpu clock tinkering that's doing it.

 

Great feedback. Next time use control panel > Administration Windows Log

Thank you,

 

We all know what the issue is Casper. And it should have been gone a long time ago.