[SOLVED] err_gfx_state with MSI Afterburner

[「WarningToxic」]

The problem occurs because of your GPU clock does not sync RDR2 Engine. So the game shuts down. Therefore, we are going to downgrade the clock speed (Same as gpus that does not have OC feature)

I was having this problem after 5-10 mins in the game. I did quick research and found the solution. Never had the crash again.

My pc specs :

Intel Core i7 7700K @ 4.20GHz
16,0GB RAM
NVIDIA GeForce GTX 1080 OC

Solution:

Download MSI afterburner
Go to Settings - User Interface - MSI GAMING AFTERBURNER SKIN BY DREREX DESIGN (Pick this to prevent confusion, have same skin as mine)(See the link below)

At this point you should have this skin. Do not touch anything but Core Clock (Mhz)
Put number between -400 and -200 ( I put -204 works great for me )
Click accept
Play the game without crash

(To return to default settings simply put 0 on Core Clock (Mhz)

https://imgur.com/a/Po0YDrO

[Sorrow]

Originally posted by 「WarningToxic」:

The problem occurs because of your GPU clock does not sync RDR2 Engine.

And from where did you found this info exactly?

Your solution doesnt make any sense...
Differend GPU's have differend range of clock speed.
How do you know on what clock speed engine prefers to be played... and if so, why is that?

There are X solutions on this topic with people THINKING they fixed the problem because they dont recieve GFX error any more (for now).
That doesn't mean that with the next R update that error wont be back again.

This is on Rockstar's side... and has nothing to do with your hardware or software.
I know this because i have this error only if i alt-tabbed while loading in the online mode for the first time. The entire storyline was completed without single error on my side.

THERE IS NO CONFIRMED FIX FOR THIS....

[「WarningToxic」]

And have you tried it before you ♥♥♥♥♥ posting ? It worked for me guys. No harm to try it.

[Sorrow]

Originally posted by 「WarningToxic」:

And have you tried it before you ♥♥♥♥♥ posting ? It worked for me guys. No harm to try it.

This has nothing to do with ♥♥♥♥♥ posting.
I gaved you a valid response.... you however didn't respond what a valid argument.

Downcloacking your GPU will only give you less FPS in any game.

It won't fix any crashes,stuttering or freezes... because it has nothing to do with them in the first place. Only OC coud crash your game and that coud be on your end... not downclocking.

It ,,worked,, for you without even knowing why in the first place.
Nice solution you got there...

There is harm.
If you got a good GPU, downloacking coud even go back and even match the performances of the previous model.
Why do that? What's the logic behind it?
Exactly.... none.

[GOD RAYS ON ULTRA™]

Factory overclocks are too unstable for this game. Just use debug mode in nvidia cp no need for third-party software.
This game came to pc after these overclocked cards were engineered. Makers of these cards didn't understand the scale of this game and how it will push the system. So you can return your gpu to reference nvidia values and be much more stable.
Overclocking has went from a competitive sport to a marketing gimmick. The overclocked cards catch the consumers eye. What you really want though is a reference nvidia gpu. Just a good old-fashioned reference gpu without all of the marketing hoo-hah

[kon]

Totally worked for me! Thanks very much WarningToxic!

[~m3rcy~]

I too was getting this error numerous times daily during play. The last patch and some other tweeks I applied has my system stable, not perfect but can now last a day without issues. Some days I do get an error but now its a rare instance.
I'm currently running my EVGA 1080ti FTW3 custom loop at +500 mem and +100 core OC (Temp at load 32c).
Lowering your specs as you suggested does have logical grounds. GPU run hot even at stock speed, this leads to the GPU scaling back or game instability. It's like driving your car at high RPM vs low RPM. Issues will more like show up during sustained high RPM.

[Noxsa]

Boys, look the REAL problem was or is, just install some monitor software and look at what value the GPU CORE is running at.
i tested this like a ton, every time my GPU CORE was maxed out 95-100% i got that error or any other error! so i tweaked the settings (ingame) and keep the core around or under 90% and i don't have the error's. i did not lower anything of the card it self, you just have to tone down the game settings and your fine.
THis game is so unstable at high settings, you have no idea! and that all on R*'s crapy coding!

[~m3rcy~]

Originally posted by Noxsa:

Boys, look the REAL problem was or is, just install some monitor software and look at what value the GPU CORE is running at.
i tested this like a ton, every time my GPU CORE was maxed out 95-100% i got that error or any other error! so i tweaked the settings (ingame) and keep the core around or under 90% and i don't have the error's. i did not lower anything of the card it self, you just have to tone down the game settings and your fine.
THis game is so unstable at high settings, you have no idea! and that all on R*'s crapy coding!

Suggest using afterburner from MSI for monitoring (free and supported on GPU from other manufactures) my GPU core is at 99% under load.

[「WarningToxic」]

Originally posted by kon:

Totally worked for me! Thanks very much WarningToxic!

You welcome. For those who has the same problem just ignore Sorrow

[Sorrow]

Originally posted by 「WarningToxic」:

Originally posted by kon:

Totally worked for me! Thanks very much WarningToxic!

You welcome. For those who has the same problem just ignore Sorrow

So you do realize that you just said to ignore the rest of 99% of people who are running this game on stock gpu clocks without any problems?

Again... your solution is ridiculous and has nothing to do with the original problem.

You have m3rcy who is running it just fine on even overclocked gpu.
How do you explain that.... genius.

[「WarningToxic」]

Originally posted by Sorrow:

Originally posted by 「WarningToxic」:

You welcome. For those who has the same problem just ignore Sorrow

So you do realize that you just said to ignore the rest of 99% of people who are running this game on stock gpu clocks without any problems?

Again... your solution is ridiculous and has nothing to do with the original problem.

You have m3rcy who is running it just fine on even overclocked gpu.
How do you explain that.... genius.

GTF O from my thread and go be troll somewhere else. I found people the solution, not gonna debate your g ay ass opinion.

[kon]

Originally posted by Sorrow:

Originally posted by 「WarningToxic」:

You welcome. For those who has the same problem just ignore Sorrow

So you do realize that you just said to ignore the rest of 99% of people who are running this game on stock gpu clocks without any problems?

Again... your solution is ridiculous and has nothing to do with the original problem.

You have m3rcy who is running it just fine on even overclocked gpu.
How do you explain that.... genius.

This Sorrow is nuts. His life is a sorrow.

[hente]

Sorry about my english, not native. Anyway, I think I can't even believe this yet. And yes, I have only 4 hours of testing/playing, but this trick really seems to work.

For months I've been searching and trying multiple solutions for this err_gfx_state -error and it has driven me mad. Running full 5 minute benchmark test, -ignorepipelinecache, updated bios, run the game as administrator, changed Direct x12/Vulkan, deleting sga_files, tried too many different graphics settings.. You name it, all I have found and there have been many.

And finally this worked at least those 4 hours as I mentioned without any problems and with optimal pretty high quality settings. And like a bonus I tried Hitman 2 as it kept crashing too and it looks like this was the solution for that too.

I think I became so pessimistic with this err_gfx_state -error and again, only 4 hours played, so better not to get too excited and hold my horses so to avoid yet another dissapointment. But if this issue really is solved now, I can't thank enough for 「WarningToxic」. Thumbs up, brilliant.

Oh, I'm using Aorus Extreme 1080ti.

[「WarningToxic」]

Originally posted by hente:

Sorry about my english, not native. Anyway, I think I can't even believe this yet. And yes, I have only 4 hours of testing/playing, but this trick really seems to work.

For months I've been searching and trying multiple solutions for this err_gfx_state -error and it has driven me mad. Running full 5 minute benchmark test, -ignorepipelinecache, updated bios, run the game as administrator, changed Direct x12/Vulkan, deleting sga_files, tried too many different graphics settings.. You name it, all I have found and there have been many.

And finally this worked at least those 4 hours as I mentioned without any problems and with optimal pretty high quality settings. And like a bonus I tried Hitman 2 as it kept crashing too and it looks like this was the solution for that too.

I think I became so pessimistic with this err_gfx_state -error and again, only 4 hours played, so better not to get too excited and hold my horses so to avoid yet another dissapointment. But if this issue really is solved now, I can't thank enough for 「WarningToxic」. Thumbs up, brilliant.

Oh, I'm using Aorus Extreme 1080ti.

Glad I could help. SHARE THE SOLUTION SO EVERYBODY CAN PLAY

[quasi25]

Originally posted by Prothean™:

Factory overclocks are too unstable for this game. Just use debug mode in nvidia cp no need for third-party software.
This game came to pc after these overclocked cards were engineered. Makers of these cards didn't understand the scale of this game and how it will push the system. So you can return your gpu to reference nvidia values and be much more stable.
Overclocking has went from a competitive sport to a marketing gimmick. The overclocked cards catch the consumers eye. What you really want though is a reference nvidia gpu. Just a good old-fashioned reference gpu without all of the marketing hoo-hah

Just got a crash in the debug mode. Weirdly enough it was sooner than normal.