Eight bugs. That’s how many issues NVIDIA’s hotfix driver 610.52 addresses from the 610.47 Game Ready Driver, which shipped on May 26, 2026 with a broken G-Sync implementation on every Ada (RTX 40 series) GPU. The G-Sync frame pacing bug alone caused framerate swings from 60 to 240 fps on systems that previously held a locked 240, and Smooth Motion crashed DirectX 11 titles on launch. NVIDIA acknowledged the problems and released hotfix 610.52 on June 8, but not every affected user should install it.
If you dealt with the R595 series driver problems earlier this year, the 610 branch brings a fresh set of issues. This guide covers what 610.47 broke, what the hotfix actually repairs, when rolling back to 596.49 is the smarter move, and how to do a clean driver swap with DDU.
What 610.47 Broke
The 610.47 Game Ready Driver introduced at least five distinct issues affecting RTX 40 and RTX 50 series GPUs. The problems appeared immediately after installation and persisted across reboots, settings resets, and Windows updates.
G-Sync frame pacing on Ada GPUs. The most visible problem. With G-Sync enabled, the monitor’s refresh rate stopped tracking the actual framerate and instead jumped to its maximum, producing severe stuttering. Users on the NVIDIA GeForce Forums reported frame pacing so erratic that games became unplayable even at high average framerates. NVIDIA employee Manuel confirmed the bug in the official feedback thread. Driver 595.97 (late March 2026) was the last version where G-Sync worked correctly before the 610 branch.
Smooth Motion crashes and ghosting. Smooth Motion, NVIDIA’s frame interpolation feature for non-DLSS games, broke in two ways. First, some DirectX 11 games crashed to desktop immediately when Smooth Motion was enabled. Second, games that did launch with Smooth Motion active showed visible ghosting and jittering artifacts. DSO Gaming confirmed both issues affected multiple titles across different hardware configurations.
V-Sync plus DLSS Frame Generation instability. Multi-monitor setups running V-Sync with DLSS Frame Generation experienced intermittent crashes and screen flickering. The problem appeared when CPU or GPU starvation events triggered Frame Generation to fall behind, causing visible corruption until the starvation ended.
Monitor EDID and sleep failures. Some monitors stopped being recognized after the driver update, appearing as “NVIDIA NV-Failsafe” in display settings. Others failed to wake from sleep mode entirely, requiring a hard reboot to restore the display.
World of Warcraft stability. WoW players saw increased crash frequency, particularly on DirectX 12 with certain GPU and monitor combinations.
Which GPUs and Games Got Hit Hardest
The G-Sync frame pacing bug targeted Ada architecture (RTX 40 series) GPUs specifically. Community reports from NeoGAF and the NVIDIA forums identified the RTX 4090, 4080 Super, and 4070 as the most frequently affected models. RTX 50 series (Blackwell) users were less affected by the G-Sync issue, though Smooth Motion problems hit both generations.
Games with confirmed severe performance degradation on 610.47:
| Game | Problem | Severity |
|---|---|---|
| Doom Eternal | Frame swings 60 to 240 fps on a system locked at 240 before | Critical |
| Forza Horizon 6 | Flickering, stuttering, FPS from over 100 to below 30 | Critical |
| Rocket League | Constant stutter with G-Sync enabled | High |
| Crimson Desert | Jittering, erratic fan behavior, temperature spikes | High |
| Horizon Forbidden West | 30 to 50% FPS drop with ReBAR enabled | High |
| Horizon Zero Dawn Remastered | 30 to 50% FPS drop with ReBAR enabled | High |
| World of Warcraft | Increased crash frequency on DX12 | Moderate |
| Subnautica (2018) | Failed to launch; stuck on white screen | Moderate |
The Horizon titles deserve a note: the FPS drops only occurred with Resizable BAR (ReBAR) enabled. Disabling ReBAR in BIOS or NVIDIA Control Panel restored normal performance on those games while running 610.47.
What Hotfix 610.52 Actually Fixes
NVIDIA released hotfix 610.52 on June 8, 2026. The official fix list covers eight items:
- G-Sync frame pacing on Ada GPUs (the headline fix)
- Smooth Motion DX11 ghosting and jittering
- Smooth Motion game crashes on launch
- Monitor EDID detection (NV-Failsafe labeling)
- Monitor wake from sleep
- V-Sync plus DLSS Frame Generation stability in multi-monitor setups
- World of Warcraft stability improvements
- Memory allocation failures (general stability)
Early community feedback on the guru3D forums and Forza Horizon 6 Steam threads suggests the G-Sync fix works for most RTX 40 series users. The Smooth Motion fixes also appear effective, with users confirming DX11 titles launch correctly again.
Two things the hotfix does not address: the voltage behavior issues inherited from the 595 driver branch (relevant to overclockers) and the ReBAR performance regression in the Horizon titles. If those affect you, the hotfix alone is not enough.
610.52 is also not a WHQL-certified driver. NVIDIA classifies it as an optional hotfix, meaning it has not gone through Microsoft’s full driver certification process. For most gamers that distinction does not matter in practice, but enterprise environments or users who only install certified drivers should wait for the next official Game Ready release.
Sorting out your GPU driver is only half the equation if your online matches still spike. WTFast reroutes game traffic through optimized servers to cut the network side of the problem.
Driver sorted, but your ping still spikes in matches?
WTFast routes your game traffic through dedicated servers, cutting ping by 30 to 50% for most players.
610.52 or 596.49: Which One to Install
The answer depends on your hardware and which features you use.
Install 610.52 if:
- You run G-Sync on an RTX 40 series card and want to stay on the latest branch
- You use Smooth Motion in DX11 games
- You run multi-monitor with V-Sync and DLSS Frame Generation
- Your monitor had EDID or sleep/wake issues on 610.47
Roll back to 596.49 if:
- 610.52 still stutters on your specific monitor and GPU combination (some edge cases remain, particularly the ASUS PG27UCDM)
- You overclock your GPU (voltage behavior from the 595 branch carries into 610)
- You play Horizon Forbidden West or Horizon Zero Dawn Remastered with ReBAR enabled
- You prefer WHQL-certified drivers only
- You do not use G-Sync or Smooth Motion and want proven stability
596.49 is the community’s consensus “known good” driver for the RTX 40 series right now. It shipped without the G-Sync, Smooth Motion, or monitor detection bugs. If you do not need anything specific from the 610 branch, 596.49 is the safer choice.
For RTX 50 series owners, 610.52 is generally the better option. The 596 branch had its own issues on Blackwell GPUs, and early reports indicate 610.52 runs cleaner on RTX 5070 and 5080 hardware.
Clean Driver Swap With DDU
Whether you are installing the hotfix over a broken 610.47 or rolling back to 596.49, a clean install through DDU (Display Driver Uninstaller) prevents leftover files from causing persistent issues. The current version is 18.1.5.4.
Before you start: Download both DDU and your target driver (596.49 or 610.52) to a folder on your desktop. You will need them available offline.
For a deeper look at how outdated or corrupted drivers cause gaming issues, see our GPU driver update guide.
Step 1: Boot into Safe Mode. Open Settings, then System, then Recovery, then Advanced Startup, then click Restart Now. In the recovery menu, select Troubleshoot, then Advanced Options, then Startup Settings, then Restart. Press 4 or F4 for Safe Mode.
Windows 11 24H2 note: your PIN may not work in Safe Mode. Before rebooting, go to Settings, then Accounts, then Sign-in Options, and disable “For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device.” You will need your Microsoft account password instead.
Step 2: Run DDU. Right-click Display Driver Uninstaller.exe, select Run as Administrator. Set Device Type to GPU and select NVIDIA. Click “Clean and Restart.” DDU will remove all NVIDIA driver files, registry entries, shader cache, and scheduled tasks.
Step 3: Install the target driver. After the restart, disconnect from the internet before Windows can automatically download a generic driver. Run the NVIDIA installer for your chosen driver version. Select “Custom (Advanced)” and check “Perform a clean installation.”
Step 4: Reconnect and verify. Re-enable your internet connection. Open NVIDIA Control Panel and confirm the driver version under System Information (bottom left). If you use G-Sync, open “Set up G-SYNC” and verify the checkbox is active and your monitor is detected at the correct refresh rate.
The full DDU process takes about 10 minutes, including the two reboots. It is worth the time. “Express” driver installs over a broken driver frequently leave corrupted shader cache or registry entries that cause the same stuttering to persist.
Post-Install Settings to Verify
After any driver change, three settings catch the most common leftover problems.
Shader cache. Open NVIDIA Control Panel, then Manage 3D Settings. Find “Shader Cache Size” and set it to “Driver Default” (or 10 GB if you have the SSD space). The shader cache from the previous driver is invalid after a DDU wipe; the first launch of each game will recompile shaders, which can cause brief one-time stuttering. That is normal and will not recur after the initial compile.
ReBAR (Resizable BAR). If you play Horizon Forbidden West or Horizon Zero Dawn Remastered and experience 30 to 50% FPS loss, disable ReBAR in your BIOS. This is a known issue on the 610 branch that the hotfix did not address. Other games benefit from ReBAR being on, so toggle it per game if your BIOS supports profiles.
G-Sync and refresh rate. In NVIDIA Control Panel, open “Set up G-SYNC” and confirm it shows your monitor’s full VRR range. Then open “Change Resolution” and verify the refresh rate matches your monitor’s native maximum. After the 610.47 bug, some users reported their refresh rate got locked to 60 Hz even after the hotfix.
While you are resetting your environment, close unnecessary background processes that kill FPS before launching your first test game.
Once your driver is clean and your settings are verified, the only remaining lag source in online games is the network path between you and your game server. That is exactly where a routing optimizer makes the biggest difference.
Clean driver, verified settings, still lagging online?
WTFast’s gaming network bypasses congested ISP routes between you and your game server.
NVIDIA’s Driver Quality in 2026
The 610.47 situation is not an isolated incident. The RTX 50 series launch era has been rough: driver 591.76 caused FPS drops on RTX 40 series cards in January, 595.59 broke overclocked GPUs with a 16% performance penalty, and now 610.47 shipped with broken G-Sync. XDA Developers documented the pattern in March 2026, noting that driver quality has declined as NVIDIA pushes frequent updates to support new game launches.
The practical takeaway: do not install new Game Ready Drivers on day one. Wait 48 to 72 hours and check the feedback thread on the NVIDIA GeForce Forums before updating. Keep one known-good driver installer (right now, 596.49) saved locally so you can roll back without needing an internet connection. And if a hotfix drops within two weeks of a Game Ready release, that alone tells you the original release had serious problems.
Your GPU hardware is fine. The silicon has not changed. The driver sitting between your GPU and your games is what determines whether you get smooth frames or a stutter mess, and right now the safest move is to stay one version behind until NVIDIA’s quality control catches up. If your Windows 11 settings are already optimized and your driver is clean, you have done everything on your end. The rest is on NVIDIA.