Jump to content
The simFlight Network Forums

MSFS Crashing Due To SimConnect Errors


jaybird1nyc
 Share

Recommended Posts

I’ve been running MSFS since launch day and fortunately I've been in the camp of never had a CTD before this update (well, maybe a couple, but very early on). Here’s something to look at though; I’m running FSUIPC7 and when I had the last 2 CTDs I looked at the log that FSUIPC7 produces. Same event triggered both CTDs, both SimConnect errors.

Here are the SimConnect events:
Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
Failed on SimConnect_CallDispatch for Message, return = 0xC000014B

After those 2 errors MSFS ends with a CTD and FSUIPC7 closes normally.

I know FSUIPC7 is not at fault here, but any ideas what could be causing this?

Link to comment
Share on other sites

  • Replies 51
  • Created
  • Last Reply

Top Posters In This Topic

20 hours ago, jaybird1nyc said:

when I had the last 2 CTDs I looked at the log that FSUIPC7 produces. Same event triggered both CTDs, both SimConnect errors.

Here are the SimConnect events:
Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
Failed on SimConnect_CallDispatch for Message, return = 0xC000014B

After those 2 errors MSFS ends with a CTD and FSUIPC7 closes normally.

It's the other way around. Those errors occur because SimConnect has stopped responding even to the basic request to carry on sending data. MSFS has really crashed by then, taking SimConnect down with it of course.

As John says, you need to find the Windows crash data for MSFS (in Windows event viewer) and report the crash to Asobo on ZenDesk. The more folks do this the more likely the problems with be attended to.

Pete

 

Link to comment
Share on other sites

Hi Pete,

So you're saying that MSFS has already crashed prior to those errors being logged by FSUIPC? I know that this has nothing to do with FSUIPC, only indirectly involving the logging features of it might point to the underlying cause of the crash.

Here is a snippet of my log prior to those SimConnect errors that I already posted.  You can see other SimConnect errors that were handled, and there are more of these types of errors occurring multiple times, in almost every log I look at.

 

1184062 System time = 26/12/2020 10:48:07, Simulator time = 10:48:05 (15:48Z)
1406406 TransmitClientEvent failed! (Event=65762, Param=6157, nGroup=0, fSame=0
1406422 TransmitClientEvent failed! (Event=65765, Param=-13680, nGroup=0, fSame=0
1406437 TransmitClientEvent failed! (Event=65762, Param=5732, nGroup=0, fSame=0
1406468 TransmitClientEvent failed! (Event=65765, Param=-14066, nGroup=0, fSame=0
1406468 TransmitClientEvent failed! (Event=65762, Param=5512, nGroup=0, fSame=0
1406468 **** Too many TransmitClientEvent errors received! Re-connecting now … ****
1406734 SimConnect_Open succeeded
1406750 Running in “KittyHawk”, Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
1406750 MSFS version = 11.0.282174.999
1406750 Initialising SimConnect data requests now
1406781 User Aircraft ID 1 supplied, now being used
1406781 C:\USERS\JAY\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
1406781 User Aircraft ID 1 supplied, now being used
1406781 C:\USERS\JAY\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
1407109 System time = 26/12/2020 10:51:50, Simulator time = 10:51:48 (15:51Z)
2716640 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
2716640 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
2719390 MSFS no longer running - exiting

Definitely going to gather up as many crash logs as I can locate from Windows to send to Asobo but thought that looking at these errors prior to the CTD might provide some insight.

Thanks Pete and John,

Jay

Link to comment
Share on other sites

1 minute ago, jaybird1nyc said:

So you're saying that MSFS has already crashed prior to those errors being logged by FSUIPC? I

Those two errors, yes. They basically mean SimConnect has "disappeared".

2 minutes ago, jaybird1nyc said:

only indirectly involving the logging features of it might point to the underlying cause of the crash.

If it is related to the SimConnect interaction, which is definitely possible, then probably a Simconnect log would be more informative for Asobo, but the Windows crash data sohlud get them to the point of failure, and is still the most important information.

5 minutes ago, jaybird1nyc said:

Here is a snippet of my log prior to those SimConnect errors that I already posted.  You can see other SimConnect errors that were handled, and there are more of these types of errors occurring multiple times, in almost every log I look at.

Those sorts of problems would certainly be good information for Asoso as well. But they do look like a result of MSFS being too busy on all fronts to bother with its SimConnect responses. Do you have performance problems with MSFS?

The log shows that the two errors indicating the crash occurred 22 minutes later than those earlier response problem log entries, so they are certainly not a direct cause of the crash, and problem are not at all related.

Has this all changed with the latest MSFS update, or, for you, has this always been occurring with other versions?

Pete

 

Link to comment
Share on other sites

8 minutes ago, Pete Dowson said:

Do you have performance problems with MSFS?

Actually no.  I run MSFS on mostly high settings @ 1080p 30hz.  Stays locked @ 30fps pretty much the entire time with very few stutters or pauses.

10 minutes ago, Pete Dowson said:

Has this all changed with the latest MSFS update, or, for you, has this always been occurring with other versions?

Yes, it appears to be the case.  I haven't had a CTD since August.  It's only been happening with this latest update.  I can't be certain, but I believe it has to do with AI traffic.  Real-time AI traffic to be specific.  All of my CTDs have come with real-time AI traffic enabled.  My last 4 flights have been fine, with ALL traffic disabled.  Haven't tried offline traffic yet.

Jay

Link to comment
Share on other sites

33 minutes ago, jaybird1nyc said:

1406406 TransmitClientEvent failed! (Event=65762, Param=6157, nGroup=0, fSame=0

These errors have been known to be caused by the number of SimConnect clients being exceeded. Its a known problem in all ESP based sims since FSX.
To verify if this is the cause, you could activate server-side SimConnect logging (via a SimConnect.ini file) to see if the number of clients/connections is being exceeded, and if so increase the maximum number of clients available via your SimConnect.xml file.
 

John

Link to comment
Share on other sites

7 minutes ago, jaybird1nyc said:

Yes, it appears to be the case.  I haven't had a CTD since August.  It's only been happening with this latest update.  I can't be certain, but I believe it has to do with AI traffic.  Real-time AI traffic to be specific.  All of my CTDs have come with real-time AI traffic enabled.  My last 4 flights have been fine, with ALL traffic disabled. 

Interesting. FSUIPC reads AI traffic data so it can populate the offsets used by many external applications. Maybe John could make a test option to stop FSUIPC7 reading any Traffic (a "NoTrafficAtAll=Yes" parameter, perhaps) as a test. If this prevents the CTDs even with all the MSFS traffic enabled then this would be good information for Asobo.

Pete

 

Link to comment
Share on other sites

11 minutes ago, Pete Dowson said:

Maybe John could make a test option to stop FSUIPC7 reading any Traffic (a "NoTrafficAtAll=Yes" parameter, perhaps) as a test. If this prevents the CTDs even with all the MSFS traffic enabled then this would be good information for Asobo.

There is already the option
     ProvideAIdata=No

Maybe you can try with that to see if it makes a difference?

John
 

Link to comment
Share on other sites

Ok, John, will do.  At work now but I'll try it later on and report back.

Oh, something else interesting.  Even with all traffic disabled, my FSUIPC7 log shows that there were AI aircraft spawned.  I don't have access to the log right now but I remember seeing that there was some line saying MaxAIAircraft (?) was 78, or words to that effect.  So, on those last 4 successful flights (with all traffic off) FSUIPC was still reporting a large number of AI aircraft.  Once it was 78, then something well in excess of 100, different amounts each flight.  Could this be the static aircraft on the ground being reported as AI aircraft?

Jay

Link to comment
Share on other sites

13 minutes ago, jaybird1nyc said:

I don't have access to the log right now but I remember seeing that there was some line saying MaxAIAircraft (?) was 78, or words to that effect.  So, on those last 4 successful flights (with all traffic off) FSUIPC was still reporting a large number of AI aircraft.  Once it was 78, then something well in excess of 100, different amounts each flight.  Could this be the static aircraft on the ground being reported as AI aircraft?

Any and all AI (and real world) aircraft will provide data in response to FSUIPC's requests, whether on the ground or not.

But 'static' aircraft are usually just part of the scenery and not reported. They are just scenery objects.

Pete

 

Link to comment
Share on other sites

Yes, that's what I thought as well.  However, my traffic options are both disabled and yet my log shows a large number of AI aircraft.  I'm not at my PC now but there is a slider in Options/General/Traffic that allows you to control the level of static aircraft shown.  It's called  "Ground Aircraft Density" (was that slider there before, I can't remember?)  If MSFS is using AI controlled aircraft as static ground objects then that could certainly be a problem.

Jay

Link to comment
Share on other sites

19 hours ago, jaybird1nyc said:

Even with all traffic disabled, my FSUIPC7 log shows that there were AI aircraft spawned.  I don't have access to the log right now but I remember seeing that there was some line saying MaxAIAircraft (?) was 78, or words to that effect.  So, on those last 4 successful flights (with all traffic off) FSUIPC was still reporting a large number of AI aircraft.  Once it was 78, then something well in excess of 100, different amounts each flight.  Could this be the static aircraft on the ground being reported as AI aircraft?

This shouldn't be the case. If you have correctly added the ProvideAIdata=No to the correct place, you should see the following informational message logged near the beginning of your FSUIPC7.log file, after the device scan log:
       641 ### Note: AI Traffic related facilities and data are inhibited!
and there should be no other log messages relating to the number of AI traffic.

Can you check again please, and if you see such a message can you post your FSUIPC7.log and .,ini files and I'll take a look.

John

 

Link to comment
Share on other sites

Hi,

I added the ProvideAIdata=No to the ini file and got as John stated the "  641 ### Note: AI Traffic related facilities and data are inhibited!" recorded in the log.

I had tons of CTD after the latest msfs release - doing a test flight now from EHAM/EGLL  now, with ProvideAIdata=No  as the only change.

 

Lars

Link to comment
Share on other sites

You're correct John, I do see that message in my log after putting in ProvideAIData=No.  I wrote the post you quoted before adding the line.  I was just pointing out that there were a large number of AI aircraft being reported by FSUPC7 even with no traffic options being enabled.  Very curious, I thought.🤔

Link to comment
Share on other sites

Ok, so 1st flight with ProvideAIData=No and live traffic enabled ended well.  No CTD.  

Here is a snip from my log showing some SimConect errors tho:

   124703 -------------------- Starting everything now ----------------------
   663078 C:\Users\Jay\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\aircraft-mooney-m20r-ovation-carenado\SimObjects\Airplanes\Carenado_M20R_Ovation\aircraft.CFG
   663203 Sim stopped: average frame rate for last 545 secs = 67.3 fps
   663203 -------------------------------------------------------------------
   665891 Aircraft="Carenado M20R Ovation D-ERWO"
   671516 Planned flight from KVRB to KOPF
   671516 C:\USERS\JAY\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
   671531 C:\Users\Jay\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   689500 #### ERROR: No SimConnect data seen for more than set stall time!
   693516 #### ERROR: No SimConnect data seen for more than set stall time!
   697531 #### ERROR: No SimConnect data seen for more than set stall time!
   701516 #### ERROR: No SimConnect data seen for more than set stall time!
   705516 #### ERROR: No SimConnect data seen for more than set stall time!
   709516 #### ERROR: No SimConnect data seen for more than set stall time!
   713516 #### ERROR: No SimConnect data seen for more than set stall time!
   717516 #### ERROR: No SimConnect data seen for more than set stall time!
  1477125 TransmitClientEvent failed! (Event=65764, Param=-256, nGroup=0, fSame=0
  1477203 TransmitClientEvent failed! (Event=65764, Param=-451, nGroup=0, fSame=0
  1477281 TransmitClientEvent failed! (Event=65764, Param=-512, nGroup=0, fSame=0
  1477375 TransmitClientEvent failed! (Event=65764, Param=-651, nGroup=0, fSame=0
  1478047 TransmitClientEvent failed! (Event=65764, Param=-512, nGroup=0, fSame=0
  1478047 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
  1478203 SimConnect_Open succeeded
  1478203 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  1478203 MSFS version = 11.0.282174.999
  1478203 Initialising SimConnect data requests now
  1478203 User Aircraft ID 1 supplied, now being used
  1478234 .PLN
  1478234 SimObjects\Airplanes\Carenado_M20R_Ovation\aircraft.CFG
  1478234 User Aircraft ID 1 supplied, now being used
  1478234 .PLN
  1479094 System time = 31/12/2020 10:16:01, Simulator time = 10:15:59 (15:15Z)
  5402781 Sim stopped: average frame rate for last 3924 secs = 29.9 fps
  5402781 -------------------------------------------------------------------

Any thoughts?

Link to comment
Share on other sites

43 minutes ago, jaybird1nyc said:

689500 #### ERROR: No SimConnect data seen for more than set stall time!
   693516 #### ERROR: No SimConnect data seen for more than set stall time!
   697531 #### ERROR: No SimConnect data seen for more than set stall time!
   701516 #### ERROR: No SimConnect data seen for more than set stall time!
   705516 #### ERROR: No SimConnect data seen for more than set stall time!
   709516 #### ERROR: No SimConnect data seen for more than set stall time!
   713516 #### ERROR: No SimConnect data seen for more than set stall time!
   717516 #### ERROR: No SimConnect data seen for more than set stall time!
  1477125 TransmitClientEvent failed! (Event=65764, Param=-256, nGroup=0, fSame=0
  1477203 TransmitClientEvent failed! (Event=65764, Param=-451, nGroup=0, fSame=0
  1477281 TransmitClientEvent failed! (Event=65764, Param=-512, nGroup=0, fSame=0
  1477375 TransmitClientEvent failed! (Event=65764, Param=-651, nGroup=0, fSame=0
  1478047 TransmitClientEvent failed! (Event=65764, Param=-512, nGroup=0, fSame=0

These errors indicate problems receiving data via simconnect. Each time that error is reported, the connection is closed and re-initiated. This can cause problems with the number of clients configured to use SimConnect, especially if you have any other SimConnect clients (i.e. add-ons that also use SimConnect).

If its due to a slow pc with too many things running, you could try increasing these ini parameters in your [General] section to see if it improves:

Quote

TrafficStallTime=1
InitialStallTime=30
NormalStallTime=1

Maybe try with:

Quote

TrafficStallTime=2
InitialStallTime=30
NormalStallTime=2

Or you could also try without re-connecting by giving -ve values, i.e.

Quote

TrafficStallTime=-1
InitialStallTime=30
NormalStallTime=-2

This would then just log messages (the '-' indicates to not automatically re-connect in this situation).
It maybe worth playing around with these parameters to se what works for your system. but if its being overloaded then you will always get issues....

Such issues are usually due to pushing your system to its limits, either CPU or GPU bound. 

John

 

Link to comment
Share on other sites

Thanks for the good info John. I'll play around with those values to see if there's any change.

Meanwhile, I just finished my 2nd flight with ProvideAIData=No and live traffic with no CTD so hopefully we're on the right path.

Again, thanks for your help and I wish you and your family a very Happy & Healthy New Year!

Jay

Link to comment
Share on other sites

Hello !

I'm following this thread and feel like I've solved my problem.

Since the VR update I had a problem leaving FSUIPC in the background, namely CTD.

The problem was also :

Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
Failed on SimConnect_CallDispatch for Message, return = 0xC000014B

I applied the code line ProvideAIdata=No since I no longer have a CTD, on two flights of one hour then two hours.

After my conf file, we notice that FSUIPC doesn't see IA traffic anymore:

********* FSUIPC7, Version 7.0.3 (23rd December 2020) by John Dowson *********
Checking for FS path in 'C:\Users\admin\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = G:\FS2020\
WebSocket server found: D:\STOCK ET TRAVAIL\DOCUMENTS\FS 2020\FSUIPC\FSUIPC 7.0.3\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Home Single Language 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "D:\STOCK ET TRAVAIL\DOCUMENTS\FS 2020\FSUIPC\FSUIPC 7.0.3\FSUIPC7.ini"
Checking the Registrations now ...
User Name=""
User Addr=""
FSUIPC7 not user registered
WIDEFS7 not user registered, or expired
      109 System time = 30/12/2020 21:43:51
      109 FLT path = "C:\Users\admin\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      109 -------------------------------------------------------------------
      156 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      187 FS path = "G:\FS2020\"
      187 ### Note: AI Traffic related facilities and data are inhibited!
      187 LogOptions=00000000 00000001
    26312 === Hot key unregistered
    26312 === Stop called ...
    26312 === Closing external processes we started ...
    27312 === About to kill any Lua plug-ins still running ...
    28468 === About to kill my timers ...
    28468 === Restoring window procs ...
    28468 === Unloading libraries ...
    28468 === stopping other threads ...
    28468 === ... Button scanning ...
    28468 === ... Axis scanning ...
    28468 === Releasing joystick devices ...
    28468 === Freeing macro memory
    28468 === Removing any offset overrides
    28468 === Clearing any displays left
    28468 === AI slots deleted!
    28468 === Freeing button memory ...
    28468 === Closing my Windows ...
    28468 === Freeing FS libraries ...
    29468 === Closing devices ...
    29468 === Closing the Log ... Bye Bye! ...
    29468 System time = 30/12/2020 21:44:20
    29468 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Memory managed: 1 Allocs, 1 Freed
********* FSUIPC Log file closed ***********

 

Before in the end of the log file I had (for example) :

Minimum frame rate was 16.0 fps, Maximum was 160.5 fps
Average frame rate for running time of 3048 secs = 21.3 fps
Maximum AI traffic for session was 63 aircraft
Traffic deletions 0 aircraft
Memory managed: 2 Allocs, 1 Freed
********* FSUIPC Log file closed ***********

Hopefully this can help you!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.