Enotria: The Last Song — Fatal Error & Crashing Fix
Enotria: The Last Song is an Unreal Engine 5 soulslike whose fatal-error crashes cluster around two specific causes people rarely check: leftover save files from the free demo, and a known instability on certain Intel CPUs. Here is each cause — with the demo-save cleanup and the profile-swap trick that revives a save that crashes on load.
Error codes
Fatal error / crash to desktop on startup
The game closes with a UE fatal error before or just after the menu
Cause: Leftover demo save files conflicting with the retail build, or a corrupted profile.
- Delete the old demo save files, then start a fresh game on the retail version — demo-era saves are a confirmed crash cause on launch.
- In the main menu, choose a different profile and start a new game, then re-load your previous profile/save — this clears the state that crashes on load.
- Run the game as Administrator to rule out permission-locked save writes.
Crash specific to Intel CPUs
The game crashes reliably on certain Intel processors
Cause: Known Intel-CPU instability with the UE5 build.
- Update your motherboard BIOS to the latest microcode — Intel's stability microcode reduces UE5 crashes.
- Disable CPU overclocks/undervolt curves and XMP/EXPO stress profiles; on 13th/14th-gen, cap all-core multiplier via Intel XTU.
- Confirm your PC meets the minimum system requirements before deeper troubleshooting.
Freezing during gameplay
The game hangs mid-session and must be force-closed
Cause: Overlay/antivirus interference or thermal pressure.
- Run as Administrator and disable Discord/Steam/GeForce overlays.
- Add Enotria.exe to antivirus exceptions and cap the frame rate to reduce heat.
Fixes that work for most Enotria: The Last Song (PC / Steam, Unreal Engine 5) errors
- Delete leftover demo saves and verify integrity of game files in Steam.
- Clean-install the latest GPU driver with DDU and install the newest Microsoft Visual C++ Redistributables (x86 + x64).
- Update motherboard BIOS microcode and disable overclocks if you are on an Intel CPU.
FAQ
Why do demo saves crash the retail game?
Enotria's demo and retail builds store saves in the same location; the older demo save format is read by the newer retail build and triggers a fatal error on load. Deleting the demo saves and starting fresh fixes it.
Does the profile-swap trick lose progress?
No — you start a new game on a second profile only to get past the crashing load, then re-select your original profile; your save is intact.
Other games
- Assassin's Creed Shadows Error Codes — DX12 0x887a0006, 0x80070057, ANIMUS & Fixes
- Kingdom Come: Deliverance II Errors — Crash at Startup, DX11/DX12, Nvidia 572.16 & Fixes
- Split Fiction Errors — 'UE-Split Game Has Crashed' Fatal Error, DX11/DX12 Crash & Fixes
- S.T.A.L.K.E.R. 2 Error Codes — 887A0006 (D3D12 Device Removed), LowLevelFatalError, Shader Crash & Fixes
- Black Myth: Wukong Error Codes — Denuvo 'Something Went Wrong', Error 577, D3D12 Device Crash & Fixes
- Cyberpunk 2077 Error Codes — Access Violation, 0xC000001D, Flatlined, CE-34878-0 & Fixes
- Fall Guys Error Codes — 200_001, 200_1040, 201_003, 200_2147483647, LS_0013 & Fixes
- Hunt: Showdown Error Codes — 0x30001, 0x3001, 0x3003, 0x4004, 0x107d1 & Fixes