I have done two flights: one in Fenix 320 and another one in PMDG 737 to Flight Beam KIAD. Both times I got CTD (with memory error) approaching (about 5 miles out) runway 19L,19C, 19R on ILS. Can anyone confirm similar results or it just something wrong with my setup?

Problem Event Name:    MoAppCrash
Package Full Name:    Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Application Name:    praid:App
Application Version:    1.26.5.0
Application Timestamp:    00000000
Fault Module Name:    FlightSimulator.exe
Fault Module Version:    1.26.5.0
Fault Module Timestamp:    00000000
Exception Code:    c0000005
Exception Offset:    000000000083fed0
OS Version:    10.0.22000.2.0.0.768.101
Locale ID:    1033
Additional Information 1:    b403
Additional Information 2:    b4034a13398cd20520afe9699b2b7735
Additional Information 3:    9560
Additional Information 4:    956080d8e1d8803d38d752796dd58f54

I have had a few of these memory error CTD's lately. They have been a little sporadic for me, and at different locations. I have been trying to pin down the culprit, but so far no success. All of my hardware has passed several tests, so I have ruled that out (and yes, I know how to properly test RAM, as well as video cards etc.). Still trying to figure out the cause. I had a few before the latest WU and a few after, so I cannot blame WU10. 

Jump onto their discord channels and report the bug. I have very occasionally had to do this with the FBW A320N and the problem was triaged and fixed within the hour. 

Edited June 18, 20223 yr by gb09f

Errors in addon airports can certainly cause CTD's. Even a simple error in taxi/runway connection can cause this.

I had one yesterday for the first time in a long time. It's the nature of the beast.

Just had one, I was just establishing the ILS 28L into Dublin with FBW A32NX. Event viewer gave me this:

FlightSimulator.exe

1.26.5.0

00000000

VCRUNTIME140.dll

14.30.30704.0

615a9215

c0000005

00000000000015fe

2d04

01d882fc1b59b006

C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll

df093e0b-66f3-4c70-83f8-ea3b5b62e679

Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe

App

Had the same a few times over the past few weeks. Strange thing is (I was on the SU9 Beta) and never saw this at all during the Beta, But only started after SU9 was released.

28 minutes ago, Virtpilot said:

Just had one, I was just establishing the ILS 28L into Dublin with FBW A32NX.

A lot of people including myself cannot fly around EIDW airport right now in MSFS, regardless of whether you have MK Studios or not, CTD is a major issue around Dublin.

12 minutes ago, shamrockflyer said:

A lot of people including myself cannot fly around EIDW airport right now in MSFS, regardless of whether you have MK Studios or not, CTD is a major issue around Dublin.

Oh... Good to know, thanks. What a pity.

Do you have Drzewiecki Washington landmarks installed ?  There are reports of it causing issues since the last world update.  I very rarely get a ctd but had one the other day while sitting at DCA.  I know KIAD is a little further out than KDCA but worth a shot if you have it.

35 minutes ago, mobeans10 said:

Do you have Drzewiecki Washington landmarks installed ?  There are reports of it causing issues since the last world update.  I very rarely get a ctd but had one the other day while sitting at DCA.  I know KIAD is a little further out than KDCA but worth a shot if you have it.

No I don’t ! Before last update I could fly in and out KIAD no problem. What gets me is that CTD happens almost at the same spot with two different aircraft.

I am digging this old thread because the very same problem happened to me four times in two days at FB KIAD, two incoming flights CTD when on the STAR to RWY 01R, and two outgoing flights from KIAD to EDDF a few minutes after take-off from RWY 30 when climbing through 15'000 feet, with totally different aircraft.

As I am using AddonLinker, it was easy for me to ensure that no other add-on was the culprit (for example DD KDCA and Washington landmarks were de-selected), I tried with and without AIG traffic and in my last trial, the only selected add-on was the airport itself, so there is little doubt. Has anyone else found the reason for this phenomenon?

Edited September 29, 20232 yr by Bernard Ducret

57 minutes ago, Bernard Ducret said:

As I am using AddonLinker, it was easy for me to ensure that no other add-on was the culprit (for example DD KDCA and Washington landmarks were de-selected), I tried with and without AIG traffic and in my last trial, the only selected add-on was the airport itself, so there is little doubt. Has anyone else found the reason for this phenomenon?

Did you also try without DD KDCA?
Just to make sure it is just this addon.

Apart from addons managed by AddonLinker, there might be other addons in your community folder still active. And of course there are addons in the Official folder too, from marketplace purchases, World Updates, etc.

5 minutes ago, orchestra_nl said:

Did you also try without DD KDCA?

As per my post, the only active airport add-on was FB KIAD in the last two flights, I have KDCA and Washington Landmarks, but both were unlinked at all times. As far as other active addons in my CF, none would matter since I never had a CTD in several months with frequent flights on several different planes, and this only happened around KIAD.

I will make another flight tomorrow out of KMIA to test. 

48 minutes ago, Bernard Ducret said:

As per my post, the only active airport add-on was FB KIAD in the last two flights, I have KDCA and Washington Landmarks, but both were unlinked at all times. As far as other active addons in my CF, none would matter since I never had a CTD in several months with frequent flights on several different planes, and this only happened around KIAD.

I will make another flight tomorrow out of KMIA to test. 

Sorry, I misread. What I meant was to test without the suspecting airport, FB KIAD in this case. If the issue does not occur with the default KIAD and no other addons are active, it must be the KIAD addon. You could request Flightbeam to look into it.

I had a similar issue with EDDW (BMOTW). MSFS would CTD if I had a flightplan with an approach to or SID from the airport. It might be that one or more of the procedures that come with the airport has a bug. Since airports also can add fixes one of these might cause a conflict somewhere. If only MSFS would be able to deal with these conflicts instead of crashing.