Nvidia Geforce Drivers Release Announcement thread

I feel this is relatively inconsequential to the end consumer: if they pay $1000 for a GPU they want VRR to work and they want Fortnite to not crash, regardless if it's one bug causing 99 issues or 99 bugs causing 1 issue.
Both aren't just Nvidia driver things, VRR if it's not Gsync/compatible may not work and that would be a monitor issue, Fortnite may have it's own bugs.
 
Both aren't just Nvidia driver things, VRR if it's not Gsync/compatible may not work and that would be a monitor issue, Fortnite may have its own bugs.
VRR suddenly not working well out of nowhere is a bug.

I find it hard to believe Epic would put out a notice telling people that it’s Nvidia’s fault if it was in fact not their fault. This is the same developer that is behind like 90% of modern games through Unreal 5 lol I think they know what they’re talking about.
 
List of confirmed bugs in 576.02 is growing really fast... again

Open Issues:
  • [GeForce RTX 50 series notebook] Resume from Modern Standy can result in black screen [5204385]
  • [RTX 50 series] Cyberpunk 2077 will crash when using Photo Mode to take a screenshot with path tracing enabled [5076545]
  • [RTX 50 series] Red Dead Redemption 2 crashes shortly after starting a game in DX12 mode. No issue in Vulkan mode [5137042]
  • [RTX 50 series] Colors may appear slightly saturated in games when in game-resolution is below native resolution of monitor and display scaling is set to 100% [5158681]
  • Forza Horizon 5 lights flicker at night time [5038335]
  • Track corruption in Forza Motorsport in benchmark or night races [5201811]
  • [RTX 50 series] Hogwarts Legacy may display flickering when Frame Generation is enabled [5216455]
  • [RTX 50 series] Portal RTX displays rainbow colored artifacts after updating to GRD 576.02 [5108472]
  • [RTX 50 series] [Final Fantasy VII Rebirth/Monster Hunter Wilds] Game may crash during shader compilation after updating to GRD 576.02 [5230492]
  • [RTX 50 series] Horizon Forbidden West freezes after loading a game save [5227554]
  • GPU monitoring utilities stop reporting GPU temperature after waking PC from sleep [5231307]
  • [RTX 50 series] Marvel Rivals displays broken shadows when Global Illumination set to "Lumen GI - Ultra Quality" or "Lumen GI - High Quality" [5231701]
  • Flickering/corruption around light sources in Ghost of Tsushima Directors Cut [5138067]
  • [RTX 50 series] Lumion 2024 may crash when entering render mode [5232345]
  • [RTX 50 series] [Black Myth]: Game will randomly crash when Wukong transforms [5231902]

Most interesting is this one:
  • GPU monitoring utilities stop reporting GPU temperature after waking PC from sleep [5231307]
Unwinder - author of RivaTuner/MSI Afterburner confirmed that's internal driver error and also stated that could cause stability issues
Unwinder said:
Stuck thermal sensor is just a part of problem. When it stops reporting data, NVIDIA driver's GPU boost thermal adjustment for V/F curve stops working too, causing GPU to clock higher than it did before....
Unwinder said:
Not true. It is by far not "only" Afterburner as you wrongly claim. NVIDIA's official NvAPI_GPU_GetThermalSettings API is broken in this driver, which affects thermal monitoring in all tools using it (which includes OS task manager, PresentMon and every single hardware vendor's specific software like ASUS GPU tweak, EVGA Precision X1 or MSI AB).

NVIDIA also has undocumented private thermal monitoring API, NvAPI_GPU_ThermChannelGetInfo (which includes hotspot and VRAM monitoring interface), which still works in this driver and which can be optionally used by GPUZ or HwInfo, but ironically it is reverse engineered unoffficial fuctionality and NVIDIA doesn't allow partner's software to rely on it (that's exactly why you never see VRAM temperature in any partner's software, but can see it in independent ISV's products like HwInfo).

Also, stuck thermal sensor is just a part of problem. When the sensor is stuck in this driver, it also blocks driver's thermal GPU boost V/F curve adjustment. So GPU starts boosting much higher than before (due to not seeing temperature increase). So it bumps performance but may negatively affect stability of some PCs.

Let's see if there will be some damaged cards. It seems this bug can be triggered if you are using Fast Boot/HiberBoot
 
List of confirmed bugs in 576.02 is growing really fast... again

Open Issues:
  • [GeForce RTX 50 series notebook] Resume from Modern Standy can result in black screen [5204385]
  • [RTX 50 series] Cyberpunk 2077 will crash when using Photo Mode to take a screenshot with path tracing enabled [5076545]
  • [RTX 50 series] Red Dead Redemption 2 crashes shortly after starting a game in DX12 mode. No issue in Vulkan mode [5137042]
  • [RTX 50 series] Colors may appear slightly saturated in games when in game-resolution is below native resolution of monitor and display scaling is set to 100% [5158681]
  • Forza Horizon 5 lights flicker at night time [5038335]
  • Track corruption in Forza Motorsport in benchmark or night races [5201811]
  • [RTX 50 series] Hogwarts Legacy may display flickering when Frame Generation is enabled [5216455]
  • [RTX 50 series] Portal RTX displays rainbow colored artifacts after updating to GRD 576.02 [5108472]
  • [RTX 50 series] [Final Fantasy VII Rebirth/Monster Hunter Wilds] Game may crash during shader compilation after updating to GRD 576.02 [5230492]
  • [RTX 50 series] Horizon Forbidden West freezes after loading a game save [5227554]
  • GPU monitoring utilities stop reporting GPU temperature after waking PC from sleep [5231307]
  • [RTX 50 series] Marvel Rivals displays broken shadows when Global Illumination set to "Lumen GI - Ultra Quality" or "Lumen GI - High Quality" [5231701]
  • Flickering/corruption around light sources in Ghost of Tsushima Directors Cut [5138067]
  • [RTX 50 series] Lumion 2024 may crash when entering render mode [5232345]
  • [RTX 50 series] [Black Myth]: Game will randomly crash when Wukong transforms [5231902]

Most interesting is this one:
  • GPU monitoring utilities stop reporting GPU temperature after waking PC from sleep [5231307]
Unwinder - author of RivaTuner/MSI Afterburner confirmed that's internal driver error and also stated that could cause stability issues



Let's see if there will be some damaged cards. It seems this bug can be triggered if you are using Fast Boot/HiberBoot
There's also this redditor that says the automatic throttling might be affected too
 
Let's see if there will be some damaged cards. It seems this bug can be triggered if you are using Fast Boot/HiberBoot
Which is pretty much everyone as it's the default regime in Windows.

But still no problems, right? Nvidia's drivers are the same as they've ever been!
 
There are at least two APIs for reading the temperature. nVidia's statistic overlay works just fine and there is no problem with standard fan curve. Maybe MSI Afterburner and co. only using "their" temperature data from the other API for controlling a custom fan curve.
 
There are at least two APIs for reading the temperature. nVidia's statistic overlay works just fine and there is no problem with standard fan curve. Maybe MSI Afterburner and co. only using "their" temperature data from the other API for controlling a custom fan curve.
Someone said that "partners" like msi Afterburner only allowed to use the official API. Not the NVIDIA internal-only API that also have Hotspot temperature
 
There are at least two APIs for reading the temperature. nVidia's statistic overlay works just fine and there is no problem with standard fan curve. Maybe MSI Afterburner and co. only using "their" temperature data from the other API for controlling a custom fan curve.
The problem does exist for the driver, and only happens under specific circumstances. It documents this in the post.
 
I'm fairly sure that if that bug would be able to kill GPUs we'd already seen a hotfix.
So far people are reporting funny temperatures in monitoring s/w, and that's pretty much it.
It also unclear what steps one must take to trigger it - does it have to be a sleep cycle or is just fast startup enough (so a default power cycle would be enough)? Looks like the former and not the latter.
 
The problem does exist for the driver, and only happens under specific circumstances. It documents this in the post.
Like i said: nVidia's overlay is not affected by the API problem. It does not have any impact on the GPU until a third party app is involved like MSI Afterburner.
 
Like i said: nVidia's overlay is not affected by the API problem. It does not have any impact on the GPU until a third party app is involved like MSI Afterburner.
The overlay is part of a separate app. Many people are reporting stock fan curves not working properly.

I'm fairly sure that if that bug would be able to kill GPUs we'd already seen a hotfix.
So far people are reporting funny temperatures in monitoring s/w, and that's pretty much it.
It also unclear what steps one must take to trigger it - does it have to be a sleep cycle or is just fast startup enough (so a default power cycle would be enough)? Looks like the former and not the latter.
I don’t think it will kill GPUs but there have been reports of system instability.
 

GeForce Hotfix Display Driver version 576.15 is based on our latest Game Ready Driver 576.02. This hotfix addresses the following:


  • [RTX 50 series] Some games may display shadow flicker/corruption after updating to GRD 576.02 [5231537]
  • Lumion 2024 crashes on GeForce RTX 50 series graphics card when entering render mode [5232345]
  • GPU monitoring utilities may stop reporting the GPU temperature after PC wakes from sleep [5231307]
  • [RTX 50 series] Some games may crash while compiling shaders after updating to GRD 576.02 [5230492]
  • [GeForce RTX 50 series notebook] Resume from Modern Standy can result in black screen [5204385]
  • [RTX 50 series] SteamVR may display random V-SYNC micro-stutters when using multiple displays [5152246]
  • [RTX 50 series] Lower idle GPU clock speeds after updating to GRD 576.02 [5232414]
 
Back
Top