Gothic 1 Remake Crash on Startup PC Fix

What is the Gothic 1 Remake Startup Crash?

The Gothic 1 Remake (Alkimia Interactive / THQ Nordic) is built on Unreal Engine 5.4 and ships with the same shader-precompile and DX12 pipeline pitfalls that have plagued recent UE5 launches like Clair Obscur: Expedition 33, Monster Hunter Wilds, and Avowed. On launch day many players hit a black window followed by LowLevelFatalError [File:Unknown] [Line: 198] Rendering thread exception:, an "Unreal Process has crashed: UE-G1R" dialog, or an instant crash-to-desktop before the menu draws.

When does it occur?

• The first time you launch the game (during shader precompile on first boot).
• After the day-one patch on Steam or GOG.
• When using a fresh NVIDIA Game Ready or AMD Adrenalin driver from the past 7 days.
• When DLSS Frame Generation, FSR 3.1, or XeSS is enabled on a save that was made under a different upscaler.
• When using a controller hooked through Steam Input with Big Picture overlay active.
• On systems with G-SYNC + HDR enabled in the Windows 11 25H2 display panel.

Common causes

• A corrupted UE5 shader cache at %LOCALAPPDATA%\Gothic1Remake\Saved\ShaderCache.
• A stale pipeline.cache left from the pre-launch demo build (Steam app ID 1297900).
• DirectX 12 selected on a GPU that ships better Vulkan stability (RDNA2/RDNA3 AMD cards).
• An RTX 50-series driver bug paired with the UE5 video-engine timeout (NVIDIA 580+ branch).
• Easy Anti-Cheat or BattlEye conflict from a different game blocking the splash process.
• An overclocked GPU memory profile in MSI Afterburner that survives the UE5 shader stress test for 4-5 seconds before crashing.
• Windows 11 "Hardware-accelerated GPU scheduling" toggled OFF, which UE5.4 expects ON for D3D12 residency.

Step-by-step fixes

1. Wipe the shader cache. Close the game, open %LOCALAPPDATA%\Gothic1Remake\Saved\ShaderCache and %LOCALAPPDATA%\Gothic1Remake\Saved\D3DShaderCache, delete every file inside, then relaunch and let the precompile screen run to 100% without alt-tabbing.
2. Force Vulkan on AMD. Right-click the game in Steam, Properties -> General -> Launch Options, paste -vulkan. On NVIDIA RTX 50-series, instead force DX12 with -dx12 and disable Frame Generation in the in-game graphics menu.
3. Update GPU drivers cleanly. Use DDU (Display Driver Uninstaller) in Safe Mode, then install NVIDIA 580.88 WHQL or AMD Adrenalin 26.5.2 — both contain the UE5.4 residency fix.
4. Disable Hardware-accelerated GPU scheduling. Settings -> System -> Display -> Graphics -> Default graphics settings — toggle it OFF if you're on Intel Arc, ON if you're on NVIDIA/AMD. UE5 reacts differently per vendor.
5. Verify integrity in Steam / GOG. Steam: Properties -> Installed Files -> Verify integrity. GOG Galaxy: More -> Manage installation -> Verify / Repair. Any missing .pak file kills the startup loader silently.
6. Disable overlays. Turn off Steam, Discord, NVIDIA App, MSI Afterburner / RTSS, GeForce Experience Game Filters, and Razer Synapse overlays. The RTSS overlay in particular crashes UE5 between the engine init and the first render frame.
7. Set the engine ini to skip the intro. Edit %LOCALAPPDATA%\Gothic1Remake\Saved\Config\Windows\Engine.ini, add [/Script/MoviePlayer.MoviePlayerSettings] then bWaitForMoviesToComplete=False and bMoviesAreSkippable=True. This bypasses the WMF media player crash on N/KN editions of Windows.
8. Reset the GPU clocks. In MSI Afterburner click the reset (curve) button, apply, then re-test. Even +50 MHz on memory is enough to fail UE5's shader precompile sanity check.

If it still doesn't work

Open %LOCALAPPDATA%\Gothic1Remake\Saved\Logs\Gothic1Remake.log and search for the last LogD3D12RHI: Error or LogVulkanRHI: Error line — the message that follows the colon is the actual GPU fault, not the surface-level "fatal error" dialog. Post that line in the official THQ Nordic Discord #g1r-bug-reports channel with your dxdiag.txt attached; the Alkimia QA team has been responding within 24 hours during launch week. If the log ends on Hang detected on GPU 0, your card is being killed by the day-one shader stress — undervolt by 50 mV in Afterburner and try again before assuming hardware failure.