Potential Fix for BF6 Freezing for AMD users

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!

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!

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

Thanks for sharing!