How do you revert?
1 Like
Do a fresh install but make sure your Win11 version is the 23H2 build.
1 Like
I am happy to report that I have successfully solved a significant instability issue in my system.
The core problem turned out to be related to my RAM configuration. When building my AMD system, I originally installed two 32GB Trident Z5 sticks (64GB total). I was unaware that the
XMP (Extreme Memory Profile)** was optimized for Intel CPUs and could cause instability on an AMD platform. I had suspected the issue might be related to data read/write errors.
After doing some research, I discovered that EXPO (Extended Profiles for Overclocking) certified RAM sticks are specifically designed, tested, and certified to work seamlessly with AMD motherboards and chipsets
The Solution: Switching to EXPO RAM
I switched out my 64GB Trident Z5 RGB XMP RAM for Corsair Dominator DDR5 64GB EXPO RAM. Upon installation, my motherboard immediately enabled the EXPO profile options. I activated these settings and made no other changes to the computer.
Since I was running a clean installation of Windows 11 and a default Microsoft Flight Simulator 2024 with no add-ons, I repeated my original stress test: a takeoff from KDFW (Dallas/Fort Worth) with heavy photogrammetry enabled on the NEO V2.
The results were immediate and dramatic:
-
The distinctive audio popping was gone.
-
There was still a slight, barely noticeable micro-pause when new photogrammetry loaded, but the major audio and performance issues were resolved.
Further Performance Testing
I then expanded my testing to optimize frame rates, using both photogrammetry (FG) and non-photogrammetry (Non-FG) settings:
-
Targeted Frame Rate: I set my maximum target FPS in the settings to my achievable rate of 71 FPS (based on the in-game developer mode counter).
-
Dynamic Target: I set the dynamic FPS target to 60 FPS (10 FPS below my high target).
With these settings, the micro-stutters I had previously experienced were eliminated.
Finally, I tested Frame Generation (x2) to match my Odyssey Ark Gen 1 refresh rate of 120Hz. The simulator performed exceptionally, maintaining an FPS between 115 and 119. Only when flying over dense areas like downtown Dallas, where vast amounts of photogrammetry were loading, did I observe a minimal, expected stutter—well within what is normal for a flight simulator handling this much data.
Conclusion
For me, the solution was a combination of two things:
-
Installing the Correct RAM: Switching from XMP to EXPO certified RAM resolved the underlying system instability. (For others with XMP RAM, manually tuning the RAM timings in the BIOS is an option, but I opted for a straightforward replacement.)
-
Optimized FPS Targeting: Setting a realistic maximum target FPS that the simulator can achieve, combined with a dynamic lower target, allows the system to recover quickly from any minor micro-pauses that occur during data loading.
It was a lengthy troubleshooting process, but I am thrilled to have finally found the solution!
9 Likes
I doubt that this is the solution to the problem as a whole, as both are absolute beginner mistakes…
4 Likes
I’ll keep you updated on how it goes. Currently on a flight from KFLL to KDAL with the IFly 737. Haven’t had any issues. Will do another two flights tonight so it’s bound to happen if still is an issue.
1 Like
A little tip for anyone using an audio interface (Focusrite, etc.):
In your interface settings, set the sample rate to 48000 Hz and the buffer size to 1024 or higher if possible.
When I did this, all audio problems were almost completely resolved. Only when a lot is loaded at once (e.g., when boarding passengers in a career mission or returning to the menu) do these problems sometimes still occur.
1 Like
All right. Try these…
Windows 10 Latency Fix ntoskrnl.exe
Additional tips for anyone desperate (like I was) on seeing if we can find the tip. Using LatencyMon I found that what was giving me latency was the Nvidia Audio Kernel (nvlddmkm.sys high dpc latency). I then found that this issue has gone back maybe 5-6 years with several people looking for solutions. Lead me to this thread.
While my experience improved, I was curious why I was still getting some very small stutters. Turns out Windows 10 and 11 introduced two a couple of “hidden” power management settings that could throttle down your CPU causing this latency. So I attempted the fixes. so far my 2nd flight has gone significantly smoother than my first flight. Additionally, the latency is currently significantly better then my initial test.
I am trying to see if we can test this to provide the devs more clues as to what may be happening.
3 Likes
All right everyone. I can confirm my above fixes are now 100% fixing the issue. No more stutters or latency issues. Audio popping is gone.
Here are my settings for everyone curious to try.
In my BIOS. EXPO 2 turned on.
AMD 7900X3D Curve Optimizer negative 20.
Turned off on board graphics.
Additionally, I turned off Hardware Graphics Acceleraton on Edge. I also turned off to keep Edge asleep in a suspended state when I exited it.
1 Like
Thought you need to have hardware acceleration turned on to enable frame gen.
2 Likes
@PILOTOWAWAWA How long did you test your solution, one or two days?
We’ve had so many “solutions” here, but none of them lasted long enough to be a real fix. Even after 2–3 weeks, the stutters came back. Maybe take it easy and test it a bit longer than just a couple of days before calling it a “fix” and getting everoyne hope here up.
Your solution is way too simple, and I’m sure many users already have those settings by default, since they’re standard and nothing special.
4 Likes
I’d also add there are plenty of “solutions” posted in this topic, but be aware that a solution that worked for someone else doesn’t automatically mean it’ll work for you. I’d also be cautious when changing settings, just make sure you know what you’re doing and that you can revert back if needed.
For me, reverting to 23H2 resolved my stutters. I’ve flown for a few days now without a single stutter. That said, I can’t 100% confirm whether it was 24H2 or 25H2 causing the issue because it could’ve been bad drivers, and the fresh install might’ve fixed it. The only way to know for sure would be to install 24H2 again and see if the stutters return, which I might do.
2 Likes
Agree that it’s just a “one-day example”
My scenario is clear to me for two reasons.
1st - even with default Windows and MSFS freshly installed, the issue persisted. (That’s what I encountered after nuking my system Monday night into Tuesday at 2AM.
2nd, the solutions I have offered do not appear in the history of this thread. The only thing I had seen and used was finding where the issue was with Latencymon.
Once I uncovered that the latency came from NVLDDMKM.SYS I then proceeded to find solutions for that issue. (Again, in the history of this thread I didn’t see anyone mention or say that it was the source of their issue.)
As soon as I applied those alterations (which were not “default” given that I had literally just installed Windows 11 and they were already enabled instead of disabled like I needed), the popping and stuttering in the same scenario went away.
At this point, I have tested back-to-back the simulator with the previous beta and the new one released today for about 18 hours with default and now add-ons that showed the problem before.
Finally, if I find a potential solution, why not offer it to others who were as desperate as me? In the numbers we have power, now others can experiment and see if I can help them, or if it truly was just me.
To your credit, I’ll continue testing and update on how it a going. Right now doing a KSMF-KDFW in the Fenix. No stutters or popping. The Dallas -Arlington photogrammetry used to cause it in the past. So I’ll see if it does again. Given I flew into KDAL last night with the IFLY I doubt it will.
2 Likes
I don’t mean to rain on your parade but I thought I had 100% solved my issue, for it only to come back a few weeks later without me changing anything. What is more likely the case, is the server load/external factor has changed thinking you have solved it. But I guess you will know after at least a couple of weeks of testing.
1 Like
Let’s see! Maybe that’s the case.. Why would that show up under latency in NVLDDMKM?
1 Like
it will be back when you update to 24h2 or higher. i tried it allready. i got 3 friends with stutters, all switched to 23H2 and never get the audio stutters back again.
1 Like
I had the stutters for a while, but today the first time it was so bad at a moment it triggered a CTD….20 min before landing a 2.5hr flight… pff
Been testing in 24H2 for a couple of days. Now trying 25H2 and havent had it either.
Im going to have an unpopular take but here it is. So I dont see anyone with a 14900k in the chat with any of these problems. I figured we’ll lets try to get this 7950x3d to run like a 14900k lets stabilize the voltages with a positive offset of 5. On the ground it got rid of the microstutters…ok in cruise sound stutter plus a main thread of 30+ ms. I think we were all duped by people flying stock no Add-Ons no Fenix into believing this chip is any good for 2024. Too many variables. Cross CCD latency,unpredictable voltages, scalar, pbo bla bla bla. Thats why users with the 14900k just crank it to 6ghz and call it a day. This chip might be amazing for call of duty and fortnite but msfs2024 throw it in the trash. I dont know who’s really to blame Asobo for lack of x3d optimization or AMD
1 Like