Drivers 3072 Published by

NVIDIA released the GeForce/RTX Spark Hotfix Driver 621.12 on October 27, 2026, a rapid-response patch aimed squarely at a video-freeze and black-screen regression introduced by driver 621.01 three days earlier. The hotfix addresses four issues total: the headline video bug affecting RTX 50-series GPUs, an Unreal Engine 5.8 crash, RTX Spark display corruption through a StarTech Thunderbolt adapter, and flickering on the MSI Prestige N16 Flip. It ships as optional beta software that is not WHQL-certified and is available only through NVIDIA's Customer Care site. Users who aren't affected by any of the four issues can safely skip it, though those hit by the freeze may prefer the hotfix over rolling back to 617.42 since it keeps Advanced Shader Delivery support intact.





NVIDIA Ships a Six-Day Hotfix to Plug a Video Bug It Introduced

NVIDIA's GeForce/RTX Spark Hotfix Driver 621.12 arrived six days after driver 621.01 stopped video playback from working on a pile of RTX 50-systems.

On October 27, NVIDIA published the GeForce/RTX Spark Hotfix Display Driver, version 621.12. It's not a new driver branch. It's not a feature drop. It's a targeted patch layered on top of the Game Ready Driver NVIDIA shipped three days earlier. And in practice, it exists almost entirely because that earlier driver, 621.01, broke video playback on a number of systems.

Hotfixes are NVIDIA's emergency lane. They skip much of the normal QA gauntlet, ship as optional beta software "as-is," and vanish once their fixes land in the next official release. This one is a textbook case of the system working the way it was designed.

Nvidia

The four fixes

The headline item, logged as bug 6979343, resolves the exact regression NVIDIA introduced. After updating to 621.01, video playback in Google Chrome, Microsoft Edge, and VLC could freeze or blank the screen for several seconds on some RTX 50-series GPUs and RTX Spark systems. The display then recovers on its own, no reboot required.

NVIDIA acknowledged the problem around October 24 and filed a bug report before shipping this fix. In the interim, users were rolling back. The community-proven fallback is GeForce driver 617.42 from October 6, and plenty of people say it kills the freezes entirely. That's strong evidence this was a driver regression and not failing hardware.

The other three fixes are more scattered. Bug 6914378 stops Unreal Engine 5.8 from crashing when Ray Lighting Mode is set to Hit Lighting. This one doesn't care about your GPU generation, it hits RTX cards beyond Blackwell, per OC3D, so it matters mainly to developers.

Then there are the RTX Spark quirks. Bug 6054761 addresses display corruption when an HDMI monitor is routed through a StarTech Thunderbolt 3 to HDMI 2.0 adapter. And bug 6945359 covers intermittent flickering on the MSI Prestige N16 Flip AI+, that convertible with a Tandem OLED panel. If you're not running an ARM-based laptop with a third-party Thunderbolt bridge, two of these three won't touch your life at all.

Three of these four are specific to platforms and peripherals most readers will never own. The video bug is the only one that bites broadly.

Why 621.01 broke things

The 621.01 driver, which shipped October 21, did two big things at once. It moved NVIDIA onto its new R620 driver branch, a deep codebase switch where regressions love to hide. And it added support for Microsoft's Advanced Shader Delivery (ASD), which offloads shader compilation to the cloud to speed up game launches. Both sound like wins. One of them apparently broke video decoding.

Symptom-wise, the reports were loud and consistent. Some users saw LiveKernelEvents indicating GPU timeout-and-recovery, meaning Windows was resetting the driver underneath whatever you were running. Most reports came from RTX 5080 owners, often on dual or triple-monitor setups, though an RTX 4090 user hit it too. NVIDIA framed the bug as affecting "some" RTX 50-series GPUs, which reads like it isn't confined to a single SKU.

The ugliest part is the screen-sharing angle. Launch a game while a video is already playing in the background and the driver can trip. A background YouTube blanking your game display is a near-universal pain point on modern multi-monitor rigs, and it's exactly the kind of thing that makes people furious fast.

What you should do

You don't have to install 621.12 just because the number is newer. NVIDIA's own words on the matter: hotfix drivers are "beta, optional and provided as-is," and "the safest option is to wait for the next WHQL certified driver." If none of the four issues applies to your setup, skip it and wait.

If you're stuck on the video freeze, your choices are to apply the hotfix or roll back to 617.42. Fair warning on the tradeoff: rolling back means losing Advanced Shader Delivery support. The hotfix keeps ASD working, which tips the balance for most people. For either path, run Display Driver Uninstaller first to strip the current driver, then install clean. Grab the GeForce build for standard x64 Windows, and the RTX Spark build only if you're on Windows on ARM64.

Both packages live exclusively on NVIDIA's Customer Care site. It's a bit of a gamble to install beta software on a bug-free system, but if the freeze is biting you, the fix arrives well before 621.01 would otherwise be superseded. Six days from bug report to patch is a fast turnaround, and it's the hotfix program doing exactly what it exists to do.