Jump to content
The simFlight Network Forums

Simconnect Race


Recommended Posts

Peter,

Think I am chasing a race condition after installing fsuipc 4.80. I had been successfully running fsx utilizing fsuipc 4.73 and wanted to upgrade to the latest 4.80. Here are two logs one successfully launches fsx and one terminates prematurely.

The one which terminates is running from an SSD disk (C:). This is why I think I am chasing a race in simconnect? I tried initdelay=120 without any noticable difference (terminated !) I was able to run from the SSD disk with the earlier version 4.73. I have not "intentionally" changed anything else!!

********* FSUIPC4, Version 4.80 by Pete Dowson *********

User Name="Tom McCaa"

User Addr="tmccaa@csc.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX

Module base=61000000

1172 System time = 15/03/2012 21:31:45

1172 FLT UNC path = "C:\Documents and Settings\tmccaa\My Documents\Flight Simulator X Files\"

1172 Trying to connect to SimConnect Acc/SP2 Oct07 ...

1266 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

2906 LogOptions=10000000 00000001

2906 Wind smoothing fix is fully installed

2906 G3D.DLL fix attempt installed ok

2906 SimConnect_Open succeeded: waiting to check version okay

2906 Trying to use SimConnect Acc/SP2 Oct07

71516 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

71516 Initialising SimConnect data requests now

71516 FSUIPC Menu entry added

71719 C:\Documents and Settings\tmccaa\My Documents\Flight Simulator X Files\kjyo.FLT

71719 C:\Documents and Settings\tmccaa\My Documents\Flight Simulator X Files\jyo mrb vor a.PLN

71719 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

71719 C:\Documents and Settings\tmccaa\My Documents\Flight Simulator X Files\jyo mrb vor a.PLN

74000 System time = 15/03/2012 21:32:58, Simulator time = 21:32:55 (02:32Z)

74016 Aircraft="Cessna Skyhawk 172SP Paint1"

136109 Starting everything now ...

------ This session launched successfully...

********* FSUIPC4, Version 4.80 by Pete Dowson *********

User Name="Tom McCaa"

User Addr="tmccaa@csc.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX

Module base=61000000

578 System time = 16/03/2012 06:23:52

578 FLT UNC path = "C:\Documents and Settings\tmccaa\My Documents\Flight Simulator X Files\"

594 Trying to connect to SimConnect Acc/SP2 Oct07 ...

625 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

2328 LogOptions=10000000 00000001

2328 Wind smoothing fix is fully installed

2328 G3D.DLL fix attempt installed ok

2328 SimConnect_Open succeeded: waiting to check version okay

2328 Trying to use SimConnect Acc/SP2 Oct07

This one aborted FSX......and was lanched from a SSD disk..

Help???

Tom in the States...

Link to comment
Share on other sites

Think I am chasing a race condition after installing fsuipc 4.80. I had been successfully running fsx utilizing fsuipc 4.73 and wanted to upgrade to the latest 4.80. Here are two logs one successfully launches fsx and one terminates prematurely.

By "terminates prematurely" I presume you mean "crashes"? What does the Windows error log show? I need the details, please. Better still, please update to 4.811 (Download Links subforum) so you are on the same version as me, then I can make use of any module address you find in the log.

The one which terminates is running from an SSD disk (C:). This is why I think I am chasing a race in simconnect? I tried initdelay=120 without any noticable difference (terminated !) I was able to run from the SSD disk with the earlier version 4.73. I have not "intentionally" changed anything else!!

I run from an SSD. That won't make any difference. Maybe there's a difference in the FSUIPC4.INI file? Compare them and see. But first check with 4.811. Are you using two different PCs or two installs of FSX on the same PC? If the latter, could there have been a problem with the SmConnect part of the install?

The logs don't show anything.useful except that SmConnect never responded to the Open request to it, presuymably because of the crash beforehand. Maybe a SimConnect log will show something -- see the FAQ thread on that.

Regards

Pete

Link to comment
Share on other sites

By "terminates prematurely" I presume you mean "crashes"? What does the Windows error log show? I need the details, please. Better still, please update to 4.811 (Download Links subforum) so you are on the same version as me, then I can make use of any module address you find in the log.

Tom - By terminates I mean FSX goes away without anything on the screen. I'll look in the Windows log after trying 4.811 as suggested. It will be a few days since my simulator is at my apartment in Washington D.C. where I work. I am at home in Pennsylvania now.

I run from an SSD. That won't make any difference. Maybe there's a difference in the FSUIPC4.INI file? Compare them and see. But first check with 4.811. Are you using two different PCs or two installs of FSX on the same PC? If the latter, could there have been a problem with the SmConnect part of the install?

Tom - I am using the same pc. I made a full system backup to the SSD( bootable) of the working disk (C:) and then opened the machine and swapped in the new SSD disk. There is only one drive installed when I am testing . There should be no difference between the two disk contents including the o/s.

The logs don't show anything.useful except that SimConnect never responded to the Open request to it, presuymably because of the crash beforehand. Maybe a SimConnect log will show something -- see the FAQ thread on that.

Tom - Good point. If FSx went down not giving SimConnect time to respond, thus the log trail I have. I have some work to do before getting back to you.

Tom - Thank you for the quick response. Well worth the upgrade expense. You earn your Dollars or Pounds

Link to comment
Share on other sites

I am trying to get Dr Watson to field the application abend. Is there any other error log that would be helpful?

The details will be in the Windows error logs. In Win7 just go to the Start button, enter "event viewer" and press Enter. In the display window that comes up the Windows Logs entry will contain the error details in the Applications folder. Search for the relevant event which will be an error with a red exclamation icon. You can double click it and copy the data for pasting back here.

I've moved on since 4.811, so if the crash is in FSUIPC the module address wil be wrong. The current update is FSUIPC4811d. It changes almost daily whilst I'm helping someone else solve a problem with LINDA and the PMDG NGX.

Regards

Pete

Link to comment
Share on other sites

Pete,

I am running XP but I see they have an Event Viewer in the Admin Tools. I'll see where that takes me tonight?

If I want to temporarliy backup to FSUIPC 4.73 once I have upgraded to a newer version (4.811), can I backup easily. Guess I could alway take a sync point huh?

Tom

Link to comment
Share on other sites

Pete,

I have a solid configuration with FSUIPC 4.73 which is a known starting point. If I can easily get back to that point prior to starting any upgrades you may suggest, that gives me a good solid starting point. As you know, if I try to run install from a prior version, I get an information messaging telling me FSUIPC is already at a higher version. (prohibiting a downgrade if you would).

A sync point is a "system restore point" in XP terminology. sorry...

Question: Is there a document telling me when it is safe to overwrite the fsxuipc4.dll rather that do a full install (4.80 to 4.811 ex)

Stick with me, I am a quick learner.

Thank you

Tom

Link to comment
Share on other sites

As you know, if I try to run install from a prior version, I get an information messaging telling me FSUIPC is already at a higher version. (prohibiting a downgrade if you would).

That's only because it can see the FSUIPC4.DLL in your modules folder. There's no other record it checks.

Question: Is there a document telling me when it is safe to overwrite the fsxuipc4.dll rather that do a full install (4.80 to 4.811 ex)

Full installs are needed for folks who've not had FSUIPC before, or who have reinstalled Windows or moved to a different PC. It is also the only way to ensure you have the correct relevant documentation and other files to match that version. The individual updates, for interim versions, are just the DLL and a list of changes.

Regards

Pete

Link to comment
Share on other sites

Pete,

Ok got it... I have updated to fsuipc4.811d and retested. Looks like the event viewer/system has trapped a simconnect problem. Here is the log and the first occurance of message.

Type Date Time Source Category Event User Computer

Error 3/20/2012 3:24:04 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/20/2012 3:24:04 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/20/2012 3:24:04 PM SideBySide None 32 N/A IFS_ATD_PC_100

Error 3/20/2012 3:24:01 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/20/2012 3:24:01 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/20/2012 3:24:01 PM SideBySide None 32 N/A IFS_ATD_PC_100

Dependent Assembly Microsoft.FlightSimulator.SimConnect could not be found and Last Error was The referenced assembly is not installed on your system.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Information 3/20/2012 3:21:26 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:25 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:25 PM Service Control Manager None 7035 tmccaa IFS_ATD_PC_100

Information 3/20/2012 3:21:23 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:22 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:21 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:21 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/20/2012 3:21:20 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:20 PM Service Control Manager None 7035 tmccaa IFS_ATD_PC_100

Information 3/20/2012 3:21:20 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:14 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:14 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:14 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/20/2012 3:21:14 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/20/2012 3:21:13 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:13 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/20/2012 3:21:13 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:21:13 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/20/2012 3:21:13 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/20/2012 3:19:51 PM b57w2k None 9 N/A IFS_ATD_PC_100

Information 3/20/2012 3:19:49 PM b57w2k None 15 N/A IFS_ATD_PC_100

Information 3/20/2012 3:20:11 PM eventlog None 6005 N/A IFS_ATD_PC_100

Information 3/20/2012 3:20:11 PM eventlog None 6009 N/A IFS_ATD_PC_100

Information 3/20/2012 3:19:19 PM eventlog None 6006 N/A IFS_ATD_PC_100

Information 3/20/2012 3:19:13 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

What do you think? Tom

Link to comment
Share on other sites

Ok got it... I have updated to fsuipc4.811d and retested. Looks like the event viewer/system has trapped a simconnect problem. Here is the log and the first occurance of message.

I don't think any of those are real errors or crashes. It looks like some add-on your are running (not FSUIPC4) is doing a manifest probe to detect the version of Simconnect to connect. I used to do that with FSUIPC as well, but changed a couple of years ago to a direct connection, by-passing the Side-by-Side connection which produces such spurious entries which otherwise occur if you want the software to work with more than one version (i.e. FSUIPC works with RTM, SP1, SP2 or FSX, plus ESP and Prepar3D versions of SimConnect).

However, seeing that, it may well be that one of the other Simconnect clients is causing the clash and resultant crash. You should do a process of elimination of the other add-ons you are running.

There should be an entry in the Applications event log for the crash itself. It will state FSX.EXE as the process and give you the module name, the code offset, and the crash code. None of that information is provided in the case of a specific library version not being found.

this reminds me. Remember way back at the beginning I suggested this:

"Maybe a SimConnect log will show something -- see the FAQ thread on that."

Did you ever get around to getting one of those?

Regards

Pete

Link to comment
Share on other sites

Pete,

Found this on the Reality XP Forum. Looks like they believe the Event are normal.

The Windows Event Viewer flags SideBySide Codes 59 and 32 referencing a Reality XP gauge?

This is normal. All our Gauge XTreme gauges uses SimConnect in a dynamic fashion to permit loading the same gauge in either Flight Simulator 9 (without SimConnect) or Flight Simulator X/ESP, otherwise, a static binding between the gauge and SimConnect would prevent the gauge loading under FS9 (or at least, for customers running FS9 without having installed FSX). The system permits searching for the most updated version of SimConnect DLL, and the Windows API that permits doing this dynamically creates entries in the event log just for information. This is a Windows API/Operating system feature, not an error in the products.

I did not see anything in the Application Event Log when I looked. I'll validate that again.

So now off to get a SimConnect Log . See where that takes us.

Thanks for the support. Not sure we're converging

Tom

Link to comment
Share on other sites

Found this on the Reality XP Forum. Looks like they believe the Event are normal.

Yes, as I said, same as the way FSUIPC4 used to do it -- I just worked out a different way in recent versions.

I did not see anything in the Application Event Log when I looked. I'll validate that again.

I've never known FSX to crash and there be no entry at all.

Regards

Pete

Link to comment
Share on other sites

Pete,

Here is the simconnect log I just captured.

0.00000 SimConnect version 10.0.61259.0

0.04949 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1032, MaxClients=64

0.09293 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64

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

0.17677 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1033, MaxClients=64

0.99744 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1"

1.25133 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1"

1.59554 Panels data export found and set to 20AF19E8

46.47738 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1"

46.71771 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>"

46.79087 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>"

47.34921 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>"

47.58572 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5"

47.59972 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60036 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60233 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60296 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60526 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60587 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60768 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60828 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60958 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61015 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61190 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61250 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61381 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61438 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61567 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61625 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61763 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61822 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62048 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62110 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62290 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62353 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62486 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62544 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

49.11832 Panels data export found and set to 20AF19E8

50.94373 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.1.1"

Also, The Application Event Viewer.

Type Date Time Source Category Event User Computer

Information 3/21/2012 6:49:18 PM gusvc None 0 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:58 PM SecurityCenter None 1800 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:58 PM WebrootSpySweeperService None 0 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:18 PM gusvc None 0 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:18 PM gupdate None 0 N/A IFS_ATD_PC_100

Event Log System

Type Date Time Source Category Event User Computer

Information 3/21/2012 7:01:32 PM Windows Update Agent Installation 19 N/A IFS_ATD_PC_100

Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2000 N/A IFS_ATD_PC_100

Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2000 N/A IFS_ATD_PC_100

Information 3/21/2012 7:01:15 PM Microsoft Antimalware None 2002 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:40 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:40 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:40 PM SideBySide None 32 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:37 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:37 PM SideBySide None 59 N/A IFS_ATD_PC_100

Error 3/21/2012 6:56:37 PM SideBySide None 32 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:19 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:18 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:18 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:17 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:14 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:14 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/21/2012 6:49:12 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:11 PM Service Control Manager None 7035 tmccaa IFS_ATD_PC_100

Information 3/21/2012 6:49:11 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:11 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/21/2012 6:49:10 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:10 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/21/2012 6:49:05 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:49:05 PM Service Control Manager None 7035 SYSTEM IFS_ATD_PC_100

Information 3/21/2012 6:49:05 PM Service Control Manager None 7036 N/A IFS_ATD_PC_100

Information 3/21/2012 6:47:28 PM b57w2k None 9 N/A IFS_ATD_PC_100

Information 3/21/2012 6:47:26 PM b57w2k None 15 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:00 PM eventlog None 6005 N/A IFS_ATD_PC_100

Information 3/21/2012 6:48:00 PM eventlog None 6009 N/A IFS_ATD_PC_100

Thanks Tom

Link to comment
Share on other sites

Here is the simconnect log I just captured.

How does it compare to the same system on the normal disk, which you say works?

There are also a lot of other SimConnect clients loading. I think you'll need to carry out some process of elimination. try stopping all of them and adding them back one at a time. These are they:

0.99744 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1"

1.25133 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1"

46.47738 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1"

46.71771 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>"

46.79087 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>"

47.34921 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>"

47.58572 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5"

Additionally there's something wrong in any case -- is your DLL.XML file corrupt? Else what causes this? ---

47.59972 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60036 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60233 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60296 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60526 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60587 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60768 DLL already loaded: Path="Modules\EliteFSX.dll"

47.60828 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.60958 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61015 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61190 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61250 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61381 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61438 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61567 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61625 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.61763 DLL already loaded: Path="Modules\EliteFSX.dll"

47.61822 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62048 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62110 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62290 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62353 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

47.62486 DLL already loaded: Path="Modules\EliteFSX.dll"

47.62544 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

Also, The Application Event Viewer.

There's nothing relevant there. you need to find the FSX.EXE crash information.

Regards

Pete

Link to comment
Share on other sites

Pete,

The SimConnect from the working FSX is similiar except it does not CTD.

0.00000 SimConnect version 10.0.61259.0

0.11085 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1037, MaxClients=64

0.16999 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64

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

0.37548 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1038, MaxClients=64

1.67181 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1"

1.98385 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1"

2.32682 Panels data export found and set to 20AF19E8

83.10054 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1"

83.56004 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>"

83.81151 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>"

86.96876 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>"

87.76411 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5"

87.78331 DLL already loaded: Path="Modules\EliteFSX.dll"

87.78385 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.78506 DLL already loaded: Path="Modules\EliteFSX.dll"

87.78555 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.78752 DLL already loaded: Path="Modules\EliteFSX.dll"

87.78896 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.79083 DLL already loaded: Path="Modules\EliteFSX.dll"

87.79134 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.79253 DLL already loaded: Path="Modules\EliteFSX.dll"

87.79298 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.79500 DLL already loaded: Path="Modules\EliteFSX.dll"

87.79548 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.79835 DLL already loaded: Path="Modules\EliteFSX.dll"

87.79888 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.80011 DLL already loaded: Path="Modules\EliteFSX.dll"

87.80058 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.80262 DLL already loaded: Path="Modules\EliteFSX.dll"

87.80317 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.80521 DLL already loaded: Path="Modules\EliteFSX.dll"

87.80632 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

87.80758 DLL already loaded: Path="Modules\EliteFSX.dll"

87.80804 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

89.64034 Panels data export found and set to 20AF19E8

92.79150 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.0.0"

92.80194 DLL already loaded: Path="Modules\EliteFSX.dll"

92.80248 DLL Load Failed: Error=-2 Path="Modules\EliteFSX.dll"

> 173.26540 [255, 1]Open: Version=0x00000002 Name="Saitek Flight Sim X Plugin"

> 173.26583 [255, 2]SubscribeToSystemEvent:EventID=1, SystemEventName="SimStart"

> 173.26610 [255, 3]SubscribeToSystemEvent:EventID=2, SystemEventName="SimStop"

> 173.26628 [255, 4]SubscribeToSystemEvent:EventID=3, SystemEventName="Paused"

> 173.26646 [255, 5]SubscribeToSystemEvent:EventID=4, SystemEventName="Unpaused"

I cut if off here .. everything appears to work .

Don't know why the EliteFSX.dll is multi-loading? May have to open a tickey with eflite on this one. What xml may be corrupted?

Still have not idea about the fsx abort. I did a search of all files created by date FSX aborted. Did not find anything looking like an error log. I don't know if I have an abent handler disabled? Is that possible on XP?

Thanks Tom

Link to comment
Share on other sites

Pete,

I did find the DLL.XML and removed the duplicate eliteFSX.DLL. That cleaned that up but still CTD. I'll keep at it.

Tom

0.00000 SimConnect version 10.0.61259.0

0.06595 Server: Scope=local, Protocol=Auto, Address=127.0.0.1, Port=1030, MaxClients=64

0.12191 Server: Scope=global, Protocol=IPv4, Address=(null), Port=13300, MaxClients=64

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

0.22515 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=1031, MaxClients=64

1.27885 Exe Launched: Path="C:\Program Files\GoFlight\GFDevFSX.exe" CommandLine="" Version="2.0.3.1"

1.50951 Exe Launched: Path="C:\Program Files\Saitek\Pro Flight Panels\SaiPanels.exe" CommandLine="-run" Version="1.0.0.1"

1.74049 Panels data export found and set to 20AF19E8

78.90816 DLL Loaded: Path="C:\Flight1 Aviation Technologies\VisPro Communication Module\module\VISProFSX.dll" Version="1.50.0.1"

79.12700 DLL Loaded: Path="C:\Program Files\SquawkBox\sbtrans10.dll" Version="<Unknown>"

79.27962 DLL Loaded: Path="C:\Program Files\SquawkBox\sbaicontrol10.dll" Version="<Unknown>"

80.13062 DLL Loaded: Path="C:\Program Files\SquawkBox\sbmod10.dll" Version="<Unknown>"

80.49370 DLL Loaded: Path="Modules\EliteFSX.dll" Version="2.0.1.5"

82.96193 Panels data export found and set to 20AF19E8

86.82857 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.8.1.1"

Link to comment
Share on other sites

The SimConnect from the working FSX is similiar except it does not CTD.

Have you tried eliminating the other Simconnect clients, yet? It must be some sort of conflict.

Don't know why the EliteFSX.dll is multi-loading? May have to open a tickey with eflite on this one. What xml may be corrupted?

The DLL.XML file -- the one loading the DLLs. You'll have an EXE.XML too. Those two are the files you can edit to enable/disable each of the program which is being loaded. They are in the same folder as your FSX.CFG file.

Still have not idea about the fsx abort. I did a search of all files created by date FSX aborted. Did not find anything looking like an error log. I don't know if I have an abent handler disabled? Is that possible on XP?

Sorry, I don't know. I suppose you might be able to stop tstuff by stopping Windows services. I've never had any trouble. but i don't use XP any more, not for FSX. Only for the mini-PCs in my cockpit.

[LATER]

It just occurred to me: you are using Windows XP on an SSD? The main reason I changed to Windows 7 was for SSD support. All of my FSX PCs (two cockpits and a development system) are using SSDs, but all with Windows 7. I don't think XP works well with SSDs and it certainly doesn't use TRIM on them, so they get slower and slower and slower as everything clogs up.

Maybe this problem is simply related to poor SSD support in XP?

Pete

Link to comment
Share on other sites

Pete,

Ok I think we are starting to converge now!

I as pealing back the onion so to speak. I got to the dll.xml and removed almost everything being started manually. same CTD. Then went to the fsx.cfg and removed all of the TRUST section and selectively started each .dll. It appears that when any of the RXP (FLN, FLT, GNS) run, I CTD. But FSX sometimes displays a window informing me that FSX has a fatal error. So there is no crash because FSX is helping me out by gracefully handling the fatal error and terminating gracefully? THANK YOU FSX!!!

I'll have to keep your SSD thread for later. I'll get to non SSD drive configuration that has the problem just so I can eliminate the SSD as a variable for now.

Boy. Thanks for the guidance and helpful hints on where to look for snippets of information.

Not sure what any of this has to do with FSUIPC upgrade other than changing load order/timings? Still think I have been chasing a race condition.

Tom

Link to comment
Share on other sites

Pete,

Ok.. Think I have isolated the problem to the RXP s/w which went south after the FSUIPC 4.80 upgrade. Think we just changed the load order and probably timing between the s/w modules. I now have a FSX that loads with 4.80 and does not CTD. Now I have to put it all back together.

THANK YOU FOR ALL YOU SUPPORT!!!

Next time someone complains about the cost of an upgrade, send them my way...You can not get this type of support from any other s/w provider that I have worked with....

Tom

Link to comment
Share on other sites

Ok.. Think I have isolated the problem to the RXP s/w which went south after the FSUIPC 4.80 upgrade. Think we just changed the load order and probably timing between the s/w modules. I now have a FSX that loads with 4.80 and does not CTD. Now I have to put it all back together.

Good, hope it goes together well. Good flying!

Pete

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.