Phantom Blade Zero PC graphics glitches: white sky squares and hair bugs on Radeon, stutter on NVIDIA 621.01
Update the game first: S-GAME's patch of 4 November 2026 (version 1.0302256) fixes the character-hair corruption on AMD cards, and AMD's own advice to switch off High-Quality Hair predates it. The sky corruption on Radeon RX 9000 is still an open AMD known issue with no fix. On GeForce, S-GAME asked players to stay on 617.42 only until NVIDIA's next driver update - two have shipped since, 621.14 and 621.24 - so test the current driver before rolling anything back. Neither NVIDIA release mentions this game.
Start here
Phantom Blade Zero launched on 28 October 2026 into an unusually awkward driver situation. NVIDIA had published 621.01 eight days earlier as the Game Ready driver for this exact game; the developer then told players to roll back off it. Separately, AMD added the game to its own known-issues list for Radeon RX 9000 cards. Most of the launch-week guides blend the two into one list of steps, which means roughly half of what they tell you to do cannot apply to your machine.
Symptoms
- White or light-coloured squares and rectangles appear in the sky, most often in the opening scenes and the horse-and-carriage sequence
- Character hair renders as extremely long or spiky strands in cutscenes, sometimes filling the screen
- Missing textures and blocky artefacts during cinematic sequences, while ordinary gameplay looks correct
- Frame rate is unstable or inconsistent on a GeForce card running driver 621.01
- A long one-off compilation step before you reach gameplay, and occasional brief hitches when moving between areas
Why this happens
A Radeon RX 9000 driver fault that AMD has acknowledged but not yet fixed
AMD's Adrenalin 26.10.2 release notes list "Visual corruption may appear in the sky and on character hair while playing Phantom Blade Zero on Radeon RX 9000 series graphics products" under Known Issues, not Fixed Issues. This is the corruption reported on RX 9070 XT, RX 9070 and RX 9060 XT cards, and it appears overwhelmingly in cutscenes rather than in gameplay. AMD publishes a workaround for the hair only and says nothing about the sky artefacts, so there is currently no vendor-endorsed fix for the squares.
Turn off High-Quality Hair, if the hair is still wrong after updating (Radeon RX 9000 only) · Roll back to an earlier Adrenalin release (Radeon RX 9000 only)
Performance instability on NVIDIA 621.01, reported by the developer and not by NVIDIA
S-GAME's launch-day letter says the studio "observed some performance instability with NVIDIA's latest 621.01 driver" and that 617.42 gave the best experience in its testing. NVIDIA's own 621.01 release notes say the opposite by omission: the driver is presented as Game Ready for this game, and section 3.2, "Open Issues in Version 621.01 WHQL", lists only "N/A". So the only party describing a problem here is the game's developer, and it has not said what the instability consists of or which cards it affects.
Try the current Game Ready driver, and only then consider 617.42 (GeForce only)
Engine-level shader compilation and traversal stutter, which no driver change fixes
The PC build runs on Unreal Engine 5.7.4 and performs a lengthy shader and PSO compilation step before gameplay. That step is what removes most shader-compilation stutter, so the long wait on first launch is the game working as designed rather than a fault. Occasional traversal stutter when crossing into new areas remains, is uncommon, and is not something a driver rollback addresses. If this is what you are seeing, none of the driver fixes below will change it.
Fixes
Update the game to version 1.0302256 or later
about 20 minS-GAME's 4 November patch fixes the character-hair corruption on AMD cards outright, cuts startup shader-compilation time and makes NVIDIA Reflex work with V-Sync. Patch-level and driver-level rendering bugs look identical from the outside, so settle this first.
Applies to: Phantom Blade Zero on PC, all GPUs
- In Steam, open your Library, select Phantom Blade Zero and let any pending update finish. A fresh download already includes the latest version.
- Check the version. S-GAME's patch notes of 4 November 2026 cover version 1.0302256; at or above that, the character-hair fix is included.
- Launch the game and let shader compilation finish. The patch no longer compiles ray-tracing shaders at startup, so if you previously had Ray Tracing off you recompile once on the first launch after updating. Turning Ray Tracing on later compiles those shaders separately on the next restart.
- If you crash or stutter after updating, S-GAME asks you to clear the shader cache: right-click the game in Steam, choose Manage then Browse local files, delete the files inside PBZ\ProjectPBZ\Saved\Cache and relaunch.
PBZ\ProjectPBZ\Saved\Cache - Remove any third-party mods before concluding anything. S-GAME lists mod incompatibility as a known issue with this patch.
- Re-check whether your problem is still there before you touch any driver.
Confirmed by the vendor.
Work out which of the two problems you actually have
about 3 minThe AMD fix and the NVIDIA fix address different faults on different hardware, and applying the wrong one wastes a large download for no effect.
Applies to: Phantom Blade Zero on PC, all GPUs
- Press Windows+R, enter dxdiag, open the Display tab and read off the adapter name and driver version.
dxdiag - If it is a Radeon RX 9070 XT, RX 9070 or RX 9060 XT and your problem is squares in the sky, broken hair, or missing textures in cutscenes, you are on the AMD known issue. Update the game first - the hair half is fixed in version 1.0302256 - then use the High-Quality Hair step if hair is still wrong. The NVIDIA rollback has nothing to do with your card.
- If it is a GeForce card and your problem is unstable or inconsistent frame rate rather than visual corruption, you are in the territory S-GAME describes for 621.01. Move to the current driver (621.24) and retest before considering the 617.42 step.
- If the artefacts appear only during cinematics and your gameplay is clean, that matches every Radeon report in the threads and does not match anything either vendor describes for GeForce.
- If your frame rate dips briefly only when crossing into a new area, that is traversal stutter in the engine. Neither driver change will fix it and you can stop here.
Source: AMD, S-GAME, Steam Community, Wccftech
Turn off High-Quality Hair, if the hair is still wrong after updating (Radeon RX 9000 only)
about 2 minThis is the workaround AMD publishes, but AMD's entry is dated 30 October and S-GAME fixed the hair rendering on 4 November, so update the game first and treat this as the fallback.
Applies to: Radeon RX 9000 series (RDNA 4)
- Do this only if you are on version 1.0302256 or later and the hair still renders incorrectly - S-GAME's 4 November patch fixes it game-side on AMD cards.
- Open the game's Settings and find the graphics options.
- Set High-Quality Hair to off. AMD names this setting directly in the 26.10.2 known-issue entry.
- Return to the cutscene that showed the problem and confirm the hair now renders normally.
- Expect the sky squares to remain either way. AMD's recommendation covers character hair only, the game patch does not mention the sky, and a reporter who disabled the setting still saw squares during the cart sequence.
Confirmed by the vendor.
Source: AMD, Steam Community, Steam Community, S-GAME
Roll back to an earlier Adrenalin release (Radeon RX 9000 only)
Check before applyingabout 25 minSeveral reporters say the corruption is absent on 26.9.1 and 26.8.1, though one found that rolling back changed nothing.
Applies to: Radeon RX 9000 series (RDNA 4)
Before you do this
Downgrading a graphics driver loses the fixes and game-specific optimisations in the releases you skip, including, on 26.10.2, fixes for Steam launcher crashes and for FSR hangs in other games. Do this only while the corruption bothers you more than those, and expect to undo it when AMD ships a fix.
- Note your current driver version from AMD Software, so you can return to it.
- Download the Adrenalin version you intend to install from AMD's own download pages before uninstalling anything, so you are not left without a driver.
- Run the AMD Cleanup Utility. AMD's own release notes say to use it when downgrading to a previous version of Adrenalin.
- Install the older driver and restart. Reporters name 26.9.1 and 26.8.1 as versions where the squares and hair corruption were absent.
- If the corruption is unchanged, go back to the current driver. One reporter clean-installed 26.10.1 and rolled back to 26.9.2 with no improvement either way, so this does not work for everyone.
Reported to work by 3 users; not confirmed by the vendor. 1 report it did not help.
Source: Steam Community, Steam Community, Steam Community, AMD
Try the current Game Ready driver, and only then consider 617.42 (GeForce only)
Check before applyingabout 30 minS-GAME asked players to stay on 617.42 only until NVIDIA's next driver update. Two WHQL drivers have shipped since - 621.14 on 4 November and 621.24 on 12 November 2026 - so that condition has been met, and rolling back to 617.42 now means running a driver several releases old.
Applies to: NVIDIA GeForce cards running 621.01 or newer
Before you do this
617.42 predates the 621.12 hotfix, so rolling back also gives up NVIDIA's fix for the video-playback freeze and black screen on RTX 50 Series and RTX Spark GPUs, and it predates Advanced Shader Delivery, which NVIDIA uses to skip shader compilation in other titles such as Call of Duty: Modern Warfare 4 and Gears of War: E-Day. You are trading those for a change the game's developer recommends and NVIDIA has not acknowledged.
- Install the current Game Ready driver first - 621.24, released 12 November 2026 - and retest. S-GAME's request to stay on 617.42 was explicitly only until NVIDIA's next driver update, and that has now happened twice.
- Be aware that neither 621.14 nor 621.24 mentions this game in its fixed-issues or open-issues list, so NVIDIA has documented no fix for it and retesting is how you find out. 621.14 does fix a separate 621.01 regression that froze or black-screened video playback on RTX 50 Series and RTX Spark.
- If the instability persists on the current driver and you still want to try 617.42, download it from NVIDIA’s driver download pages before uninstalling your current driver.
- Run the installer, choose Custom (Advanced), and tick "Perform a clean installation". S-GAME asks for the clean option specifically.
- Restart and confirm the version in the NVIDIA app or dxdiag. Device Manager's "Roll Back Driver" returns to whatever was previously installed, which may not be 617.42, so check rather than assume.
- Note that a clean installation resets driver-level settings, so any per-game profiles or custom settings you rely on will need redoing.
Confirmed by the vendor, though some users report it does not help.
Source: S-GAME, NVIDIA, NVIDIA, NVIDIA, Steam Community, NVIDIA, NVIDIA
Known issues
The character-hair corruption is fixed game-side. S-GAME's patch notes for version 1.0302256, 4 November 2026, list a fix for character hair rendering incorrectly on certain AMD graphics cards with specific driver versions. This arrived after AMD's 26.10.2 notes, which still carry the disable-High-Quality-Hair recommendation.
Affects Phantom Blade Zero version 1.0302256, Radeon RX 9000 series · Status: fixed
AMD has acknowledged the corruption and has not fixed it in the driver, and its entry is now partly out of date. The sky and character-hair corruption on Radeon RX 9000 appears under Known Issues in Adrenalin 26.10.2, dated 30 October 2026, which recommends disabling High-Quality Hair. S-GAME then fixed the hair rendering game-side on 4 November 2026, so AMD's recommendation is a step behind the game. The sky corruption remains unaddressed by either side.
Affects AMD Software: Adrenalin Edition 26.10.2 Optional, Radeon RX 9000 series · Status: workaround only
Turning off High-Quality Hair does not stop the sky squares. AMD recommends the setting for character hair corruption only. One reporter who disabled it confirmed the hair was fixed while the white squares still appeared during the cart sequence, so a reader whose only complaint is the sky gets nothing from this step.
Affects Radeon RX 9000 series · Status: open
Rolling back the Adrenalin driver does not work for everyone. Three reporters describe the corruption as absent on 26.9.1 or 26.8.1, but one reporter clean-installed 26.10.1 and then rolled back to 26.9.2 and saw no improvement from either. AMD has not endorsed a rollback for this issue, so treat it as worth trying rather than as the fix.
Affects AMD Software: Adrenalin Edition 26.8.1 through 26.10.2 · Status: open
NVIDIA shipped 621.01 for this game and has documented no problem with it. NVIDIA announced it on 20 October 2026 as the Game Ready driver for Phantom Blade Zero, and section 3.2 of the release notes, "Open Issues in Version 621.01 WHQL", contains only "N/A". The instability is reported solely by S-GAME, which has not said what it consists of or which GPUs it affects. NVIDIA's own documentation will not tell you whether your driver is affected.
Affects NVIDIA GeForce Game Ready 621.01 WHQL · Status: open
The 621.01 instability is not universally reproduced. Wccftech's PC performance analysis was carried out on 621.01 and its reviewer reports encountering no driver-specific issues. One player on an NVIDIA card reports the opposite, that rolling back to an older driver made the game run near perfectly. Taken together this looks configuration-dependent rather than universal, which is a reason to test before committing to the rollback.
Affects NVIDIA GeForce Game Ready 621.01 WHQL · Status: unknown
Hotfix 621.12 is not a documented fix for this game. The hotfix released on 27 October 2026 lists four fixed issues, none of which mentions Phantom Blade Zero. Its Unreal Engine entry names Unreal Engine 5.8 with Ray Lighting Mode set to Hit Lighting, while this game's PC build runs Unreal Engine 5.7.4. NVIDIA also calls the hotfix beta and optional and says the safest option is to wait for the next WHQL driver, so it is not a substitute for S-GAME's advice.
Affects NVIDIA GeForce/RTX Spark Hotfix 621.12, Unreal Engine 5.7.4 · Status: unknown
The driver S-GAME said to wait for has now arrived. S-GAME asked players to stay on 617.42 "until NVIDIA releases its next driver update". NVIDIA shipped Game Ready 621.14 on 4 November 2026 and 621.24 on 12 November 2026, so that condition has been met. Neither release mentions Phantom Blade Zero in its fixed or open issues, and S-GAME has published no revised driver guidance, so test the current driver rather than assuming either way.
Affects NVIDIA GeForce Game Ready 621.01 WHQL, NVIDIA GeForce/RTX Spark Hotfix 621.12, NVIDIA GeForce Game Ready 621.14 WHQL, NVIDIA GeForce Game Ready 621.24 WHQL · Status: unknown
If none of this worked
This page covers two specific faults: cutscene corruption on Radeon RX 9000, and frame-rate instability on GeForce 621.01. If the game crashes to desktop, fails to launch, or hangs on a loading screen, that is none of the above — neither vendor nor S-GAME has documented a crash tied to a driver version, and the launch-week guides offering crash fixes with error codes are not citing any vendor source for them. If your complaint is a long wait on first launch, that is the shader and PSO compilation step working as intended. If it is a brief hitch when entering a new area, that is traversal stutter in the engine. And if you have a Radeon card older than RX 9000, or a GeForce card on 617.42 or earlier, nothing documented here applies to your configuration.
Common questions
- Should I install the 621.12 hotfix instead of rolling back to 617.42?
- Not for this game. The hotfix's fixed-issues list does not mention Phantom Blade Zero, and its Unreal Engine entry is for Unreal Engine 5.8 with Hit Lighting while this game's PC build runs 5.7.4. The hotfix is worth having if you also hit the video-playback freeze on an RTX 50 Series card, which it does fix, but it is not an answer to S-GAME's instability report.
- Why would NVIDIA ship a Game Ready driver that the developer says to avoid?
- Game Ready is NVIDIA's label for a driver it has optimised for a title ahead of release; it is not a statement that the shipping game is free of problems. S-GAME's testing is dated 28 October, launch day, after the day-one patch. What is notable is what NVIDIA has published since: section 3.2 of the 621.01 release notes still reads "N/A", and the 621.12 hotfix does not mention this game, so NVIDIA has documented no Phantom Blade Zero problem at all.
- I have a Radeon RX 9000 card and the sky squares are my only problem. What actually works?
- Nothing vendor-endorsed, which is the honest answer. AMD lists the sky corruption as a known issue without a workaround. Three players report it absent on 26.9.1 or 26.8.1, so a rollback is worth trying, but one player saw no difference from rolling back at all. The alternative is to wait for an Adrenalin release that moves this entry from Known Issues to Fixed Issues.
- Does disabling ray tracing or path tracing help?
- No source supports that for either fault. AMD names only the High-Quality Hair setting, and S-GAME names only the driver version. The day-one patch does change ray tracing and path tracing performance, which is a reason to install it, but neither vendor connects those settings to the corruption or the instability.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.
Report a problem with this pageRelated problems
- Video stutters or the screen goes black in Chrome after the NVIDIA 621.01 driver
- Death Stranding 2 hangs or crashes with FSR enabled on a Radeon RX 9000 card
- Cyberpunk 2077 crashes or the driver times out when a video plays on your second monitor (Radeon RX 9000)
- Gears of War: E-Day Compiles Shaders for Minutes on NVIDIA RTX
- NVIDIA driver writes to the SSD constantly (NVDisplay.Container.exe, nvlog.nvlgstg)
- No Sound Over HDMI or DisplayPort on an AMD Graphics Card After a Windows 11 Update
Sources
AMD · Release notes · checked Nov 12, 2026
- AMD lists as a known issue: "Visual corruption may appear in the sky and on character hair while playing Phantom Blade Zero on Radeon RX 9000 series graphics products. Users experiencing character hair corruption are recommended to disable the High-Quality Hair setting in the game."
- AMD's recommendation covers character hair corruption only; the release note offers no workaround for the sky corruption
- AMD advises using the AMD Cleanup Utility when downgrading to a previous version of AMD Software: Adrenalin Edition
- 26.10.2 is an Optional driver, last updated 30 October 2026, and its Fixed Issues list does not include the Phantom Blade Zero corruption
- 26.10.2's Fixed Issues include an intermittent application crash when launching the Steam launcher on Radeon products, and an application hang in Death Stranding 2 with AMD FSR enabled on RX 9000
- Reason and MadnessOfficial
S-GAME · Documentation · checked Nov 1, 2026
- S-GAME's Creative Director and CEO writes: "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."
- S-GAME asks players to "stay on this version until NVIDIA releases its next driver update, which we expect to arrive soon"
- S-GAME describes the problem as performance instability, and names no crash, hang or visual fault
- A day-one patch of approximately 5 GB "significantly improves ray tracing and path tracing performance, alongside several bug fixes", and players who pre-loaded must install it before launching
- The announcement is dated 28 October 2026 and names no AMD or Radeon driver
NVIDIA · Release notes · checked Nov 1, 2026
- The 621.01 release notes are dated 21 October 2026 and section 2.4.1 is headed "Game Ready for Phantom Blade Zero & Call of Duty: Modern Warfare 4"
- Section 3.2, "Open Issues in Version 621.01 WHQL", lists only "N/A"
- The notes mention Phantom Blade Zero only as a Game Ready title and record no performance problem with it
NVIDIA · Documentation · checked Nov 1, 2026
- NVIDIA announced on 20 October 2026 that the GeForce Game Ready 621.01 WHQL driver is the Game Ready driver for Phantom Blade Zero
- NVIDIA says the driver is for "the best possible experience when Phantom Blade Zero launches on October 28th"
- On GeForce RTX GPUs, Phantom Blade Zero is accelerated by DLSS 4.5 with Dynamic Multi Frame Generation
- NVIDIA describes Advanced Shader Delivery for Call of Duty: Modern Warfare 4 and Gears of War: E-Day, not for Phantom Blade Zero
NVIDIA · Knowledge base · checked Nov 1, 2026
- The hotfix lists four fixed issues: a video playback freeze or black screen on some RTX 50 Series/RTX Spark GPUs after updating to 621.01, an Unreal Engine 5.8 crash when Ray Lighting Mode is set to Hit Lighting, RTX Spark HDMI corruption through a StarTech Thunderbolt 3 adapter, and intermittent flickering on the MSI N16 Flip
- Phantom Blade Zero appears nowhere in the hotfix's fixed-issues list
- NVIDIA describes the hotfix as beta and optional, with an abbreviated QA process, and says "The safest option is to wait for the next WHQL certified driver"
- NVIDIA says the fixes will be included in the next official driver, at which point the hotfix will be removed
S-GAME · Release notes · checked Nov 12, 2026
- S-GAME's patch notes for version 1.0302256, published 4 November 2026, state under Bug Fixes: "Fixed an issue that caused character hair to render incorrectly on certain AMD graphics cards with specific driver versions"
- The patch updated the shader compilation process to significantly reduce startup times, and ray tracing shaders are no longer compiled by default at startup; players who previously had Ray Tracing disabled recompile shaders once on first launch
- The patch reduced stuttering that could occur when using a controller connected via Bluetooth, and made NVIDIA Reflex work when set to Auto with V-Sync enabled
- S-GAME lists two common issues with this update: some third-party mods are incompatible and should be removed, and players hitting crashes or stuttering after updating should clear the game's shader cache under PBZ\ProjectPBZ\Saved\Cache and relaunch
- The notes say nothing about the sky corruption on Radeon, so that half of the AMD known issue is not addressed by this patch
NVIDIA · Release notes · checked Nov 12, 2026
- GeForce Game Ready 621.14 WHQL is dated 4 November 2026 (RN-08399-621.14_v01) and is the next WHQL driver after 621.01
- Its fixed issues are incorrect visual colors in Call of Duty: Modern Warfare 4 and a video playback freeze or black screen on some GeForce RTX 50 Series GPUs and RTX Spark after updating to 621.01; its open-issues list reads N/A
- Phantom Blade Zero is not mentioned anywhere in the 621.14 release notes
NVIDIA · Release notes · checked Nov 12, 2026
- GeForce Game Ready 621.24 WHQL is dated 12 November 2026 (RN-08399-621.24_v01) and is the current Game Ready driver
- Its fixed gaming bugs list reads N/A, its fixed general bugs are a Chaos Vantage OptiX Denoiser failure and incorrect colors with DJI D-Log H.265 playback, and its open-issues list reads N/A
- Phantom Blade Zero is not mentioned anywhere in the 621.24 release notes
Wccftech · News · checked Nov 12, 2026
- The PC version runs on Unreal Engine 5.7.4 and offers hardware ray tracing, path tracing, DLSS 4.5, FSR 4.1 and XeSS 2.0
- The game "features a lengthy shader/PSO compilation step before gameplay", which removes most shader compilation stutter
- Occasional traversal stutters are still present, but are uncommon and rarely severe
- The reviewer tested on 621.01 and did not encounter any driver-specific issues
Steam Community · Forum · checked Nov 1, 2026
- Seven distinct posters report white squares in the sky, naming Radeon RX 9070 XT, RX 9070 and RX 9060 XT cards
- One poster reports that on Adrenalin 26.8.1 there are "no white boxes in the sky or weird hair"
- The thread's opening poster reports that checking for driver updates, resetting shaders, verifying files and changing settings all failed to help
- One poster reports that disabling High Quality Hair fixed the hair but that the sky squares still appeared during the cart sequence
- Posters locate the sky corruption mainly in the opening scenes and the horse-and-carriage sequence
- Graphic bug :: Phantom Blade Zero General DiscussionsCommunity report
Steam Community · Forum · checked Nov 1, 2026
- Three distinct posters on Radeon RX 9070 XT report hair strands filling the screen in cutscenes, and the opening poster also reports small white rectangles in the sky during the carriage chase
- One RX 9070 XT poster reports that turning off high quality hair "fixed it"
- One poster recommends downgrading the Adrenalin driver to 26.9.1
- One poster with an NVIDIA card reports having to roll back to an older NVIDIA driver and that the game then "runs near perfect"
Steam Community · Forum · checked Nov 1, 2026
- Three distinct posters report the glitches, confined to cinematic sequences rather than gameplay: "There will be missing textures, weird blocks in the sky and hair going crazy."
- The opening poster reports that a clean install of Adrenalin 26.10.1 and a rollback to 26.9.2 both produced no improvement, and that verifying game files did not help either