FSX crashes to desktop (CTD)

[Pete Dowson]

I think I may have overloaded the TCP side of things as I had removed the 'pipes' line from my simconnect.xml and was using TCP exclusively for both local and global connections.

But the "Auto" setting, will use a Pipe if specified in the "Local" entry.

If you showed me the first part of your SimConnect log I could tell. The ID numbers assigned to each client program are in ranges. At the start of the log there are entries listing the Simconnect services being established, as here for instance:

0.01346 Server: Scope=global, Protocol=IPv4, Address=LEFT, Port=500, MaxClients=64

0.04459 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64

The "MaxClients" value reserves the IDs. So above clients 0-63 would be using the IPv4 protocol via Port 500, whilst those with IDs 64-127 would be using the local Pipe.

Additionally I think the Pipe ID allocation runs from low (64 here) to high, whilst the others run from high (63 here) to low.

So, you can tell from the ID assigned which protocol it is using. For example:

> 8.25427 [64, 1]Open: Version=0x00000004 Name="FSUIPC4"

here FSUIPC is ID 64, using the Pipe.

Regards

Pete

[neorecon]

From the top of the config:

0.00000 SimConnect version 10.0.61259.0

0.01439 Server: Scope=global, Protocol=IPv4, Address=192.168.1.14, Port=500, MaxClients=64
0.01931 Server: Scope=local, Protocol=Auto, Address=::1, Port=49942, MaxClients=64
0.03655 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.03994 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49943, MaxClients=64
0.04635 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49944, MaxClients=64

It's interesting because I did not specify IPv6 or Pipe in my simconnect.xml. It must enable them by default if it isn't specified?

And from the bottom where the error occurs:

< 646.47949 [128] >>>>>  EXCEPTION=2, SendID=11683, Index=0  <<<<<  Unrecognized Data Received. [128, 11683]
> 646.47953 [128, 11684]RequestSystemState:RequestID=1, szState="Sim"
< 646.48651 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48654 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48659 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48662 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48667 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48669 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48675 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48677 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48737 [128] EventFrame: 0  10.296438
< 646.50543 [128] ObjectData: RequestID=9  DefineID=9  dwSize=72
< 646.50557 [128] ObjectData: RequestID=7  DefineID=7  dwSize=48
< 646.50559 [128] ObjectData: RequestID=10  DefineID=10  dwSize=1504
> 646.56970 [128, 1778608580]
< 646.56974 [128] >>>>>  EXCEPTION=5, SendID=1778608580, Index=61259  <<<<> 646.56976 [128, 1800271806]
< 646.56977 [128] >>>>>  EXCEPTION=5, SendID=1800271806, Index=61259  <<<<> 646.56979 [128, 35652893]
< 646.56980 [128] >>>>>  EXCEPTION=5, SendID=35652893, Index=61259  <<<<

[Pete Dowson]

0.01439 Server: Scope=global, Protocol=IPv4, Address=192.168.1.14, Port=500, MaxClients=64
0.01931 Server: Scope=local, Protocol=Auto, Address=::1, Port=49942, MaxClients=64
0.03655 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.03994 Server: Scope=local, Protocol=IPv6, Address=::1, Port=49943, MaxClients=64
0.04635 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=49944, MaxClients=64

It's interesting because I did not specify IPv6 or Pipe in my simconnect.xml. It must enable them by default if it isn't specified?

You have to explicitly Disable the Pipe, as I showed back in one of the messages here. I showed specific SimConnect.xml examples for you to make it easy.

I've never seen a log with so many SimConnect servers simultaneously enabled: one for remote use ("global" actually means "remote"), and FOUR (4) all for Local use? Why?

I think you should check your SimConnect.xml file and get it simplified down. I would be surprised if you are not overloading things.

< 646.47949 [128] >>>>>  EXCEPTION=2, SendID=11683, Index=0  <<<<<  Unrecognized Data Received. [128, 11683]
> 646.47953 [128, 11684]RequestSystemState:RequestID=1, szState="Sim"
< 646.48651 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48654 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48659 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48662 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48667 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48669 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48675 [128] ObjectData: RequestID=14  DefineID=14  dwSize=292
< 646.48677 [128] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 646.48737 [128] EventFrame: 0  10.296438
< 646.50543 [128] ObjectData: RequestID=9  DefineID=9  dwSize=72
< 646.50557 [128] ObjectData: RequestID=7  DefineID=7  dwSize=48
< 646.50559 [128] ObjectData: RequestID=10  DefineID=10  dwSize=1504
> 646.56970 [128, 1778608580]
< 646.56974 [128] >>>>>  EXCEPTION=5, SendID=1778608580, Index=61259  <<<<> 646.56976 [128, 1800271806]
< 646.56977 [128] >>>>>  EXCEPTION=5, SendID=1800271806, Index=61259  <<<<> 646.56979 [128, 35652893]
< 646.56980 [128] >>>>>  EXCEPTION=5, SendID=35652893, Index=61259  <<<<

Client 128 is using the Pipe -- you'd have 0-63 for the "global" connection, 64-127 for the local connection on port 49942 and 128-191 for the Pipe.

So it still comes down to memory corruption somehow. It may well be a bug in Simconnect. It would be worth your while trying a test with the pipe disabled, as I suggested, but also one with a more "normal" set of SimConnect servers -- one for your remote connection, and the two locally, Auto or IPv4 and Pipe.

Regards

Pete

[neorecon]

Took some tinkering to get it to finally configure correctly, but I have my simconnect configured as suggested IP & Pipes LOCAL and one IP GLOBAL

0.00000 SimConnect version 10.0.61259.0

0.01549 Server: Scope=global, Protocol=IPv4, Address=192.168.1.14, Port=500, MaxClients=64
0.03492 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.04292 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=59591, MaxClients=64

I'm going to try with this and also with pipe disabled as you suggested today. Hopefully one of these will get the problem resolved.

Thanks again for all of your assistance.

[neorecon]

Quick update after a weekend of testing:

Here's what I did:

Step 1: Reinstalled FSX up to SP2, Installed FSUIPC 4.272. I did not configure FSUIPC for the CH Controllers. I flew from KMSP to PHNL (8+ Hr flight) with no issues.

Step 2: Installed some of my scenery add-on's including UTX, GEX, and MyTraffic X 5.1b. Configured Traffic to 88%. Flew a flight from KMSP to PHNL again with no issues

Step 3: Installed WideFS 6.76 on client computer and ran AI Smooth. Flew flight from KMSP to PHNL again with no issues.

Step 4: Tonight will configure CH Controllers through FSUIPC and will fly same long haul flight again.

Final Step: Add Active Sky X to the mix to have programs connecting through WideFS and SimConnect.

[neorecon]

Well as soon as I resorted back to using FSUIPC to manage my controllers I got a crash. Before I enabled them in FSUIPC I had completed several long flights with no issues. Some of the long flights included using a client PC running AI Smooth via Wide FS.

I was able to reduce my 'sessions' down to two: One Global and One Local:

0.00000 SimConnect version 10.0.61259.0

0.01407 Server: Scope=global, Protocol=IPv4, Address=192.168.1.14, Port=500, MaxClients=64
0.02009 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=51990, MaxClients=64

But a few seconds before landing the following occurs...and according to the logic you mentioned above, these all look to be happening to the 'local' port of simconnect, which is the one that FSUIPC connects through?

< 6699.85736 [127] >>>>>  EXCEPTION=2, SendID=76560, Index=0  <<<<<  Unrecognized Data Received. [127, 76560]
> 6699.85742 [127, 76561]TransmitClientEvent:ObjectID=23318, EventID=65731, dwData=1, GroupID=1, Flags=0
> 6699.85744 [127, 76562]TransmitClientEvent:ObjectID=23318, EventID=65869, dwData=-475, GroupID=1, Flags=0
< 6699.86371 [127] ObjectData: RequestID=14  DefineID=14  dwSize=376
< 6699.86374 [127] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 6699.86398 [127] ObjectData: RequestID=14  DefineID=14  dwSize=376
< 6699.86399 [127] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 6699.86421 [127] ObjectData: RequestID=14  DefineID=14  dwSize=364
< 6699.86423 [127] ObjectData: RequestID=24  DefineID=24  dwSize=96
< 6699.86449 [127] EventFrame: 0  12.710634
< 6699.88603 [127] ObjectData: RequestID=7  DefineID=7  dwSize=48
< 6699.88606 [127] ObjectData: RequestID=9  DefineID=9  dwSize=64
< 6699.88608 [127] ObjectData: RequestID=10  DefineID=10  dwSize=1432
> 6699.93905 [127, 1634739258]
< 6699.93908 [127] >>>>>  EXCEPTION=5, SendID=1634739258, Index=61259  <<<<> 6699.93910 [127, 1644167160]
< 6699.93913 [127] >>>>>  EXCEPTION=5, SendID=1644167160, Index=61259  <<<<> 6699.93914 [127, 55]
< 6699.93915 [127] >>>>>  EXCEPTION=5, SendID=55, Index=61259  <<<<

Suggestions?

[Pete Dowson]

Suggestions?

I know that there is absolutely no way anything in FSUIPC itself can change the data BETWEEN SimConnect and FSX, which is what appears to be happening. Could you report this to Microsoft (for SimConnect), via tell_fs@microsoft.com, and then use the work-around you already know about. I will also send details direct to my contacts in Microsoft.

I'm on holiday soon until May 19th, But I am making notes now to add some diagnostics to FSUIPC -- I'll see if I can trap the occurrence of the first logged SimConnect error (the Exception 2), and then make FSUIPC log profusely everything it does regarding SimConnect. Even if it isn't a bug in FSUIPC (and it isn't looking like one), at least it may provide a clue as to how to work around it more tidily and automatically.

Incidentally, this is still only when brakes are assigned "direct to FSUIPC calibration", right?

If you don't hear from me soon after May 19th, please remind me about this.

Regards

Pete

[neorecon]

I don't think it is tied to the brakes, it seems I the problem returned when I went to using FSUIPC to manage the controllers (Yoke, Throttle, and pedals). I will forward this information on to microsoft, and again I appreciate your assistance.

Over the weekend on the remote chance this is something Vista or driver related I'm going to do a test run on Windows XP with the exact same setup to eliminate any hardware issue on my end.

Thanks again for your assistance with this!

[Pete Dowson]

I don't think it is tied to the brakes, it seems I the problem returned when I went to using FSUIPC to manage the controllers (Yoke, Throttle, and pedals).

That's odd. All the other reports, preceding this one, pointed only to toe brakes assigned in FSUIPC in "direct mode". This is the first ever report of it happening without that setup.

Perhaps you could please confirm exactly what axes you are assigning where, and in what mode. There are several combinations, as pointed out earlier in the thread:

Assigned in FSX, Not calibrated in FSUIPC

Assigned in FSX, Calibrated in FSUIPC

Assigned in FSUIPC, routed via FS controls, not Calibrated in FSUIPC

Assigned in FSUIPC, routed via FS controls, calibrated in FSUIPC

Assigned in FSUIPC, routed direct to FSUIPC calibration

All previous reports of the problem pointed to toe brakes (only) using the last option above.

Please try to narrow it down before i return.

Thanks,

Pete

[neorecon]

We'll do....now go enjoy your holiday!

[Albrecht EDDV]

Hi,

any news about this topic? I'm still hoping to hear the end of this story...

Best regards

Albrecht

[bitchin betty]

Likewise...

Mine seems to be related to a reverse thrust inputs.

Every time I land and roll out it crashes with either an MSVCR80.DLL error or API.DLL error.

My brake axis is assigned via FSX.

Thank you

[Pete Dowson]

Likewise...

"Likewise" to a thread which ended a year ago isn't a lot of help. If you have a problem you want help with, please start a new thread and post full details.

Regards

Pete