Fix Avowed “Fatal Error” / Crash on Launch by Disabling Ray Tracing
DagdaKamiDec 29, 2025 @ 4:50pm381
Modding or ConfigurationEnglish
How to fix
In %LOCALAPPDATA%\Alabama\Saved\Logs\, the log contains errors like: RayTracingDevice->CreateStateObject ... DXGI_ERROR_DEVICE_REMOVED and/or “GPU Crashed or D3D Device Removed.”
Fix (works even if you cannot reach the in-game settings)
Open Steam, go to Library.
Right-click Avowed → Properties.
Under General → Launch Options, add: -noraytracing
Launch the game.
Why this works
This crash can occur during DirectX 12 ray tracing pipeline initialization, where the game can trigger a GPU device removal/reset (DXGI_ERROR_DEVICE_REMOVED).
Optional: If you still crash
Try forcing DirectX 11 instead: set Launch Options to -d3d11 (remove other flags while testing).
Verify game files in Steam (Properties → Installed Files → Verify integrity).
Do a clean GPU driver update, and disable overlays (Steam/Discord/GeForce/AMD), which are common UE crash contributors.
Where to find the log (for confirmation)
Logs: %LOCALAPPDATA%\Alabama\Saved\Logs\
Crashes: %LOCALAPPDATA%\Alabama\Saved\Crashes\
Fix (works even if you cannot reach the in-game settings)
Open Steam, go to Library.
Right-click Avowed → Properties.
Under General → Launch Options, add: -noraytracing
Launch the game.
Why this works
This crash can occur during DirectX 12 ray tracing pipeline initialization, where the game can trigger a GPU device removal/reset (DXGI_ERROR_DEVICE_REMOVED).
Optional: If you still crash
Try forcing DirectX 11 instead: set Launch Options to -d3d11 (remove other flags while testing).
Verify game files in Steam (Properties → Installed Files → Verify integrity).
Do a clean GPU driver update, and disable overlays (Steam/Discord/GeForce/AMD), which are common UE crash contributors.
Where to find the log (for confirmation)
Logs: %LOCALAPPDATA%\Alabama\Saved\Logs\
Crashes: %LOCALAPPDATA%\Alabama\Saved\Crashes\