Been getting a lot of these also. CTD while loading game, mid flight and sometimes just in the menu.
Solved this by deleting the cache file. Been back in game for a few hours now with no crashes.
General Options > data > delete rolling cache file.
Backup or deleting everything in Community folder doesn’t solved it too. Infact I have followed every single steps in this guide.
Have look, maybe it will help you.
Did not work for me, still crashed after around 5 minutes and still get the same crash message in event viewer
Faulting application name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000019e3567
Faulting process id: 0x818
Faulting application start time: 0x01d783b361ffb500
Faulting application path: D:\SteamLibrary2\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary2\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 7950b76f-ae57-4fce-985a-fbc9f1e6f075
Faulting package full name:
Faulting package-relative application ID:
Exactly the same ! i ve done all was written here , community folder empty , deleting the cache file ;
I had no CTD before the last update of july 27th ; All went ok before , even with my HP Reverb G2 and my old graphic card 1080 GTX …
Now , its a shame
Multiple CTD , the last message in the event viewer is ( in french because i live in France )
Nom de l’application défaillante FlightSimulator.exe, version : 1.18.13.0, horodatage : 0x00000000
Nom du module défaillant : FlightSimulator.exe, version : 1.18.13.0, horodatage : 0x00000000
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000001123df0
ID du processus défaillant : 0x2548
Heure de début de l’application défaillante : 0x01d783b5d42bd453
Chemin d’accès de l’application défaillante : D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Chemin d’accès du module défaillant: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
ID de rapport : 3e88d904-8541-4dd4-b248-1e822e66b28a
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
Please , don t wait too long before release a new hotfix !
Thanks
Sadly I have nothing in my Community folder, so I have no idea what could be the issue. Still crash when I click 'Fly".
At least we’re all being kept in the loop by Asobo.
can we possible collect the locations where its happens ?
I noticed ,as example, that not all add-ons are compatible for now. As example I had installed EGLC (London) airport, but in case I would start from it or start in-the-air neartby the airport, the game freeze ( not crash) while loading into the flight. I deinstalled the add-on for now and all is fine at these location.
I’am not sure what had happened in case I entered these area from an existing flight.
( note: it is a market place add-on )
The AI issue was already mentioned.. possible try too.
I wonder are there any of the " IT’S YOUR SYSTEM " guys suffering this CTD now..
I still have no CTDs… as mentioned only these Freeze in case EGLC is installed.
But thanks that you ask 
Bunch of CTD’s mostly during loading, today i had another 2 but it’s not available in event viewer.
Pakiet błędów 1352684324421254551, typ 5
Nazwa zdarzenia: MoAppCrash
Odpowiedź: Niedostępny
Identyfikator pliku CAB: 0Podpis problemu:
P1: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: VCRUNTIME140.dll
P6: 14.29.30035.0
P7: 608dc4a3
P8: c0000005
P9: 00000000000013fd
P10:Dołączone pliki:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBE9B.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0BF.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0DF.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0DD.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0FE.tmp.txtTe pliki mogą być dostępne tutaj:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_a179f4a8a1520d31d8098a4b52dc555a76d34eb_e0737c83_76a1d697-b046-4aaa-8885-545c243a774fSymbol analizy:
Ponowne wyszukiwanie rozwiązania: 0
Identyfikator raportu: 368746ea-9885-42dc-af25-e3d2a058c884
Stan raportu: 268435456
Wartość skrótu pakietu: ab02bef09ed0fbab02c5b339ea5e3d97
Identyfikator GUID pliku CAB: 0
Nazwa aplikacji powodującej błąd: FlightSimulator.exe, wersja: 0.0.0.0, sygnatura czasowa: 0x00000000
Nazwa modułu powodującego błąd: VCRUNTIME140.dll, wersja: 14.29.30035.0, sygnatura czasowa: 0x608dc4a3
Kod wyjątku: 0xc0000005
Przesunięcie błędu: 0x00000000000013fd
Identyfikator procesu powodującego błąd: 0x2c6c
Godzina uruchomienia aplikacji powodującej błąd: 0x01d782fd24b1363d
Ścieżka aplikacji powodującej błąd: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Ścieżka modułu powodującego błąd: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30035.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Identyfikator raportu: 368746ea-9885-42dc-af25-e3d2a058c884
Pełna nazwa pakietu powodującego błąd: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Identyfikator aplikacji względem pakietu powodującego błąd: App
Pakiet błędów 1843924179855047036, typ 5
Nazwa zdarzenia: RADAR_PRE_LEAK_64
Odpowiedź: Niedostępny
Identyfikator pliku CAB: 0Podpis problemu:
P1: FlightSimulator.exe
P2: 0.0.0.0
P3: 10.0.19043.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:Dołączone pliki:
\?\E:\TMP\RDRE46D.tmp\empty.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE47D.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE48E.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4AB.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4DB.tmp.txtTe pliki mogą być dostępne tutaj:
Symbol analizy:
Ponowne wyszukiwanie rozwiązania: 0
Identyfikator raportu: 44e36294-71b3-4091-bfad-d16108239e5b
Stan raportu: 268435456
Wartość skrótu pakietu: 4f337be3224a6e313996ef45a503797c
Identyfikator GUID pliku CAB: 0
Pakiet błędów 1616011227730912042, typ 5
Nazwa zdarzenia: MoAppCrash
Odpowiedź: Niedostępny
Identyfikator pliku CAB: 0Podpis problemu:
P1: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001c7b300
P10:Dołączone pliki:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER839E.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER863F.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8650.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER864E.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER866E.tmp.txtTe pliki mogą być dostępne tutaj:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_a4b3854dc15b3c3831ece956815d2f0956efabc_e0737c83_b5b34cea-6b85-4eb2-af58-5a4c99f04d03Symbol analizy:
Ponowne wyszukiwanie rozwiązania: 0
Identyfikator raportu: 27f65334-eb5b-4ac9-8889-858134ade2cc
Stan raportu: 268435456
Wartość skrótu pakietu: fbeb6759c0c28e9b366d39a64df1a32a
Okay, for full clarity:
Faulting application name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.18.13.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000026873b8
Faulting process id: 0x5138
Faulting application start time: 0x01d783b970e1eca8
Faulting application path: E:\SteamLibrarySSD\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: E:\SteamLibrarySSD\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 660c5f4d-bff3-4ac7-b8db-c73638359c72
Faulting package full name:
Faulting package-relative application ID:
I CTD whenever I click fly. I did not have anything in my community folder, I did have a IFR training thingy I downloaded. Deleted it all through the content manager. Still when I click fly, it goes black for a few seconds and then crashes to desktop.
Specs:
AMD Ryzen 7 5800H with Radeon Graphics
NVIDIA GeForce RTX 3060 Laptop GPU
16 GB RAM
Windows 10
not sure whether our former experiance is valid for SU5. But former these combination was often less free disc space, or a not sufficent pagefile size.
we can nothing fix .. we can discuss about possible workarounds. Dont forget to create a official ZenDesk Ticket.
On other side I dont know what we can discuss. You gave us zero informations about your issue.
I have almost 100GB free on my SSD, you think it is not enough?
I’ve done with less before this update lol
this is enough , but may be not enough for windows decision about pagefile size. You can try the old solution and manualy change the windows virtual memory (pagefile ) setting to min/max 8192/20000. With a bit luck 
Would that be my external SSD that has the MSFS install or the one Windows is installed on?
In any case I have no idea how to change that and the tutorials I found on the windows website are out of date lol
I have been having CTDs since the update but just tried with AI traffic set to real time and manged to complete one flight. If you use VR make sure that traffic is adjusted in both VR and PC settings that seemed to work for me.
All my above CTD’s are with ai traffic set to real time.
Ah thats good to hear.. You’ll be able to spend even more time making sure we are complaining about CTD in the right post Categories