Subnautica 2 — Common Errors & How to Fix Them
The crashes and error messages players actually hit in Subnautica 2, what causes each one, and the fix that works.
Last updated 2026-09-25 · evergreen reference
Below are the errors Subnautica 2 players report most often on PC, paired with the cause and the fix that actually resolves it. Subnautica 2 runs on the Unreal Engine 5 (Early Access), and several of these faults are engine-level rather than game-specific — which is why the same fix keeps appearing across different 2026 releases. Work through them in order: the cheap, reversible steps first, and the invasive ones (BIOS updates, clean driver installs, page file changes) only if the symptom matches.
The errors and their fixes
Symptom, cause, and the fix that resolves it.
Crash on launch
**Cause:** Typical Early Access causes: unverified files, stale drivers, a corrupted DirectX shader cache, or overlay conflicts with the UE5 pipeline.
**Fix:** Verify game file integrity, do a clean driver install, clear the DirectX shader cache from Windows Disk Cleanup, run the executable as administrator, and disable Discord and GeForce Experience overlays.
Do not force DirectX 11
**Cause:** Subnautica 2 requires DirectX 12 for Lumen and Nanite.
**Fix:** Editing Engine.ini to force DX11 causes an immediate crash. Leave the renderer on DX12 and lower Lumen instead.
“The game may not have exited correctly”
**Cause:** A standard Unreal notification that simply means the last session ended unexpectedly.
**Fix:** If the game then crashes on that window every launch, clear the temporary cache files inside the game folder in %LOCALAPPDATA% — without touching the Saved folder — and verify file integrity through Steam.
Fabricator or base crafting consumes resources and produces nothing
**Cause:** A known Early Access interface bug where the crafting animation stalls or tool slots get confused.
**Fix:** Save the game and reload the same save; base mechanics restart fully. Also avoid placing portable containers directly on the floor inside base modules, as they can fall through the floor and block the construction grid.
Freeze when swimming out of caves into open water
**Cause:** Dynamic object streaming plus Lumen lighting as the ocean loads new invisible sectors.
**Fix:** Confirm the game is on an SSD — on a hard drive these freezes are unavoidable — and lower Global Illumination to Medium or Low.
Friends cannot join co-op, or the loading screen never ends
**Cause:** Version mismatch or blocked network services.
**Fix:** Make sure every player has the same game version, restart Steam and the game, verify files, try changing the host, and check firewall, antivirus and VPN settings. Disabling crossplay temporarily can isolate it.
Frame rate degrades after two to three hours
**Cause:** A known memory leak in the Early Access build.
**Fix:** Save and restart the game every few hours. The developer has confirmed this will be patched before full release.
Fix order if you do not know which one you have
Cheapest and most reversible first.
1. Verify and restart
Verify game file integrity through your launcher and restart the PC. This clears stuck background tasks and driver hooks, and repairs the corrupt downloads that launch-day server load makes common.
2. Drivers, cleanly
Install the latest GPU driver from the vendor site rather than Windows Update, and choose the clean-install option. Both NVIDIA and AMD ship game-ready drivers for major releases that fix compatibility outright.
3. Strip overlays and background hooks
Disable Steam, Discord, Xbox Game Bar, GeForce Experience and MSI Afterburner overlays, along with RGB utilities and hardware monitors. These inject code into the game process and are one of the most frequent crash triggers.
4. Rebuild the shader cache
Clear the DirectX shader cache from Windows Disk Cleanup and delete the game’s own shader cache folder, then let it rebuild. Corrupted shader caches cause crashes that look like hardware faults.
5. Only then touch hardware settings
Remove GPU and CPU overclocks including RAM XMP/EXPO, check temperatures, and if the crash pattern points to CPU instability rather than the GPU, update the motherboard BIOS before assuming your hardware is faulty.
When it is not your PC
Engine and patch bugs worth knowing about.
Known engine-level issues
Several Subnautica 2 faults trace back to the Unreal Engine 5 (Early Access) rather than to your hardware — shader compilation crashes, overlay conflicts and memory leaks during long sessions are the recurring three. These get patched; the workarounds above exist to keep you playing until then.
Reporting it usefully
When you report a crash, include the exact error message, when it started, whether it followed a patch or driver update, your GPU model and driver version, and whether ray tracing, overlays or overclocks were enabled. That distinction is what separates a game bug from a system problem.
Related pages
This is an independent player reference and is not official documentation for Subnautica 2. GameRulePro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.
Keep fixing
Can I run it? FPS calculator
Check whether your hardware, not the settings, is the limit.
Open →All fix & optimization guides
Every crash, black-screen and FPS guide we have published.
Open →Game database
System requirements and projected FPS for 335 titles.
Open →Release calendar
Launch dates and platforms for upcoming games.
Open →