Crash to desktop without error message

I wonder are there any of the " IT’S YOUR SYSTEM " guys suffering this CTD now…

4 Likes

I still have no CTDs… as mentioned only these Freeze in case EGLC is installed.

But thanks that you ask :wink:

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: 0

Podpis 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.txt

Te pliki mogą być dostępne tutaj:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_a179f4a8a1520d31d8098a4b52dc555a76d34eb_e0737c83_76a1d697-b046-4aaa-8885-545c243a774f

Symbol 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: 0

Podpis 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.txt

Te 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: 0

Podpis 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.txt

Te pliki mogą być dostępne tutaj:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_a4b3854dc15b3c3831ece956815d2f0956efabc_e0737c83_b5b34cea-6b85-4eb2-af58-5a4c99f04d03

Symbol 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

1 Like

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 :slight_smile:

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.

1 Like

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 :wink:

1 Like

This is listed in the change log as a known issue, though it doesn’t make the distinction between AI traffic, and “Live” traffic.

@AltamiraDan … yes… I will do that… and the reason is that we , the community, can still find post and can also react in a usefull way to posts.

CTD all the time. Last time when I put Bing Maps geothing on.
PC: GTX3090 , i9, etc…
Finding a sollution is nice but didn’t we pay Asobo for that?

1 Like

here is a post with the steps: FlightSimulator.exe crash to desktop error 0xc0000005 - #8 by MichaMMA ( may be you find some more in forum )

… normaly it is your C: drive where the pagefile lies.

yep… we had this discussion already… Of course is a CTD not nice, nobody is happy about, etc… but may be it is nothing what the devs must fix ( because eg. users system side, e.g these usage of process lasso tool ) , or may be a workaround is quicker than waiting till the next update, etc… and therefore is this forum here. And therefore it is important that users report here issues to ZenDesk too ( also if these ticket are “seemingly” closed ).

after couple of crashes flew all day with brakes and some flights even without out of the game, to main menu and flight again, crash was once in cri cri somewhere at india or georgia(kaucasus) then spitfire twice haifa and may be at kyiv, i don’t sure, must be something after update rewrite in system, then have some long loading with bell-47g but this is normal, because first it was old incompatible version, then new version first time reload own settings in new sim, then everything ok in corsair, and cri cri, and many time in bell-47g…

1 Like

Sorry, I didn’t read 4500 messages. CTDs are after SU5, so devs problem and devs sollutions. I don’t like work arounds. I payed for a game, I like to play. And as we speak I’m reporting to ZenDesk.

5 Likes

Alas, same story. Wonder what is causing it. I don’t feel like doing a reinstall until I know for sure that it solves it.

Anyway, thank you for your help. Just wish I could check out the performance gains :pensive:

3 Likes