FSUIPC7.2.6 MSFS Still experiencing CTDs

[Martin G]

Firstly thanks to Pete for all his work over the years.

Since MSFS update 5 been having lots of CTDs and the event viewer keeps referring to FSUIPC as the faulting module.

Pete I know you have worked hard to resolve but the latest is still causing CTDS.  Downloaded it today and the error comes up after a CTD when trying to load:

 

Faulting application name: FSUIPC7.exe, version: 7.2.0.6, time stamp: 0x610ba6ec
Faulting module name: FSUIPC7.exe, version: 7.2.0.6, time stamp: 0x610ba6ec
Exception code: 0xc0000005
Fault offset: 0x00000000000198a4
Faulting process ID: 0x4024
Faulting application start time: 0x01d78a193b4c2823
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report ID: 1b9cfdb2-d43a-4eb3-8292-67208e7906c5
Faulting package full name: 
Faulting package-relative application ID: 

I know it is not your fault that MSFS keeps crashing - I contacted Zendesk but they say they are not responsible for third party software.  Even downloaded their latest hotfix today.  Still happens everytime.  Please help!

 

[John Dowson]

17 hours ago, Martin G said:

Since MSFS update 5 been having lots of CTDs and the event viewer keeps referring to FSUIPC as the faulting module.

This has been reported many many times now, and my answer is always the same....

If MSFS crashes, it is a problem with MSFS that mist be reported to Asobo. FSUIPC7 is an executable, a separate process to the FS. If FSUIPC7 crashes, it should not affect MSFS. What is more likely happening is that MSFS is crashing, which then causes a fault in FSUIPC7 (as the SimConnect connection is no longer available). FSUIPC7 detects this (and a windows event is raised) butt then exits gracefully. You can verify this by checking your FSUIPC7.log file - it should show that GSUIPC7 has exited gracefully as MSFS us no longer detected. If it doesn't, then please show it to me.

Another way to verify this is to start FSUIPC7 manually before the MSFS, and deselect the option 'Exit with FS'. Doing this, when you start MSFS you will get an error (which you can acknowledge and ignore) sating that FSUIPC7 is already running if/when it tries to auto-start FSUIPC7. But when MSFS CTDs, FSUIPC7 will disconnect and keep running.

Therefore, please verify that it is MSFS that is crashing, and if so, please check the Asobo forums and/or report to Asobo via zendesk.

John

Later... Btw, also check the event log for an MSFS crash event before the FSUIPC7 fault event. This should be sent to Asobo, together with the crash report/dump if one is available.

Edited August 6, 2021 by John Dowson
Further info added