Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
Faulting module name: mf3055c24e74fe5af_0.dll, version: 0.0.0.0, time stamp: 0x65d8800d
Exception code: 0xc0000005
Fault offset: 0x0000000000e16484
Faulting process id: 0x0x17E0
Faulting application start time: 0x0x1DA6649BA71AC72
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Users\XXXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a300-600\mf3055c24e74fe5af_0.dll
Report Id: 1ade0561-d429-4168-9717-9b7a4f8b4554
Faulting package full name: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Any ideas?

How many times?  First load (after install or update)?  Ideas require more info.  For example, with the exception of the last update, I had a CTD on first load (including all prior updates).  However, it would never happen again until another update.  V1.08 was the first time I did not CTD on first load.  Not saying this is normal, as it is not, but that has been my experience. 

10 hours ago, Crabby said:

How many times?  First load (after install or update)?  Ideas require more info.  For example, with the exception of the last update, I had a CTD on first load (including all prior updates).  However, it would never happen again until another update.  V1.08 was the first time I did not CTD on first load.  Not saying this is normal, as it is not, but that has been my experience. 

Yes, that's what happens. Always after an update, the first load is a CTD.

Afterward, everything is ok.

7 hours ago, artox67 said:

Yes, that's what happens. Always after an update, the first load is a CTD.

Afterward, everything is ok.

Yea, that is why I stopped paying attention to the first load and never reported it at all.  To me it is only a very very very minor nuisance.