Crash & Startup / Red Dead Redemption 2 / RAGE

Red Dead Redemption 2: Fixing ERR_GFX_STATE and RAGE Launch Crashes

A practical recovery path for Red Dead Redemption 2’s ERR_GFX_STATE, Vulkan/DX12 startup failures, and corrupted settings.

Official Steam Store header artwork for Red Dead Redemption 2.

ERR_GFX_STATE is RAGE telling you the graphics state file or device creation failed. The file is not your save, so it can be rebuilt — carefully.

Fixing ERR_GFX_STATE and RAGE Launch Crashes

Verified field fix

The shortest safe order for this issue:

  1. Back up the Settings folder and delete only the generated graphics state file.
  2. Try DirectX 12 or Vulkan separately with overlays disabled.
  3. Verify the game files and remove any GPU tuning profile before the next launch.

Reset only the graphics state

Exit the game and Rockstar launcher, back up the Settings folder, and remove the generated graphics state file. Do not delete the whole profile or save folder. Launch in windowed mode at a conservative resolution and let the game recreate the settings.

PowerShell — inspect and back up RDR2 settings
$settings = Join-Path $env:USERPROFILE "Documents/Rockstar Games/Red Dead Redemption 2/Settings"
$backup = Join-Path $env:USERPROFILE "Desktop/RDR2-settings-backup"
if (Test-Path $settings) {
  Copy-Item $settings $backup -Recurse -Force
  Get-ChildItem $backup -File | Select-Object Name, Length, LastWriteTime
}
This copies the settings; it does not delete them. Remove only the generated graphics state after the backup is confirmed.

Test APIs one at a time

DirectX 12 and Vulkan can behave differently with the same driver. Test one API, one overlay state, and one GPU clock profile at a time. Return the driver to stock settings if the crash follows a new undervolt or overclock.

Field notes before you change the build

A crash report for Red Dead Redemption 2 is only useful if it can be repeated. Record the last visible frame, the exact game build, the GPU driver, and whether the failure happens before or after the anti-cheat splash. “It crashed” is a category, not a reproduction.

If the client fails again after a clean launch, test a second save or a fresh profile before changing the RAGE configuration. That separates a local game-state problem from a client, driver, or protected-launch problem.

  • Do not delete the entire config, save, or game folder before making a backup.
  • Do not reinstall Windows for a single-title startup failure.
  • Do not stack launcher flags and driver rollbacks in the same test run.

Check it before you keep it

Launch in windowed mode with the conservative profile

0 / 5 complete

Keep the rollback boring

A known-good local profile and one current log are more valuable than another speculative repair pack. If the fix works, save the exact steps with the patch number.

The line to keep

Rebuild the graphics state, not the save. A clean settings reset and one API at a time solve most RAGE startup errors.

Did this fix work on Patch 1.0.1491.50 — launcher stability?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 1.0.1491.50 — launcher stability. Votes are local-only telemetry.

Red Dead Redemption 2: bench questions

2 answers
Will deleting the settings remove my Red Dead story progress?
Settings and saves are separate. Back up both, but delete only the generated graphics state when troubleshooting this error.
Is Vulkan better than DirectX 12?
It depends on your GPU and driver. Test the same save and route with each API rather than assuming one is universally faster.
Filed under

Crash & Startup

Patch tested: 1.0.1491.50 — launcher stability

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.