566.14 Removes CTDs and Stutters? (3XXX Series Card)

Hello.

I have been haunted by CTDs in MSFS 2024 (DXGI Error Device Hung and others) for days. To make things worse, it also occurred in MSFS 2020. Normally, this possible solution used to work but not this time. I decided to uninstall my driver using DDU and installed the 12th November’s 566.14.

Surprisingly, not only does it remove CTDS in both sims but also does it eliminate stutters in MSFS 2020 (I have always had occasional stutters in 2020, not in MSFS 2024). The reason why I revert to 566.14 is because the driver was officially stated as optimized for MSFS 2024. I heard nothing but good things about 566.34 too.

If you are struggling with CTDS and stutters, it wont hurt to try. Hope this helps

1 Like

I always go back to 566.14. I suggest you all keep that .exe file installer somewhere on your hdds. Why? I caught Nvidia was changing installers 2 times so far on their websites, probably for whitelisting profiles etc but who knows… it is Nvidia, i can expect anything from them at this point to push 3000 4000 series card users to 5000 series. And 566.36 also great for 3000 4000 series cards (it just hates my LG C1 tv). We are expecting a good driver for all of the GPUs soon, after windows11 24H2 KB5058499 release (june 10th). Try to Stay on 23H2 if you guys can as much as possible, initial 24H2 KB5058499 tests are not looking good so far. 590.10 also not good. If you guys need, google drive (debloated) > 566.14 - 566.36

1 Like

I absolutely agree that driver 566.36 is primo for pre-5000 series card owners. Though 566.14 is good choice too and I understand your reasoning for using it.

2 Likes

I remember this sim being smoother etc when I first got it a few months ago so figured I’d give this a go.

I’ve done a DDU uninstall of the latest driver and then installed 566.36. I have the latest DLSS files via swapper but have lost the ability to select Preset K for DLSS / DLAA. However, tentatively, this does seem better. Switching between preset camera positions doesn’t appear to be stuttering anything like as much and the audio popping seems to have stopped.

I’ll stick with it a bit and see how I get on.

2 Likes

I’ve been using 572.16 with no issues in VR, very smooth

1 Like

Just got back on 566.36 myself today..

End of the day, with me and 202,4, that CPU usage is CRAZY high and lowering it to older drivers may result in lowering the CPU’s core usage.

FWIW I’m on a 4090

Looks like cartoons on a 4070ti.

It really sounds to me that there is something fundamentally wrong with your computer to be honest.

You’re literally on every thread saying how bad it all is, now that changing a GPU driver makes everything look like a cartoon. That is, of course, not possible.

Downgrade Drivers to 566.63 - NOPE

CPU usage is still 100% - nothing else but MSFS, yet GPU usage is lowered to 24%

I thought it was improved; however, when I loaded a bigger aircraft into the sim, the CPU usage started going up and up. Movement spikes to 100%, and sounds start to crack.

Other games are all fine, even 2020. 2024 is the only sim/game that I have played that eats my CPU on all cores at 100%

Might have to downgrade drivers even older? Like 5 years ago?

Even a clean windows install doesn’t even resolve it, CPU always high

Well, that or buy a new CPU :man_shrugging:t3:

566.63 was the first drivers with RTX 5000 support, right ?
Saw you also tested 566.36 with no much success, did you try with the .14 ?

No. 566.36 was the last driver BEFORE 5000 series support.

And with it you lose the ability to use the latest DLSS.

For older drivers all you need is DLSS Tweaks
Also if you want to change latest .dll files, you can use DLSS Swapper or you can manually download them from techpowerup DLSS - FrameGen

For DlssTweaks, put the files where FlightSimulator2024.exe is (where ever you installed example C:\XboxGames\Microsoft Flight Simulator 2024\Content), run the DLSSTweaksConfig.exe where FlightSimulator2024.exe is, adjust them similar like this. You don’t have to do DlssQualityLevels section. Don’t forget to Save.
Manual downloaded dll files goes to the same place where FlightSimulator2024.exe is.

DLSSSwapper don’t forget to download dll files there.

Nvidia dlss indicator registry files, enable disable to check ingame overlay.

Here is result on older driver 566.14 Imgur: The magic of the Internet

1 Like

I did a flight with the 777F today, Seattle to San Fran using 566.36 with my 9800x3D and 4090, and the whole experience was smooth, including the landing.

I need to test more but it’s still suggesting this driver may well be a good one, and if it is the last non-5000 series driver I’d say that raises some questions for Nvidia.

I should also say that since switching to this driver that annoying audio crackling has also stopped. Although the latest deep learning output isn’t available to me using this platform (Profile K - DLSS4) using DLAA I’m seeing no blurring of the screens.

3 Likes

True. And as a consequence, I have surmised that the latest DLSS updates are what causing pre-5000 series cards to perform badly with the 572.xx branch and later drivers.

1 Like

Using DLSS Tweaks, DLSS Swapper or any other third-party apps to “modify” the driver package is just asking for trouble. If the driver and the game don’t support a particular feature, forcing it to do so with a third-party app is ill-advised.

2 Likes

I’m not having any problems with the 572 on my 4070 so I’m gonna stay put for now.

I just don’t get it.

Microsoft Flight Simulator 2024 is running on DirectX 12, so why isn’t my GPU not being fully utilized? That’s the whole point of DX12, better multi-threading, more efficient GPU use. I’d understand this kind of CPU-heavy bottleneck in DX11, but in DX12? Come on!

I’ve gone through another round of tweaking today turned a bunch of settings from High to Medium, even some to Low or Off and yes, the Cessna 172 now holds a stable 60 FPS, which is great… but my GPU is sitting at just 20%, while the CPU is pegged at 80–100% most of the time.

No matter what I do, the CPU load is always high. I can’t get it to relax. It’s like the sim just doesn’t want to offload anything to the GPU. And I’ve tested this across different aircraft and environments.

Now, with the NVIDIA 566.36 drivers?
Yes, they’ve helped!
In other games and even in MSFS 2020, performance is better. But not in 2024. The improvement just isn’t there.

Throw in a heavier aircraft or spawn into a busy airport, even on Medium settings, and boom, CPU hits 100%, while the GPU struggles to get past 40%.

This isn’t how DX12 is supposed to work. There’s clearly something broken, either in the sim’s engine optimization or how the workload is being distributed. It’s frustrating when the hardware isn’t being used to its full potential, especially when MSFS is this demanding.

That’s not going to resolve the issue, I can say that with confidence.

I know people running top-tier setups, like the Ryzen 9 9800X3, and even they’re seeing CPU usage spike into the 60% when flying something demanding like the Fenix A320. This isn’t just an issue for mid-range systems, it’s happening on high-end rigs too.

One friend of mine is using that 9800X3D paired with an RTX 5080, and even with that level of hardware, he’s hitting serious limitations. His VRAM is capped at 16GB, and in MSFS 2024, he’s constantly running into memory bottlenecks. As a result, he’s been forced to turn down a lot of settings not for FPS reasons, but because he’s literally running out of VRAM in certain scenarios.

It just goes to show that this isn’t a simple throw more hardware at it situation. The optimization in MSFS 2024 clearly has issues, especially when even the best consumer CPUs and GPUs are struggling to keep up in high-fidelity environments or with complex aircraft. Whether it’s poor thread distribution on the CPU side, inefficient use of GPU resources, or the way the sim handles memory, there’s something fundamentally off.

This isn’t just about older or budget systems falling behind, even the latest and greatest are being pushed to their limits, and not always for the right reasons. Until Asobo or Microsoft seriously address how MSFS 2024 utilizes modern hardware, these problems are going to persist, no matter how powerful your rig is.