NVIDIA's latest Game Ready Driver (version 621.01), released on October 21, 2026, has several confirmed bugs. It marks the debut of NVIDIA's new R620 driver branch and has introduced stability issues across different setups. [1, 2]
The primary reported problems include:
Video Playback Freezes & Black Screens
An official bug report has been filed by NVIDIA regarding system freezes and temporary black screens during video playback. [1, 2]
HDMI Detection Issues: Users have reported HDMI display detection failures, specifically on the RTX 5070 Ti, where the card completely fails to recognize secondary or primary displays over HDMI.
Stuttering with Frame Generation & V-Sync
Users across the official forums are reporting heavy microstuttering when attempting to use DLSS Frame Generation concurrently with Global V-Sync settings
How to Fix It
Because NVIDIA is still collecting crash logs and has not yet deployed a hotfix, the community consensus is to roll back to the previous stable release
The primary reported problems include:
An official bug report has been filed by NVIDIA regarding system freezes and temporary black screens during video playback. [1, 2]
- The Trigger: Watching videos using Google Chrome, Microsoft Edge, or VLC Media Player.
- The Behavior: The display may freeze entirely or cut to a black screen for a few seconds before recovering. This is frequently triggered when launching a game while a browser video is active in the background.
- Affected Cards: Heavily reported by RTX 5080 and RTX 4090 users, frequently resulting in nvlddmkm Event ID 153 crashes and GPU timeout errors.
HDMI Detection Issues: Users have reported HDMI display detection failures, specifically on the RTX 5070 Ti, where the card completely fails to recognize secondary or primary displays over HDMI.
Stuttering with Frame Generation & V-Sync
Users across the official forums are reporting heavy microstuttering when attempting to use DLSS Frame Generation concurrently with Global V-Sync settings
How to Fix It
Because NVIDIA is still collecting crash logs and has not yet deployed a hotfix, the community consensus is to roll back to the previous stable release
