We are reporting this issue for a year now. Not much was done from what i see, if anything. Also Xbox version is crashing aswell which is completely inexcusable because it’s Microsoft game, Microsoft console, running on Microsoft system. They should have every debug tool possible to analyze and fix it. But they have done nothing, or tried and failed. After a year we still dont even have proper debug / log reporting / uploading tool instead we have to manually look for the files deep in system in hidden folders and searching through event viewer lmao, this game is a technical disaster.
3 Likes
Another problem that happened, my simulator crashed when I was downloading some of the free content. My download became stuck, (a 'World Update) and I believe I had crashes following this and the download would get close to finishing and stalled every time. The download was corrupted. I used the content manager to remove the scenery update that I was downloading and then I downloaded afresh and this solved my problem.
Could try this and navigate to C:/Program Files/WindowsApps/ Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe Right click the ‘Flight Simulator.exe’ opening the properties of the executable. Open the ‘Compatibility tab’ and enable, ‘Disable full screen optimisations’ You could also enable, ‘Run as administrator’. I discovered last year that I had multiple registry entries for this folder, Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe, (the name of this folder changes with each update and so it was called something else. Using CCleaner I deleted the old remaining registry entries for the old folder making sure to keep the current new folder. You could try that to see if you have multiple entries in your registry.
I am no expert in this matter however, there is no harm in checking.
You could also, (if not done so already assuming you can get the the ‘Options’ page in MSFS) re-set all your graphics settings to default in MSFS.
Using the Nvidia Settings, set all of these settings to default.
Try starting flight from a new location and turn off ‘Live weather’ to see if that makes a difference.
Disable ‘Live traffic’ and see if that helps!
I wonder if there is simply something that needs changing in the ‘flightsim.ini’ file. I cannot remember where it is located. Perhaps there is some duplicate settings in there?
Perhaps you could also try cleaning out any cached scenery from within the simulator.
If you are using overlays from Nvidia Ge-Force Experience, try disabling them! I am using the ‘skinny driver’ which I installed today which is working great. See below and follow the link from there.
New Nvidia Drivers: 471.41 WHQL 19/July/21 - #677 by CptEvillian
I want to try and help, alas this is all I can think of at the moment.
BRGDS. And good luck 
Charles
This morning I had one in the new float 172 as I was entering other airspace and opened up the ATC window. As I have no third party mods or controllers and nothing except Windows running I can pretty much guarantee it’s an in game issue that although it doesn’t affect everyone will probably still need correcting by way of a patch. I know I’m on Windows 11 with an unsupported gpu but IMO it was too far in for that to be an issue and nothing else has shown in event viewer.
Huge issue, this game is unplayable. Windows and drivers are up to date, folders were cleared, game uninstalled and reinstalled 3 times now. Instant CTD on the map. Disabled online functionality still nothing. Cleared all cache Cannot fly at all. This is bullshitt
4 Likes
Turns out my CTDs were being caused by Process Lasso, where I had set up some CPU affinities that the new FS can’t seem to deal with. It’s more or less stable for me now, except once in while it freezes for a minute plus, then comes back and keeps running. So weird…
The gaphical downgrades are awful though, everything shimmers so much in VR now and I actually have worse performance in GA planes without glass than before. The only positive for me is better FPS with glass cockpits, that’s it.
2 Likes
More CTD’s and logs from event viewer which nobody will even look at, wohoo.
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
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: FlightSimulator.exe, wersja: 0.0.0.0, sygnatura czasowa: 0x00000000
Kod wyjątku: 0xc0000005
Przesunięcie błędu: 0x0000000001c7b300
Identyfikator procesu powodującego błąd: 0x26a0
Godzina uruchomienia aplikacji powodującej błąd: 0x01d782fcbd824a21
Ś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.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Identyfikator raportu: 27f65334-eb5b-4ac9-8889-858134ade2cc
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
1 Like
Ah,ha! I thought it might be something simple like that. I turned my traffic off too. I wonder if turning the ‘live traffic’ off will work for other people too? I have noticed that ‘live weather’ has previously caused CTD when I have loaded a scenario which has live weather enabled. Simply making sure that a static version of the weather scenario was loaded when when setting up a flight stopped the CTD’s. Once the flight had successfully loaded, I could then change to live weather without having a CTD. Something else for others to try.
Brilliant one of my ideas worked for you! 
BRGDS
Charles.
My report is also send to Zendesk.
It is not acceptable, I spend almost 1000 euro for scenery addons and not to mention replaceed my old saitek panels and flightyoke stuff with the new Honeycomb Flightyoke/Throttle. So all investments are for nothing when one update (sim update 5) is rolled out to us. People like you and me are spending money not only in the MSFS software but also in all the addons, plugins, hardware.
This sounds like overreacting, however basically it is the truth.
Totally not acceptable.
So I hope that they solve this as soon as possible.
3 Likes
Yes, I also noticed that Process Laso had set my MSFS priority to low by default. A fresh install of Laso with default settings was used and I noticed this. Charles.
I am also have major freezes and CTDs. Trying to do a clean install now and the downloading freezes for mintues at a time and comes back.
I wonder if this is something server end related…
Before I started the clean install, if I disable my network connection, the sim would load up, go to menu, and fly with no issues. As soon as I re-enable my network connection it would freeze and crash. And restarting the sim couldn’t get past the splash screens.
I did this multiple times and everything I disconnected the internet from my PC, it worked fine. (Besides being offline, no photogrammetry, live weather/traffic, etc.)
And I don’t have process lasso so it’s not that. Tried updating/removing Riva Tuner, no change.
Have you tried turning off ‘live traffic’. This suggestion has just worked for Swede001. Charles
I hear you bro, I got exactly the same CTD as you showed in video.
No solution yet, I am waiting for answer via Zendesk.
1 Like
I will try this when I get home as I have the same setup going on with MSI Afterburner and a overclock. I never had issues untill the latest update I know nothing has changed on my end.
€1000 for scenery add ons!! I wonder how much of that went to Asobo? probably not much.
Have a little patience everyone.
1 Like
I am using MSI Afterburner and Razor Game Booster. No problems with overclocking a GTX 1070 here.
Charles.
Judging by what I am reading, there might be a problem with having ‘Live Traffic’ enabled. Swede001 has just turned his off and now he is flying! Charles.
Yeah I plan to but don’t have time at the moment … it’s something along the lines of ATC or Traffic for most of us and I think it will be fixed soon.
1 Like
HEY!
That worked! did exactly what you said! works perfectly now! thank you so much!
3 Likes
Did your game use to crash when clicking Fly or entering the World Map?
1 Like
Sometimes yes but mostly when I was flying around big cities and changing different camera angles, zooming etc.
But yes, I finished my first 2 hours flight just a while ago, not a single crash what so ever. So something went right there… I think it was the a.i. traffic which caused those CODs in my case.
-John