Forum Discussion
KestrelFiveFive
1 month agoSeasoned Vanguard
I have done every single "fix" detailed in this thread.
- Reinstalled OS.
- Rolled back OS updates.
- Reinstalled GPU drivers.
- Rolled back GPU drivers.
- Turned XMP off.
- Forced speeds on RAM.
- Turned XMP on.
- Tested both XMP profiles.
- Tested both single and dual channel on RAM.
- Lowered clocks on GPU.
- OCed GPU.
- Reset to factory clock on GPU.
- Undervolted GPU.
- Undervolted CPU.
- BIOS is the most recent version.
- Reinstalled the game.
- Deleted Javelin folder.
- Reinstalled Javelin.
- Added amended .cfg file relating to CPU cores.
- Reinstalled Steam client.
- Added a variety of 16 different launch options within Steam>BF6.
- Tested with GPU Hardware Scheduling turned on and turned off.
- Changed GPU timeouts within Registry Editor (insane that this is even a suggestion).
- Created exceptions for BF6.exe within Defender (insane that this is even a suggestion).
- Created exceptions for Javelin exe within Defender (insane that this is even a suggestion).
- Disabled Defender entirely (insane that this is even a suggestion).
The laundry list is so long that there are other things I have done that I can't even remember. No other game has issues and never have I ever had to do so much work for a game to simply not crash. This is pathetic from a company like this and the lack of communication is even sadder.
The singular source is the game calling an FSR2 module that doesn't exist. You can see this in any crash log posted on this thread. They all have "FSR2ResourcesIsNull". This is not a GPU, CPU, RAM or OS problem.
TooonArmy62
1 month agoSeasoned Adventurer
Couldn’t agree more 👍🏻