NVIDIA's Latest 576.02 WHQL Driver Add Up to 8% Performance Bump in Synthetic Benchmarks

[Vya Domus]

Funny, a while ago there were some rumors Nividia might have artificially limited their 40s series GPU and most called it a conspiracy theory.

Also quite interesting that the uplifts come precisely for the GPUs that are competing with AMD's, huh, what coincidence.

 

[absoluteUnit]

on my max OC'd 5070, seeing a roughly 7% increase in FPS on 3dmark steel nomad, and a 2% increase in FPS for port royal. not too bad.

 

[ishank1995]

My 5080 still gets lower scores on Port Royal and Speedway than on older drivers (second from 572 branch I think it was). But not sure how stock scores look as I OC'ed it. But during Speedway clocks fluctuate a lot going from 3200 to 3000 and back. I was getting over 10k now it's 9600.

I have 5080 as well and for some reason, my performance drops when i push gpu above 3k Ghz, might be same issue with you too. It just eats more power for less performance some how.

 

[MarkoB88]

Fack synthetic benchmarks...

BTW definition of Benchmarking is showing what competition doesn't have ...

 

[Globespy]

From reading on reddit a lot of 40 series owners are still getting black screens and other issues (like stuttering while vsync is on) with the new drivers. So I'm staying on 566.36 for now.

4090 user here. I run Vsync/Gsync on all games (Gsync monitor), and with games that have Reflex I change the NVCP Vsync to 'use 3D application settings' and use in game Vsync because it just works better with native Nvidia Reflex titles, which makes sense (there's an article out there you can find like I did).
All games I've tested run very well on these drivers, actually smoother than the trusty 566.36 which I also had been on.
I did have one black screen event, then remembered I hadn't changed Windows TDRDelay/TDRddiDelay registry value from 2 seconds (decimal) to 10 seconds (decimal) and 60 seconds (decimal) on the ddiDelay (see attached pic) - if you don't have these registry keys, simply create DWORD (32) keys and name them exactly like in the attached pic and then change decimal values - if you know this already that's cool, just for those that don't so no need to let me know you already know that since you have better things to do right?
Absolutely no issues since and several 5000 series on the Nvidia forums reported back similar results after trying these suggestions.
It's a shame that Nvidia doesn't openly let people know about this, since it's really a Windows issue and always has been for years - why it became more prevalent with newer drivers, I do not know.
But it's an easy fix that would stop the hoards of angry/toxic posts on the forums. Not saying Nvidia haven't released some awful drivers lately (the entire 572 series was a cluster that I could not get working), but this new driver seems solid and is my daily driver until it gives me reason to change over the coming weeks.

 

[tommo1982]

Interesting when AMD did this regularly it was celebrated and portrayed as something desireable (fine wine)...

Not desired. It was to be expected. AMD was known to have poor drivers upon launch. Given a year or so, the issues were amended and the performance was as it should have been on day one. I've seen the benchmarks. I don't remember the same for Nvidia though. Until recently their drivers were very good.
Current situation is actually good. AMD can recover some market share and Nvidia has to do "something". Them being a monopoly might lead them the Intel path. We don't want that, do we?

 

[PerfectWave]

that-s why i dont trust syntethic bench LUL

 

[RejZoR]

Wasn't performance degrading in recent times and they just fixed it back?

 

[iameatingjam]

I'm still gonna stick with 561.09 until I run into some kind of roadblock.

 

[Tropick]

My last AMD card was a Radeon 8500 over 20 years ago (I know it was ATI then). The ongoing nvidia driver shambles will make me return to AMD for my next card if nothing changes. AMD's cards are getting more enticing as well.

Back in 2022 I decided to upgrade my aging 980Ti workhorse. That thing was a wonderful GPU but I was not about to pay the premiums Nvidia was asking for the 3090Ti and so on Black Friday I opted to roll the dice on AMD for the first time since the early 2010s. Saw that the Navi 21 silicon was getting some good reviews and snagged a 6950XT OC Formula for a pretty attractive price. While there have been some not so great driver releases (24.1.1 broke a lot of Navi 2x features when the 3x silicon was released, but all were corrected in the week following) the overwhelming majority of releases have been welcome additions. With Nvidia acting the way they are these days, and AMD having some very compelling offerings, there's a good chance my next upgrade will be an AMD card as well. If my 6950XT wasn't still performing so admirably, I probably would've been in line at my local Microcenter trying to scoop up a 9070XT when they released.

 

[katzi]

I decided to roll the dice on this new driver, on my 3080'd system, so far it's been good - but can't speak for everyone else.

 

[Visible Noise]

I've had zero issues with any of these drivers on my 4090... I know that I'm going to go home from work today and it's going to happen now but I haven't had an issue yet. And no I'm not an Nvidia fanboy.

Same here. I‘m sorry for the people that are having issues, but I haven’t had a single blip.

 

[chrcoluk]

I have a weird constant logging issue with display container running, but I stopped it by killing the nvidia display container service and making a script that starts the service just for using the control panel.

However with that said I may downgrade again, as the drivers havent gave me any benefit either.

 

[Quicks]

Driver seems fine no BSOD, well did not have any issues with previous drivers either.

But for some reason with this driver on MSI afterburner the GPU temperature gets stuck on 24C.

 

[meem55]

576.02 is potentially dangerous for GPU when apps like Afterburner and GPU Tweak are used. There is a bug where temperature and fan are not read out. This includes manual fan curves.
On my system (MSI RTX4070 Ti Super Slim) for example with Afterburner, it gives a constant temperature of 22 degrees Celsius. Luckily I can roll back to previous 572.83 which are giving no issues here.

This from NVidia forum: https://www.nvidia.com/en-us/geforc...57602-feedback-thread-released-41625/3524070/

RTX5090 here. With Driver GRD 576.02 GPU Temp stuck at 27ºC randomly. BE WARNED, the fan curve of programs like GPU Tweak or MSI Afterburner WONT WORK because of this reading. I've reached memory temps of 100ºC on memory and 91º of GPU core.

Also on Reddit:

https://www.reddit.com/r/ZephyrusG14/comments/1k27vuv

 

[redeye]

is it a 3d mark approved driver?…
… did all of the QA testers at Nvidia move to AMD, because I haven’t had any problems with the adrenaline drivers for AMD cards.

 

[Taisho]

My last AMD card was a Radeon 8500 over 20 years ago (I know it was ATI then). The ongoing nvidia driver shambles will make me return to AMD for my next card if nothing changes. AMD's cards are getting more enticing as well.

It sucks when you are too deep into rabbit hole and belong to the 0.01% user base that have to buy nVidia because it's the only GPU with fully working (3rd party) sRGB gamut clamp and gamma correction based on ICC profile.

 

[Frizz]

This driver made MH Wilds crash consistently even with stock settings. Nvdmk or some other cannot be found entry in event viewer. Apart from this it weirdly conflicated with iCUE and I was getting a gray screen on the main display when I try open Corsair iCUE.

 

[mahanddeem]

576.02 is potentially dangerous for GPU when apps like Afterburner and GPU Tweak are used. There is a bug where temperature and fan are not read out. This includes manual fan curves.
On my system (MSI RTX4070 Ti Super Slim) for example with Afterburner, it gives a constant temperature of 22 degrees Celsius. Luckily I can roll back to previous 572.83 which are giving no issues here.

This from NVidia forum: https://www.nvidia.com/en-us/geforc...57602-feedback-thread-released-41625/3524070/


Also on Reddit:

https://www.reddit.com/r/ZephyrusG14/comments/1k27vuv

This exact issue happened to my 4090 one time (first boot after driver install). Temp with MSI AB temp stuck at 30c and GPU shooted to 85c because custom fan curve stuck at %30, luckily it didn't damage it. Next boot was all normal.

 

[MaxR]

black screen installing new drivers over old ones. solved everything using ddu, I haven't noticed any problems so far, in fact the 5080 seems to perform more consistently

 

[lolwowmage]

It sucks when you are too deep into rabbit hole and belong to the 0.01% user base that have to buy nVidia because it's the only GPU with fully working (3rd party) sRGB gamut clamp and gamma correction based on ICC profile.

what all works for nvidia to do this?

 

[Darkholm]

576.02 is potentially dangerous for GPU when apps like Afterburner and GPU Tweak are used. There is a bug where temperature and fan are not read out. This includes manual fan curves.
On my system (MSI RTX4070 Ti Super Slim) for example with Afterburner, it gives a constant temperature of 22 degrees Celsius. Luckily I can roll back to previous 572.83 which are giving no issues here.

This from NVidia forum: https://www.nvidia.com/en-us/geforc...57602-feedback-thread-released-41625/3524070/


Also on Reddit:

https://www.reddit.com/r/ZephyrusG14/comments/1k27vuv

Can confirm. Yesterday I played F1 24 and GPU temp, GPU fan speed (rpm and %) were 0 in Afterburner OSD.

I thought it was due to Afterburner, but now I know why. Wow, and yet Radeon drivers are the ones which are faulty and are reason for wars all around the globe.

 

[Legacy-ZA]

For those with stutters:

Does hardware polling software like RTSS & HWiNFO64 have a discernible impact on performance?

[MEDIA] They mention in this Hardware Unboxed video that polling software like HWiNFO64 can cause a difference in performance, but is that really true?...

forums.guru3d.com

 

[mechtech]

Does that mean prices are going to go up 8% in price??

 

[Darkholm]

None of those workarounds works for me (RTX 4080) so I reverted to 566.36 and all is OK.