Nvidia GeForce 327.23 WHQL - Download & Discussion

same experience with AO and lots of issues with shadows in multiple games, specially Bioshock Infinite, micro-stutter is still an unresolved issue that not everyone notices and Nvidia is trying to get away with, also voltage increase and temperature increase, and don't tell me it's summer or whatever, hotter days with 314.22 the GPU was down 8-9 degrees, so it's the 32x.xx drivers causing these issues. How they pass WHQL certification time after time is a mistery, what a mess, I swear if next drivers are not perfect as 314.22 I'm selling my 3 GB 660 Ti SLI setup (2 good cards in SLI for 60 fps 1080p gaming IMO) and buying whatever AMD has in store to counter Nvidia 7XX GPUs. I don't care about performance when it's full of bugs and issues. Are you reading ManuelG ? still waiting (3 months and counting) your reply about the Nvidia drivers supporting or not the Windows 7 update KB267038...

 

Today my game Freeze at League of Legends with this driver.
i go back and stay now with 314.22 until AMD bring out their next GPU.

 

Why its the problem of the customers?
If they can´t take care of their Product dont release so much Series of Cards.

 

blaming the customers or some specific GPUs is the most laughable and yet amazing thing I've ever read over here, the drivers are supposed to work reasonably well no matter what Nvidia GPU you're using, if Nvidia can't take care of this then how can we blame the GPUs or the customers ??? seriously ???? they should start making different drivers for different GPU series don't you think ? but blaming the issues on the customers ? whoa, just wow !

 

Aye. Skyrim AO is really, really light too. Basically only noticeable if you start pixel peeping two different images (on & off). In UE3 games it's basically as good as off, sometimes there's small black/dark artifacts caused by it (watch the Mirror's Edge building closely when AO is enabled, something similar in game too). As far as I can tell it's as good as disabled in game.

 

They do, they are just not used by developers.

The complications are there, the current state of drivers prove it.

Architectures can still conflict with each other no matter how small the change. It's happened before many times, yet every time it does people act like its something new.

You are all missing my point, I'm not just talking on a hardware level for Architectures but the Software/Driver package FOR those Architectures.

Code is different from hardware. We had 400 series bugs that lasted forever on the GTX 460 for example, when the GTX 600 series came out due to Boost. It's just an example. There are many more examples than that also. These cards are made to do more than GTX 500 and under, and things can conflict through software.

Heck we had bugs with the GTX 480/470 etc when the GTX 580 was launched that lasted a couple of months.

So many hardware combinations exist now, while yes that is important, it makes more to do for coders.

People with outdated hardware should expect complications. I understand the point about the architecture changes not being super drastic, but the features behind the architecture, and the software written for them is. The BIOS has changed a good bit on GTX 600 series and up as well.

These things do impact coding.

Reporting the problems is great, but the constant whining and bickering to Nvidia isn't making the problem go away, just being annoying.

 

I have a GTX 670 and I was very satisfied until drivers 314.22.
It is not necessary to complain more.. next vga will be RED...

 

Really thats funny as i can remember almost everyone who posts on Guru3D saying how bad the 320.**'s were in one way or another especially Titan and 780 users.

I could make a Poll on here and many other forums asking wether the 320.**'s are a good or bad branch of driver and i guarantee the MAJORITY would agree and vote that they were bad so i dont no wtf your going on about tbh.

 

In comes the complimentary 314.22...oh wait.

Well to be honest I gave up reading and started skipping any comments related to the drivers after 314.22 not being up to par.

I guess I've been lucky to have no issues with any of the beta or WHQL drivers since 314.22. Onwards and upwards.

 

Guys with problematic drivers+card behavior, have you tried the card`s BIOS tweaking? May be lowering boost (on keplers) and/or power target. It would be 100% enthusiast- and guru-like.

Edit: By the way, are there OpenGL titles among the problematic ones?

Edit2: Beside the number of card HW generations NVidia (and AMD) has to deal with: DirectX versions, OpenGL versions, WDDM versions, x86 and x64 architectures, OpenCL versions, motherboard BIOS old and EFI, various display/TV connectors+protocols, PCI Express versions, single and SLI configurations.

 

I simply want to know why 314.22 were bug-free drivers with a good compromise between perfect stability and nice performance / IQ and then everything went downhill from 32x.xx on, what was the "change" ?

 

Suspect only driver team project manager can answer to that question.

 

GhostXL ..... agree with everything you said bro.

 

They weren't bug free. In fact there is a whole list of bugs in that driver with the release notes. Personally, I've not had a driver crash in ages unless caused by something I did by overclocking or forcing AA modes in some games. I'm not really sure why the older gen seems to have more issues...maybe it's a conspiracy by Nvidia to make people upgrade their hardware...

 

These are nice drivers for me.

 

This and every other driver after 314.22 are released for "all" card series, even the 400 series, which I own. They are supposed to work, but they don't. If NVIDIA can't handle this then they should start branching out and keep a 314.22 variant for us the minority. What they are doing right now is inexcusable and it's not our fault. You don't wanna see the kind of chaos these drivers bring upon Windows 8.1.

 

These work fine for me.