Dear All,

I have had a CTD on two separate flights - one to Boston and one to Atlanta, both times just after I landed and started to taxy to the gates.

I have flown to both of these airports previously without any issues so I am unsure what the problem is.

On the first occasion, I had some freezes during the flight, which lasted about 5-10 seconds.  I put the problem down to Gees, which had recently added. I was flying the Fenix A321. I subsequently removed Gees and had a trouble free flight to KRSW in an A300F.

On my last flight, I was flying the iFly 737-8 and everything was running well.  I had no issues loading the flight sim, or during the flight prior the CTD.

Before these CTD's, MSFS2020 had been running perfectly without any issue.

I checked the event viewer and for the last CTD, it stated:

Faulting application name: FSUIPC7.exe, version: 7.5.0.5, time stamp: 0x6910614c
Faulting module name: ntdll.dll, version: 10.0.26100.7462, time stamp: 0x9225342c
Exception code: 0xc000041d
Fault offset: 0x000000000000aa83
Faulting process id: 0x463C

So I am somewhat bemused as I've not touched the current version of FSUIPC since I installed it on the 6th of December.

Any help would be appreciated.

Best regards,

Peter

Moderators- please remove "FSUIPC Related" as I have found out that FSUIPC didn't cause the problem. 

I recommend you post this issue to the FSUIPC support forum. There is a new support forum there and John Dawson does a good job responding to issues from the program’s users. Attach a copy of the FSUIPC ini and log files to your topic and it should be sorted out quickly. 
Rich

20 minutes ago, rlashier said:

I recommend you post this issue to the FSUIPC support forum. There is a new support forum there and John Dawson does a good job responding to issues from the program’s users. Attach a copy of the FSUIPC ini and log files to your topic and it should be sorted out quickly. 
Rich

You apparently missed the post right above yours  where the OP said:

Moderators- please remove "FSUIPC Related" as I have found out that FSUIPC didn't cause the problem.