FSUIPC MSFS Crash To Desktop after landing

[Kiddo]

As the title gives off already after landing for my VA flight from LGAV-LFGP my sim crashes and according to the event display it was FSUIPC 7. 
Is there anyway to fix this? Dont want to get spooked by another crash after 3h of flying

here is the failbucket
 

Fehlerbucket 1585784603163444315, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FSUIPC7.exe
P2: 7.3.0.3
P3: 62544f1b
P4: ntdll.dll
P5: 10.0.19041.1566
P6: 1be73aa8
P7: c0000005
P8: 0000000000063416
P9: 
P10: 

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER49D2.tmp.WERInternalMetadata.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FSUIPC7.exe_18472f1ad686b6286c57b927fc0ab87ad381b39_b5521bd1_b3154dd3-ab0e-470f-a0fa-82217101ac69

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: bde493bc-7c3c-4691-8c2e-e59ff918f72a
Berichtstatus: 268435456
Bucket mit Hash: 5599625602997f94d601d6b1d9d7445b
CAB-Datei-Guid: 0

[John Dowson]

Please always attach your FSUIPC7.log file if you think FSUIPC7 has crashed - this usually shows that FSUIPC7 exited normally due to an MSFS CTD. If/when MSFS crashes, this can cause an exception (in the event viewer) for FSUIPC7, but this is usually due to the MSFS CTD. Check the event viewer again to see if there is an MSFS crash reported before the FSUIPC7 event, but it is the FSUIPC7.log file that would help in determining what actually happened.

In all cases, MSFS CTDs should be reported to Asobo. As FSUIPC7 is an external program that only communicates with MSFS via the MSFS-provided SDK, and crash in FSUIPC7 (if it did actually crash) should not affect MSFS, and if it does, it is an issue with the SDK (which is an Asobo/MSFS issue).

John

[Kiddo]

6 hours ago, John Dowson said:

Please always attach your FSUIPC7.log file if you think FSUIPC7 has crashed - this usually shows that FSUIPC7 exited normally due to an MSFS CTD. If/when MSFS crashes, this can cause an exception (in the event viewer) for FSUIPC7, but this is usually due to the MSFS CTD. Check the event viewer again to see if there is an MSFS crash reported before the FSUIPC7 event, but it is the FSUIPC7.log file that would help in determining what actually happened.

In all cases, MSFS CTDs should be reported to Asobo. As FSUIPC7 is an external program that only communicates with MSFS via the MSFS-provided SDK, and crash in FSUIPC7 (if it did actually crash) should not affect MSFS, and if it does, it is an issue with the SDK (which is an Asobo/MSFS issue).

John

Thanks for the reply, I see. Then I will check it all out again and come back again if I have anything new. I already reported it on the MSFS forum as well so thats also happening.
Thanks again for the help!