Forum Discussion
I have a 5080 and use an Intel CPU, and have had this issue since launch.
This is not unique to AMD.
As i mentioned, have you tried reinstalling windows and the game fresh? I have had no issues ever since switching to nvidia.
And you can look through the comments here. They are mainly amd user.
- HramToNohami1 month agoRising Traveler
Didnt solve issue for me. I installed BF6 to freshly installed windows with all drivers, FW updates and BIOS update installed.
- DesertTroper1 month agoNew Rookie
Well obviously its not going to solve the issue for you. Your using AMD. I have built many computers my self too. Either way what worked for me might not work for other. But facts are facts. Most people here complaining on the thread are AMD user.
- Plusaq141 month agoSeasoned Adventurer
Crashes on my 9060XT 9070XT & 5080
Not just AMD
- KestrelFiveFive1 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.
- TooonArmy621 month agoSeasoned Adventurer
Couldn’t agree more 👍🏻
- TeeeJaay1 month agoNew Novice
I have tried all of those too, what somewhat "reduced" the crashes for me is these 2 things
- Slightly upped the fan curve, as many have suspected the game is calling some graphical process that spikes the GPU with something it can't handle, this somewhat alleviated the frequent crashes I experience by 50%
- Clear the following GPU cache folders each and every time before playing, this somewhat reduced my crashing to just 1-2 crashes per day, about 4-6 hours of gaming
- C:\Users\<USER>\Appdata\Local\AMD\DX9Cache
- C:\Users\<USER>\Appdata\Local\AMD\DxCache
- C:\Users\<USER>\Appdata\Local\AMD\DxcCache
- KestrelFiveFive1 month agoSeasoned Vanguard
When OCing my GPU I changed the fan curvature. I have also run the GPU on 100% fan.
My GPU has never actually spiked over 60°C so I doubt this made any difference. If anything it probably put more stress on the GPU.
I have not tried your GPU cache clearing method, but if you're still getting crashes (albeit less frequently) then this is clearly not a solution.
- SIDEWINDR6661 month agoRising Adventurer
Did you turn on Hardware-accelerated GPU Scheduling in windows settings? In W11 it's Under System->Display->Grapgics->Advanced graphics settings.
I don't see that in your list. I went through everything you have and this was the culprit in the end nothing else was the cause for me, I reverted all my clocks etc back to performance etc.
- KestrelFiveFive1 month agoSeasoned Vanguard
Yes, I have tested with this setting turned on and off. It was on by default. I forgot to put it in the list as the list is already extensive.
I am not sensitive, you are the one insulting other users because your troubleshooting isn't working for them. I cannot understand why you are allowed to continue personally attacking users on this forum simply because your fixes are not working for them. Every accusation is a confession, and all that.