I have a reproducable CTD when I have the mini-500 installed.
It either happens in the last quarter of loading a flight, or within 2 minutes of a flight.
It doesn’t matter if I use a different aircraft.
Without the mini-500, I have no CTDs.
I also have the version from the marketplace, same thing happens. I don’t have them installed at the same time.
EventViewer Details:
Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000d6fc86
Faulting process id: 0x4344
Faulting application start time: 0x01da61c568d97a79
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f8f922ac-a042-49d4-b137-ecf2c355c8f4
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Fault bucket 1694466734533611289, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.2.0
P7: 00000000
P8: c0000005
P9: 0000000000d6fc86
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: f8f922ac-a042-49d4-b137-ecf2c355c8f4
Report Status: 268435456
Hashed bucket: 402c562c474261524783f48473978f19
Cab Guid: 0
What airport are you taking off from? Is this re-occurring at any airport? Currently have the Mini-500 (Marketplace) installed and no issues.
When is the last time you updated your Nvidia Graphics?
It’s my local airfield. But happened on other places as well, even when starting in the air.
I’m on the current Nvidia driver 551.52.
Have you tried flying the Mini-500 without community add-ons installed? That way we can narrow it down to either the aircraft or a compatibility issue. As mentioned, this is the only report of CTDs. If this was happening to everyone, it would be more likely to be an issue with our aircraft. That said, you seem to be having an isolated CTD issue.
If your sim is still crashing after having a clear community folder, then I can try to investigate further. Hope this doesn’t sound too discouraging, but with MSFS’s ecosystem, there is a million add-ons now that could affect each other and cause compatibility issues.
When we develop an aircraft, we are extremely careful to avoid overwrites with other aircraft. If anything, sometimes they share data with our other aircraft, but we never share data with other 3rd Party aircraft.
Let me know if you narrow it down further, as mentioned, really hard to diagnose something on the local user’s setup without isolating the issue further.
I double and triple checked, as I actually like to fly it. Took me 4h to narrow it down to the mini-500.
I normally use the website version. So didn’t have the store version installed.
I removed all add-ons from the community folder, got no ctd. Then added them one by one testing with the standard nxcub from my home airfield. When I came to add the mini500 I got the ctd. So I removed it again and the ctds stopped.
Then I removed them all again, no ctd.
Added back only the mini500, ctd.
Removed it, no ctd.
Redownloaded from the website, as I thought I might have an older version, which wasn’t the case, did it anyway. Added it, ctd.
Removed it, no ctd.
Installed store version, ctd.
Edit:
I actually was adding this to my earlier reply while you we’re answering, so I put it in a new one.
Can you provide me your local airfield ICAO:
This is going to be a hard problem to diagnose but I will try. I just verified with a few team members and none of us are having issues with the website or marketplace version installed (with or without other add-ons in our community).
Going to try to narrow down the problem. Unfortunately MSFS doesn’t generate the best crash reports.
Can you check in this folder:
\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MSFSReport-OldCrashes
And provide me your latest crash report .txt document.
It’s EDSR.
I was thinking it might be a combination of addons, that’s why I tried it isolated. But it still happened, and also didn’t have it before SU15. Was actually searching online and on the forums if anyone had the same/similar issue with the mini500.
I also have frequent CTDs with Fault bucket ID 1694466734533611289, type 5 and I have the Mini 500 installed, I will try removing it from my community folder and see if my CTDs stop.
here’s the latest report from the crash with the store version:
MSFSReport-Crash-520390717.txt (28.1 KB)
this is the one before the other, so should be the one with only the redownloaded version in the community folder.
MSFSReport-Crash-3622002530.txt (27.8 KB)
Can you replace the following file in your SimObjects/Airplanes/gotfriends-mini-500/panel folder and see if this resolves any issues:
Uninstalled the store version, added the website version to the community folder and replaced the panel.cfg.
No other addons in community folder.
Still got the CTD 15sec after takeoff from EDSR. Here’s the report:
MSFSReport-Crash.txt (24.5 KB)
Someone from our team will be installing the SU-15 beta shortly to verify this issue further. This may take some time to diagnose, and we can’t guarantee a resolution unless we are able to replicate the issue.
That said, I thank you in advance for your patience with our team as we work towards finding you a solution. My apologies for the troubles it’s caused so far.
1 Like
No worries, I just thought of some other things, but they shouldn’t affect it.
I have FlightTracker plugin for the streamdeck and a logitech switch panel, which both need external software to work with msfs to get and set states of the aircraft (landing gear, lights, autopilot, gauges).
I tried to deactivate both, but still got the ctds.
It’s pretty late here as well, so I will have a look at it again tomorrow.
Sounds good, if we have anything new for you to test, I will either notify you here or PM you privately with the files. Cheers! Thanks again for the heads-up report.
So here are some other things i tested:
-
clearing the NVIDIA and MSFS caches and scenery index, ctd
-
switching to DX12 (used from here on out), ctd
-
installing both at the same time 
This one was during loading:
MSFSReport-Crash-2882285727.txt (24.6 KB)
(removed the community folder version after, so from now on was the store version)
-
choosing a random airport somewhere on the globe (VTUK), was able to fly for around 2-3 min then ctd
MSFSReport-Crash-195556908.txt (28.5 KB)
-
then i actually got a ctd during sim startup (choosing safe mode) with a different fault bucket (maybe unrelated):
MSFSReport-Crash-2161439522.txt (11.9 KB)
Fault bucket 1688695630559148430, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.2.0
P7: 00000000
P8: c0000005
P9: 00000000007e4c27
P10:
-
disabling SMT in bios (because why not), starting back at EDSR, ctd
-
removing mini500 store version with content manager, so no version of the mini500 installed anymore, made two roughly 10-15min flights from EDSR to EDTZ, one in safe mode, one in normal mode, no ctd
With that I’m pretty much out of ideas now. 
Just tested again with the the new beta release 1.37.4.0, and the issue seems to be gone for now. Whatever changed there has solved it, for now.
Sorry, if this caused some inconveniences.
1 Like