S-GAME told Phantom Blade Zero players to roll back their Nvidia drivers. Here's why that matters
The rollback advice landed in the middle of a documented 621.01 bug run, a hotfix that traded away Advanced Shader Delivery, and a proper WHQL driver that only showed up on November 4.
Phantom Blade Zero launched on October 28 into a strange situation. NVIDIA had shipped a Game Ready driver for the game six days earlier, and the studio that made the game spent part of launch day telling players to get off it.
The advice, in S-GAME's own words
The recommendation sits at the end of a launch letter titled "Reason and Madness", posted on the game's Steam news page on October 28 and signed by creative director and CEO Soulframe Liang. The driver note reads:
We've observed some performance instability with NVIDIA's latest 621.01 driver. Based on our testing, version 617.42 currently offers the best experience in Phantom Blade Zero. If you've installed a driver newer than 617.42, we recommend rolling back to 617.42 and choosing the clean installation option. Please stay on this version until NVIDIA releases its next driver update, which we expect to arrive soon.
Three limits sit around that statement. It applies to GeForce drivers only; the studio's guidance for AMD and Intel owners is simply the latest release. S-GAME never described what the instability looked like, which cards it hit, or how wide the gap was, and no independent measurements have appeared either way. The wording also covers every driver newer than 617.42, which matters later, because NVIDIA shipped two more builds in the following two weeks.
A developer steering players away from the official Game Ready driver for its own launch is rare. The launch was big enough that the advice reached a lot of people: trackers logged day-one Steam concurrent peaks of roughly 723,000 (SteamDB), with later sampling climbing to 823,104 (SteamCharts).
What 621.01 broke
Driver 621.01 arrived on October 21 as a WHQL Game Ready release for Phantom Blade Zero, Call of Duty: Modern Warfare 4, NBA 2K27, Cyberpunk 2077 and the Crimson Desert Enhanced update. It was also the first build on NVIDIA's new R620 branch and the first with Advanced Shader Delivery, a feature that lets supported games install precompiled shader files instead of compiling everything on your PC.
Within days, NVIDIA's official feedback thread filled with reports that had little to do with game performance. The pattern, as collected by Igor's Lab, hwbusters, ComputerBase and WinFuture:
- Video playback freezing in Chrome, Edge, VLC or Twitch, sometimes followed by a black screen that lasts a few seconds and recovers on its own
- nvlddmkm Event ID 153 entries in the Windows Event Viewer, often alongside LiveKernelEvent 141 or 117, the signatures of Windows resetting an unresponsive graphics driver
- Micro-stutter with G-SYNC enabled; one report describes a 480 Hz G-SYNC monitor dropping the picture every 10 to 15 seconds, stable at 360 Hz
- A missing DLSS Frame Generation Preset C profile, and "Prefer Maximum Performance" failing to hold high clocks on some systems
- Black screens at boot or when waking from sleep
Most reports came from RTX 5080 owners, with RTX 4090 users describing the same class of problem, and multi-monitor setups overrepresented. One RTX 5080 owner logged six driver interruptions in about 24 hours during light video playback. NVIDIA confirmed a bug report was filed and asked affected users to submit watchdog dumps from C:\Windows\LiveKernelReports\WATCHDOG. Players who rolled back to 617.42, the October 6 release, reported that the playback failures stopped.
None of these symptoms map exactly onto the "performance instability" S-GAME described, and NVIDIA never published a cause. The overlap is enough, though, to see why a studio shipping a demanding action game that week would prefer its players on the older, quieter branch.
The hotfix that traded away Advanced Shader Delivery
NVIDIA posted hotfix driver 621.12 on October 27, one day before the game unlocked. It fixed four issues from 621.01: video playback freezes and black screens on RTX 50 series and RTX Spark GPUs, a crash in Unreal Engine 5.8 when Ray Lighting Mode was set to Hit Lightning, HDMI corruption through a StarTech Thunderbolt 3 to HDMI 2.0 adapter on RTX Spark devices, and flickering on the MSI N16 Flip.
Two things made the hotfix a poor answer for Phantom Blade Zero players. The fix list never mentioned the game. And because hotfix drivers ship with attestation signing rather than WHQL certification, 621.12 dropped Advanced Shader Delivery, which requires WHQL identities and metadata profiles to function. TweakTown flagged that trade at the time. The G-SYNC stutter, Event ID 153 entries, missing Preset C and broken Prefer Maximum Performance reports from 621.01 stayed open.
The driver S-GAME was waiting for
NVIDIA released Game Ready 621.14 on November 4, a full WHQL build aimed at World of Warcraft: Forever, with optimizations for Doom: The Dark Ages' new Slaughter Mode and DLSS 5 support for Hogwarts Legacy and War Thunder. Its fix list covers the RTX 50 video playback freeze and black screen (issue 6979343) and incorrect colors in Modern Warfare 4 (issue 6972531).
That satisfies the condition in S-GAME's letter: "until NVIDIA releases its next driver update." The 621.14 release notes do not re-list every hotfix item, so the status of the G-SYNC stutter and the other forum-reported issues on the new build is unclear from the notes alone. We have not seen an updated statement from S-GAME about 621.14 as of November 6. Read the original advice as expiring on its own terms, with the studio's tested recommendation still pointing at 617.42.
If you still want 617.42
Rolling back is straightforward. Download 617.42 from NVIDIA's driver archive, run the installer, choose Custom (Advanced) and tick Perform a clean installation, which is the option S-GAME asked for. The NVIDIA App can also install older versions. Device Manager's Roll Back Driver button is the wrong tool here; it returns you to whatever was installed before, which may be 621.12 or something else entirely, so check the version number afterwards.
The rollback costs something. 617.42 has no Game Ready profile for Phantom Blade Zero, and it loses Advanced Shader Delivery, which affects Modern Warfare 4's precompiled shaders; that game rebuilds its shader cache locally on the older driver, with longer first loads.
Whether any of this is worth doing depends on your system. S-GAME described instability in its own testing. The forum reports describe a separate set of failures. Plenty of players ran 621.01 with neither.
What we did not test
We ran no driver benchmarks and no comparisons between 617.42, 621.01, 621.12 and 621.14. Everything above about 621.01's symptoms comes from user reports and outlet write-ups of the NVIDIA feedback thread, and the S-GAME quote comes from its Steam letter as quoted by multiple outlets. For our measured look at this game's early PC state, see the first patch audit.
