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 fixThe shortest safe order for this issue:
- Back up the Settings folder and delete only the generated graphics state file.
- Try DirectX 12 or Vulkan separately with overlays disabled.
- 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.
$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
} 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 completeKeep 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 answersWill deleting the settings remove my Red Dead story progress?
Is Vulkan better than DirectX 12?
Crash & Startup
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.
Red Dead Redemption 2: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Red Dead Redemption 2 on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on RAGE.
Red Dead Redemption 2: Shader Stutter, Frame Pacing & RAGE Config Tuning
A measured stutter-hunting routine for Red Dead Redemption 2: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact RAGE settings file to edit.
Red Dead Redemption 2: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Red Dead Redemption 2 without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.