Best posts made by Zurtx01
@Ubi-Viral 'Sorry to hear that you are all experiencing this crashing issue. It seems like you are all using RX cards.'
From what I have seen over the past couple of days, there are just as many, and probably a lot more, using the latest Nvidia 3070-3090s.
We have all also tried everything on our end, latest drivers, no overclocking, etc.
This isn't an issue of our hardware/software, this is a Far Cry 6 problem. Too many of us with similar setups are all having the same issue.
Crashing/BSOD and often PCs hard resetting following the crash.
Would be really nice if you guys at Ubi could actually recognize this and let us know if you have any idea when it will be fixed. There is no way I am going to risk damaging my system playing a game that has such a nasty habit of messing with our PCs.
Decided to give it another try, with Nvidia new driver and a few days since I last tried.
Played maybe 10 minutes, if that, and surprise surprise, BSOD IRQ error, reset of PC.
Can you guys (Ubi) please let us know if there is an incoming patch for those of us with high end PCs that keep crashing.
If there is nothing incoming, I will just refund and wait till it goes on sale somewhere down the track.
I have a pile of other games that don't crash my system, that I can play in the meantime.
@ForwardTwo thanks mate for posting the details. I checked forums this morning and didn't see this post, so added my own.
Refreshed forum page and saw this listed, so asked admin if they could link mine to yours since it has been up longer.
Also ran sfc /SCANNOW with no integrity violations.
This is the only game doing this, even that buggy as hell crap game about the future city didn't cause any BSOD. (it just had a ton of other issues heh)
My system is an i9-10900 @3.7GHz, RTX3090, win10pro, Meg Z490 Godlike MB with 64gb ram, and game is installed on 970EVO plus 1TB SSD.
All drivers are up to date, and there is no overclock on any component.
All game settings are at max, 4k on a 120hz refresh screen. In game benchmark ran somewhere around 82-105ish or similar and average was (I think) 96 or so, I didn't write it down.
Benchmark ran perfectly smooth with no hitching or issues at all.
I completed the initial escape scene, and meeting a certain character and escorting him back to base on the starting island. For however long that took (an hour or so) there were no issues aside from the occasional missing voice audio in conversations.
The game was turned off at that point, and I started it again the following day.
This time, I was playing for somewhere around maybe 15 minutes when I had a BSOD occur, restarting my system. Temps are not an issue, PC is very well cooled and not overclocked, and all games I play have had zero issues at max 4k settings.
Restarted game, playing for maybe 10 minutes when I left PC with game running to have dinner, coming back a short time later, to find that my PC had reset again.
Third time playing, again for a short period, and this time the game just vanished, closing down with no error message or anything.
I have not played the game again since this occurred, as I am not willing to risk damaging my system to play a game with some serious issues.
I decided to post this here, as the BSOD issue was not listed on the Known Issues thread, and similar posts talking about game crashing were often either on console, crashing from losing connection with UBI+, or lower end PCs.
Are people with high end systems still having crashing issues, or BSOD causing system restarts? (I read a few of these issues on another site, not UBI forums)
Are there any fixes to this issue yet?
Thanks all for any assistance.
EDIT: Damn, last time I checked forums my issue wasn't listed. Just refreshed the forum, and saw the post: Blue Screen of Death with Page Fault Errors
If a mod could attach/move my comment onto that post, I would appreciate it.
This crashing issue is happening to what seems to be everyone with a high end PC trying to play at maxed settings. (although a few have tried to drop to low, it still happens)
Still waiting for this issue to be added to known issues, as it is DIFFERENT to those who cannot launch it.
Starting isn't the issue, crashing is.