have fun fiddling with your pc, we are all impressed.

 this is an EA BF6 game problem and until devs or tech support chime in your recommendations have already been tried and done.

 Doesnt work…game problem…no one has ever had to work harder to try to get this game to work than people on this post

 have a look around

Can you read or comprehend english?  I said you need this settiing ON regardless of anything else.  I did not say it would fix YOUR problem, I said you will never resolve the issue with the GPU scheduling OFF.

I've been round the block and then some mate, nice ASSumption.  I have been modding PC's since the dawn of PC's and gaming since the very first text based adventure games.

Spoken like someone who has fiddled with their PC and messed it up and trying to blame someone else.  Have you tried factory settings on your BIOS and a fresh install of windows (you can install it to another drive for testing) and BF6?  If this works then the issue is SOMETHING you did or something you changed or added etc.  You can then on the test windows start installing drivers/utils for clocking etc. one by one (test after each install) and see which one breaks BF6.

If you have GPU scheduling on then check other things like clocking etc.  My point is that you need GPU scheduling ON regardless. :)

Long Text Warning – Step‑by‑Step Guide 

I found the problem that was causing all the issues for me. The EA engine, much like Capcom’s RE Engine in Monster Hunter Wilds, is extremely clock‑sensitive due to how DX12 works. I tried different workarounds for three months and none of them helped. This fix finally worked for me after a fresh Windows install. You can test it yourself and see if it solves the issue for you as well.

I have a 9800X3D with a 7900XTX, and my Radeon drivers are 25.12.1. In my case, the issue was that my GPU came with a factory overclock — I have an ASUS TUF Gaming model using the Radeon app.

My card had a 3000 MHz boost clock from ASUS, Auto OC pushed it to 3100 MHz, and I also used Auto Undervolt based on forum recommendations for this DXGI error, which resulted in a 2900 MHz boost.

I didn’t realize this at first because I just plugged it in and played, so I never touched the Radeon settings. I assumed the card wasn’t overclocked, but later I found out that many GPUs come with factory overclocks and the Radeon app does NOT lock them. So I went to AMD’s website to check the advertised clocks for my card:

• Boost Frequency: Up to 2500 MHz
• Game Frequency: 2300 MHz

This is much lower than the 3000 MHz (or 2900 MHz undervolted) that my card was running at out of the box.

So I manually set the max boost to 2500 MHz as advertised — and it worked. I stopped having crashes in both games where I had issues. In Monster Hunter and Battlefield 6, I had specific spots that would always crash, and after two weeks of playing, I never had another crash.

I even tested overclocking my CPU and RAM and still had no crashes, so the problem was definitely the GPU software. I tried raising the GPU clocks again to find the limit, and in my case, anything above around 2700 MHz caused crashes. I’ve now been playing perfectly for the past month, including the previous two weeks.

I created profiles for both games using the Radeon app — one global profile for all games, one specifically for Battlefield 6, and one for Monster Hunter Wilds. Now, when I launch those games, the correct settings are applied automatically. No other changes were needed (like disabling overlays, etc.) — just the max‑clock limit.

This worked for me, but it might not work for you. Ponly limiting your clocks to the advertised values.

I added a Picture linked with the steps to help you out a bit.

1. Check your GPU’s advertised clocks

   Go to AMD’s website and look up the advertised Boost Frequency and Game Frequency for your specific AMD GPU (I described mine above: 7900XTX). We will use the highest advertised value, which should be the Game Frequency.

2. Update your Radeon app

   Open the Radeon app and update to the latest driver. After updating, open the Radeon app again and go to Performance. You will see three tabs: Metrics, Tuning, and Settings.

3. Create a game profile

   Open the Tuning tab. In the top‑right corner, click Add Game Profile and select Battlefield 6 or whichever game is causing the error. If you have multiple games with the issue, you must create individual profiles for each one.

   This will add a profile for that game. It will start with Default settings under the automatic tuning section. Click Custom under Manual Tuning.

   (Optional) If you didn’t create a game profile

   You will be editing your global settings. You will see three sections: System, CPU, and GPU. We only want to modify the GPU, so click GPU and expand it if it’s collapsed.

4. Enable GPU tuning

   You will see several tuning options:

   • GPU Tuning
   • VRAM Tuning
   • Fan Tuning
   • Power Tuning

   We only need GPU Tuning. It will be disabled by default — click the toggle to enable it.

5. Enable advanced controls

   After enabling GPU Tuning, new options will appear. They will be displayed in percentages, but we want precise MHz control. Enable Advanced Control (below the clock speed and voltage metrics). This will switch the controls from % to MHz.

6. Set your max frequency

   In Max Frequency, type your advertised Game Clock. In my case, it was 2500 MHz, but I tested and could play without DXGI errors up to 2700 MHz.

   You can test your own limit, but do NOT exceed what your GPU partner brand advertises (ASUS in my case). If you’re unsure, stick to AMD’s advertised Game Clock.

   (Optional) Power tuning

   In the same tuning tab, you will see Power Tuning. I enabled it and set the limit to –2% since I wasn’t pushing 3000 MHz anymore. This didn’t seem to affect the error, but if you still get crashes, try adding this step.

7.  

   Save and apply

   At the bottom center of the screen, you will see a small popup to save your tuning. Click Apply. This will save your GPU tuning for the game profile you selected in step 3.

   Restart your PC for good measure, then launch the game and test it.
   
   Other GPU brands and software and Final.

   Hopefully this helps some of you who are less tech‑savvy. It looks like a long process on paper, but it takes 10 minutes max.
   I added a Picture linked with the steps to help you out a bit.

   If this does not fix your DXGI error, please check in the Radeon app to make sure the profile was actually saved.

   For Nvidia users: I heard some drivers fixed most of the issues, but you can probably replicate this method in GeForce Experience or other tools like MSI Afterburner. I don’t use those tools, so I can’t guide you. But the logic is the same limit the max clock of the GPU to the one advertised by the manufacturer AMD or Nvidia 

   Attention: If you have GPU overclocking software installed, it can overwrite your Radeon or Nvidia profiles. I recommend uninstalling any OC software, because even if disabled, it may still apply old settings. You may also need to use DDU to remove leftover settings.

   If this still doesn’t solve the issue and you followed everything correctly, I wish you luck. I battled this for three months before finding my solution. EA should really be on top of this — the user shouldn’t have to tweak these things to fix the issue. Whether the root cause is the game or DX12, I can’t say.

   

I never said that the solution working for me is the general solution for everyone out there. Instead I explicitly mentioned that it helps in _my_ case.
It's just feedback so that during these days of thousands of **bleep** workaround suggestions those with an AMD card have a confirmed and easily applied workaround which may also work for them and should be considered trying.

its an Ea problem brotha dont listen to Sidewindrr666

Thanks for confirming this...someone telling me it is my hardware and turn on gpu scheduling has not been around the block....or around since the beta which is how long my game was crashing for...

i have 4 PC´s and its always on by default. this "tip" was one of the first while te Beta and 99% said it is on by default...  You are wasting your Time/ Money when you try to find the Problem on your side. This Failure happens for years in Frostbit just nevere in that extent

Dude do whatever you want. Its a fact that its not a Driver or GPU problem. EA staff said that already. its just to many variants of PC Setup and "Trigger Points" for that Crash. 99% of 9070XT Users dont have that problem. For some works x for others y. we try that since the beta there is just no working solution for everybody