Red Dead Redemption 2 — How to Fix "ERR_GFX_STATE"

What causes the ERR_GFX_STATE error in Red Dead Redemption 2, and the fixes in the order that works.

Last updated 2026-09-25 · evergreen reference

The "ERR_GFX_STATE" failure in Red Dead Redemption 2 has a specific cause, and knowing it saves you from working through a dozen unrelated fixes. This page covers what the error actually looks like, why it happens, and the fixes ranked by how often they work.

What the error looks like

Confirm you are dealing with the same failure.

Recognising "ERR_GFX_STATE"

The game loads to the main menu, then closes with an "ERR_GFX_STATE" error the moment you continue into story mode. Some players only hit it after reaching a specific point in the story; others get it on every launch.

Why it happens

The cause determines the fix.

Cause 1

A Vulkan pipeline-cache fault. The error is tied to the Vulkan renderer specifically — players already running DirectX 12 generally do not see it.

Cause 2

The cache files become corrupt and the game fails to rebuild them cleanly, which is why deleting them works but the error often returns on the next launch until you also change the API.

Cause 3

A third-party startup item interfering with the renderer at initialisation, which is why disabling startup apps fixes it for a subset of players.

Fixes, in the order that works

Cheapest and most reversible first.

Switch the graphics API to DirectX 12

In Settings > Graphics > Advanced, change Graphics API from Vulkan to DirectX 12 and restart. This is the simplest fix and the one Rockstar’s own support path points at. You can switch back to Vulkan later by loading a save on DX12 first.

Delete the sga_ pipeline cache files

Go to Documents\Rockstar Games\Red Dead Redemption 2\Settings and delete every file beginning with sga_ (for example sga_vulkan_final_init.vkPipelineCacheWindows). Launch, load your save, move the character to a different area and make a new save.

Add -ignorepipelinecache

In Steam: right-click the game > Properties > Launch Options. On Epic: Settings > the game > Additional Command Line Arguments. Rockstar documented this argument for exactly this error.

Edit system.xml by hand if the menu will not open

In Documents\Rockstar Games\Red Dead Redemption 2\Settings, open system.xml and change kSettingAPI_Vulkan to kSettingAPI_DX12. This is the recovery path when the game crashes before you can reach Settings.

Rule out startup conflicts and stale drivers

Disable third-party startup items and services via Task Manager and msconfig, then test. If the error began right after a driver update, roll the driver back rather than forward.

How to confirm it is fixed

One successful launch is not proof.

Retest properly

Load the exact save that was failing, ride for ten minutes through a demanding area, then quit and relaunch once more — the error frequently returns on the second launch if only the cache was deleted and the API was never changed.

If none of this works

What to do after the list is exhausted.

Gather evidence before asking

Collect your crash log, a DxDiag and the list of fixes you already tried. For Red Dead Redemption 2, support will ask for all three, and a report with evidence gets a far better response than "it crashes".

Reinstall last, not first

A reinstall is the most time-consuming fix and repairs the same files that verification and cache repair handle in minutes. Try it only after the targeted fixes above have failed.

Related pages

This is an independent player reference and is not official documentation for Red Dead Redemption 2. GameRulePro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.

Keep fixing

Related tools from our network

A focused set of free calculators and guides across related topics — no account required.