• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**THE NVIDIA DRIVERS THREAD**

IN THE feedback thread on the GeForce forum since the release of 610.74 WHQL, users have reported the following issues:

  • Driver stability: repeated nvlddmkm failures (Event ID 14 and 153), TDR resets, and spontaneous reboots with Kernel-Power error (Event ID 41). The owner of RTX 5090 reports constant TDR in World of Warcraft – the problem appeared at 610.52, it is not present at 610.47, the rollback eliminates failures.
  • Game crashes and drawdowns: Battlefield 6 – desktop flights; Overwatch – Rendering device lost error after several matches; Cyberpunk 2077 – path-traced photo mode flight and frame rate drop from 80 to 10 FPS when opening menus, maps and inventory; World of Tanks: HEAT – frame rate drop and full graphics card crash on RTX 3080, on 610.62 the problem is not played; Cities: Skylines II – flights and performance loss, which disappear after rolling back to 596.49.
  • Frame Generation and Smooth Motion: strong jerks with the combination of Frame Generation x2 and V-Sync in 007 First Light and Assassin's Creed Black Flag Resynced – complaints about this bundle have been received since issue 610.47; in DOOM: The Dark Ages – Revelations, the Multi Frame Generation multiplier does not affect frame rates, and forced activation via NVIDIA App causes twitches; Smooth Motion bundle, G-Sync and FPS limiter breaks the uniformity of frame output in Total War: Warhammer III and Escape from Tarkov.
  • VRR flicker: low-frequency compensation (LFC) is triggered earlier than expected and overestimates the frequency multiplication, which is why there is noticeable flicker on VRR monitors; According to Guru3D users, the last release without these problems remains 581.94 Hotfix.
  • Monitors and DisplayPort: signal loss on DisplayPort monitors immediately after logging into Windows (RTX 3070, temporary solution – launching DisplaySwitch.exe/extend); black screen when turning on the Samsung Odyssey G5 until the on-screen menu button is pressed; output drop to all displays when switching input on an LG C9 TV until forced reboot; accidental driver crashes in a configuration of two DisplayPort + HDMI monitors (RTX 5060 Ti); broken HDR and VRR on Apple Studio Display XDR; loading the second monitor in low resolution – the problem stretches back to the 591.86 driver.
  • Shadow artifacts: flickering and shifting of vegetation shadows in Elden Ring (observed from branch 581); flickering of distant shadows in Wuthering Waves and Horizon Zero Dawn Remastered – defect appeared in 610.74, missing at 610.62.
  • Laptops: modern Standby Deep Sleep State (DRIPS) freezes when Windows Quick Start is enabled; The author of the detailed report associates the problem with the PowerSettings parameters in the registry that the NVIDIA High Definition Audio driver prescribes – removing them eliminates the freeze.
  • Other: for one user, the RTX 5060 Ti was no longer determined by the system after the driver was installed; automatic overclocking in NVIDIA App is reset after each reboot.
 
Last edited:
Neil79 said:
IN THE feedback thread on the GeForce forum since the release of 610.74 WHQL, users have reported the following issues:

  • Driver stability: repeated nvlddmkm failures (Event ID 14 and 153), TDR resets, and spontaneous reboots with Kernel-Power error (Event ID 41).
Click to expand...

I've gotten this 3 times over the last few days, DDU'd and went back to a previous Studio and was ok.
 
Neil79 said:
IN THE feedback thread on the GeForce forum since the release of 610.74 WHQL, users have reported the following issues:

  • Driver stability: repeated nvlddmkm failures (Event ID 14 and 153), TDR resets, and spontaneous reboots with Kernel-Power error (Event ID 41). The owner of RTX 5090 reports constant TDR in World of Warcraft – the problem appeared at 610.52, it is not present at 610.47, the rollback eliminates failures.
  • Game crashes and drawdowns: Battlefield 6 – desktop flights; Overwatch – Rendering device lost error after several matches; Cyberpunk 2077 – path-traced photo mode flight and frame rate drop from 80 to 10 FPS when opening menus, maps and inventory; World of Tanks: HEAT – frame rate drop and full graphics card crash on RTX 3080, on 610.62 the problem is not played; Cities: Skylines II – flights and performance loss, which disappear after rolling back to 596.49.
  • Frame Generation and Smooth Motion: strong jerks with the combination of Frame Generation x2 and V-Sync in 007 First Light and Assassin's Creed Black Flag Resynced – complaints about this bundle have been received since issue 610.47; in DOOM: The Dark Ages – Revelations, the Multi Frame Generation multiplier does not affect frame rates, and forced activation via NVIDIA App causes twitches; Smooth Motion bundle, G-Sync and FPS limiter breaks the uniformity of frame output in Total War: Warhammer III and Escape from Tarkov.
  • VRR flicker: low-frequency compensation (LFC) is triggered earlier than expected and overestimates the frequency multiplication, which is why there is noticeable flicker on VRR monitors; According to Guru3D users, the last release without these problems remains 581.94 Hotfix.
  • Monitors and DisplayPort: signal loss on DisplayPort monitors immediately after logging into Windows (RTX 3070, temporary solution – launching DisplaySwitch.exe/extend); black screen when turning on the Samsung Odyssey G5 until the on-screen menu button is pressed; output drop to all displays when switching input on an LG C9 TV until forced reboot; accidental driver crashes in a configuration of two DisplayPort + HDMI monitors (RTX 5060 Ti); broken HDR and VRR on Apple Studio Display XDR; loading the second monitor in low resolution – the problem stretches back to the 591.86 driver.
  • Shadow artifacts: flickering and shifting of vegetation shadows in Elden Ring (observed from branch 581); flickering of distant shadows in Wuthering Waves and Horizon Zero Dawn Remastered – defect appeared in 610.74, missing at 610.62.
  • Laptops: modern Standby Deep Sleep State (DRIPS) freezes when Windows Quick Start is enabled; The author of the detailed report associates the problem with the PowerSettings parameters in the registry that the NVIDIA High Definition Audio driver prescribes – removing them eliminates the freeze.
  • Other: for one user, the RTX 5060 Ti was no longer determined by the system after the driver was installed; automatic overclocking in NVIDIA App is reset after each reboot.
Click to expand...
There is a reason why a studio version isn't out for this version. Always pay attention to this, if Studio isn't out around the same time, then the GRD is bugged, as always seems to be the case now.
 
That's exactly why I ended up sticking with Studio for my laptop and backup desktop. They're a little behind the latest optimisations, but they have broadly always been stable, as long as there isn't a major drive path issue.
 
mrk said:
There is a reason why a studio version isn't out for this version. Always pay attention to this, if Studio isn't out around the same time, then the GRD is bugged, as always seems to be the case now.
Click to expand...

I've had no issues with the latest drivers whereas I did awhile ago. I only ever use NVCleanInstall and don't use the app either.

But seems to be plaguing the 5X series cards
 
Clean install is not really needed any more nor DDU etc as the NV installer has been doing correct housekeeping for many years now - That side of things has been well sorted for a long time tbh.

Yeah seems 50 series mainly affected, typical :p

Either way, Studio always! I have yet to see a noticeable optimisations gain in a latest game release by using the latest GRD over the previous Studio either. Sometimes I think NV just release them to jump on the game release bandwagon. You can enforce the latest DLSS model in older drivers anyway via NVApp or one of the multiple other methods.
 
Last edited:
If we only buy games on steam sale, or other store front sale, is there ever a reason NOT to use studio drivers?
Edit: or in other words, does this make GRD obsolete?
 
Last edited:
Not seen a recent game release alongside GRD pave any benefit of using GRD over the then active Studio driver. All the game features still exist in Studio, and you can just use manual override to get DLSS 4.5 anyway if needed.

So yeah may as well just stick to Studio. Nvidia never actually state what optimisations are made for a game release either, I assume they are nothing of any note given the framerates between GRD and Studio remain the same, and both support DLSS 4.5 anyway so the image is going to be the same as well.
 
that's what I thought too, but then I remember watching digital foundry videos where they mention shader compilation stutters in UE5 games.... I think
 
That's unrelated to drivers, that is/was an issue in UE5 and not enough shaders being precompiled.
 
mrk said:
Clean install is not really needed any more nor DDU etc as the NV installer has been doing correct housekeeping for many years now - That side of things has been well sorted for a long time tbh.
Click to expand...

Well I don't need any of that telemetry and NVAPP required rubbish. So I end up only installing Driver ( core ) via nvcleaninstall .

Haven't used DDU for awhile now
 
You must log in or register to reply here.
Back
Top Bottom