State of Nvidia drivers affecting back to RTX 3000 cards

SpyderTracks

SpyderTracks

We love you Ukraine
If you’re having odd issues of crashes and black screens and have a recent Nvidia card, it may well be driver related

 
T

TonyCarter

VALUED CONTRIBUTOR
The December (566.36) one was fine for me (y)

The a few of the interim ones (572.16 to 572.60) including the first for 50-series GPUs were not (n)(n)

But the latest (572.83) one seems to be working fine on my 4090 (y)
 
SpyderTracks

SpyderTracks

We love you Ukraine
There’s a new bug which could be pretty bad if you’re running a custom fan curve on the GPU, please do be aware

DO NOT INSTALL DRIVER 576.02 WITHOUT WATCHING THIS FIRST!

 
T

TonyCarter

VALUED CONTRIBUTOR
SpyderTracks said:
There’s a new bug which could be pretty bad if you’re running a custom fan curve on the GPU, please do be aware

DO NOT INSTALL DRIVER 576.02 WITHOUT WATCHING THIS FIRST!

Click to expand...
giphy.gif
 
T

TonyCarter

VALUED CONTRIBUTOR
SpyderTracks said:
Can you verify the same behaviour?
Click to expand...
Not without installing it...and I tend to be a few weeks behind the curve on most updates...specifically so I'm not the sacrificial guinea pig. Also, my system is either on or off - never in sleep or standby, so not sure I'd trigger this (unless the GPU is going into some sort of sleep state?).

Here's the list of 'bug fixes' in 576.02 (from https://us.download.nvidia.com/Windows/576.02/576.02-win11-win10-release-notes.pdf). The what's new basically says they've added support for the 5060Ti and DLSS4 for Black Myth Wuhan!


576.02.jpg
 
SpyderTracks

SpyderTracks

We love you Ukraine
TonyCarter said:
Not without installing it...and I tend to be a few weeks behind the curve on most updates...specifically so I'm not the sacrificial guinea pig.

Here's the list of 'bug fixes' in 576.02 (from https://us.download.nvidia.com/Windows/576.02/576.02-win11-win10-release-notes.pdf). The what's new basically says they've added support for the 5060Ti and DLSS4 for Black Myth Wuhan!


View attachment 44160
Click to expand...
Apparently aside from this bug, it’s addressed a lot of issues effectively. It’s just this could be a pretty significant issue for some, could potentially lead to outright failure of the GPU say if someone was rendering long term without knowing the issue.
 
SpyderTracks

SpyderTracks

We love you Ukraine
Lols, I just watched the end of it which I hadn’t before I posted this.

I have a feeling Jay may be missing out on future review samples!!!

Have to say, fair play to him, it's about time nVidia got some serious pushback from the community.

 
T

TonyCarter

VALUED CONTRIBUTOR
Ran an initial couple of Furmark2 benchmarks and got the following.

Furmark GL donut (3440x1440, AA off)
  • Average FPS 299
  • Max GPU Hotspot 79ºC
  • Max GPU 70ºC
  • Max VRAM 68ºc
  • Max fan speed 45%
Furmark GL knot (3440x1440, AA off)
  • Average FPS 81
  • Max GPU Hotspot 83ºC
  • Max GPU 73ºC
  • Max VRAM 68ºc
  • Max fan speed 46%
Will now try to 'fake' a sleep/hibernate to see if I can trigger anything.
 
T

TonyCarter

VALUED CONTRIBUTOR
Can't get mine to go to sleep, as I've obviously done some tweaks in the BIOS and Windows power plans to ensure sleep/hibernation never happens.

Tried changing the power setting to energy saving and sleep after 2 minutes, and 'sleep on power button', but it sleeps the screen for about 5 seconds and then comes back on...

But it might also only be a 50-series problem...so another win for the 40-series ;)

giphy.gif

giphy.gif
 
You must log in or register to reply here.
Top