Extremely annoying to play MSFS on the RX 6900 XT. Who shares this frustration?
Extremely annoying to play MSFS on the RX 6900 XT. Who shares this frustration?
Hi there
Recently I purchased an AMD card to play more of Microsoft's new flight simulator. It turned out the drivers weren't working properly and caused a lot of crashes. At first I thought it might be a problem with my combination of motherboard and card. But after sharing my issue on the AMD forums, others started joining in. Maybe we can figure out why these CTDs keep happening. Or someone experienced can help identify the exact cause. Here’s my final post on the AMD community site: https://community.amd.com/t5/drivers-sof...ad-message. Any assistance would be really appreciated. Cheers, Jerry
I’m struggling to understand the rest of the system and what you’re referring to by “ctd.” Acronyms can be confusing, as people often assume only one meaning. Usually there are many possible interpretations. I can sometimes guess from the surrounding text, but this time none of the options make sense—it seems like a failure, yet none of them fit.
Thanks for the update. A crash to desktop is essentially a CTD situation. The program stops, the screen goes black, then the game freezes or closes abruptly. This occurs in both cases. Based on my Windows Reliability History, the cause appears to be: Source FlightSimulator.exe stopped working – Date 29.04.2021 21:10. Status Report sent. Description: Faulting Application Path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Problem signature Problem Event Name: APPCRASH Application Name: FlightSimulator.exe Application Version: 1.15.8.0 Application Timestamp: 00000000 Fault Module Name: VCRUNTIME140.dll Fault Module Version: 14.28.29913.0 Fault Module Timestamp: 6041a7e8 Exception Code: c0000005 Exception Offset: 0000000000001597 OS Version: 10.0.19042.2.0.256.48 Locale ID: 1031 Additional Info: 8c66 8c662f6c7f00d6de72ab9c998f8b8ef9 15cb 15cb13b5f83ab4ecfcdcdbdf6753a385 Further details: Bucket ID f9a129599b844953eda465b41dff65eb (2135943947552253419) So, it’s consistently exception code c0000005. Debugging with Microsoft Visual Studio shows the app halting because it keeps trying to write to unallocated memory. I don’t recall any Visual Studio attempts before. My machine is a Rio Toro Enigma G2 850W MSI MEG ACE Z390 with 64GB dual channel storage, using a mix of SATA HDDs and SSDs for data. Any suggestions?
Aha. That clarifies things. Sometimes the app quits but Windows stays stable, and other times everything crashes while the system remains intact—no typical “BSD” crash to desktop usually here, just a full machine failure. I really dislike those troubleshooting dumps; they can backfire more than help. You handled acronyms well, so I’ll give it a try, though it might not work. There are folks around who seem better at this than me. All I know is the issue likely comes from the app or a specific .dll inside it, which is failing to load properly. I haven’t heard many reports of GPU problems like this, though it’s becoming less common due to the GPU shortage. DLL stands for dynamic load library, essentially a chunk of data the game uses while running. Why it’s not working smoothly isn’t clear to me. It could be the app is trying to access it incorrectly or missing something needed. If it’s just a personal issue, a fresh install of MSFS might help. Or maybe not. Edited May 12, 2021 by Bombastinator
Hello everyone! Struggling with CTDs on my new AMD graphics card pushed me to dig deeper. Eventually, I realized I’d wish to trade in my RX 6900 XT and splurge on a car. Unbeknownst to me, the situation was far from ideal! My setup includes: a Rio Toro Enigma G2 850W MSI MEG ACE Z390 with 64GB dual channel Kingston KHX3600C18D4/32GX SSDs, and a mix of SATA HDDs for storage. For graphics, I’m using MSI RTX 3090 Gaming X Trio, Gigabyte RTX 2080 Ti Windforce (120 MHz auto overclock on air), and an XFX RX 6900 XT. The main issue? Unusually tight mainthread control, which kept one core maxed out and limited my graphics choices. Many CTDs work well with AMD cards but struggle with Nvidia drivers. I encountered serial errors like FlightSimulator.exe freezing, with logs showing APPCRASH, VCRUNTIME140.dll, and a specific exception code c0000005. Debugging in Visual Studio revealed the app was stuck trying to write to unallocated memory.
I tried adjusting system settings via msconfig.exe—turning off the “Number of processors” option freed up cores. Restoring it back to full enabled the issue, boosting performance. It seems Nvidia’s driver sometimes misjudges performance based on core count rather than actual capability. My suspicion is that AMD drivers are more intelligent, better utilizing available cores and threads. This fix not only resolved the crash but also improved stability across games like FlightSimulator and other resource-heavy apps.
Performance now feels smoother, especially in demanding scenarios. I’m hopeful this will prevent future memory allocation problems and CTDs. I’ll keep monitoring updates on MSFS’ support page for further guidance. Cheers!