CDT during flight

Hello, on every flight CDT. always the same error in the log
i see no issues in System. No CPU overclocking, no GPU overclocking.
no issues with temperatures.

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x5f5b8327
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x5f5b8327
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001160dd0
ID des fehlerhaften Prozesses: 0xeb0
Startzeit der fehlerhaften Anwendung: 0x01d6923a70c866c4
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 7715be4a-7cbb-4a6e-8c3b-537fa2ac8567
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x5f5b8327
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x5f5b8327
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001160dd0
ID des fehlerhaften Prozesses: 0xcd0
Startzeit der fehlerhaften Anwendung: 0x01d691cbfb903fad
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: e18d4968-76ba-4135-88f4-0fde2e013f17
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

@FragezeichenAUT Welcome to the forums.

There are quite a few threads on the forums where people are reporting crash to desktops and it seems there is no one single cause. Reports indicate that the ‘fix’ for one user doesn’t work for another user etc. Tracking down the cause is very time consuming. I suggest maybe using the forum search function to find other threads for this issue. If you wanted to be brave, even though it is time consuming, you could take the plunge and go ahead and reinstall windows. It might actually save you time in the long run. However, it doesn’t guarantee that it will solve your problem if the CTD is caused by hardware weaknesses (unlikely but possible) or driver issues.

To get you started, here are two links (Link1 , Link2 ) to existing mega-threads about CTDs.

It would also be a good idea to check out the known issues post to see if you are affected by one of those.

For advanced troubleshooting, if none of the other fixes seem to work, then there may also be some useful information contained in this detailed thread: Community Troubleshooting Guide.

2 Likes