What NVIDIA has confirmed
Driver 621.01 is a WHQL release for 64-bit Windows 10 and Windows 11. GameGPU reported that it shipped on October 21, 2026 and that the installation file size is 1,04 GB. VideoCardz reports that users report that video playback in web browsers and media players can cause the display to freeze or temporarily go black. NVIDIA has registered the problem as a bug and is collecting additional diagnostic information.
The response came in NVIDIA's official 621.01 feedback thread. NVIDIA representative Manuel confirmed that the company had filed a bug report. The company requested watchdog crash dumps from affected users to investigate the freezes. NVIDIA has not announced when a fix will become available. EJS Computers dates that reply to October 23.
A filed bug and a request for dumps means the investigation has started. It does not tell you the root cause, which hardware is affected, or when a hotfix will arrive.
Summary: NVIDIA has acknowledged the bug and is investigating. There's no fix or date yet.
The symptoms
The reports first collected by the Japanese site GAZLOG follow a consistent pattern:
- Where it happens: users describe freezes while watching videos in Chrome, Edge and VLC.
- One trigger: In some cases, launching a game while a browser video is playing triggers the problem.
- Recovery: The display typically recovers after several seconds without requiring a system restart.
That brief blackout followed by recovery fits Windows Timeout Detection and Recovery (TDR), and EJS Computers says the same. When the GPU stops responding for about two seconds, Windows resets the display driver instead of letting the whole system hang. The black screen is annoying, but it is Windows recovering, not the PC dying. EJS also notes that nothing in the reports suggests hardware damage.
Which cards are affected?
NVIDIA hasn't said. Several reports involve GeForce RTX 5080 graphics cards, although an RTX 4090 user has also described similar behavior. EJS adds that GAZLOG found some of the RTX 5080 systems were running two or three monitors, and that NVIDIA has published no list of affected models.
These are anecdotes, not a compatibility matrix. A cluster of RTX 5080 reports could reflect that card's owners being active on forums as easily as a card-specific defect. Owners of other GeForce cards shouldn't assume they're safe, and RTX 5080 owners shouldn't assume they're affected.
How to check your own PC
Event Viewer gives you the most useful clues:
- Open Event Viewer.
- Go to Windows Logs > System.
- Look for errors with Event ID 153 where the Source is nvlddmkm, NVIDIA's kernel display driver.
- Check whether the timestamps match the freezes.
VideoCardz notes that affected systems sometimes record Event ID 153 associated with the nvlddmkm driver. One user also reported Windows LiveKernelEvent 141 and 117 errors, which indicate GPU timeout and recovery events.
Check the Source column carefully. EJS warns that an Event ID 153 from "disk" is a different problem related to a storage drive. Event IDs are only unique within their source.
Not every Event 153 is this bug
The 621.01 feedback thread shows that nvlddmkm Event 153 errors have more than one cause. One RTX 5070 Ti owner describes black screens with Netflix (PlayReady SL3000 hardware DRM) + multi-monitor and lists Drivers 610.88, 616.92, 617.42, 621.01 as tested with the problem still happening. Another user in the same thread logged nvlddmkm 153 on an RTX 5080 while watching YouTube. That user said even going back to 617.14 and still happening.
These reports haven't been verified. Still, they show that "video plus black screen plus Event 153" isn't proof of the 621.01 regression. Some similar problems clearly predate this driver. As TweakTown puts it, NVIDIA's release notes for driver 621.01 list no open issues, and the user reports cover a wide range of other complaints too.
Here's a practical test. If the freezes started right after you installed 621.01 and stop when you go back to 617.42, your case fits the reported pattern. If they continue on 617.42, look for another cause, such as multi-monitor setups, DRM-protected playback, or your display hardware.
Summary: Event 153 from nvlddmkm is a clue, not a diagnosis. A rollback is the best test.
The workaround: roll back to 617.42
Multiple users report that reverting to GeForce 617.42, released on October 6, resolves the video playback freezes. This suggests a regression introduced with 621.01, which belongs to NVIDIA's newer R620 driver branch. VideoCardz adds that the exact cause hasn't been confirmed. This fix comes from users, not from NVIDIA.
EJS Computers describes two ways to do it.
Option 1: Device Manager rollback (quickest)
- Open Device Manager.
- Expand Display adapters.
- Right-click your NVIDIA card and select Properties.
- On the Driver tab, click Roll Back Driver.
- Restart the PC.
It worked if Device Manager or the NVIDIA Control Panel shows the previous driver version and video plays without the freezes.
Option 2: Clean install of 617.42 (if Roll Back is grayed out)
The Roll Back button is often grayed out after a clean install, because Windows has no previous driver package saved.
- Download driver 617.42 for your GPU from NVIDIA's driver site.
- Run the installer and select Custom (Advanced).
- Check Perform a clean installation.
- Finish the install and restart.
Option 3: The thorough route with DDU
EJS passes on GAZLOG's suggestion to remove 621.01 completely with Display Driver Uninstaller (DDU) and then install 617.42. This is a community tool, not an NVIDIA method. It's more involved, so it's best kept for when the simpler options don't work.
Don't let 621.01 come back
EJS warns that the NVIDIA app and Windows Update may offer 621.01 again. Skip it until a newer driver lists this fix. Rolling back and then clicking "Update" an hour later puts you right back where you started.
Staying on 621.01: one thing to try
If you want to keep the new driver, EJS cites Windows Digitals' suggestion to turn off hardware (graphics) acceleration in your browser. Nobody has confirmed that this fixes the bug, so treat it as an experiment. It would also do nothing for VLC, which appears in the reports, and turning off acceleration moves more video decoding onto the CPU, which can mean higher CPU use on high-resolution streams. That last point comes from general industry knowledge, not from these reports.
What you lose by rolling back
621.01 is a Game Ready release. GameGPU reports that it covers Phantom Blade Zero, Call of Duty: Modern Warfare 4, NBA 2K27, Cyberpunk 2077 ?? Crimson Desert Enhanced: Charting the Unknown. TweakTown notes that it also brings Advanced Shader Delivery for Modern Warfare 4 and Gears of War: E-Day.
EJS points out that, according to GAZLOG, Modern Warfare 4 was already optimized in 617.42. Rolling back mainly costs you Advanced Shader Delivery and the Game Ready profiles for Phantom Blade Zero (October 28) and Crimson Desert Enhanced (October 29). If you're playing either of those at launch, weigh that against the video freezes.
The release also contains fixes. Guru3D lists fixes for occasional black flashes during gameplay on QHD monitors operating at 360 Hz, and frame rates dropping to 320 FPS on 360 Hz G-SYNC Pulsar monitors. The driver also resolves freezing in Meta Horizon Link streams connected over USB. If you own one of those setups, rolling back brings those problems back. Don't confuse the 360 Hz black-flash fix with the playback bug, which is a separate, newly reported issue.
Other 621.01 reports
EJS cites two more problems from GAZLOG's roundup:
- 480 Hz G-SYNC monitors: some users see a black screen every 10 to 15 seconds, and dropping to 360 Hz makes it stable.
- No picture at boot or after sleep: some RTX 40 and RTX 50 owners report this. It goes back to driver 616.56 and also happens on 617.42. Users say returning to 610.88, released July 28, avoids it.
Wider community complaints include stuttering with G-SYNC/VRR enabled in certain games, and mVolt+ voltage limit issues. None of these have been confirmed by NVIDIA in the way the playback bug has, and TweakTown notes that experiences on Guru3D's forums vary from user to user.
How long might a fix take?
There's a recent precedent, but it doesn't predict this one. EJS notes, citing GAZLOG, that when a similar display issue hit driver 616.56, NVIDIA was already testing a fix on September 1 and shipped Hotfix 616.86 on September 4. This time the bug has only been registered, with no reported fix in testing, so EJS suggests it may take longer. Nobody outside NVIDIA knows the timeline.
The bottom line for Windows gamers
EJS describes this as a software bug, not a hardware failure. The evidence so far points to the driver, but "software bug" doesn't explain every black screen on every PC. If your symptoms don't match, keep troubleshooting before blaming 621.01. Don't replace a working graphics card over this either.
A sensible plan:
- Confirm the pattern: freezes during video playback, starting after the 621.01 install, with nvlddmkm Event 153 entries.
- Roll back to 617.42 using Device Manager or a clean install.
- Block the reinstall by skipping 621.01 in the NVIDIA app and watching Windows Update.
- Help NVIDIA if you're comfortable doing it. The company asked for watchdog dumps in its 621.01 feedback thread.
- Wait for release notes that name this fix before updating again.
If you're seeing this bug, tell us your GPU, how many monitors you run, and whether 617.42 fixed it. Those details help other readers, and they help NVIDIA's investigation too.
Update: Hotfix 621.12 targets the video-playback freezes (October 27, 2026)
NVIDIA has reportedly released hotfix driver 621.12 to address video freezes and black screens introduced by 621.01 on some GeForce RTX 50-series GPUs and RTX Spark systems, according to MIXED News on October 27. This supersedes our earlier statement that no fix was available: affected users now have a targeted hotfix to try rather than relying solely on a rollback.
According to MIXED News, NVIDIA describes 621.12 as an optional beta with a shorter testing process than a regular driver release. The outlet reports that NVIDIA considers waiting for the next WHQL-certified driver the safest option, and that these fixes will also enter the next official release. Users whose systems are unaffected therefore have no immediate reason to install the beta.
MIXED News reports that NVIDIA provides separate downloads: GeForce packages for Windows 10 and Windows 11 on x64 PCs, and an RTX Spark package for Windows 11 on ARM64. Match the package to your system. The reported video-playback fix specifically names RTX 50-series GPUs and RTX Spark; it does not establish that similar symptoms reported on RTX 40-series cards are resolved.
References
- Nvidia fixes RTX 50 video freezes and black screens with hotfix 621.12 - MIXED News MIXED News · 2026-10-27T17:54:48+00:00
- NVIDIA 621.01 Black Screens? What to Do Until the Fix - EJS Computers EJS Computers · 2026-10-24T11:17:10+00:00
- NVIDIA confirms GeForce 621.01 driver bug causing video freezes and black screens - VideoCardz.com VideoCardz.com · 2026-10-24T07:45:28+00:00