I just started, avoiding the loading of FSUIP7, and the simulator started without any problems… empty community folder… What’s the solution? Can anyone comment on which external programs require FSUIP7? Thanks a lot!
Experiencing the Crash during loading 3rd party aircraft like iFly MAX8 or Fenix A320 Aircraft into the simulator, so after you press “Start” and before you reach “ready to fly”
Build 1.5.10.0
Fault bucket 1172182527730605683, type 4
Steam Store.
Everything was working fine up to build 1.5.9.0
AsoboReport-Crash.txt (24.2 KB)
AsoboReport-RunningSession.txt (23.8 KB)
Store version CTD at +/- 50 load
exe.xml is empty and content.xml is empty
Buket here:
Log Name: Application
Source: Windows Error Reporting
Date: 26/06/2025 09:43:39
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: DADDY
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1: 141
P2: ffff828492350460
P3: fffff8033b1aa730
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 256_1
P9:
P10:
Attached files:
\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20250625-1318.dmp
\?\C:\Windows\SystemTemp\WER-447078-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f938ef78-ceb6-429d-a7ee-3d2a859811eb.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ca6c0718-eb55-48a0-a36e-216407a8708a.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4c1587d9-e4bb-4fd1-a150-e9c96e968ee0.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7c9a31a-a79e-40c1-85ef-0329f89d3433.tmp.xml
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_edf2afdccf42569d198f7c0a1a11035813abde7_00000000_ee0e945e-bb6c-41c5-b0bf-e7b87dd4f851
Analysis symbol:
Rechecking for solution: 0
Report Id: ee0e945e-bb6c-41c5-b0bf-e7b87dd4f851
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:
1001
0
4
0
0
0x8000000000000000
24001
Application
DADDY
0
LiveKernelEvent
Not available
0
141
ffff828492350460
fffff8033b1aa730
0
0
10_0_26100
0_0
256_1
\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20250625-1318.dmp
\?\C:\Windows\SystemTemp\WER-447078-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f938ef78-ceb6-429d-a7ee-3d2a859811eb.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ca6c0718-eb55-48a0-a36e-216407a8708a.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4c1587d9-e4bb-4fd1-a150-e9c96e968ee0.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d7c9a31a-a79e-40c1-85ef-0329f89d3433.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_edf2afdccf42569d198f7c0a1a11035813abde7_00000000_ee0e945e-bb6c-41c5-b0bf-e7b87dd4f851
0
ee0e945e-bb6c-41c5-b0bf-e7b87dd4f851
2049
0
If it can be useful… I was stopped at the LFPO airport (pay scenario) with the cessna 172… after activating Batc everything was normal but after about 5\7 minutes I had a CDT here is the report.
Nome applicazione con errore: FlightSimulator2024.exe, versione: 1.5.10.0, timestamp: 0x00000000
Nome modulo non valido: ucrtbase.dll, versione: 10.0.26100.4202, timestamp: 0x32a4a0e5
Codice eccezione: 0xc0000005
Offset errore: 0x0000000000060599
Id di processo in errore: 0x8F84
Ora di avvio dell’applicazione in errore: 0x1DBE671F01817B2
Percorso dell’applicazione in errore: C:\Program Files\WindowsApps\Microsoft.Limitless_1.5.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Percorso del modulo in errore: C:\WINDOWS\System32\ucrtbase.dll
Id di rapporto: 79d3932e-cca5-4eb0-b0b6-1e50bd69d0df
Nome completo del pacchetto guasto: Microsoft.Limitless_1.5.10.0_x64__8wekyb3d8bbwe
ID applicativo relativo al pacchetto guasto: App
Hi.
For me this beta has been somewhat stable.
I’m on the Steam version.
Not using FSUIPC.
The addons I use and don’t seem to have problems are BATC, GSX, Simrate Panel, Navigraph EFB Simbrief App, Briefing Panel and Handlebar Mod.
The only CTD’s I have are when trying to use PMDG 737-800. In previous betas I could use the aircraft without issues. Now it CTD’s when trying to spawn.
I didn’t do any files cleaning for this beta version and I do use some 3rd party airports and aircraft.
Cheers
3 Likes
Fault bucket 1856377202958665170, type 5
Guys, whatever happens next. PLEASE rename your Community Folder, backup flightsimulator.exe, usercfg.opt, exe.xml, camera.cfg’s, content.xml (not really necessary) and export your User Controls. Lord knows what will happen next.
2 Likes
I’m also having CTD. Loading into Menu is no Problem. CTD happens when I try to load into Airport with iniBuilts A350 for Example.
When I try to load with default Cessna 172 I was able to load into an airport. No Problem.
Currently I don’t have any exe.xml in place.
Fehlerbucket 1856377202958665170, Typ 5
Fehlerhafter Anwendungsname: FlightSimulator2024.exe, Version: 1.5.10.0, Zeitstempel: 0x00000000
Fehlerhafter Modulname: FlightSimulator2024.exe, Version: 1.5.10.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000002db8078
Fehlerhafte Prozess-ID: 0x6E40
Fehlerhafte Anwendungsstartzeit: 0x1DBE671C3465DD3
Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\Microsoft.Limitless_1.5.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Fehlerhafter Modulpfad: C:\Program Files\WindowsApps\Microsoft.Limitless_1.5.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Berichts-ID: bb31eb1e-9c20-4272-aef5-c70a28fe69eb
Vollständiger Name des fehlerhaften Pakets: Microsoft.Limitless_1.5.10.0_x64__8wekyb3d8bbwe
Fehlerhafte paketbezogene Anwendungs-ID: App
The latest update Beta version of SU3 for FS2024 causes me constant crach to desktop be alert.
Update: loading into OEMA with FlyByWire A320 was no Problem.
Dear MSFS team,
CTD many time when I loading my game to start after I clicked on the airport.
Also please see the crash report. I can’t update cos I am new, it said??
Well here below…
CM Edit: Removed report as it was too long. We just need Fault Bucket IDs
1 Like
I had now a blue screen when I tried to load into EDDL with FlyByWire A320. With same Aircraft into OEMA was no problem.
Nice to see that the bad SU3 updates bring us new active users into the forum 
For me, reading all this, I’m happy to have left the SU3 beta a while ago.
It’s a good thing to give us the possibility to test before release.
But we have now reached a state where it seems MS/Asobo have just outsourced all Quality Assurance to us, the customers. That’s just not acceptable anymore, the amount of game breakers not found before sending it out
3 Likes
Same here when loading into new update it CTD. Removing community folder solves it and really hard to work out whats causing it. Thought I had it but next reload it crashes again. Something really wrong here
Last was great for me! This one wont even load
After lot testing it seems that is the result for me (PC-Steam):
- Fenix A3xx: some airport it can start, many other (eg.LDDU, EDDL) not working or CTD
- Inibuild A350 : CTD, also clearing WASM dir.
- PMDG 777: CTD all the time.
- Justflight Piper PA28 bundle IS WORKING, but the avionics sometimes is shutdown, sometime can start.
- GSX not working
PS: PMDG 777-200ER is working fine after WASM reset.
For what I see, the CTD errors don’t appear in the event viewer most of the time. Many DLL/EXE of Winwing and Fenix remain locked
On 1.5.9 everything worked fine for me. 
1 Like
Guys, you can mention add-ons all you want. But it’s pretty much certain that there is a MAJOR issue with SimConnect. As soon as ANY 3rd party tries to access it … poof!
6 Likes
indeed. MS Store version here. CTDs here as well every time when loading into a flight.
But NO CTDs with Community folder disabled. So there must be something which causes the CTDs…
I have the store version, and today I updated to SU 3 beta 1.5.10.0. The CTDs that appeared in 1.5.9.0 when loading an MSFS 2020 aircraft disappeared. I started the C 152 and then launched an Air Manager panel. A CTD from MSFS 2024 immediately occurs. If Air Manager is started but no panel has been opened yet, the CTD occurs when MSFS 2024 loads.
Since many people are experiencing this issue and are certainly using other applications like AOO or similar, I suspect the error is related to the WASM interface.
Interesting re: Fenix. I tried on a default/Asobo airport only (EDDS), will try others when i got the time…
Also, quick question - anyone know why i wouldn’t even see a crash report in the event viewer for msfs2024? It just…CTDs silently. Maybe I’m dumb and have some other settings messed up on the machine?