Game Crashes

[Mopar63]

While playing story mode I have experienced game crashes after around an hour of play.

System specs are a Ryzen 3800X, 16GB of DDR4 3200, 1TB NVME drive, Sapphire Pulse 5700XT (Latest AMD drivers)

Game settings are for 1440P with in game settings tweaked to give an average of about 90 FPS using the benchmark. Game play is very smooth.

What happens is the game starts fine, a few minutes into play the screen flashes to show my desktop then comes back to the game and appears to run fine. Can game for about an hour and then the game crashes out, without an error message. Looking at the event viewer I see the error listed below. I have tried the removal of the SGA files, run in Vulkan and DX12, clean removal and reinstall of drivers, clean Windows install. I have turned off every background app on the system so only Steam is running. This is very frustrating as the save system is not easy to use and I often lose a LOT of the game play I have completed and am forced to go over it again.
 

 

 

 

Quote

Faulting application name: RDR2.exe, version: 1.0.1311.12, time stamp: 0x5f16fa51
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000001
Faulting process id: 0x1424
Faulting application start time: 0x01d6733522ef47be
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Red Dead Redemption 2\RDR2.exe
Faulting module path: unknown
Report Id: 9ad0e757-e227-4c63-9192-7310b414404c
Faulting package full name: 
Faulting package-relative application ID: 

 

[~Tiger~]

Hello.

 

Have your problems started after the release of the update which was released at the beginning of the week?

[Mopar63]

Sounds about right, however it is not on every system. I just tried using my backup computer and it is working fine...

 

[fainflynn]

my game also crashes.  in one instance...and happens to crash every time.  this is when confrontinig emmett grainger and blowing up the pile of pig poop.  always crashed at the explosion.  this just started with the last update.  always worked before