FSUIPC or MSFS?

[N987PL]

Still having CTD issues with all add-ons suspended (in Community Folder).  Every time CTD occurs, I get a fatal error for FSUIPC too.  I don't know if FSUIPC is causing the problem or if it's MSFS.  Latest drivers from NVIDEA (511.65) are loaded, all Windows updates are current, etc.  Here's my Specs and error text follows:

Processor            Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz   3.70 GHz

Windows Build  Windows 10 Pro (64)

                                21H2

OSBuild              19044.1503

Installed RAM    32.0 GB (31.9 GB usable)

Memory             CORSAIR Dominator Platinum

System type      64-bit operating system, x64-based processor

DISC                   Samsung 980 Pro 1 TB, Samsung SSD QVO 870 2 TB, Samsung 960 Pro 1 TB, Western Digital 500G Spinning

GPU                    EVGA RTX 3090 FTW3 Hybrid

MOBO                ASUS ROG Maximus XII Extreme

Display               ASUS ROG PG35VQ        

 

Window Log Error:

 

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000

Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000015c1d59

Faulting process id: 0x51f0

Faulting application start time: 0x01d81c2fea1c324f

Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Report Id: 2b796096-b89d-484b-9516-099b0a667025

Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

 

Faulting application name: FSUIPC7.exe, version: 7.2.1.5, time stamp: 0x61efef58

Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9

Exception code: 0xc0000409

Fault offset: 0x000000000008ead3

Faulting process id: 0x54a4

Faulting application start time: 0x01d81c302d870e45

Faulting application path: F:\FSUIPC7\FSUIPC7.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 6e4136e3-69de-41bc-87cb-9d275558fbff

Faulting package full name:

Faulting package-relative application ID:

 

FSUIPC7.ini FSUIPC7.log

[John Dowson]

6 minutes ago, N987PL said:

Every time CTD occurs, I get a fatal error for FSUIPC too.

This is normal. When MSFS crashes, this causes a fault (but not fatal)  in FSIOPC as the connection to the simulator is lost. FSUIPC will detect this and then close down gracefully, as indicated by your log:

Quote

   ...
   154203 Starting aircraft lua Autos....
   154203 System time = 07/02/2022 08:39:39, Simulator time = 08:39:26 (14:39Z)
   371219 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
   371219 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
   373437 MSFS no longer running - exiting
   373469 === Hot key unregistered
   373469 === Stop called ...
   373484 === Closing external processes we started ...
   374000 === About to kill any Lua plug-ins still running ...
   ...

 

8 minutes ago, N987PL said:

I don't know if FSUIPC is causing the problem or if it's MSFS. 

It is MSFS. FSUIPC7 is a separate executable and in no way should it cause MSFS to crash. Try checking the Asobo / MSFS forums for any possible causes (there are many!), and report your issue to Asobo if you cannot find anything that looks relevant to your situation.

John 

[N987PL]

OK.  Thanks MUCH John for your response.  I will focus on MSFS support.  Many are having CTD issues.  I guess I'm having the same problems as others.  Great to know FSUIPC is not the culprit!

[N987PL]

John, just received an error for FSUIPC that didn't result from a MSFS CTD.  Seems to be different error than before.  Attaching logs below and Windows log.

FSUIPC7.log FSUIPC7.ini systeminfo_21422.docx

[John Dowson]

13 hours ago, N987PL said:

just received an error for FSUIPC that didn't result from a MSFS CTD. 

Are you saying that MSFS did not CTD or close? Your log still indicates that FSUIPC7 closed as MSFS couldn't be found:

Quote

   953531 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
   953531 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
   954031 MSFS no longer running - exiting

If this is not the case, can you restart FSUIPC7 when this occurs and then continue as normal?

The windows error (a fault, not a CTD) is also due to the simconnect connection being abruptly terminated, which also results in those simconnect failure messages.
So, if MSFS is not crashing, it is still losing its SimConnect connection.

The MSFS monitor, that checks MSFS is still tunning every second or so, does not use simconnect but windows facilities to determine if MSFS is still running. It is this that is failing to find MSFS and so exits FSUIPC7. There is a known issue on Windows 11 machines where this can fail and MSFS is still running, and this can be fixed by setting the following ini parameter in the [General] section iof your FSUIPC7.ini file:
      DisableMSFSMonitor=Enum

However, due to those simconnect failures, it does look like an issue with MSFS and I'm not sure this will help, although you should try this if you a certain that MSFS is still running ok when this occurs.

John

[N987PL]

Thanks for your response.  The screen just froze and did not CTD in MSFS.  The FSUIPC error was the only error log I found at that time.  I'm still  on Windows 10 Pro (64bit).  I have seen in many MSFS forums to hold a bit on Windows 11.  Would changing the DisableMSFSMonitor variable in FSUIPC.ini help me with Windows 10?  I'll try anything at this point.

[John Dowson]

2 minutes ago, N987PL said:

The screen just froze and did not CTD in MSFS.

So MSFS froze? Check the Asobo forums and report this to them.

3 minutes ago, N987PL said:

The FSUIPC error was the only error log I found at that time.

But this error was logged/produced due to a simconnect failure in MSFS, so needs reporting to Asobo.

4 minutes ago, N987PL said:

Would changing the DisableMSFSMonitor variable in FSUIPC.ini help me with Windows 10?

No, this won't help with you issue as it is with MSFS and not FSUIPC7.

John

[N987PL]

OK John.  Once again, thanks much for your prompt reply.  I'll go back to ASOBO.

[John Dowson]

If it is related to a simconnect issue, then logging simconnect could maybe point to something. However, if MSFS is freezing this really could be anything (e.g. related to weather or AI, your rolling data cache, an aircraft issue, etc) and nothing to do with simconnect.  You really need to try and narrow it down.
You probably won't get any response from Asobo, but worth checking there to see if anyone else has a similar issue with a possible cause or solution.

John

 

[N987PL]

Problem ended up being the latest Realtek audio driver.  Uninstalled it and no more CTDs.  

[John Dowson]

5 hours ago, N987PL said:

Problem ended up being the latest Realtek audio driver.  Uninstalled it and no more CTDs.  

Ok, interesting. Thanks for reporting back.

John