Found a possible fix for the abnormal TN value issue

After quite a bit of digging, I think I’ve finally found a solution for this strange TN value spike problem.
Coming from many years working at DELL, especially as L2 technical support for frontline engineers, I’ve picked up some “detective-style” troubleshooting habits.
After talking with several people across the forums and doing multiple rounds of testing, here’s what I’ve discovered:

🧩 The Fix (currently only confirmed on laptops):

Go into your BIOS or Windows settings and disable integrated graphics output.

For DELL gaming laptops, this setting is usually called “Hybrid Graphics” — disable it.
After doing this, the TN value may still fluctuate a little, but based on my own tests, it no longer spikes to the insane 400–1000 ms range.

On other laptop brands, you might need to check your BIOS options, system manual, or contact the manufacturer’s support team for how to fully disable the iGPU output.

🔬 Testing Summary:

I searched across Google and even consulted AI tools — no existing solution was documented.

I confirmed that changing CPU or power-related BIOS settings (like SpeedStep, C-States, etc.) actually makes the issue worse, which pointed toward a CPU-timing-related cause.

The problem never appears in offline modes, Portal private matches, or single-player campaigns — only in online multiplayer.

Multiple community members and streamers confirmed that desktop PCs do not have this problem, which made me suspect the integrated GPU (iGPU) layer specifically.

After disabling the iGPU via BIOS (this is preferable to just doing it in Windows), the issue improved dramatically.
Now my TN values range between 30–300 ms, typically hovering around 120 ms, and even during heavy moments (like many players clustered together) it might reach 400 ms — but at least the game is now playable.

💡 My theory:

I suspect there’s a regression or hidden logic in the Frostbite engine or the final release build of Battlefield that tries to access or sync with the integrated GPU when it’s present.
Since the iGPU isn’t actually handling the game’s rendering tasks, this unnecessary interaction could be causing the TN timing spikes.

This bug did not appear in the BF6 BETA, which makes me think some new or legacy code was reintroduced in the final packaged build that triggers the issue whenever a hybrid graphics configuration exists.

✅ Recommendation:

If you’re on a laptop and seeing abnormal TN values, try disabling the integrated graphics output and share your results here — it would be great to confirm this across different hardware setups.