Nvidia Confirms Black Screen Bug in Latest Game Ready Driver
Nvidia has officially acknowledged a disruptive bug plaguing the recently released GeForce Game Ready Driver 621.01. Countless users recently reported abrupt screen freezes and fleeting black screens. These frustrating anomalies primarily occur while streaming video content through web browsers like Google Chrome and Microsoft Edge. Furthermore, localized media players, including VLC, also trigger the exact same display malfunctions.
Fortunately, the affected screens typically restore themselves to normal functionality after merely a few seconds. Nvidia actively recognized this widespread predicament and currently gathers crash dump files from impacted individuals. This crucial data collection will help engineers investigate the underlying architectural causes.
Video Playback Triggers System Freezes
Several affected users indicated that these erratic behaviors manifest almost exclusively during active video playback. Under certain specific circumstances, launching a demanding video game while simultaneously streaming a browser video aggressively provokes the glitch. Once the visual disruption strikes, the graphical interface usually recovers autonomously within moments. Consequently, victims do not need to endure a full system reboot.
Currently, numerous RTX 5080 owners have formally reported enduring this specific graphical instability. Additionally, a notable contingent of RTX 4090 enthusiasts has echoed shockingly similar complaints across official support channels.
Diagnostic Errors and Temporary Solutions
System diagnostic tools reveal fascinating technical details regarding this failure. The Windows Event Viewer on compromised systems frequently displays Event ID 153. This specific error code correlates directly with the Nvidia display driver component known as nvlddmkm. Moreover, other frustrated operators documented Windows LiveKernelEvent 141 and 117 errors. These critical diagnostic records inherently relate to catastrophic GPU timeouts and subsequent driver crash recoveries.
According to GAZlog and widespread discussions found within the official Nvidia community feedback thread, a temporary solution exists. Rolling back the system software to the older GeForce 617.42 driver gracefully circumvents the problem. Nvidia originally published that highly stable software iteration on October 6. Nevertheless, the definitive technical catalyst triggering this bizarre phenomenon remains unconfirmed by Nvidia engineers.
