Red Dead Redemption 2’s RAGE engine is unusually talkative when it fails, and that is your biggest advantage. A launch crash almost always leaves an error code in a small dialog or in the Rockstar Games Launcher: ERR_GFX_STATE is the most common and points at the graphics pipeline cache or an overlay hooking the Vulkan renderer; ERR_GFX_D3D_INIT means the DirectX 12 path could not initialize; ERR_MEM_VIRTUAL_INSUFFICIENT and ERR_MEM_EMBEDDEDALLOC_ALLOC are page file and memory problems; and “The Rockstar Games Launcher exited unexpectedly” is the launcher itself, not the game. The game defaults to Vulkan, supports DirectX 12 as an alternative, and keeps every setting in a readable XML file at %USERPROFILE%\Documents\Rockstar Games\Red Dead Redemption 2\Settings\system.xml alongside a set of sga_*.dat pipeline cache files that go stale with each driver update. Because the launch crash happens before you can reach any menu, most fixes below work through that folder, the launcher, and Steam or Rockstar launch arguments. Ordered by frequency and how little they change, this is the sequence that resolves the majority of launch failures in 2026.
- Likely Causes
- Fix 1: Delete the pipeline cache files
- Fix 2: Disable every overlay
- Fix 3: Switch between Vulkan and DirectX 12
- Fix 4: Remove mods and script hooks
- Fix 5: Increase the page file
- Fix 6: Verify game files
- Fix 7: Repair the Rockstar Games Launcher
- Fix 8: Reset system.xml
- Fix 9: Update the GPU driver and return overclocks to stock
- If Nothing Works
- FAQ
Quick answer: Our top pick in 2026 is the Stale pipeline cache (sga_*.dat files) — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Stale pipeline cache (sga_*.dat files) | ERR_GFX_STATE after a driver or game update |
Easy |
| Overlay hooking Vulkan (MSI Afterburner, Discord, GeForce Experience) | Launch succeeds with overlays disabled | Easy |
| Renderer initialization failure (Vulkan or DX12) | ERR_GFX_D3D_INIT or crash before the Rockstar logo; other API works |
Easy |
| Insufficient page file | ERR_MEM_VIRTUAL_INSUFFICIENT or a memory error code |
Moderate |
| Mods left in the game folder | dinput8.dll, version.dll or an lml folder present after an update |
Easy |
| Rockstar Games Launcher or Social Club damaged | “Launcher exited unexpectedly” or sign-in loops | Moderate |
| Corrupted game files | Verification through the launcher or Steam replaces files | Easy |
| Outdated GPU driver or unstable overclock | Event Viewer shows a driver reset; crashes in other games | Moderate |
Fix 1: Delete the pipeline cache files
How to check
If the crash shows ERR_GFX_STATE and started after a GPU driver update or a game patch, the compiled pipeline cache no longer matches the driver.
What to do
Close the game and the Rockstar Games Launcher. Open %USERPROFILE%\Documents\Rockstar Games\Red Dead Redemption 2\Settings and delete every file beginning with sga_ (they have a .dat extension). Leave system.xml alone for now. Launch the game; the first start will take longer while the cache rebuilds. As an alternative that does not delete anything, add -ignorepipelinecache to the launch arguments (Steam: game Properties, Launch Options; Rockstar: Settings, My installed games, Red Dead Redemption 2, Launch arguments).
How to undo it
Nothing to revert for the deletion. Remove the launch argument when you no longer need it.
Fix 2: Disable every overlay
How to check
RDR2’s Vulkan renderer is notoriously intolerant of injected overlays. MSI Afterburner with RivaTuner Statistics Server is the classic ERR_GFX_STATE trigger, followed by Discord, GeForce Experience or the NVIDIA App, Xbox Game Bar, and the Steam and Rockstar launcher overlays.
What to do
Exit RivaTuner Statistics Server and Afterburner completely from the system tray. Turn off the Discord overlay, the NVIDIA in-game overlay, Game Bar, the Steam overlay for RDR2, and in the Rockstar Games Launcher, Settings, uncheck the in-game overlay. Launch. Re-enable one at a time afterward to find the specific culprit.
How to undo it
Reverse each toggle.
Fix 3: Switch between Vulkan and DirectX 12
How to check
Because you cannot reach the in-game menu, the renderer is controlled in system.xml. Open it in Notepad and look for the <API> line; it reads kSettingAPI_Vulkan or kSettingAPI_DX12. ERR_GFX_D3D_INIT means DX12 failed; a crash with no code on Vulkan suggests trying DX12.
What to do
Close the game. Back up system.xml, then edit the <API> value to the other renderer and save. Alternatively add -vulkan or -dx12 to the launch arguments, which overrides the file. Vulkan usually performs better on AMD and modern NVIDIA hardware; DX12 is sometimes more tolerant of overlays and older drivers.
How to undo it
Restore the backed-up system.xml or remove the launch argument.
Fix 4: Remove mods and script hooks
How to check
Look in the game’s install folder (Steam: Steam\steamapps\common\Red Dead Redemption 2) for dinput8.dll, version.dll, ScriptHookRDR2.dll, an lml folder or a ModManager folder. Any of these after a game update will crash on launch until the mod is updated, and they also block Red Dead Online.
What to do
Move those files and folders to a backup location outside the game directory. Launch. If stable, wait for updated mod versions before restoring them.
How to undo it
Move the files back.
Fix 5: Increase the page file
How to check
ERR_MEM_VIRTUAL_INSUFFICIENT or ERR_MEM_EMBEDDEDALLOC_ALLOC in the crash dialog is explicit: the game asked for virtual memory it could not get. A disabled or tiny page file, common after “optimization” guides, is the usual cause.
What to do
Open System Properties, Advanced, Performance Settings, Advanced, Virtual Memory. Enable automatic management, or set a custom size of at least 16384 MB initial and maximum on your system drive. Reboot.
How to undo it
Return to the same dialog and restore your previous configuration.
Fix 6: Verify game files
How to check
A crash right after the Rockstar logo, or an error naming a missing file, suggests damaged content.
What to do
Rockstar Games Launcher: Settings, My installed games, Red Dead Redemption 2, Verify Integrity. Steam: right-click the game, Properties, Installed Files, Verify integrity of game files. Epic: Verify from the library. Let it complete and launch again.
How to undo it
Not applicable.
Fix 7: Repair the Rockstar Games Launcher
How to check
“The Rockstar Games Launcher exited unexpectedly,” a sign-in loop, or a launcher that closes as soon as the game starts points at the launcher or Social Club rather than RDR2.
What to do
Close the launcher. Delete the contents of %LOCALAPPDATA%\Rockstar Games\Launcher except the Profiles folder if you want to keep local sign-in data. Reinstall the Rockstar Games Launcher from its installer; the game itself is not removed. Add the launcher and game folders to your antivirus exclusions, and if Windows Security’s Controlled Folder Access is on, allow RDR2.exe and the launcher to write to Documents, since the game must write system.xml there.
How to undo it
Remove the exclusions and Controlled Folder Access allowances.
Fix 8: Reset system.xml
How to check
If the game crashes at the same point regardless of renderer and overlays, a stale display value such as an unsupported resolution or refresh rate may be to blame.
What to do
Close the game. Rename system.xml to system.xml.bak. Launch; the game recreates defaults in a safe mode. Rebuild your settings in the menu once you are in.
How to undo it
Delete the regenerated file and restore the backup.
Fix 9: Update the GPU driver and return overclocks to stock
How to check
Event Viewer, Windows Logs, System, will show a display driver warning near the crash if the driver is involved. ERR_GFX_STATE also appears on GPUs with unstable memory overclocks, including factory-overclocked cards under load.
What to do
Install the current driver with the clean installation option and repeat Fix 1, since a new driver invalidates the cache. Reset any GPU overclock to stock in your tuning software, and disable XMP/EXPO and CPU overclocks in BIOS for testing.
How to undo it
Roll back the driver and reload your saved overclock profiles.
If Nothing Works
Write down the exact error code and check Rockstar Support’s article for that code; most are documented. Look in Event Viewer’s Application log for the faulting module named alongside RDR2.exe. Test a fresh Windows user account and a launch with no third-party software running. If you own the game on Steam, try launching PlayRDR2.exe from the install folder directly to see whether the Steam layer is involved. Persistent ERR_GFX_STATE at stock settings with no overlays is rare and usually indicates a driver regression, in which case rolling back one driver version and waiting for the next is the practical answer.
FAQ
What does ERR_GFX_STATE mean?
The renderer hit an invalid state, most often from a stale pipeline cache, an overlay hook or an unstable GPU overclock. Delete the sga_*.dat files and disable overlays first.
Is Vulkan or DirectX 12 better for RDR2?
Vulkan usually performs better and is the default; DirectX 12 is the fallback when Vulkan crashes. Both are set through system.xml or launch arguments.
Will deleting the sga files lose my saves?
No. Saves live in a separate Profiles folder under Documents\Rockstar Games\Red Dead Redemption 2 and are synced to the Rockstar cloud.
Why does the game crash only after a driver update?
The pipeline cache is compiled against a specific driver. A new driver invalidates it, and the game does not always rebuild it cleanly on its own.
Ready to decide? Our #1 pick for 2026 is the Stale pipeline cache (sga_*.dat files).
Live price & availability on Amazon.
