Error Troubleshooting

RDR2_b1491.exe!sub_142C1EB38

Likely Cause

RedM client crash caused by an internal error or server-side script conflict. This issue was widely reported after a RedM update (crashing all servers regardless of custom mods) GITHUB.COM , and community members have noted it can be triggered by a misbehaving server mod REDDIT.COM .

Recommended Fixes

1. Clear the RedM cache (delete caches.xml and the cache folder) to remove any corrupted data.

2. Verify your RDR2 game files via Steam/Epic/Rockstar launcher to fix any missing or damaged base game files.

3. Update RedM to the latest version – ensure you’re on the newest RedM client, as such crashes introduced by updates are often fixed in subsequent patches.

4. Contact the server admins or try a different server – if the crash occurs only on a specific server, alert its developers (the issue may stem from a buggy resource on the server).

RDR2_b1491.exe!sub_14111C988

Likely Cause

RedM client crash likely caused by a buggy server resource or game state glitch leading to an access violation. In practice, many “sub_*****” crashes are linked to server-side script issues. (e.g. a mod triggering a client error) or occasional client-side hiccups after extended play (e.g. crashes after spending time in densely populated areas).

Recommended Fixes

1. – Delete RedM caches and restart the game (to refresh any cached scripts or data)

2. Check for game file integrity by running a file verify for RDR2 (corrupt game files can cause unpredictable crashes).

3. Reduce mod load if possible: avoid doing the specific in-game actions or areas right before the crash (as a temporary workaround) and see if stability improves.

4. Report the issue to server owners – if multiple players on the same server get this crash, the server developers should investigate and update/remove the faulty script.

RAGE error: 0x9952DB5E:212

Likely Cause

A graphics-related RAGE engine error (commonly the ERR_GFX_STATE crash in RDR2). This often stems from GPU driver or API conflicts – for example, an unstable GPU driver or factory overclock can trigger graphics device crashes in RedM.

In other cases, using the Vulkan vs. DX12 rendering API can cause issues on certain systems.

Recommended Fixes

1. Switch Graphics API – change RDR2’s rendering API from Vulkan to DirectX 12 (or vice versa). You can do this by editing the System.xml in your RDR2 Documents settings (replace "VULKAN" with "DX12" or vice versa)

, or by launching RDR2 single-player and toggling the API in the graphics settings

2. Update or Roll Back GPU Drivers – ensure your graphics drivers are up to date, or try using a known stable driver version. Some players fixed this error by downgrading Nvidia drivers (especially for RTX 3080/3090 series cards) because newer drivers or GPU overclocks caused instability

3. Clear shader/cache files – delete any .sga files in your Documents Rockstar Games RDR2 settings folder to clear cached shaders (they will regenerate). Also consider clearing RedM’s cache and updating DirectX.

4. Other tips – run the game in windowed mode if fullscreen is crashing, and disable any overlay or background app that might hook into the game. These steps can sometimes bypass graphics initialization errors.