Updated November 12, 2026
Does Phantom Blade Zero shut down or restart your entire PC while compiling shaders? Some players experience a sudden power-off or automatic reboot when shader compilation reaches around 25% or 35%, preventing the game from reaching the main menu.
This is different from an ordinary startup crash. If your entire computer loses power, the problem may involve CPU temperatures, system stability, firmware, or power delivery rather than damaged game files alone.
There are several ways to narrow down the cause without immediately reinstalling Windows, replacing hardware, or repeatedly forcing your PC through another shutdown.
.webp "Phantom Blade Zero PC Shuts Down During Shader Compilation – Troubleshooting Guide")
Quick Answer: What to Do First
If Phantom Blade Zero shuts down or restarts your PC during shader compilation, stop repeatedly launching the game until you have checked your system.
Start with these steps:
- Identify whether the PC completely loses power, automatically restarts, or only closes the game.
- Check CPU temperatures, cooling fans, and airflow.
- Inspect Windows Event Viewer for unexpected shutdowns and hardware errors.
- Return custom CPU, GPU, and RAM tuning to known-stable settings.
- Check power connections and investigate possible PSU problems.
- Review applicable motherboard BIOS and CPU microcode updates.
- If Windows remains running and only the game crashes, follow S-GAME's shader-cache troubleshooting instructions.
Important: Clearing the shader cache may help game crashes or stuttering, but it is not a confirmed fix for a computer that completely loses power.
📋 Table of Contents
- PC Shuts Down, Restarts, or Game Crashes?
- Why Shader Compilation Can Trigger a Shutdown
- Fix 1: Check CPU Temperatures and Cooling
- Fix 2: Check Windows Event Viewer
- Fix 3: Return CPU, GPU, and RAM to Stable Settings
- Fix 4: Check PSU and Power Connections
- Fix 5: Check BIOS and CPU Microcode Updates
- Fix 6: Follow S-GAME's Shader Cache Guidance
- Does the -noraytracing Launch Option Help?
- What If Phantom Blade Zero Still Shuts Down Your PC?
- Frequently Asked Questions
PC Shuts Down, Restarts, or Game Crashes? Identify Your Symptom
Before changing settings, determine exactly what happens when Phantom Blade Zero reaches shader compilation.
| Symptom | What happens | What to check first |
|---|---|---|
| Entire PC powers off | The computer suddenly loses power and may require pressing the power button again. | Cooling, PSU, power connections, hardware stability |
| PC automatically restarts | Windows disappears and the computer immediately begins booting again. | Event Viewer, WHEA errors, system stability |
| Game closes to desktop | Phantom Blade Zero closes, but Windows continues working. | Game files, shader cache, graphics drivers, mods |
| Shader compilation freezes | The percentage stops moving, but the PC remains powered on. | CPU activity, storage space, game files, shader behavior |
This distinction matters because a fix for a game crash may do nothing for a full-system power failure.
If Phantom Blade Zero simply closes to desktop, start with our Phantom Blade Zero startup crash and Denuvo troubleshooting guide.
If the screen goes black and your Radeon driver reports a timeout while Windows remains running, see our Phantom Blade Zero AMD RX 9070 XT and 7900 XTX crashing guide.
If your PC stays powered on but the game recompiles shaders every time you launch it, follow our Phantom Blade Zero compiling shaders every launch guide. That is a separate problem from a complete system shutdown.
Why Does Phantom Blade Zero Shut Down During Shader Compilation?
Shader compilation prepares graphics instructions used to render the game's environments, lighting, and visual effects.
This process can place a substantial workload on the CPU. Depending on your hardware, cooling, firmware, and system configuration, shader compilation may expose instability that does not appear during lighter tasks.
Possible contributing factors include:
- High CPU temperatures: Cooling problems may become more noticeable under sustained CPU workloads.
- Unstable CPU settings: Overclocking, undervolting, or aggressive boost settings can cause instability.
- Memory instability: RAM settings that appear stable during normal use may fail under certain workloads.
- Outdated BIOS or CPU microcode: Relevant firmware updates can address documented processor stability problems.
- Power delivery problems: A failing PSU, loose connection, or another electrical issue can cause unexpected shutdowns.
- Software or driver failures: These may cause crashes, freezes, or automatic restarts, although they do not automatically explain a complete loss of power.
Does shutting down at 25% or 35% mean anything?
The exact compilation percentage is not a diagnosis.
A shutdown at 25% does not necessarily have a different cause from one at 35%. Those percentages indicate where the interruption occurred, not which component failed.
Do not assume Phantom Blade Zero has damaged your CPU or PSU. The game may be exposing an existing instability, but the symptoms alone cannot identify the underlying cause.
Fix 1: Check CPU Temperatures and Cooling
If your computer shuts down while compiling shaders, begin with cooling.
Step 1: Check CPU temperatures
Use a reputable hardware monitoring utility, such as HWiNFO, to inspect CPU temperatures while the system is operating safely.
Pay attention to:
- CPU package temperature
- Maximum recorded temperature
- CPU thermal throttling indicators
- Fan speeds, where available
Compare the readings against the thermal specifications for your exact processor.
Different CPUs have different operating limits. There is no single temperature that proves every processor is overheating.
If the computer is already experiencing repeated unexplained power loss, avoid launching Phantom Blade Zero merely to collect another temperature reading.
Step 2: Inspect cooling and airflow
With the PC powered off and unplugged, inspect:
- Dust buildup around heatsinks and vents
- Restricted case airflow
- Loose or disconnected cooling cables
- Visible damage to accessible cooling components
- Obvious signs of liquid-cooling problems
When the system is operating safely, check fan speeds through BIOS monitoring or a hardware monitoring utility.
Avoid removing or reseating a CPU cooler unless you are comfortable doing so correctly.
Step 3: Check for problems outside the game
If your computer also shuts down during other demanding applications, the issue is less likely to be limited to Phantom Blade Zero.
However, do not repeatedly run demanding stress tests on a computer that is already experiencing unexplained power loss.
Investigate the cooling or power problem first.
What this fix can solve: Shutdowns associated with inadequate cooling or thermal instability.
What it cannot establish: Whether Phantom Blade Zero itself is defective or whether a particular hardware component has failed.
Fix 2: Check Windows Event Viewer for Kernel-Power and WHEA Errors
Windows Event Viewer can help you determine whether the system recorded an unexpected shutdown or a hardware-related error.
How to check Event Viewer
- Press Windows + X.
- Select Event Viewer.
- Expand Windows Logs.
- Select System.
- Look for errors or critical events around the time the PC shut down.
- Open relevant entries and check their details.
Three types of events are particularly useful.
Kernel-Power Event ID 41
A Kernel-Power 41 event indicates that Windows detected an unexpected shutdown or restart.
However, Kernel-Power 41 does not tell you what caused the shutdown.
It can appear after a power interruption, system freeze, hardware instability, or another failure that prevents Windows from shutting down normally.
Do not replace your PSU solely because Event 41 appears.
WHEA-Logger events
Windows Hardware Error Architecture (WHEA) entries can provide information about certain hardware errors.
Depending on the event, these may involve processors, memory, or other hardware components.
If WHEA errors appear near the shutdown, record their event IDs and details.
They may help narrow down the problem, but a WHEA event does not automatically mean your CPU needs replacing.
BugCheck events and Windows minidumps
If Windows encounters a stop error and automatically restarts, you may find a BugCheck event or a crash dump.
Check:
C:\Windows\Minidump
If the folder contains a dump file corresponding to the failure, it may help identify a driver or system-level crash.
Not every restart creates a minidump, and the presence of one does not automatically prove a driver is responsible.
What if there are no useful errors?
A sudden power loss can prevent Windows from recording a detailed explanation.
If Event Viewer only shows an unexpected shutdown, continue with the stability and power checks below.
Fix 3: Return CPU, GPU, and RAM to Stable Settings
Overclocking and undervolting can improve performance or efficiency, but unstable settings may cause crashes or restarts under specific workloads.
Even a configuration that works in other games may not be stable under every type of load.
Settings worth checking
| Component | Settings to review |
|---|---|
| CPU | Manual overclocking, undervolting, Curve Optimizer, aggressive boost tuning |
| GPU | Core overclock, memory overclock, undervolt |
| RAM | XMP, EXPO, manual memory frequency and timings |
Recommended approach
If you have customized these settings:
- Record your existing configuration.
- Return one category of tuning to a known-stable default.
- Check system stability without repeatedly provoking a hard shutdown.
- Continue only when the system is safe to test.
For CPU and memory settings, follow your motherboard manufacturer's documentation.
Avoid making several unrelated changes simultaneously, because that makes it harder to identify which adjustment helped.
If the PC shuts down even at standard settings, continue with the power checks.
Important: Disabling XMP or EXPO is a diagnostic step, not proof that your RAM is defective.
Fix 4: Check PSU and Power Connections
A sudden loss of power can indicate a power delivery problem, although it is not enough to diagnose a defective PSU.
Potential issues include inadequate power capacity, damaged cables, loose connections, or an aging power supply.
Safe checks you can perform
With the PC shut down, switched off, and unplugged:
- Inspect the external power cable for visible damage.
- Check that the wall connection is secure.
- Look for obvious damage to accessible cables and connectors.
- Ensure case ventilation is not blocked.
- Consider whether similar shutdowns have occurred in other demanding applications.
If you are experienced with PC assembly, inspect accessible internal power connectors according to your hardware manufacturer's instructions.
Do not force connectors or work inside the computer while it is connected to power.
What not to do
Never open the PSU enclosure. Power supplies can retain dangerous electrical charges even after being disconnected.
Do not attempt electrical measurements or internal PSU repairs without appropriate professional training.
If you notice a burning smell, sparks, damaged connectors, or repeated unexplained shutdowns, stop using the computer and seek qualified assistance.
Replacing a PSU should be based on a proper diagnosis rather than an assumption that Phantom Blade Zero requires more power.
Fix 5: Check BIOS and CPU Microcode Updates
A motherboard BIOS update may help if the shutdown is connected to a known processor stability problem.
A BIOS update containing newer CPU microcode has helped resolve shader-compilation crashes on some systems.
However, that does not mean every Phantom Blade Zero shutdown requires a BIOS update.
How to check safely
- Identify your motherboard's exact manufacturer and model.
- Press Windows + R, enter
msinfo32, and open System Information. - Find the BIOS Version/Date entry.
- Visit the official support page for your exact motherboard.
- Read the available BIOS release notes.
- Look for updates addressing CPU stability, compatibility, or relevant microcode changes.
- Follow the manufacturer's instructions if an applicable update is available and your system is safe to update.
This is especially worth investigating if your processor or motherboard has a documented stability issue that a firmware update specifically addresses.
Important BIOS safety warning
BIOS updates are not risk-free.
Using the wrong firmware or interrupting an update can leave a system unable to boot.
Do not attempt a BIOS flash while your PC is experiencing unexplained power interruptions. Resolve the power problem first or have a qualified technician perform the update.
If your system is otherwise stable and there is no relevant firmware improvement, updating the BIOS should not be your first troubleshooting step.
What this fix can solve: Certain documented firmware or CPU stability problems.
What it cannot guarantee: A fix for every Phantom Blade Zero shutdown.
Fix 6: Follow S-GAME's Shader Cache Guidance
Phantom Blade Zero received changes to its shader compilation process in patch 1.0302256.
The update changed how ray-tracing shaders are compiled during startup.
Instead of compiling ray-tracing shaders by default, the game now handles them according to the player's ray-tracing configuration.
This can reduce unnecessary shader compilation for players who do not use ray tracing.
However, the patch does not establish a universal fix for complete PC shutdowns.
How shader compilation works after the update
The updated shader compilation process behaves differently depending on your previous ray-tracing settings.
- Ray tracing previously disabled: The first launch after updating may require a one-time shader compilation.
- Ray tracing previously enabled: The game can start without that additional initial compilation.
- Ray tracing enabled later: The required ray-tracing shaders will compile separately when the game next restarts.
If the game recompiles shaders once after updating, allow the process to finish provided your computer remains stable.
A one-time compilation is expected for some graphics configurations and does not necessarily mean the update failed.
Clear the shader cache if the game crashes or stutters
S-GAME recommends clearing the game's shader cache when certain crashes or stuttering problems appear after updating.
To do this:
- Close Phantom Blade Zero.
- Open your Steam Library.
- Right-click Phantom Blade Zero.
- Select Manage → Browse local files.
- Open the following folder:
PBZ\ProjectPBZ\Saved\Cache - Delete the files inside the specified Cache folder.
- Restart the game and allow the required shader compilation to complete.
Do not delete the entire Saved folder. It may contain data unrelated to the shader cache.
If you are unsure which folder is correct, do not delete anything until you have verified the path.
Remove incompatible mods if crashes started after updating
Some third-party mods may become incompatible with newer game versions.
If Phantom Blade Zero started crashing after an update and you use mods, temporarily remove them according to their installation instructions.
Test the game without those modifications before making further changes.
Do not delete unrelated files or save data while removing mods.
Will clearing the shader cache stop a full PC shutdown?
Not necessarily.
This procedure targets game-side crashes and stuttering associated with cached data.
It does not repair an overheating CPU, unstable memory, or faulty power delivery.
If your computer is losing power, resolve the system stability problem before trying to compile shaders again.
Verify game files if only the game crashes
For crashes that return you to the Windows desktop, you can also verify the installation:
- Open Steam.
- Right-click Phantom Blade Zero.
- Select Properties.
- Open Installed Files.
- Select Verify integrity of game files.
Steam will check the installation and replace files that fail verification.
This is a reasonable step for game-only crashes, but it is not a hardware shutdown fix.
Does the -noraytracing Launch Option Help?
Some players have experimented with the following Steam launch option:
-noraytracing
This argument is intended to disable ray-tracing functionality in supported Unreal Engine configurations.
It has helped some players with repeated shader compilation, but its effect depends on the game build and rendering configuration.
There are two important limitations:
- It is not a confirmed fix for complete PC shutdowns during Phantom Blade Zero shader compilation.
- The game's updated shader compilation process already avoids compiling ray-tracing shaders by default when they are not needed.
If you are troubleshooting a computer that repeatedly loses power, do not rely on this launch option as a substitute for checking hardware stability.
If you previously added the option while testing, you can remove it from Steam → Properties → General → Launch Options to return to normal launch behavior.
What If Phantom Blade Zero Still Shuts Down Your PC?
If your entire computer continues to lose power during shader compilation, avoid repeatedly reproducing the failure.
At this point, the safest approach is to narrow down whether the issue is specific to the game or affects the system more broadly.
Check these questions
- Does the PC shut down in other demanding games?
- Does the shutdown happen only during initial shader compilation?
- Does Windows restart automatically, or does the computer lose all power?
- Are there WHEA or BugCheck events near the failure?
- Are CPU temperatures approaching the processor's documented thermal limits?
- Is the system running custom CPU, GPU, or memory settings?
- Is the motherboard running a BIOS version with known stability issues?
If the computer also loses power outside Phantom Blade Zero, prioritize hardware diagnostics.
If the problem occurs only in this game and the system passes appropriate stability checks, collect information for a support report.
Information to include in a support report
Provide:
- CPU and GPU models
- RAM capacity and configuration
- Windows version
- Graphics driver version
- Motherboard model and BIOS version
- Phantom Blade Zero game version
- Whether the system shuts down, reboots, or only crashes
- Approximate shader compilation percentage
- Relevant Event Viewer errors
- Troubleshooting steps already attempted
Do not send passwords, license keys, or other private account information.
A detailed report is more useful than simply saying the game crashes at 35%.
You can submit your report through the official Phantom Blade Zero support website.
Frequently Asked Questions
Why does Phantom Blade Zero shut down my PC at 35% shader compilation?
Shader compilation can place significant load on the CPU and expose cooling, firmware, memory, or power instability. The 35% mark does not identify the cause. Check whether the PC loses power or restarts, then investigate temperatures, Event Viewer, and system stability.
Why does my PC restart at 25% shader compilation?
An automatic restart can result from several system-level failures, including hardware instability or a Windows stop error configured to restart automatically. Check Event Viewer for WHEA or BugCheck events. The 25% mark alone does not establish the cause.
Can Phantom Blade Zero shader compilation damage my CPU?
Normal shader compilation is not inherently supposed to damage a properly functioning CPU. Modern processors have thermal and power protections, but those protections do not eliminate every hardware risk. If your PC repeatedly shuts down, stop testing until the cause has been investigated.
Does patch 1.0302256 fix shader compilation shutdowns?
The patch changes how ray-tracing shaders are compiled and includes shader-cache troubleshooting guidance. It does not establish a confirmed universal repair for computers that completely lose power during compilation.
Should I update my BIOS to fix Phantom Blade Zero crashes?
Consider a BIOS update if your motherboard manufacturer provides a relevant CPU stability or microcode improvement. Firmware updates can resolve certain stability problems, but they are not guaranteed to fix your system. Never flash firmware while power delivery is unreliable.
Can clearing the shader cache fix a complete PC shutdown?
Clearing the cache can help certain game crashes or stuttering issues, but it does not fix underlying cooling, memory, or PSU problems. If the entire PC loses power, prioritize system diagnostics.
Does -noraytracing stop shader compilation crashes?
It may change ray-tracing behavior in some configurations, but it is not a confirmed fix for Phantom Blade Zero full-system shutdowns. The game's updated shader process already handles ray-tracing compilation differently.
Why does Phantom Blade Zero compile shaders again after an update?
Game updates, graphics settings changes, and shader-cache changes can require recompilation. Enabling ray tracing after it was disabled can also trigger another compilation under the updated shader system. Recompilation by itself is not necessarily a bug.
Final Thoughts
If Phantom Blade Zero shuts down or restarts your entire PC during shader compilation, the most important step is identifying whether the problem is a system-level shutdown or an ordinary game crash.
For complete power loss, begin with cooling, system stability, Event Viewer, and power delivery. Review firmware updates only when they are relevant and safe to apply.
For game-only crashes or stuttering, S-GAME's updated shader compilation behavior and cache-clearing guidance provide additional troubleshooting options.
There is no single confirmed fix that applies to every PC shutting down at 25% or 35% shader compilation. Working through the symptoms in the correct order is safer and more effective than changing unrelated settings or replacing hardware without evidence.
Comments
Post a Comment