Red Dead Redemption 2 — Common Errors & How to Fix Them

The errors Red Dead Redemption 2 players actually hit on PC, what causes each one, and the fix that works.

Last updated 2026-09-25 · evergreen reference

These are the failures that Red Dead Redemption 2 players report most often, with the cause behind each one rather than a list of things to try at random. Because Red Dead Redemption 2 has online play, anti-cheat and network-related failures are included alongside the graphics ones.

Errors, causes and fixes

Start from the symptom that matches yours.

ERR_GFX_STATE after loading into story mode

What is happening: A Vulkan pipeline-cache fault. Rockstar documented this one; it returns whenever the cache is rebuilt badly.

Fix: Switch Graphics API to DirectX 12, or delete every file starting with sga_ (e.g. sga_vulkan_final_init.vkPipelineCacheWindows) in Documents\Rockstar Games\Red Dead Redemption 2\Settings. You can also add -ignorepipelinecache as a launch argument.

Out of Memory on 8 GB cards

What is happening: Ultra textures and MSAA push past the VRAM budget, and the page file is too small to absorb the overflow.

Fix: Texture Quality to High, MSAA off, resolution scaling at 100% or lower. Set the page file to 1.5x initial and 2–3x maximum of your installed RAM, then restart.

"Unexpectantly closed" with no error text

What is happening: On NVIDIA cards, the game can fail when the default audio output device is not the NVIDIA High Definition Audio device.

Fix: Right-click the speaker icon in the tray, open Sound settings, and select NVIDIA High Definition Audio under Output.

Black screen on launch or freeze during missions

What is happening: Intro video playback or a stuck graphics state after a driver change.

Fix: Disable fullscreen optimizations on both PlayRDR2.exe and RDR2.exe, then verify files. If it persists, switch API and clear the sga_ files again.

The order to work in

Cheapest and most reversible first.

1. Rule out the universal causes

Verify game files, update the GPU driver with a clean install, and close overlays, recorders and RGB utilities. Across every engine, these three resolve the largest share of crashes before you touch anything game-specific.

2. Match the fix to the symptom

A crash that happens in the same place every time in Red Dead Redemption 2 is usually asset or configuration damage — a cache, a config file or a mod. A crash that happens at random intervals is far more often a driver, an overlay, thermals or unstable memory tuning.

3. Change one thing, then retest

Load the same save, visit the same area and repeat the same action. If you change five settings at once you will never learn which one mattered, and you will end up reinstalling a game that did not need it.

Collecting evidence

What to gather before you ask anyone for help.

Logs beat descriptions

Most engines write a log you can attach: Warframe keeps EE.log in %LOCALAPPDATA%\Warframe, tModLoader writes client.log under Documents\My Games\Terraria\tModLoader\Logs, and Fallout 4 with Buffout 4 writes crash logs to My Games\Fallout4\F4SE. Find the equivalent for Red Dead Redemption 2 before you post.

Note the trigger and the timing

Whether it crashes on launch, in a specific area, after a set number of minutes, or only online. That single distinction separates config damage from thermals from network faults, and it is the first thing any support agent will ask.

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.