Error ffffff

[BeeJeeBeeHee]

I am getting the Unknown Error ffffff/Crash constantly now. Once in a while does not bother me but today it has been every time I have tried to set up a wilderness camp (there is a challenge for that today). No matter how long I have been logged in. Also happened a few other random times, including when I was trying to get a legendary pelt to Gus.

 

Edit: Windows 10 Pro. GeForce 2070 Super. Driver version 466.27 (because the one after black-screened everything, and am hesitant to get newer ones).

 

More: Also, the crash occurred 3 times today (6/26) so far. One happened after I used a reviver on sampled animal. After relog, It still used the reviver but didn't save challenge credit. Another happened immediately after getting out fishing pole. The other totally random as far as I could tell.

 

I have checked my mic and speakers. I have validated files in Steam. What is going on?? Please help.

Edited June 26, 2021 by BeeJeeBeeHee
More info

[Krommer]

It is a bug that they have to fix:

 

People who play on PC in the Reddit mention it a lot too, with screenshots of that FFFFFF thing.

[FRIDA_KAHLO]

I get it fairly predictably (perhaps half the time) the first time I try and use deadeye in a session but occasionally also random times like you describe.

 

Now that you mention it I am using nvidia 1660 which was just a few months apart from the 2070 release. Is anyone else having the error post their video card too?

 

I really don't have the slightest clue how to ease the problem though. Sorry. But I don't know any cures for this (For a good time, ask West Dickens). I believe I haphazardly tried disabling video settings and using directx versus vulkan api, and none of it panned out. However, since I wasn't keeping track or very thorough, I wouldn't rule that out. Hmm

 

I might get back to you more later if I find some out, eh well you do the same BeeJeeBeeHee if you find something. But it's a guessing game like troubleshooting intermittent "CHECK ENGINE" in your car without opening the hood and the special diagnostic reader. *shrug*.

 

You mention "no matter how long" you were logged in. Why? This caught my eye because when I see FFFFFFFF it is a 64 bit number that is all 1s. It might be an unitialized memory pointer exception. In other words, in my case with the "first time I try deadeye" scenario, it makes me wonder if something I do or not, sometimes is causing it to be initialized properly or not.

 

I feel like we should put in official support tickets on something like this I've just been too lazy and jaded. Did you? There may be debugging files spit out during such a crash that support could use

Edited June 27, 2021 by FRIDA_KAHLO

[kcole4001]

I use an AMD card and most times I get this error it's because of graphics drivers, which makes no sense: it works fine one day and the next I get errors without having updated drivers, though I find that AMD has released a new driver update.

After updating drivers it stops.

 

[UltimateAntic]

On 6/27/2021 at 7:19 PM, FRIDA_KAHLO said:

Now that you mention it I am using nvidia 1660 which was just a few months apart from the 2070 release. Is anyone else having the error post their video card too?

GTX 980 user here, had the same issue as well.

[FRIDA_KAHLO]

I think kcole4001 idea is solid my driver might be behind. I am going to try that. In fact GeForce experience itself was updating itself so I do not think it is automatically doing the things I thought it was doing. I feel like on "The Princess Bride" and the geforce experience is telling me, wrt automatic updates, "you keep using that word, but I do not think it means what you think!" I'm running driver 466 and the latest "game ready" one is 471. OK this cowpoke is upgrading driver and I'll know pretty soon if deadeye isn't givin me a check engine! Thanks good idea

 

And the original post BeeJeeBeeHee also was using a version 466. So far so good 

 

I really would have bet you my butcher table that my drivers were up to date an hour ago, but, now I can use it as a sturdy base to chop up some humble pie on. Or do a prospector jig upon. So far so good here with driver version 471.3. I'm optimistic

 

2 hours later.. back to the drawing board. It makes sense to have the drivers update but I got error:FFFFFFFF on 3 of 7 runs of the game upon activating deadeye

 

Edited June 27, 2021 by FRIDA_KAHLO
driver version # 471

[BeeJeeBeeHee]

On 6/27/2021 at 10:19 AM, FRIDA_KAHLO said:

You mention "no matter how long" you were logged in. Why? This caught my eye because when I see FFFFFFFF it is a 64 bit number that is all 1s. It might be an unitialized memory pointer exception. In other words, in my case with the "first time I try deadeye" scenario, it makes me wonder if something I do or not, sometimes is causing it to be initialized properly or not.

 

I feel like we should put in official support tickets on something like this I've just been too lazy and jaded. Did you? There may be debugging files spit out during such a crash that support could use

 

It seemed like a possibility that a combination of actions or cumulative actions might be a cause. Perhaps a hiccup in save points or something. Especially when some things seem to be "rewound" after the error/crash and some things do not. Like the use of a consumable being saved, but the challenge credit for using it was not. There were other times this sort of thing happened but I do not recall the specifics. I am not really familiar with how it all works so just guessing. I started attempts to troubleshoot, but there are soooo mannnyy variables, I just gave up.

 

I have not submitted an official ticket. I suppose it would be wise. I did upgrade to the latest graphics driver today, but it did not solve the issue. 

 

Thank you everyone for your input. Hopefully a solution comes around soon.