Here's why you should regularly update your chipset drivers

I last updated my chipset drivers after a BIOS update in October.

Since SU4 I’ve been struggling with audio/video dropouts whenever flying over major cities like NYC and Tokyo.

I tracked down a problem using LatencyMon, finding that my Kernel Timer Latency was extremely high. Here’s what it looked like. The number should be under 1000µs.

I tried a lot of performance tuning tricks, but couldn’t improve that number until…
After updating the chipset drivers I immediately got this:

That’s an 1800% improvement.

After updating the drivers I did a flight over NYC. No visble or audible stutters or dropouts. Performance on paper was just ‘OK’ (still seeing frame drops, but no audio/video stuttering) so now I can chalk it up to SU4 and/or the Azure servers.

For reference, here’s the result when flying over the flat land of rural Texas.

And finally, Kombustor 4K test.

Temps look good in AIDA64 CPU/ GPU/ RAM stress test:

ETA: I tried one other change. I’ve tested the sim with HAGS On and Off, and always found better results with it Off. So this improvement with it On surprised me.

Median FPS +8.2%
1% Low +6.7%

4 Likes

which software are the last screenshots to record the FPS?

I have to check on my system with HAGS on vs off.

Good reminder about updates. I’ve been saying for years that motherboard and chipset drivers should always be kept up to date.

One small but important note: even if you’re using a motherboard from a specific vendor, component manufacturers usually provide newer drivers than motherboard vendors. For example, if you’re running a Ryzen CPU on an ASRock or MSI motherboard, chipset drivers should be downloaded directly from AMD rather than from ASRock/MSI, as motherboard vendor packages are often behind the reference releases.

Also, don’t forget about keeping Windows up to date. Recent Windows updates include improvements that positively affect performance and stability on AMD-based platforms.

More details here: https://forums.flightsimulator.com/t/windows-11-25h2-24h2-and-msfs-observations-insights-issues-and-tips/657704/278?u=tenpatrol

CapFrameX
https://www.capframex.com/download

I’m using CapFrameX beta version 1.7.7. This version is no longer officially available, so you can test with beta version 1.7.6 instead.
The latest builds are available on GitHub, not on the official CapFrameX website.
https://github.com/CXWorld/CapFrameX/releases/tag/v1.7.6_beta

Download beta installer.zip

PS: The version of CapFrameX can also affect benchmark results.

2 Likes

I checked both AMD and ASRock sites. The ASRock version was more recent.
Also, wouldn’t the motherboard version include drivers specific to the motherboard?
Wouldn’t that normally be preferable?

Should I install Windows Pro 25H2?
I’m currently on Build 24H2

Thanks for this tip.

I would love to see screenshots of other computers’ Kernel Timer Latency using LatencyMon.
The software is easy to run, and can be downloaded free here. Brief instructions are in the screenshots above.

I downloaded CapFrameX Beta 1.7.6

I saw this note. I don’t use frame gen but others do.

Important : This version is not compatible with Nvidia’s Multi Frame Generation! We are working on a solution with Nvidia.

this is where i’m at

5 Likes

LOL

Check my PM. I’ll point you in the right direction.

Chipset drivers are made by AMD, not motherboard vendors.
AMD’s package is the core version.
Motherboard vendors receive this package from AMD and repackage it for their support pages. They do not modify the chipset logic - motherboard manufacturers may add bloatware.
In short, there are no motherboard-specific chipset drivers on AMD platforms.


Exception: Intel platforms - there it’s usually better to use chipset drivers from the motherboard vendor.


The newer version is on AMD website and that won’t change.
Below is a comparison - it clearly shows that AMD chipset driver version is newer than ASRock.

AMD

ASRock

ASUS

MSI

I’m on Windows 11 Pro 25H2 and I personally have no issues with this version.
Whether you choose to upgrade from 24H2 or stay on it is entirely up to you.

If you want to talk about Windows 11 - its versions - and their impact on MSFS 2020/2024, feel free to continue the discussion in the thread linked below:
https://forums.flightsimulator.com/t/windows-11-25h2-24h2-and-msfs-observations-insights-issues-and-tips/657704/278

Not sure where my confusion came from. Not enough coffee yet?
Or maybe I’m just getting old and senile. :wink:

Thanks for clarifying. The AMD version is indeed more current.
I’ve downloaded it and will install over the ASRock version.

As for 25H2… Of course it’s up to me, señor.
I’ll head over to the other thread. Thanks for the link.

1 Like

I9 14900, MSI Pro Z790-P

Even though most of you have AMD’s you are all aware of the Intel issues and I am certainly trying to stay out of hot water and keep mine up to date. My BIOS and ME Firmware are guaranteed up to date, but this thread made me question the chipset. After some research, my installed chipset (Apps - version) version is later than the one listed on the MSI page for my MB. When I went to Intel’s website, it instructs pre-built system customers to refer to the builder, which in turn goes right back to MSI.

I cannot find anywhere on Intel’s website a list of chipset downloads, of either my current version of 10.1.20020.8623 or the prior version on the MSI website of 10.1.19899.8597. The current version is dated 4/22/2025 which is 6 weeks after I got the computer and I sure didn’t update it myself. Do I possibly have an Intel update utility and not know it? If I have the most current version right now I am ok with it, I just don’t know how to verify it in the future.