Potential Fix for BF6 Freezing for AMD users

Thanks for sharing!

Hello friend.

Penguin took a closer look at this and thinks your findings can plausibly be helpful in some cases.

One important observation from earlier: (From just one case, every other attempts where this has been done, including the other common solutions was also not the solution) Reason for Penguins silence too recently, without lots of food to deliver to the table about the current issue since recent update, but hypothesis still exist about this)👇

Penguin previously detected a software level conflict involving AMD Adrenalin. in one isolated case, the freezing issue was resolved by switching away from the Adrenalin driver stack to the Microsoft WHQL version delivered through Windows 11.

This can suggest the issue may not only be shader related, but potentially a driver/software layer interaction problem. (Adrenalin services, overlays or background components interfering with scheduling or shader handling.)

Here is what's directly related to your observation friend.
👇
The key detail in your post is the longer shader compilation followed by stable framepacing. That may also suggest the issue can involve shader cache integrity or pipeline compilation behavior.

This is where Penguin is stuck/lost and wondering as possible explanations attempting to understand what's going on with a community members PC(Discord Direct Messages individual cases).And Argos_Odeus​ post on top here seems related to recent work:

1. Adrenalin drivers may reuse or partially rebuild cached shaders?
2. Could the cache become inconsistent (after updates, crashes or driver changes)? That may cause runtime stutters/freezes despite high FPS and otherwise solid PC gaming systems. 
3. The WHQL driver might force a cleaner compilation path avoiding these inconsistencies?

If accurate 👉 The longer compiling time you observed could indicate:

No reuse of previous cache
Full pipeline state creation
Reduced runtime shader compilation

= Stable frametimes and no freezing.

Penguin also agrees your point about the Windows update 👉(KB5079473) is important. If kernel behavior changed, there could be a temporary mismatch with newer Adrenalin builds, while WHQL drivers remain aligned.

Penguin suggest to test this further:

1. Test Adrenalin with fully cleared shader cache, in order to isolate (cache vs driver issue)
2. Compare frametime consistency and not only FPS
3. When users report this, check if they are on RDNA2 or RDNA3 (Any different behavior, freeze/crash statistics between players on RDNA2 or RDNA3?)
4. Also observe the freezing behavior over multiple sessions (to detect if the cache degrades over time or not, if it does, the frequency of freezes will very likely increase) Cause👉effect💥

Look out for if multiple players report this.

Penguin already on lookout for patterns like this too friends

Big Fan Of Battlefield!
Many Thanks
Penguin

EA_LunardustCat​ ImPenguinFriend​ Hello thank you for reading this post I hope more people try this and report as soon as possible! In meantime I am gonna keep testing it!

Once again Thanks in advance!

Okay I did manually found the driver for the Navi series, so for those who want to install it via the device manager in safe mode after using DDU (via the u0199096.inf file) or simply click and let the .cab file do it's job then download it from here

https://www.catalog.update.microsoft.com/Search.aspx?q=PCI%5CVEN_1002%26DEV_7550  

Last but not least the PCI\VEN_1002&DEV_7550 <---- ID represents the Navi series yours might be different. 

-Good luck!

It is not a driver issue it is a javelin kernel issue that mostly affects am5 boards using x3d chips but not exclusive. Reinstalling video drivers does nothing.

I am using AM4 system with 5800x3D so i don't think that it affects only the AM5 users, did you try what I posted please do!

Hello friend

Penguin thinks there can be multiple root causes for Javelin EA Anticheat making the game freeze.

The point is not whether EA Javelin anti-cheat is involved or not, it is already known that it is.

The point is that different system configurations can still affect how and when these freezes happen.

Drivers windows update, BIOS, CPU types, different XMP memory profiles, shader compilation can all play a role. EA Javelin Anti cheat might trigger the freeze often but not always for the same reason.

That's why some fixes work for some players, and not for others.

Many thanks for the post friend as it gave the opportunity to provide this clarification 😀

Big Fan Of Battlefield!
Many Thanks
Penguin

Latest may 5th update does nothing except reset all my options to default making me even less likely to play. Still freezing. Trying for steam refund yet again.

Have you tried using the 25.20.42.14 driver from Microsoft? If not, I’d recommend using DDU to completely remove your current driver first, then either installing it through Windows Update or downloading it manually from here.

https://www.catalog.update.microsoft.com/Search.aspx?q=PCI%5CVEN_1002%26DEV_7550 

I have reasons to believe that, aside from the shaders compilation, another possible culprit could be the RyzenMasterDriver module, which is not loaded by Microsoft’s AMD driver.

if you have a Navi GPUs rx 5000 series and above!

Is there a possibility that AMD’s FSR 4 driver implementation is responsible for the crashes/freezes?? For example, if someone (like myself) installs the driver through the Windows Update Catalog manually or Windows Update automatically, that installation does not include additional system modules such as ryzenmasterdriver.sys or amdxcffx64.dll (which apparently brings FSR 4.1 support).

In contrast, Microsoft’s 25.20.42.14 driver only installs a basic version of the driver, which in my opinion is actually better because fewer modules mean fewer DPCs in the system.

What I noticed today while gaming was that switching between FSR Quality and Balanced modes happened instantly. However, with AMD’s 26.3.1 drivers (while FSR 4.1 was loaded) there was a slight pause before the upscaling loaded.

I honestly think you guys should get in touch with AMD’s engineers because I’m convinced that FSR 4, combined with shader compilation, is causing this issue — at least on AMD cards.

As always I am trying to help but no one is trying what I mentioned from my comment above I did play 4hours today 3 the multiplayer mode and the other one the RedSec this is the third day with no crashes whatsoever!

-Thanks in advance!

EA_LunardustCat​ ImPenguinFriend​