NVIDIA Just Dropped an Emergency Driver After GeForce Users Started Complaining

NVIDIA has released an out-of-band hotfix driver, GeForce 610.52, aimed at fixing bugs that appeared for users after installing the previous Game Ready 610.47 package. The update isn't WHQL-certified, is being distributed through support channels, and is intended only for those experiencing specific issues.

The release notes list eight major fixes. Some of them affect RTX 4000 series card owners. The developers have restored frame pacing when G-Sync is active — previously, some monitors would suffer from micro-stutters. They've also fixed a bug where certain displays wouldn't read their extended EDID data and would be detected by the system as "NVIDIA NV-Failsafe," breaking proper resolution and refresh rate behavior.

A separate batch of fixes targets multi-monitor setups. In scenarios where V-Sync and DLSS Frame Generation were both enabled, games could crash. Additionally, they've resolved an issue with monitors waking from sleep, where some models simply wouldn't come back on after being idle for a while.

World of Warcraft players get a patch that eliminates crashes that were happening during various in-game actions. For Smooth Motion, two defects have been fixed: the first showed up as flickering or double imaging in some DirectX 11 titles, and the second would instantly crash the game on launch if Smooth Motion was pre-enabled. The overall list also includes improved stability in situations where the system failed to allocate a new memory block.

Download GeForce Hotfix Display Driver 610.52 from NVIDIA's support site. The full list of fixes with internal tracking numbers is also posted there. No automatic updates through GeForce Experience for this version — installation is manual only. This isn't the first time a stopgap driver has addressed issues with DLSS Frame Generation and G-Sync when paired with multiple displays. The next major Game Ready update will likely include all accumulated fixes in full and return to the normal certification cycle.

Have you run into any of the issues described above after updating to 610.47? Have you already installed the hotfix? Share your experience in the comments.