If Clair Obscur: Expedition 33 crashes on startup, the most common causes are outdated GPU drivers, corrupted shader cache, or a conflict with overlay software, and updating your graphics driver and verifying game files resolves the issue for most players. This article explains the specific steps to fix the crash, what causes it, and how to prevent it from happening again.
Why Does Clair Obscur: Expedition 33 Crash on Launch?
Clair Obscur: Expedition 33 is a visually demanding Unreal Engine 5 title. Startup crashes typically stem from one of a few predictable problems:
- Outdated or corrupted GPU drivers – the game relies on recent driver optimizations, and old drivers often fail to initialize the DirectX 12 or Vulkan renderer.
- Corrupted shader cache – the game compiles shaders on first run. If this process is interrupted or the cache is corrupted, the game may crash before the main menu appears.
- Overlay software conflicts – Discord, GeForce Experience, MSI Afterburner, and similar tools can interfere with the game’s rendering pipeline.
- Missing or corrupted game files – an incomplete download or a failed update can leave essential files broken.
- Insufficient system resources – the game requires a 64-bit processor, 16 GB of RAM, and a DirectX 12 compatible GPU. If your system barely meets the minimum, the game may crash during the initial load.
Step-by-Step Fixes to Try
Work through these fixes in order. Most players resolve the issue at step 1 or 2.
- Update your GPU driver. Go to the official website for your graphics card (NVIDIA, AMD, or Intel) and download the latest driver. Use the “clean install” option if available. This is the single most effective fix.
- Verify game files. On Steam, right-click the game in your library, select Properties → Installed Files → Verify integrity of game files. On Epic Games Store, click the three dots on the game tile → Manage → Verify. This replaces any corrupted or missing files.
- Disable overlays. Turn off Discord overlay (User Settings → Overlay), GeForce Experience in-game overlay, and any other screen-capture tools. Then relaunch the game.
- Clear the shader cache. Navigate to
%LOCALAPPDATA%\ClairObscur\Savedand delete theShaderCachefolder. The game will rebuild it on next launch. (The exact folder name may vary slightly depending on the version.) - Run the game as administrator. Right-click the game executable (or the Steam shortcut) → Properties → Compatibility → check “Run this program as an administrator.”
- Disable fullscreen optimizations. In the same Compatibility tab, check “Disable fullscreen optimizations.” This helps with some Unreal Engine 5 games.
- Set the game to use DirectX 11 as a fallback. Some players have found that forcing DirectX 11 (via launch options
-dx11on Steam) bypasses crashes, though the game may look slightly different. This is a temporary workaround, not a permanent fix. - Check Windows updates. Ensure your operating system is up to date, especially the .NET Framework and Visual C++ redistributables, which the game relies on.
What If the Crash Persists?
If you’ve tried all the steps above and the game still crashes, the problem may be specific to your hardware configuration. Here are a few less common but real possibilities:
- Overheating CPU/GPU. Check your temperatures using a tool like HWMonitor. If your CPU exceeds 90°C or GPU exceeds 85°C under load, the system may shut down the game to protect itself. Clean your fans and improve case airflow.
- Power supply issues. A failing PSU can cause crashes under heavy load. If you hear clicking or see system reboots, test with a different PSU if possible.
- RAM instability. Run a memory test (Windows Memory Diagnostic) to rule out faulty RAM. Disable XMP/EXPO profiles in BIOS to see if that stabilizes the game.
- Antivirus interference. Some antivirus programs quarantine game files. Add the game folder to your antivirus whitelist.
Common Misconception: “It’s a Bad Port”
Many players assume a startup crash means the game is poorly optimized. While the game does have demanding requirements, startup crashes are rarely a sign of a broken port. They are almost always environmental – a driver, a missing file, or a conflicting program. The game’s official forums and Steam community threads show that the vast majority of crash reports are resolved by the steps above. If the game were fundamentally broken, the crash would happen for everyone, not just a subset of players.
Preventing Future Crashes
Once you get the game running, you can reduce the chance of future startup crashes by:
- Keeping your GPU driver updated (but don’t install beta drivers unless you’re comfortable troubleshooting).
- Closing background applications that use heavy GPU resources (browsers with hardware acceleration, streaming software).
- Letting the shader compilation finish without interrupting it – don’t alt-tab or close the game during the first launch.
- Regularly verifying game files before major updates.
Frequently Asked Questions
Does the game crash on Xbox or PlayStation?
Console versions are generally stable, but some players have reported crashes on Xbox Series X|S when resuming from quick resume. A full restart of the console usually fixes it. On PlayStation 5, crashes are rare but can occur if the game is running from an external HDD; move it to internal storage.
Will the crash damage my save file?
No. A startup crash happens before the game loads your save, so it cannot corrupt your progress. If a crash occurs during gameplay, the game autosaves frequently, so you lose at most a few minutes of progress.
Why does the game crash only when I have Discord open?
Discord’s overlay uses a DirectX hook that can conflict with Unreal Engine 5’s rendering. Disabling the overlay or running Discord as administrator often resolves it. Some players also report that disabling hardware acceleration in Discord helps.
Can I get a refund if the game won’t run?
Steam’s refund policy allows a refund within 14 days if you’ve played less than 2 hours, even if the game crashes. Epic Games Store has a similar policy. If you’ve spent more time troubleshooting, you may still be able to get a refund by contacting support, but it’s not guaranteed.
Is there a way to skip the shader compilation?
No, and you shouldn’t. Shader compilation is necessary to prevent stuttering during gameplay. If you skip it, you’ll experience frame hitches. The compilation usually takes 2–5 minutes on a mid-range system.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Campus Tech Innovation Hubs: What They Are
- Poco C51 Airtel Prepaid Locked Variant India?
- Jenkins vs GitHub Actions: Which CI/CD Fits Your Team?
- Turn Off Backup Encryption in iTunes?
- Shared VPS Hosting: Is It Better?
- Disk Defrag Pro: What It Does and Whether You Need It