Red Dead Redemption 2

Red Dead Redemption 2

View Stats:
Raye_Raye Jan 23, 2023 @ 7:25pm
FFFFFFF error is ruining the game.
Does anyone have any suggestions on how to resolve this error? We all have been getting it in multiplayer (I play with 4 friends and they all have the random crashes). We troubleshooted drivers, peripherals, start-up programs, vRam, disabled audio devices, shaders, updated windows, etc... We are at a loss. I'm not seeing any pattern that is causing in-game. TIA
< >
Showing 1-15 of 20 comments
Donald J Trump Jan 23, 2023 @ 7:40pm 
Rockstar sleeps when they are having one of the biggest cyber security breaches in gaming history.
You think they care about some minor crashes?
Last edited by Donald J Trump; Jan 23, 2023 @ 7:44pm
Qwickkill Jan 23, 2023 @ 8:19pm 
Wait I thought the FFFFFFF error was the game and the rest was a bug, thanks for clarifying that.
Shamestick Jan 23, 2023 @ 8:42pm 
I've been doing everything I can to try and fix this error with no luck for over a month now. Spent several hours w/ R* support w/ no resolution as well. Some people say they've been able to fix it several different ways but many people are in the boat as me where none of these fixes work.
Rat wit da gat Jan 24, 2023 @ 4:02am 
The thing that's causing it is modders. If you go into your documents, look for Rockstar Games, then Red Dead Redemption 2, then go into the Settings folder. Delete everything that isn't the system.xml. Unfortunately, this is a band-aid because the next modder you come across will give you the same crash. Only way to get around it is to do a private session, look up how to start one, me and my friends added a text document into the files that worked like a passcode to keep other people without it out of the session. Ever since then, no FFFFFFF errors for any of us.
Originally posted by Rat wit da gat:
The thing that's causing it is modders. If you go into your documents, look for Rockstar Games, then Red Dead Redemption 2, then go into the Settings folder. Delete everything that isn't the system.xml. Unfortunately, this is a band-aid because the next modder you come across will give you the same crash. Only way to get around it is to do a private session, look up how to start one, me and my friends added a text document into the files that worked like a passcode to keep other people without it out of the session. Ever since then, no FFFFFFF errors for any of us.
Do you mind sharing the text document you used to keep other people?
channel 27 Jan 24, 2023 @ 4:39am 
This is the solo online that Rat wit da gat is talking about. I highly recommend myself

https://youtu.be/OFd2af8wINE
Originally posted by channel 27:
This is the solo online that Rat wit da gat is talking about. I highly recommend myself

https://youtu.be/OFd2af8wINE
thank you for sharing... will try it.
UpperHand Jan 24, 2023 @ 10:42am 
yes but then you will not have other public players in game if its pass worded?
channel 27 Jan 24, 2023 @ 10:53am 
Originally posted by UpperHand:
yes but then you will not have other public players in game if its pass worded?

Yes thats the point. No more hackers. If you want your friends to join have them do the same thing and share the password with them and you can have a group lobby.
channel 27 Jan 24, 2023 @ 10:58am 
Originally posted by UpperHand:
yes but then you will not have other public players in game if its pass worded?

And if you don't want to do that you're currently setting yourself with this. Its just not GTAO but on RDR20 too. Players beware !!!

https://youtu.be/lRqitu4zzMY
Last edited by channel 27; Jan 24, 2023 @ 10:59am
Man o' War Jan 24, 2023 @ 11:20am 
September the 6th 2022 update killed the game for many Nvidia users.

Tell me you're not a Nvidia user.
Donald J Trump Jan 24, 2023 @ 1:40pm 
Originally posted by Rat wit da gat:
The thing that's causing it is modders. If you go into your documents, look for Rockstar Games, then Red Dead Redemption 2, then go into the Settings folder. Delete everything that isn't the system.xml. Unfortunately, this is a band-aid because the next modder you come across will give you the same crash. Only way to get around it is to do a private session, look up how to start one, me and my friends added a text document into the files that worked like a passcode to keep other people without it out of the session. Ever since then, no FFFFFFF errors for any of us.
Did not work
Envi Jan 25, 2023 @ 3:14am 
I've had pretty good luck with some of the fixes I've found online when googling the issue - also one thing I have NOT found online is that for some people, myself included, slow and steady and slippery bastard are broken and cause FFFF errors on launch of deadeye.
Raye_Raye Jan 25, 2023 @ 8:26pm 
Originally posted by Shamestick:
I've been doing everything I can to try and fix this error with no luck for over a month now. Spent several hours w/ R* support w/ no resolution as well. Some people say they've been able to fix it several different ways but many people are in the boat as me where none of these fixes work.

This solved the issues for all 4 of us . Much appreciated... we opted for private sessions.
Sovereign41 Jan 26, 2023 @ 2:08pm 
Dang it. My folder system is different. No x64 or data folders.
< >
Showing 1-15 of 20 comments
Per page: 1530 50

Date Posted: Jan 23, 2023 @ 7:25pm
Posts: 20