Is anyone experiencing CTD after updating tp SU16 BETA, since I did, I have not been able to load the sim, not even in safe mode. I have tried everything on the book, except for a full reinstall.
Yes I got a CTD after directly started the sim after updating, but after I cleared my community folder and scenery indexes it started fine and fly normally.
No CTD here, but I just noticed that my community folder was already empty before I joined the beta, for troubleshooting some previous unrelated issues.
Yep ctdās half way through flights ,freezes then goes to desktop
Have you tried gliders? When I select a glider at ā14OIā and load free flight, I experience a CTD.
@ssy523, I have tried loading a glider in free flight at 14OI and it loads fine. It was the first time I tried gliding, though, and my skills leave a lot to be desired 
1 Like
No matter what I do it keeps getting CTD before the main menu, empty community folder, clean video driver installation and cleared the shader cache. airport scenery indexes as well, safe mode, you name it I have tried it, even unrolled from beta and now it doesnāt load the stable version either. might have to do a clean install.
2 Likes
I have constant CTDs (globa map, marketplace - no pattern 
) since yesterday in su15 
.
To the moderators, is there any value in capturing data for CTDs in SU16? For example I just had one, and following the forum instructions for finding the fault bucket ID, here is what comes up. Is this information useful to anyone in the beta process?
Log Name: Application
Source: Windows Error Reporting
Date: 5/06/2025 2:25:17 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: (computername)\capholland
Computer: (computername)
Description:
Fault bucket 2195708457897772692, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.39.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.39.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.39.2.0
P7: 00000000
P8: 80000003
P9: 0000000001e8c242
P10:
Tried to load into NZA Simulations YMHB and had CTD when loading flight.
All other airports I tried seemed ok. Thought at first my airport file had got corrupted somehow. However after reinstall it still crashed. Exited the beta and everything works ok again.
Since the last beta update I also experience random CTDās. All SEH 0xC0000005. First thought it was the ini A350 but also got one on the default 747 today.
Yes - this is true for both Betas and Release builds.
The pertinent information is the Fault bucket ID, e.g. in your example:
Fault bucket 2195708457897772692, type 5
Users can learn how to find that ID here: How to find your Fault Bucket ID after a crash [PC]
This ID can be matched by the test & development teams to detailed information about the errors that Windows has automatically submitted (unless you have disabled this functionality). In Windows 11, you can see these in the Reliability Monitor (not sure about Windows 10):
If there is a crash, it should show up here, and you can click on the report to see if it has been submitted.
1 Like
I am on windows 10, you can also find it in the event viewer. These are from the three CTDās I got this weekend:
Fault bucket 2204072343461027361, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.39.2.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.39.2.0
P6: 00000000
P7: c0000005
P8: 00000000002be3a6
P9:
P10:
Fault bucket 1666717600763399487, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.39.2.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.39.2.0
P6: 00000000
P7: c0000005
P8: 0000000001dda253
P9:
P10:
Fault bucket 2156384979314179535, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.39.2.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.39.2.0
P6: 00000000
P7: c0000005
P8: 0000000001dc5c16
P9:
P10:
Let me know if you need any more information, I am happy to help 
Constant CTD when loading the sim. Never make it to the Main Menu. 50 Series card with current drivers.
@XeOperator, at one point I had this problem. When first testing the FS2020 beta, I removed everything from my community folder, and also ādeletedā most of my marketplace add-ons, to reduce the total space used by FS2020 on the drive. Over time Iāve been slowly adding things back, like re-installing owned marketplace add-ons, and putting things back in the community folder.
Then at one point I ran into your exact scenario, persistent CTD in SU16 beta before it hit the main menu. It happened after I added a few too many things into my community folder at once. Hereās the steps I took to fix it. This may or may not work for you. Iām on a Windows PC with a Windows Store (not Steam) edition of FS2020:
1 - With FS2020 closed (not running, check Task Manager to be sure) if there is anything in your community folder, remove it
2 - In the Xbox Insider app, select the āleave previewā option for the FS2020 beta, and let the app complete that process
3 - Once the āleave previewā process completes, restart the computer. (You donāt always have to, but itās a good idea and in a case like yours I recommend it)
4 - When the computer restarts, relaunch FS2020. It should pull in an update and revert to the non-beta version. Hopefully you get to the main menu.
5 - Go to the ācontent managerā and delete any marketplace add-on content you might have installed. In my case I also uninstalled a couple of world updates for areas I didnāt fly in as frequently.
6 - Once you finish, exit FS2020 (and remember that youāll also need to use the āend taskā option via Task Manager)
7 - Relaunch the xbox insider app, and rejoin the FS2020 beta program. Wait for the Xbox insider app to finish processing the request, and then close out of the Xbox insider app.
8 - For good measure, I recommend again restarting your computer at this stage.
9 - When the computer starts back up, restart FS2020, and confirm that it pulls in the update needed to load the SU16 beta (at the moment it should show version 1.39.3.0 in the title bar)
Hopefully once all that is done, fingers crossed, you can now get to the SU16 beta main menu, and start flying around again.
If so, you can then slowly begin reselecting and installing one or two marketplace add-ons at a time via the content manager. Then exit FS2020, and restart, to see if that specific marketplace add-on is possibly responsible for the pre-menu CTD.
If all your marketplace content reinstalls and works fine, then itās time to follow the same process for community packages. (Exit FS2020, add an item to the community folder, restart FS2020.)
If you identify a specific marketplace add-on or community package that is causing your issue, Iām sure that will be a valuable piece of information, especially if more of us can reproduce the same result. Itās a lot of work, but thatās kind of what you sign up for when participating in a beta.
1 Like
Had another CTD recreating a flight from YCFS to YRED, when flying across the TIN area for the Gold Coast. This was about 90 minutes into the session, although maybe only 30-40 minutes into the flight, since I had to put the the flight into āactive pauseā a few times while tending to other things around the house.
Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.4.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.4.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.4.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0000000001e8dec2
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: cf43
Additional Information 2: cf43bdabb72c8cb6aa612341ddfc8c1b
Additional Information 3: d7e7
Additional Information 4: d7e71603c48881af80c12cdcf4c76362
Extra information about the problem
Bucket ID: 9e51c35fbba0564bc3aec05b20f04808 (1418282430295459848)
Another CTD, this time during a night flight from YCFS to YSBK, about 30 minutes after take-off. Was running FSLTL (Traffic Injector 1.6.8 stable) and LittleNavMap (v3.0.17) along with SU16.
No traffic injector activity concurrent with the CTD
Source
FlightSimulator.exe
Summary
Stopped working
Date
ā29/ā06/ā2025 10:12 AM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.5.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.5.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0000000001e8de82
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: cf43
Additional Information 2: cf43bdabb72c8cb6aa612341ddfc8c1b
Additional Information 3: 24e7
Additional Information 4: 24e7f363e43e7c2b2e83de80cbaacb02
Extra information about the problem
Bucket ID: 45dd1f2595b1b928747f949fe635ce54 (1477062617283808852)
Holy ā ā ā ā ! Having the same issue as you with the exact same fault bucket. I have FSLTL too oddly. Having these CTDs in flight and descent and more.
By any chance when the crash happens your PCās RAM peaks out?