Question High end PC suddenly crashes while playing RDR2 - - - it never happened before ?

theRTT

Distinguished
Jul 25, 2016
416
5
18,965
So basically what the title says. Since this week, my pc started crashing. It happens when I play Red Dead Redemption 2. The screen goes black, all fans ramp up to 200% and I hear an error sound. Sometimes the audio keeps on playing for a while. Now this has never happened before. Nothing changed to my pc and all drivers are up to date. How can this suddenly happen? I did not really change any of the settings in the game either. I play other games too, but they don't have this problem.

The temperatures also look fine.

My PC:
Gigabyte AORUS GeForce RTX 3080 Master 10G
AMD Ryzen 7 5800X
32GB RAM

I have the GPU underclocked because it had problems with it's original clock speed. That gave errors as well, but these are different. The errors I had then actually closed my game with an error that I could read. This one just shuts down my entire PC.

Can anyone help me out with this?
 
Follow up, now after another crash, I get this message on starting up the game:

ERR_GFX_D3D_DEFERRED_MEM
Out of memory. Please reboot, close other applications and ensure your computer meetsthe minimum requirements. For more information, please visit: https://support.rockstargames.com

I am pretty sure my PC does meet the requirements.
 
We will need more information.
Full component list with make/model/variant details, along with age of the build, OS version and temp details.

As Hellfire stated more info is needed.
However to give you a simple example of software that is not normally updated, Chipset Drivers!
Besides that, you could look and see if the RDR2 game settings have not changed from what you were able to play stably at before this started happening, driver changed?

I know lots of games only run at certain settings no matter the hardware, otherwise error such as your describing occurs.
 
Everything is up too date! I check those items quite often. But still, even if they are outdated, they worked fine with the "outdated" drivers. So why would that change?

RDR2 settings are the same.

OS: Windows 11

The system is around 3-4 years old.


Yesterday I played for almost two hours without crashing, recording with Nvidia Shadowplay, trying to capture what happened. But it did not crash. So when I tried to replicate the problem it didn't happen. I did use MSI Afterburner to set the clock speed to underclock it with -100 again, maybe that was bugged out and not applied anymore?

Also with MSI Afterburner I saw that the temperatures are normal: GPU around 70-75 C and the CPU around 60-65 C. GPU usage was around 99% though, but that seems all right. Would you like to see more and other information?

theRTT
 
Last edited:
That's a pretty good configuration.

Based on the last error message, it sounds like VRAM saturation during some kind of load/activity spike. This might happen sometimes due to some kind of overlay or shader cache overload.

I would be rather interested to know if this can be replicated with only the game running without any other/background apps.
 
Well, it happened again. Now with a recording, but by looking at the data in Afterburner, I don't see anything really out of the ordinary.

This was also without any background apps open.

View: https://youtu.be/6nnw6oc0Qa0


I really have no clue why this is suddenly happening. Any ideas on software I can monitor this with?
 
Well, it happened again. Now with a recording, but by looking at the data in Afterburner, I don't see anything really out of the ordinary.

This was also without any background apps open.

View: https://youtu.be/6nnw6oc0Qa0


I really have no clue why this is suddenly happening. Any ideas on software I can monitor this with?
I would try to reinstall the latest graphics driver after removing them with DDU. I would then make sure that all settings are default with the graphics card and test. If there are any issues again, try increasing the voltage on the graphics card and doing another -100 core clock offset and a -250 or -500 on the memory. Test again.
 
Last edited: