Oh, miracle. I flew from EDDB to SBGR for 13 hours without canceling CTD. I haven’t changed anything in MSFS 2020. Three things have changed.
I installed the current NVIDIA driver 466.77.
KB5004476 optional W10 update installed.
I flew 360 NM west of the route given in the FMC.
Before that I had 4 CTDs with the same settings. Flight was restarted via logbook. That’s all. EDP end of reason.
2021.06.27 Hooray, for 18 days without Ctd. Very often I flew for more than 10 hours. Just as information.
I’ve mentioned this in other threads but I believe these “fixes” are just coincidences rather than getting to the real crux of the problem. Some work for a time (or is it just a coincidence?), but not for others.
For a while I was convinced it was related to AI traffic, then to KLM1494113’s theory about the C++ drivers.
Currently my pet work around relates to virtual memory. I have disabled the system control of the swap file and instead have set the file size to 2x my RAM, of which I have 32gb installed. This will be the peg on which I will hang my hat until I start seeing the CTDs again (which I am sure I will).
EDIT
Of course after I write this I get a new Windows update which will probably end up moving the goalposts yet again.
Update:
Second response of the support was “send dxdiag and msinfo32”. So I did.
Third response after this was “Uninstall and reinstall your graphic drivers”.
Well, I guess we won’t get any help from MS / the devs…
This is the exception code and the same offset that I get. Radeon 5700XT. I suppose that this isn’t something a user could fix on their own by your statement, but just wanted to check to see if you may have found a fix. Thanks!
@Spieler38073707 I was on to Zendesk for weeks… After system reinstall and MSFS reinstall… In the end they just mark my support as solved and disabled comments
Like everyone else here I am experiencing the same crashes:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7
Faulting module name: RenoirCore.WindowsDesktop.dll, version: 0.0.0.0, time stamp: 0x5fc6a5f7
Exception code: 0xc0000005
Fault offset: 0x0000000000051c77
Faulting process id: 0x1190
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000014b4
Faulting process id: 0x4378
I’ve only been playing this for about two weeks - base game from MS Game Pass. I didn’t have any of these problems in the training flights - only when I took to the real world.
I disabled HW acceleration, uninstalled Radeon software (although running the latest driver), ran this registry hack mentioned elsewhere: Windows Registry Editor Version 5.00
And I still experience crashes. I flew an entire flight tonight for over an hour and when I get to the destination, on the runway, and radio ATC, the game crashes. It also crashed when I switch between monitors as I have a duel monitor setup. Before those measures implemented above, the game would crash midflight, when I turned on the cockpit like, and at any other time really. So far it “seems” to be running better, but clearly not perfect, not even close.
Same here, each single of my crashes have the same error, not only the flight model is bad ASOBO does not even put resources to make a Microsoft game working on a Microsoft Platform using Microsoft API…
Has anyone experienced crashes using the AI? I’ve let the AI run for multiple flights 30+ minutes and no crashes - but the flights often crash on user input such as the cockpit light as I mentioned above, or radioing ground control. I’m not a programmer of any sort so I don’t know how I would interpret this or why that would cause a CTD.
People say it’s connected to memory, however I don’t think it’s connected with our hardware memory and its potentional failure - more with software memory managment in core of MSFS.
I’ve just finished 8 hours of memtest64 with 30 out of 32GB memory - 0 errors!
And CTD still occurs:
FlightSimulator.exe
1.16.2.0
00000000
VCRUNTIME140.dll
14.29.30037.0
609de407
c0000005
00000000000012db
378c
01d75e1711e72999
D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
63e895a7-cf30-4aa3-84cc-395c1b99e282
Another day, another CTD. If anything the CTDs seem to happen in the morning rather than the evening with me. I know, I know, grasping at straws. It’s always with a heavy heart I hear the sound break up, come back then break up again knowing that the CTD is incoming and there isn’t a ■■■■ thing I can do.
If it was connected to faulty RAM modules, we should expect other games and/or software to randomly crash as well (not just MSFS). Although there have been cases where the memory (or PSU, or GPU) was at fault and replacing the modules did the trick, I’m getting the feeling that most people here who suffer from MSFS CTDs do not have any other issues with any other software, just MSFS. Otherwise it’d be much easier to identify and solve the problem.
The usual problem is that it’s only MSFS that crashes repeatedly, nothing else.
I think I got new informations:
So official support wanted me to uninstall my graphic drivers and reinstall the newest ones. So I used the AMD driver clean up utility and installed AMD drivers version 21.5.2 . When is opened MSFS I immediately recognized that the image flickering a lot. So not really an improvement. But well I thought let’s give it a try, maybe no CTDs. But I still got a VCRUNTIME140.dll error after 15 minutes. But with this drivers the game does not simply close, so it is not really a CTD but the game hangs and gives me an error message. The text of the error message translated to english is:
"The instruction at 0x00007FFA493E1597 referenced memory at 0x00000000000000. The operation written could not be carried out in the memory. "
Well guys, this looks like MSFS is giving me a nullpointer exception. Now I am curios if support will still tell me that the problem is on my side.
