Subnautica 2 PC Crashes: DX12, GPU Selection, Drivers, and Config Fix Guide

Subnautica 2’s launch has been marred by a frustrating cascade of crashes that hit the moment players try to dive in. AMD’s June 2026 driver notes (version 26.6.2) explicitly acknowledge a stack of launch-time failures tied to DirectX 12, incorrect GPU selection, and driver incompatibilities—issues that have turned the ocean floor into a bluescreen for thousands of Windows 11 users. The game’s engine, built on Unreal Engine 5 with mandatory DX12 Ultimate features, is exposing hardware and software mismatches that other recent releases have so far sidestepped.

The Crash Stack: DirectX 12, GPU Selection, and More

The typical crash sequence is brutally simple: double-click the shortcut, see the black screen, and within 15 seconds get a “Fetal error” message or a complete system hang requiring a hard reset. Event Viewer logs show a mix of LiveKernelEvent 141 (hardware error), nvlddmkm crashes on Nvidia, and amduw23g on AMD—all pointing to GPU timeout detection and recovery (TDR) failures. AMD’s release notes for Adrenalin 26.6.2 confirm that the game “may experience an application crash or driver timeout on Radeon RX 7000 series products when using DirectX 12 API with certain graphics settings.”

But it isn’t just AMD hardware. Nvidia RTX 30 and 40 series cards are also affected, primarily because the game insists on launching on the wrong GPU. Laptops with switchable graphics (Optimus or AMD SmartShift) are the worst hit: the game detects the integrated Intel or AMD Radeon iGPU instead of the discrete Nvidia or AMD dGPU. The resulting memory allocation failure or DX12 feature set mismatch causes an instant crash. Desktop users with multiple GPUs (e.g., an Intel UHD 770 alongside an RTX 4080) are seeing the same problem because the game defaults to the first enumerated adapter, which is often the iGPU.

GPU Selection: The Multi-GPU Dilemma

The fix for GPU selection is straightforward but buried in Windows settings and vendor control panels. You need to force the game to use the high-performance GPU on three levels:

• Windows Graphics Settings: Go to Settings > System > Display > Graphics. Click “Browse,” navigate to Subnautica2.exe (usually in Steam\steamapps\common\Subnautica2\Binaries\Win64), select it, and set “Options” to “High performance.”
• Nvidia Control Panel: Open Nvidia Control Panel, go to “Manage 3D Settings” > Program Settings. Add Subnautica2.exe and set “Preferred graphics processor” to “High-performance Nvidia processor.” Also, under “Configure Surround, PhysX,” ensure the PhysX setting is set to your dedicated GPU, not “Auto-select” or CPU.
• AMD Software: Open AMD Software, go to Gaming > Games, find Subnautica2, and set “GPU Workload” to the dedicated Radeon GPU. For laptops, you may need to add the game to the “Switchable Graphics Application Settings” and force “High Performance.”

After making these changes, reboot your system. This alone has resolved crashes for roughly 40% of affected users, according to community reports on the Steam forums and Reddit.

DirectX 12: The Core Culprit

Subnautica 2’s reliance on DX12 Ultimate features—ray-traced audio, mesh shaders, and sampler feedback—means it will not gracefully fall back to DX11 or even a lower feature level. If your GPU doesn’t support full DX12 Ultimate (hardware feature level 12_2), you’ll hit a wall. But even compatible cards are failing because drivers and the OS are not properly handling the game’s memory management.

AMD’s driver notes detail that the crash is specifically triggered when the game allocates ReBAR (Resizable BAR) memory pages in an unconventional order, leading to a GPU page fault. Nvidia users experience a similar issue, which manifests as a “DXGI_ERROR_DEVICE_REMOVED” or “DXGI_ERROR_DEVICE_HUNG” message. Both vendors are working with the developer, Unknown Worlds, on a permanent engine-side patch, but users can take immediate action.

Workaround A: Disable Resizable BAR in your motherboard BIOS. This lowers performance slightly but eliminates a large percentage of DX12 crashes. Reboot into BIOS, find “Above 4G Decoding” and “Resizable BAR” or “Smart Access Memory” and set them to Disabled.

Workaround B: Force a DX12 feature level reduction by adding launch options in Steam. Right-click Subnautica 2 in your library, select Properties, and in the Launch Options field, type: -d3d12 -FeatureLevel=12_1. This instructs the engine to use DX12 but limit itself to feature level 12_1, which avoids the problematic mesh shader path. Note: you may lose ray-traced audio quality.

Workaround C: Increase the TDR delay in Windows Registry to give the GPU more time to recover before Windows kills the driver. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers and create or modify the DWORD value TdrDelay to 10 (decimal). Reboot. This prevents the system from thinking the GPU is hung during the initial shader compilation phase, which can take over 5 seconds on first launch.

Driver Woes: AMD and Nvidia Users Affected

AMD’s Adrenalin 26.6.1 drivers, released just days before Subnautica 2’s early access, are notorious for crashing the game within minutes. The hotfix 26.6.2, released on June 18, 2026, addresses “application crash or driver timeout in Subnautica 2 during menu navigation and gameplay transitions.” If you’re on 26.6.1, update immediately. For Nvidia, the Game Ready Driver 555.99 (released June 12, 2026) included a profile for Subnautica 2, but users report that the driver still fails when hardware-accelerated GPU scheduling (HAGS) is enabled. Nvidia’s latest hotfix driver 556.05, available only through their customer support page, reportedly mitigates the issue.

Clean driver installation is non-negotiable. Use Display Driver Uninstaller (DDU) in Safe Mode to wipe all remnants of the previous driver before installing the new one. This clears out shader caches and registry entries that conflict with the game’s shader precompile step.

A quick compatibility list for GPUs based on user feedback:

Configuration File Tweaks That Can Save Your Game

Subnautica 2 uses Unreal Engine 5’s standard configuration system. You can fix many crashes by editing Engine.ini and GameUserSettings.ini, located in %LOCALAPPDATA%\Subnautica2\Saved\Config\WindowsNoEditor.

Disable Async Compute — Async compute can cause timeouts on AMD and older Nvidia cards. Add these lines to Engine.ini:

[SystemSettings]
r.AsyncCompute.Support=0

Limit VRAM Usage — The game aggressively allocates VRAM, sometimes exceeding the GPU’s capacity and causing out-of-memory crashes. Force a limit in GameUserSettings.ini:

[/Script/Engine.GameUserSettings]
TextureQuality=2
ShadowQuality=2
PostProcessingQuality=2

Setting these to “2” (High instead of Epic) reduces VRAM footprint by roughly 1.5GB on 4K textures.

Reduce Shader Cache Pressure — UE5’s shader precaching can stall the GPU. Add to Engine.ini:

[SystemSettings]
r.Shaders.Optimize=1
r.CreateShadersOnLoad=1

Disable Fullscreen Optimizations — Windows 11’s fullscreen optimizations often conflict with DX12. Right-click Subnautica2.exe, select Properties > Compatibility, and check “Disable fullscreen optimizations.” Then in GameUserSettings.ini, force true exclusive fullscreen:

FullscreenMode=1
LastConfirmedFullscreenMode=1

After editing, set the file to read-only to prevent the game from overwriting your changes.

Windows 11 Game Mode and Hardware-Accelerated GPU Scheduling

Two Windows 11 features are actively breaking the game for many: Game Mode and Hardware-Accelerated GPU Scheduling (HAGS). Game Mode can starve background processes of GPU time, but Subnautica 2’s shader compilation threads run as “background” processes and get terminated, causing a crash. HAGS, meanwhile, introduces latency in GPU scheduling that can trigger a TDR when the game sends intensive command buffers.

Disable both:
- Game Mode: Settings > Gaming > Game Mode > turn off.
- HAGS: Settings > System > Display > Graphics > “Change default graphics settings” > turn off “Hardware-accelerated GPU scheduling.” Reboot.

These two toggles alone have fixed crashes for many users who had already updated drivers and set the correct GPU.

Community-Proven Fixes and Workarounds

Beyond the major fixes, a collection of smaller tweaks have emerged from the community. These are low-risk and often resolve the last stubborn crashes:

• Verify game files: In Steam, right-click the game > Properties > Installed Files > “Verify integrity of game files.” Corrupted shader precompiles are common after a crash.
• Run as Administrator: The game needs write access to the config folder; some Windows user profiles restrict this. Set Subnautica2.exe to always run as admin.
• Disable overlays: Steam overlay, Discord overlay, Nvidia ShadowPlay, and AMD ReLive all inject into the DX12 pipeline and can cause device removal errors. Disable them all as a test.
• Increase virtual memory: If you have less than 32GB of RAM, set a manual page file size of 16GB minimum on your SSD. This prevents “out of memory” errors during level transitions.
• Temporarily disable XMP/DOCP: Unstable RAM overclocks cause data corruption in the GPU driver; run your memory at JEDEC speeds (e.g., 4800MHz DDR5) to rule this out.
• Delete the config folder: If all else fails, delete %LOCALAPPDATA%\Subnautica2\Saved\Config and let the game regenerate it. This clears any corrupted settings.

Looking Ahead

Unknown Worlds has acknowledged the “crash stack” in a Steam news post, promising a patch within two weeks that will address the GPU selection logic and DX12 allocation errors at the engine level. AMD and Nvidia are expected to release further driver updates with game-specific profiles. In the meantime, these fixes have helped a growing number of players get past the splash screen and into the alien ocean. The community’s troubleshooting efforts, documented across the Steam forums and r/Subnautica2, have turned into a living guide—proof that early access isn’t just about finding bugs, but also about a community that dives deep to solve them.