MSF CTD, FSUIPC named.

[Ron Attwood]

Does any of this mean anything to anyone?

This first one corresponds to a broken up/static like voice coms (TS) while on a flight

Error    03/07/2021 20:33:51    Application Error    1000    (100)

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Exception code: 0xc0000005
Fault offset: 0x000000000016ed1a
Faulting process ID: 0x32c0
Faulting application start time: 0x01d77031dc633031
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 48b738d2-b86c-462a-b3fa-5158bf3ae674
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Culminating in a CTD (Flight sim has stopped working, close the app? type)

Error    03/07/2021 20:34:19    Application Error    1000    (100)

Faulting application name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7
Faulting module name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7
Exception code: 0xc0000005
Fault offset: 0x0000000000019884
Faulting process ID: 0x1ed8
Faulting application start time: 0x01d770321749bfe1
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report ID: 63cb65cd-d870-4383-b684-b2e224a4b2e6
Faulting package full name:
Faulting package-relative application ID:

I rejoined the flight and carried on until the end. Finished at 22:08ish. I didn't notice anything untoward but found this in the Event Viewer

Error    03/07/2021 22:08:41    Application Error    1000    (100)

Faulting application name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7
Faulting module name: FSUIPC7.exe, version: 7.2.0.1, time stamp: 0x60d1ebf7
Exception code: 0xc0000005
Fault offset: 0x0000000000019884
Faulting process ID: 0x1ed8
Faulting application start time: 0x01d77043dc98d8a5
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report ID: de3dcc08-d842-4d2e-8d8b-aeb377431552
Faulting package full name:
Faulting package-relative application ID:

I can't think it was FSUIPCs fault but thought you may be able to throw some light on it.

Cheers, Ron

[John Dowson]

If/when MSFS crashes, it usually generates faults like this in FSUIPC7 as the simconnect connection is no longer available. In such cases, FSUIPC7 will also exit, as the option 'Exit with FS' is set (and always set if FSUIPC7 is auto-started by MSFS). Check your FSUIPC7.log file, it should show that FSUIPC7 closed down gracefully as  MSFS was no longer detected. If this is the case, then you should report the CTD to Asobo, including the crash event log.

If/when FSUIPC7 does actually crash, the FSUIPC7.log will be cut short, i.e. no close-down messages logged. However, if this happens it should not affect MSFS as that is in a separate process.
 

[Ron Attwood]

Thanks John. I figured something along those lines but I would never been able to put it so succinctly.  I had a look at the log and it all seems OK to me. Like the Bye bye. 🙂