Split Fiction Errors
Split Fiction runs on Unreal Engine, so its main error is the 'The UE-Split Game has crashed and will close' fatal error rather than numeric codes. It's usually an outdated GPU driver, a corrupted install, or a DirectX mode mismatch. Here's what each common problem means and the fastest fix.
Error codes
'The UE-Split Game has crashed' (fatal error)
Unreal Engine hit a fatal error and closed the game
Cause: Outdated or corrupted GPU drivers, corrupted game files, or overloaded graphics settings.
- Update your GPU driver with a clean install — the most common fix for this fatal error.
- Verify the integrity of the game files so the launcher replaces damaged files.
- Lower graphics settings from ultra/high to ease the load on the GPU and CPU.
DirectX 12 crash (try -dx11)
The game crashes under DirectX 12
Cause: A DX12 driver/hardware incompatibility.
- Add '-dx11' to the launch options to force DirectX 11.
- Update GPU drivers and clear the DirectX Shader Cache.
- Disable frame generation and overlays.
DirectX 11 crash (try -dx12)
The game crashes under DirectX 11
Cause: A DX11 configuration issue on some setups.
- Add '-dx12' to the launch options to force DirectX 12.
- Verify game files and update Windows.
- Install the latest Visual C++ Redistributables.
Crash on startup / won't launch
The game closes before the main menu
Cause: Missing runtimes, corrupted files, or antivirus/overlay conflicts.
- Install the latest Visual C++ Redistributables and DirectX runtime.
- Verify game files and run the game as administrator.
- Add the game to antivirus exceptions and disable overlays, then reinstall if crashes persist.
Fixes that work for most Split Fiction (PC, PlayStation 5, Xbox Series X|S) errors
- Verify/repair the game files (Steam: Properties -> Installed Files -> Verify integrity; other launchers: repair) — this replaces corrupted files behind most crashes and fatal errors.
- Update your GPU driver with a clean install (use DDU), and install the latest Microsoft Visual C++ Redistributables (x86 and x64) plus the DirectX End-User Runtime — missing runtimes and stale drivers cause most launch crashes.
- Clear the DirectX Shader Cache (Windows Settings -> System -> Storage -> Temporary files, or Disk Cleanup) and delete the game's local shader/cache folder in AppData\Local, then relaunch.
- Disable overlays (Steam, Discord, GeForce Experience, Ubisoft Connect) and any third-party antivirus/VPN, and add the game to your firewall exceptions.
- Check the game's official server status before assuming a local problem — many named connection errors are a maintenance window or outage and clear on their own.
FAQ
How do I fix 'The UE-Split Game has crashed' in Split Fiction?
This Unreal Engine fatal error is most often an outdated or corrupted GPU driver. Do a clean GPU-driver install, verify the integrity of the game files so damaged files are replaced, and lower graphics settings from ultra/high to reduce the load on your GPU and CPU. If it persists, force DirectX 11 with the '-dx11' launch option.
Does forcing DirectX help with Split Fiction crashes?
Yes — a DirectX mode mismatch is a common cause. If the game crashes under DirectX 12, add '-dx11' to the launch options to force DirectX 11; if it crashes under DirectX 11, try '-dx12'. Pair this with updated GPU drivers, a cleared shader cache and the latest Visual C++ Redistributables.
Other games
- Clair Obscur: Expedition 33 Errors — Fatal Error, LowLevelFatalError & Crash Fixes
- Hollow Knight: Silksong Crash & Error Fixes — Won't Launch, Startup Crash
- Indiana Jones and the Great Circle Errors — Missing Vulkan Extension, RT Crash & Fixes
- Monster Hunter Wilds Error Codes — R31A6-0-0:3, C1061-0-0, ea_1869f & Connection Fixes
- Silent Hill 2 Remake Errors — LowLevelFatalError, DX12 Crash, D3D12 Fix & More
- Rainbow Six Siege Error Codes — 2-0x0000C015, 3-0x0001000B, 8-0x00003700, Vulkan & More
- Valorant Error Codes — VAN 9003, VAL 43, VAN 152, VAN 68, Error 29 & More
- Call of Duty & Warzone Error Codes — Dev Error 6068, 6065, 6034, 6178 & More