Jump to content
The simFlight Network Forums
arnonmoscona

FSUIPC not detecting Saitek X-55 throttle and stick

Recommended Posts

Hi!

Before anything else I must state that I have checked the forums and the FAQ. My problem is similar to what was experienced by other people but the solution that worked for others and is suggested in the FAQ does not work for me.

 

  • The problem: FSUIPC (paid/registered) does not detect axes or buttons on my Saitek X-55 throttle as well as the stick
  • The Saitek rudder pedals are detected correctly
  • Two saitek throttle quadrants are detected correctly
  • All the devices, in cluding the X-55 units work just fine both in the Windows calibration utility and when mapped directly via FSX
  • I have tried to use JoysID as discussed in several places, and that had no effect. Swapping devices or assigning new IDs (not used before) to the X-55 units did not make any difference. FSUIPC still does not see them.
  • Using FSX-SE
  • I am on Windows 10 pro
  • Latest Saitek drivers
  • Latest version of FSUIPC
  • Looked at discussions here: https://www.avsim.com/forums/topic/437639-x55-not-working-with-fsuipc-fsx-solution/

As well as other places. Everybody points me to JoysID utility, but that gets me zero results...

 

Any other ideas?

 

Thanks

Arnon

 

Share this post


Link to post
Share on other sites

Here you go:

While the log looks like the X-55 is detected - it is not. If I go to FSUIPS to try to make axis or button assignmnets then it looks like nothing (can rescan until the cows come home)

********* FSUIPC4, Version 4.966c (17th April 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "D:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=217D0000
User Name="Arnon Moscona"
User Addr="arnon@moscona.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 21/05/2017 08:11:17
        0 FLT path = "C:\Users\Arnon\Documents\Flight Simulator X Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.62615.0
        0             api.dll: 10.0.62615.0
        0        controls.dll: 10.0.62615.0
        0      fs-traffic.dll: 10.0.62615.0
        0             G3D.dll: 10.0.62615.0
        0        language.dll: 10.0.62615.0
        0            sim1.dll: 10.0.62615.0
        0        visualfx.dll: 10.0.62615.0
        0         weather.dll: 10.0.62615.0
        0          window.dll: 10.0.62615.0
        0 ----------------------------------
       31 Trying to connect to SimConnect Steam ...
       47 FS path = "D:\SteamLibrary\steamapps\common\FSX\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= Saitek Pro Flight Quadrant
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0C2D (Version 2.1)
      125    Assigned joystick id 0 (fixed Registry)
      125    GUID= {F6B633E0-27FB-11E7-8002-444553540000}
      125 Product= vJoy - Virtual Joystick
      125    Manufacturer= Shaul Eizikovich
      125    Serial Number= 2.0.5
      125    Vendor=1234, Product=BEAD (Version 2.5)
      125    Assigned joystick id 1 (Registry okay)
      125    GUID= {109593D0-2812-11E7-8002-444553540000}
      172 Product= Saitek Pro Flight Quadrant
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0C2D (Version 2.2)
      172    Assigned joystick id 3 (Registry okay)
      172    GUID= {08809CA0-38D7-11E7-8006-444553540000}
      172 Product= Saitek Pro Flight X-55 Rhino Stick
      172    Manufacturer= Madcatz
      172    Serial Number= G0000609
      172    Vendor=0738, Product=2215 (Version 0.86)
      172    Assigned joystick id 2 (Registry okay)
      172    GUID= {299EC5D0-3D62-11E7-8005-444553540000}
      172 Product= <not readable at this time: maybe device disconnected?>
      172    Vendor=046D, Product=C2AB (Version 0.1)
      172    Assigned joystick id 4 (Registry okay)
      172    GUID= {C8E21EE0-393D-11E7-8003-444553540000}
      172 Product= Saitek Pro Flight X-55 Rhino Throttle
      172    Manufacturer= Madcatz
      172    Serial Number= G0001570
      172    Vendor=0738, Product=A215 (Version 0.119)
      172    Assigned joystick id 5 (Registry okay)
      172    GUID= {337E3D10-3D62-11E7-8007-444553540000}
      172 Product= Logitech Dual Action
      172    Manufacturer= Logitech
      172    Serial Number= DCCA434C
      172    Vendor=046D, Product=C216 (Version 4.20)
      172    Assigned joystick id 6 (Registry okay)
      172    GUID= {D42E67D0-38D5-11E7-8007-444553540000}
      172 Product= Saitek Pro Flight Combat Rudder Pedals
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0764 (Version 2.1)
      172    Assigned joystick id 7 (Registry okay)
      172    GUID= {9AFCE820-3942-11E7-8004-444553540000}
      172 -------------------------------------------------------------------
      172 ---------- Making INI JoyNames Section ----------
      172    Joy#0: OEMName = "Saitek Pro Flight Quadrant"
      172    Joy#0: GUID = {F6B633E0-27FB-11E7-8002-444553540000}
      172    Joy#1: OEMName = "vJoy Device"
      187    Joy#1: GUID = {109593D0-2812-11E7-8002-444553540000}
      187    Joy#2: OEMName = "Saitek Pro Flight X-55 Rhino Stick"
      187    Joy#2: GUID = {299EC5D0-3D62-11E7-8005-444553540000}
      187    Joy#3: OEMName = "Saitek Pro Flight Quadrant"
      187    Joy#3: GUID = {08809CA0-38D7-11E7-8006-444553540000}
      187    Joy#4: OEMName = "Logitech G13 Joystick"
      187    Joy#4: GUID = {C8E21EE0-393D-11E7-8003-444553540000}
      187    Joy#5: OEMName = "Saitek Pro Flight X-55 Rhino Throttle"
      187    Joy#5: GUID = {337E3D10-3D62-11E7-8007-444553540000}
      187    Joy#6: OEMName = "Logitech Dual Action"
      187    Joy#6: GUID = {D42E67D0-38D5-11E7-8007-444553540000}
      187    Joy#7: OEMName = "Saitek Pro Flight Combat Rudder Pedals"
      187    Joy#7: GUID = {9AFCE820-3942-11E7-8004-444553540000}
      187 -------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 ------ Setting the hooks and direct calls into the simulator ------
      203 --- CONTROLS timer memory location obtained ok
      203 --- SIM1 Frictions access gained
      203 --- FS Controls Table located ok
      203 --- Installed Mouse Macro hooks ok.
      203 --- Wind smoothing fix is fully installed
      203 --- SimConnect intercept for texts and menus option is off
      203 --- All links checked okay
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Trying to use SimConnect Steam
      203 Opened separate AI Traffic client okay
     1797 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     1797 Initialising SimConnect data requests now
     1797 FSUIPC Menu entry added
     1812 c:\users\arnon\documents\flight simulator x files\KFHR runway default C172.FLT
     1812 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air
    41515 Weather Mode now = Theme
    49250 User Aircraft ID 1 supplied, now being used
    49281 Aircraft loaded: running normally now ...
    97453 Aircraft="Cessna Skyhawk 172SP Paint1"
    97453 System time = 21/05/2017 08:12:54, Simulator time = 08:11:58 (15:11Z)
   128172 Sim stopped: average frame rate for last 31 secs = 45.7 fps
   128172    Max AI traffic was 0 aircraft
   142484 Starting everything now ...
   142515 ASN active function link set
   142515 Ready for ASN WX radar
   143640 Advanced Weather Interface Enabled
   167515 Sim stopped: average frame rate for last 35 secs = 40.9 fps
   167515    Max AI traffic was 14 aircraft (Deleted 0)
   169844 C:\Users\Arnon\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
   202469 === DLLStop called ...
   202469 === Closing external processes we started ...
   203469 === About to kill any Lua plug-ins still running ...
   203625 === Closing global Lua thread
   204625 === About to kill my timers ...
   204828 === Restoring window procs ...
   204828 === Unloading libraries ...
   204828 === stopping other threads ...
   204828 === ... Memory checking ...
   204828 === ... Button scanning ...
   204922 === ... Axis scanning ...
   205015 === Releasing joystick devices ...
   205015 === Freeing macro memory
   205015 === Removing any offset overrides
   205015 === Clearing any displays left
   205015 === NOTE: not calling SimConnect_Close ...
   205015 === AI slots deleted!
   205015 === Freeing button memory ...
   205015 === Closing my Windows ...
   205031 === Freeing FS libraries ...
   206031 === Closing devices ...
   206031 === Closing the Log ... Bye Bye! ...
   206031 System time = 21/05/2017 08:14:43, Simulator time = 08:12:33 (15:12Z)
   206031 *** FSUIPC log file being closed
Minimum frame rate was 36.9 fps, Maximum was 43.2 fps
Minimum available memory recorded was 1136Mb
Average frame rate for running time of 66 secs = 43.0 fps
Maximum AI traffic for session was 14 aircraft
Memory managed: 17 Allocs, 16 Freed
********* FSUIPC Log file closed ***********

 

Share this post


Link to post
Share on other sites

Hi,

Quote

The problem: FSUIPC (paid/registered) does not detect axes or buttons on my Saitek X-55 throttle as well as the stick

  • The Saitek rudder pedals are detected correctly
  • Two saitek throttle quadrants are detected correctly
  • All the devices, in cluding the X-55 units work just fine both in the Windows calibration utility and when mapped directly via FSX
  • I have tried to use JoysID as discussed in several places, and that had no effect. Swapping devices or assigning new IDs (not used before) to the X-55 units did not make any difference. FSUIPC still does not see them.
  • Using FSX-SE
  • I am on Windows 10 pro
  • Latest Saitek drivers
  • Latest version of FSUIPC
  • Looked at discussions here:

you said you use latest FSUIPC4 but as the log shows you use 4.966c, the latest Installer. The latest FSUIPC4 version is 4.966n, where Pete did rewrite over weeks the whole Controller-Input part special because of the problem with Saitek X-55 and some other Saitek products. See below the Quote from download section

Quote

TEST update 4.966n (DLL module only): FSUIPC 4.966n.zip
PLEASE READ THIS FIRST!
There are a few requested changes and fixes in this release, so you may want to try it, but it is mainly aimed at those who have been suffering joystick recognition and assignment problems, especially with Saitek X55 and X56 units. It features a totally re-written joystick scanning system which needs real exposure, but is ulitimately more logical and more understandable than the previous mess which grew like topsy to meets the needs as they arrived.

Actual changes are listed in the included PDF document, as are requirements for the data to be supplied with any feedback about the joystick system.

[Version 4.966n is different to 4.966m only in that it will now recognise devices with no axes, only buttons, or even valid prototyping boards like the Leo Bodnar BU0836, with no connections yet made on the board]

Please install this version FSUIPC 4.966n.zip

Thomas

Share this post


Link to post
Share on other sites

Thank you for pointing out this beta versions. Generally I only use Pete's production downloads, not betas.

 

I tried this version of the DLL, and unfortunately it crashes my sim (CTD on load) - and leaves no log behind when it crashes. To revert back to the production DLL it was not enough to replace the DLL back to the previous version - I had to actually install it from the installer and restart the machine. (Just restarting the machine with the production version was not enough). Once back in the production versions and a couple of FSX restarts I was back stable again, but without X-55 devices in FSUIPC. So for now I am mapping them directly in the sim rather than via FSUIPC, which gives me less flexibility - but at least it works and is stable.

 

So short story: no go with the beta DLL, and cannot help you with logs as it crashes before producing any.

 

Arnon

Share this post


Link to post
Share on other sites

Hi,

no one reported a crash up to now with latest version (4.966n).

Try renaming your original FSUIPC4.ini file, e.g. _FSUIPC4.ini, so it will create a new one on next FS start (with FSUIPC4.966n version). Maybe something corrupt in the INI file.

If FS crashes there will be a Win crash report (Event Viewer) that would help.

Thomas

Share this post


Link to post
Share on other sites
On 5/21/2017 at 10:41 PM, Thomas Richter said:

Hi,

no one reported a crash up to now with latest version (4.966n).

Try renaming your original FSUIPC4.ini file, e.g. _FSUIPC4.ini, so it will create a new one on next FS start (with FSUIPC4.966n version). Maybe something corrupt in the INI file.

If FS crashes there will be a Win crash report (Event Viewer) that would help.

Thomas

Well - I am reporting it. While I am very familiar with the windows event manager, no crash is reported by it.  Removing the FSUIPC.ini file from the directory does cause a fresh one to be created on the first launch, but thereafter it crashes nevertheless, regardless of whether the file is removed or not. Again, reinstalling the production version using the installer, recovering the backup of the ini file that was previously used by the production version, and restarting the machine - gets me back to a stable situation.

My only conclusion has to be that the beta n version is simply not stable enough yet and that I must wait with no ability to properly map the X-55 via FSUIPC until there is a more stable version.

FSUIPC has long had problems at startup with various version. The claim always seems to be that everything is perfect and some other component is to blame. But I cannot accept that. Messing with FSUIPC alone and leaving everything else intact can get you in a stable situation or an unstable one. Also, the X-55 problems appear to affect only FSUIPC and no other addon. Everything else seems to have no problems (like FSX itself, chaseplane, FS2crew, OpusFSI, other sims like Cliffs of Dover or Battle of Stalingrad). So something must be off in the way that FSUIPC handles controls that is different than what everybody else seems to do. I wouldn't complain much if this was a free addon, but it's not. It is paid, and it is not delivering the quality one might expect from a paid product. It is chronically unstable.

Share this post


Link to post
Share on other sites
7 hours ago, arnonmoscona said:

Removing the FSUIPC.ini file from the directory does cause a fresh one to be created on the first launch, but thereafter it crashes nevertheless,

On the first launch, as well as an INI is there a LOG file? At what stage does it crash on the first launch, compared to the subsequent ones, as it seems you are saying they are different?

7 hours ago, arnonmoscona said:

My only conclusion has to be that the beta n version is simply not stable enough yet

The only part of FSUIPC which is different in this so-called "Beta" version (to be released this week as 4.967, replacing 4.966c) is the Joystick Scanning, which has been completely replaced with a much more locial system than the one which has grown up with bits and pieces patched into it over the last 20 years in order to cope with different things as they cropped up.

If the crash you are getting is occurring before FSUIPC has even started, which it sounds like (except for when an INI and/or LOG is produced), then it is invariably due to a previous crash or hang on closing FS. This is actually indicated also by your previous report:

On 5/22/2017 at 4:22 AM, arnonmoscona said:

To revert back to the production DLL it was not enough to replace the DLL back to the previous version - I had to actually install it from the installer and restart the machine. (Just restarting the machine with the production version was not enough).

The Installer makes a change to the Registry each time it is run which removes FSUIPC from a list of "DLLs not to be loaded". Those DLLs seem to be automatically classified as "bad" if they were still in FS's process memory when a terminating hang or crash occurs -- i.e. one which may even not be noticed which occurs during the process termination sequence.

The main things which can cause this for FSUIPC are Lua plug-ins which use external drivers for hardware access, like LINDA. However, I see no indication of anything like that from the Log file you posted a while ago.

The reason the X-55 was not handled correctly in some (not all) configurations in previous versions of FSUIPC was because somehow their installers provide 2 entries in the Registry for both Stick and Throttle, with slightly different GUIDs. With the earlier FSUIPC scanning method these were indistinguishable so FSUIPC chose the first of the two, which seemed the obvious choice (and which does actually work for everything I've ever seen up till the X-55 and X-56).

Your earlier log shows:

      187    Joy#2: OEMName = "Saitek Pro Flight X-55 Rhino Stick"
      187    Joy#2: GUID = {299EC5D0-3D62-11E7-8005-444553540000}
      187    Joy#5: OEMName = "Saitek Pro Flight X-55 Rhino Throttle"
      187    Joy#5: GUID = {337E3D10-3D62-11E7-8007-444553540000}
 
I woould expect the correct GUIDs to be identical to those except with the 8005 and 8007 part different -- possibly 8004 and 8006 respectively, or 8006 and 8008. For use with 4.966c you could try just editing the GUID lines in the INI file. For a definitive answer to whuch GUIDs to use I would need to see the Registry entries, which I could do if you wish (I'd provide the details for you to use RegEdit to export the relevant section).

7 hours ago, arnonmoscona said:

FSUIPC has long had problems at startup with various version. The claim always seems to be that everything is perfect and some other component is to blame.

That is grossly unfair. FSUIPC is 100% stable and reliable for 99.9% and more of its many users. The main start up problems reported have almost all been due to end of session crashes which has an assortment of causes. FSUIPC just happens to be one of the last parts of the process to terminate because of how much tidying up it has to do and also to give WideServer clients time to see the closure themseves.

There have in the past been known conflicts, only occurring during the loading times, with other DLLs being loaded and initialised  -- BGLMANX.DLL was one such, and earlier versions of PMDG_Options was also one. Generally it is best to have FSIPC loading last in the DLL list, which is where the Installer places it (except for Active Sky's DLL, which is loaded even later, otherwise FSUIPC's weather radar provisions do not work. This is because of conflicts in hooking into FS's weather system).

If you are judging the reliability of FSUIPC by reports here, you are mistaking the use of a Support Forum for a consensus from users, whichit plainly isn't. 

7 hours ago, arnonmoscona said:

Also, the X-55 problems appear to affect only FSUIPC and no other addon.

Well. that's not strictly true as you will see if you review the other X-55 reports, However, one reason is that FSUIPC has grown from a purely registry and old "Joy" interface user, in FS2000 -- FS2004, into a DirectInput user, but still identifies devices primarily via the Registry. The X-55, X-56 series is the first encounter where the Registry can be misleading (and then not  for all -- the order of the GUIDs in the Registry appears random).

The whole point of the changes made in 4.966n is to remove the legacy scanning code and replace it with something which does cope properly with such discrepancies. And I am very pleased with the results. The code is now clear, relatively simple, logical and reliable. The problems you are having are very very unlilely to be due to those changes.

If I knew whether FSUIPC was actually starting or not, when you get the crash, I could look at ways of trying to identify the reasons. First, though, if you can please clarify the earlier confusion (difference between an iNI file creation start and subsequent ones), and also show me your DLL.XML and EXE.XML files (so i can see which other things are happening at the same time), then I can consider what to do.

Unfortunately I am overloaded at present with preparing for the release of FSUIPC5 for P3D4, but i will do what i can.

7 hours ago, arnonmoscona said:

I wouldn't complain much if this was a free addon, but it's not. It is paid, and it is not delivering the quality one might expect from a paid product. It is chronically unstable.

If you continue in such an objectionable and unfair manner I would be loathe to help you with anything. I try my best to help everyone here and work more than full time on support and ongoing developments.  Just look at the history of FS and FSUIPC and you will see. It was free for many years until my income dried up and I was forced to either abandon FSUIPC altogether (before FS2004 release), or move it to a payware base (and then, only for user facilities, not for its prime purpose as an application interface, which is still free). 

With more users with such an attitude I'd be inclined to stop FSUIPC4 development and support now, withdraw it alogether, and also ditch FSUIPC5. FSUIPC4 has now been continuously developed and well supported for 12 years with no upgade price or subscription once initially purchased. I would seriously ask you to reconsider you attitude and treatment of folks who do their best to help, often with little or no supporting information.

Pete

Share this post


Link to post
Share on other sites
On 5/21/2017 at 10:41 PM, Thomas Richter said:

Hi,

no one reported a crash up to now with latest version (4.966n).

Try renaming your original FSUIPC4.ini file, e.g. _FSUIPC4.ini, so it will create a new one on next FS start (with FSUIPC4.966n version). Maybe something corrupt in the INI file.

If FS crashes there will be a Win crash report (Event Viewer) that would help.

Thomas

Here are my dll.xml and exe.xml.

Respectfully, you keep saying that I have a crash "because of something else". The reality is that there is no crash with version c and there is a crash with version n. The only thing that changed between the configurations is FSUIPC. So it is abundantly clear that there is something in version n that causes a crash which is not present with version c. Regardless of whether or not something else is wrong as well, there is something in this version that causes instability. FSX is never perfect. There are lots of addons and any one of them (typically more than one) has some bugs or does not "play well with others". But you simpl;y cannot lay all the blame on some unidentified other culprit. There is somethis positively different between c and n that causes n to crash the sim in this case.

dll.xml

exe.xml

Share this post


Link to post
Share on other sites
1 hour ago, arnonmoscona said:

The reality is that there is no crash with version c and there is a crash with version n.

Yes, it happens. most of those things are matters of timing -- the occurrence of one ecent juxtaposed to another. Those happen in different orders on different systems, with different add-ons and with different updates of the same programs. Additionally every change to FSUIPC creates a different memory pattern and depending what the interaction is which is the problem it may have a serious affect or no noticeable affect at all.

It is all in the nature of complex programs in ever more complex systems, and most of every developers support time is occupied by trying to reproduce these things so they can be nailed, but that turns out to be more and more difficult becase of the huge number or variables.

I have solved many problems over many years (I started programming in 1963, when things were just starting to get complicated), and very many of these were never reproducible on my development systems. To re-create what you have set up here would be well nigh impossible.  can only try to gather sufficient information to assist you in either overcoming it, or help me to work out avoidance action.

1 hour ago, arnonmoscona said:

But you simpl;y cannot lay all the blame on some unidentified other culprit. There is somethis positively different between c and n that causes n to crash the sim in this case.

A combination of the changes in 4.966n AND other things on your system. If there were a definite bug in this version which is independent on everything else in the systam I could reproduce it as could all other users.

Sorry, but honestly you don't know what you are talking about. You are assuming some moral high ground and stating your thoughts as if they were facts. It is becoming tiresome. I will try to help,but you aren't helping at all. I don't care whether you paid, you haven't got any right to treat me in such a downright disrespectful and obstinate manner.

If I can find out what is wrong I will do. But you will need to help. If you want to continue the way you are instead I will personally refund you and revoke the license.

As well as asking for the files you attached I also asked "if you can please clarify the earlier confusion (difference between an iNI file creation start and subsequent ones), ..."

Pete

 

Share this post


Link to post
Share on other sites

I've had a look at your DLL.XML and EXE.XML file. I think you need to carry out a process of elinination. To start with rename the DLL.XML, or save it elsewhere, then re-run the FSUIPC installer. Make sure 4.966c works so we know there's no registry entry stopping the DLL later. Then copy in 4.966n, and test it. Let me know the result of that. If it still crashes, then try with the EXE one renamed too, though that's more of a long shot as EXEs aren't in-process and rarely cause conflicts. 

We'll proceed from there, assuming you've decided to be cooperative.

Pete

 

Share this post


Link to post
Share on other sites

I will help as much as I can . I've done everything you asked and I have been very respectful. I am sorry that you are taking it this way, but you must understand that I do not have any magical information. If there are logs I can give them to you. If there is any configuration, I can give it to you as well. There is no "moral high ground here or anything else", and I am not sure what you are taking as " disrespectful and obstinate ". It is certainly not intended that way. There are simply facts.

 

Let me try to explain the "confusion" describing a series of steps:

  1. I get back to my stable configuration (with the c version). Everything works except the X-55 is not visible to FSUIPC
  2. Exit FSX, wait for everything to stop (i.e. AS16 indicates that FSX has exited, there is not fsx process running etc)
  3. the machine is not restarted
  4. Delete fsuipc4.dll
  5. Delete fsuipc4.ini
  6. Replace fsuipc4.dll with the n version
  7. Start FSX
  8. A new fsuipc4.ini file is created
  9. I can see the X55
  10. Exit fsx again. Wait for everything to exit
  11. delete logs etc.
  12. Start fsx again: DTD on load
    1. no new fsuipc log file was created
    2. no crasg reported on the windows system log (application)
  13. Restart the machine
  14. Try to run FSX again. same: CTD, no logs
  15. Tried again to remove fsuipc4.ini file
  16. Start FSX again: no cigar: CTD as before. No logs
  17. Replace the fsuipc4.dll with version c
  18. Try to start fsx again: same result. CTD
  19. Run the production (version c) installer again
  20. replaced fsuipc4.ini with my backup copy (that was stable before)
  21. Restart the machine
  22. Run FSX: works like a dream. No problems (except for X55 not visible to FSUIPC). But everything else stable and running.

This is as accurate as I can be...

I am attaching my fsuipc ini file as well, if that can help you with it. If there is something special about my system with respect to controls it may be the fact that I have a Brunner yoke attached to it, which certainly connects to the system in some special way. The axis mapping is somehow direct (cannot be controlled by the sim or by fsuipc), and the buttons are exposed to the sim (as fsuipc) via vjoy. I don't know whether this information helps, but not that many people have a Brunner yoke - so you may have not encountered it otherwise.

FSUIPC4.ini

Share this post


Link to post
Share on other sites
9 minutes ago, Pete Dowson said:

I've had a look at your DLL.XML and EXE.XML file. I think you need to carry out a process of elinination. To start with rename the DLL.XML, or save it elsewhere, then re-run the FSUIPC installer. Make sure 4.966c works so we know there's no registry entry stopping the DLL later. Then copy in 4.966n, and test it. Let me know the result of that. If it still crashes, then try with the EXE one renamed too, though that's more of a long shot as EXEs aren't in-process and rarely cause conflicts. 

We'll proceed from there, assuming you've decided to be cooperative.

Pete

 

Pleased clarify. Do you want me to start with dll.xml completely absent?

Share this post


Link to post
Share on other sites

Hi,

15 minutes ago, arnonmoscona said:

Pleased clarify. Do you want me to start with dll.xml completely absent?

no. Please i.e. rename the existing dll.xml to _dll.xml so it will be ignored. Then run the Installer of FSUIPC4.966c, that will create a new dll.xml file with only FSUIPC4 to load. Now run FSX and close down to make sure it runs OK. Then paste and overwrite, as before, the installed version with the latest interim FSUIPC4.966n version and run FSX to see if it runs still OK, without any other loaded add-ons from the original dll.xml.

That is just to test if the latest interim version already causes FSX to crash on its own or in combination with one of the other add-ons. If FSUIPC4 produced a log file with the latest 4.966n version on this test, please copy and paste it into your message.

Thomas

Share this post


Link to post
Share on other sites
25 minutes ago, arnonmoscona said:

Let me try to explain the "confusion" describing a series of steps:

Okay. Here:

25 minutes ago, arnonmoscona said:
  • Delete fsuipc4.dll
  • Delete fsuipc4.ini
  • Replace fsuipc4.dll with the n version
  • Start FSX
  • A new fsuipc4.ini file is created

Is these any reason you delete the INI? It would mean re-making all your settings. Also you don't need to delete FSUIPC4 when copying in the new one, just confirm to "overwrite".

If it makes a new INI it will make a new LOG file ands also a file called "FSUPC4 JoyScan.csv". Could you show me both of those please? They are most important. The latter would also show me how to tell you how to edit your INI to make 4.966c work with the X55, which you could therefore use until we sort the 4966n problem out.

25 minutes ago, arnonmoscona said:
  • Exit fsx again. Wait for everything to exit
  • delete logs etc.

Oh dear. I do wish you wouldn't delete files. Now it means doing it all again to make those LOG and CSV files. There really is no need to delete anything. It just makes things harder.

From your list of steps i would say that the previous session to the CTD one actually crashed and disappeared rather than terminated normally, though it may look like that.  I know you said there were no FSX events in the Windows Application Log in the Event Viewer, but could you please just check again immediately after it all looks to be closed correctly?

I know crashes can occur without being recorded there -- i've had them myself, many times, when developing with Beta versions of FS and P3D. But still.

Also the FSUIPC log will hopefully show whether it whought it closed cleanly.

23 minutes ago, arnonmoscona said:

Pleased clarify. Do you want me to start with dll.xml completely absen

The Installer will make a new DLL.XML with only FSUIPC4 loading. 

25 minutes ago, arnonmoscona said:
  • Replace the fsuipc4.dll with version c
  • Try to start fsx again: same result. CTD

Well there you are. Proof that it's a crash on the preceding close, not  4.966n crashing on start up at all. 4.966c does too after a previous crash on close.

There is a positive aspect to that -- it means it is far less likely to be due to initial timing conflicts with the other DLLs being loaded.

I'm likely to be avay from the PC for most of the rest of this evening. My wife tells me I shouldn't be working all my waking hours at my age (74) and Sunday afternoon and evening have traditionally been "lazing about" periods (especially on a holiday weekend). 

Pete

 

 

 

 

 

Share this post


Link to post
Share on other sites

OK. We have some progress. I did what you said and also tinkered a lot with the dll.xml file, and got some better - but not perfect results.

Here's where it is right now:

  • Found that there is one entry in dll.xml that was related to the crash on start. It is the one named
    Reality XP GNS WAAS Hardware
    If I comment it out ( <!-- ... -->) then I no longer get the CTD on start. That DLL was actually no longer in the modules directory, as I uninstalled RXP GNS when I found out it was not compatible with FSX-SE. The uninstaller did not remove the entry from dll.xml. Clearly it was no longer loading, as the DLL is no longer there, but the section in dll.xml seems to confuse things nonetheless.
  • So now I can start FSX, restart the machine in whatever sequence (with version n) without getting CTD on start. I can get into a flight, map controls etc. So far so good.
  • Now to the bad part: whenever I exit a flight (not exit FSX - but exit a flight) I get a crash (which also means that no FSX changes get saved either). This does leave a trace in the system logs.See below. Also I am showing the fsuipc4.log
  • ********* FSUIPC4, Version 4.966n (8th May 2017) by Pete Dowson *********
    Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
    fsx.exe version = 10.0.62615.0
    Reading options from "D:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini"
    Running inside FSX Steam Edition on Windows 10
    Module base=1DB50000
    User Name="Arnon Moscona"
    User Addr="arnon@moscona.com"
    FSUIPC4 Key is provided
    WIDEFS7 not user registered, or expired
            0 System time = 28/05/2017 11:37:37
            0 FLT path = "C:\Users\Arnon\Documents\Flight Simulator X Files\"
            0 ------ Module Version Check ------
            0        acontain.dll: 10.0.62615.0
            0             api.dll: 10.0.62615.0
            0        controls.dll: 10.0.62615.0
            0      fs-traffic.dll: 10.0.62615.0
            0             G3D.dll: 10.0.62615.0
            0        language.dll: 10.0.62615.0
            0            sim1.dll: 10.0.62615.0
            0        visualfx.dll: 10.0.62615.0
            0         weather.dll: 10.0.62615.0
            0          window.dll: 10.0.62615.0
            0 ----------------------------------
           15 Trying to connect to SimConnect Steam ...
           31 FS path = "D:\SteamLibrary\steamapps\common\FSX\"
           94 ---------------------- Joystick Device Scan -----------------------
          109 Product= Saitek Pro Flight Quadrant
          109    Manufacturer= Saitek
          109    Vendor=06A3, Product=0C2D (Version 2.1)
          109    GUIDs returned for product: VID_06A3&PID_0C2D:
          109       GUID= {F6B633E0-27FB-11E7-8002-444553540000}
          109       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
          109 Product= vJoy - Virtual Joystick
          109    Manufacturer= Shaul Eizikovich
          109    Serial Number= 2.0.5
          109    Vendor=1234, Product=BEAD (Version 2.5)
          109    GUIDs returned for product: VID_1234&PID_BEAD:
          109       GUID= {109593D0-2812-11E7-8002-444553540000}
          109       Details: Btns=64, POVs=(0, 18000, 27000, 9000), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
          109 Product= Saitek Pro Flight Quadrant
          125    Manufacturer= Saitek
          125    Vendor=06A3, Product=0C2D (Version 2.2)
          125 Product= Saitek Pro Flight X-55 Rhino Stick
          125    Manufacturer= Madcatz
          125    Serial Number= G0000609
          125    Vendor=0738, Product=2215 (Version 0.86)
          125    GUIDs returned for product: VID_0738&PID_2215:
          125       GUID= {299EC5D0-3D62-11E7-8006-444553540000}
          125       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0
          125       GUID= {299EC5D0-3D62-11E7-8005-444553540000}
          125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
          125 Product= <not readable at this time: maybe device disconnected?>
          125    Vendor=046D, Product=C2AB (Version 0.1)
          125    GUIDs returned for product: VID_046D&PID_C2AB:
          125       GUID= {C8E21EE0-393D-11E7-8003-444553540000}
          125       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
          125 Product= Saitek Pro Flight X-55 Rhino Throttle
          125    Manufacturer= Madcatz
          125    Serial Number= G0001570
          125    Vendor=0738, Product=A215 (Version 0.119)
          125    GUIDs returned for product: VID_0738&PID_A215:
          125       GUID= {337E3D10-3D62-11E7-8007-444553540000}
          125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
          125       GUID= {337E6420-3D62-11E7-8008-444553540000}
          125       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255
          125 Product= Logitech Dual Action
          125    Manufacturer= Logitech
          125    Serial Number= DCCA434C
          125    Vendor=046D, Product=C216 (Version 4.20)
          125    GUIDs returned for product: VID_046D&PID_C216:
          125       GUID= {D42E67D0-38D5-11E7-8007-444553540000}
          125       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X255,Y255,Z255
          125 Product= Saitek Pro Flight Combat Rudder Pedals
          125    Manufacturer= Saitek
          125    Vendor=06A3, Product=0764 (Version 2.1)
          125    GUIDs returned for product: VID_06A3&PID_0764:
          125       GUID= {9AFCE820-3942-11E7-8004-444553540000}
          125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U0,V0,X127,Y127,Z0
          125 -------------------------------------------------------------------
          140 Device acquired for use:
          140    Joystick ID = 0 (Registry okay)
          140    0=Saitek Pro Flight Quadrant
          140    0.GUID={F6B633E0-27FB-11E7-8002-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 1 (Registry okay)
          140    1=vJoy Device
          140    1.GUID={109593D0-2812-11E7-8002-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 2 (Registry okay)
          140    2=Saitek Pro Flight X-55 Rhino Stick
          140    2.GUID={299EC5D0-3D62-11E7-8006-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 4 (Registry okay)
          140    4=Logitech G13 Joystick
          140    4.GUID={C8E21EE0-393D-11E7-8003-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 8 (Registry okay)
          140    8=Saitek Pro Flight X-55 Rhino Throttle
          140    8.GUID={337E6420-3D62-11E7-8008-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 6 (Registry okay)
          140    6=Logitech Dual Action
          140    6.GUID={D42E67D0-38D5-11E7-8007-444553540000}
          140 Device acquired for use:
          140    Joystick ID = 7 (Registry okay)
          140    7=Saitek Pro Flight Combat Rudder Pedals
          140    7.GUID={9AFCE820-3942-11E7-8004-444553540000}
          140 -------------------------------------------------------------------
          156 LogOptions=00000000 00000001
          156 -------------------------------------------------------------------
          156 ------ Setting the hooks and direct calls into the simulator ------
          156 --- CONTROLS timer memory location obtained ok
          156 --- SIM1 Frictions access gained
          156 --- FS Controls Table located ok
          156 --- Installed Mouse Macro hooks ok.
          156 --- Wind smoothing fix is fully installed
          156 --- SimConnect intercept for texts and menus option is off
          156 --- All links checked okay
          156 -------------------------------------------------------------------
          156 SimConnect_Open succeeded: waiting to check version okay
          156 Trying to use SimConnect Steam
          156 Opened separate AI Traffic client okay
         1578 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
         1578 Initialising SimConnect data requests now
         1578 FSUIPC Menu entry added
         1578 c:\users\arnon\documents\flight simulator x files\KFHR runway default C172.FLT
         1578 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air
        28703 Weather Mode now = Theme
        40906 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\A2A_C182\C182.air
        40906 c:\users\arnon\documents\flight simulator x files\KSQL with A2A C182.FLT
        47656 User Aircraft ID 1 supplied, now being used
        47672 Aircraft loaded: running normally now ...
        47890 System time = 28/05/2017 11:38:25, Simulator time = 11:20:56 (18:20Z)
        47906 Aircraft="C182_N6182G"
       117531 Starting everything now ...
       117562 ASN active function link set
       117562 Ready for ASN WX radar
       118719 Advanced Weather Interface Enabled
       143031 Sim stopped: average frame rate for last 28 secs = 27.9 fps
       143031    Max AI traffic was 89 aircraft (Deleted 0)
       268812 Sim stopped: average frame rate for last 56 secs = 27.0 fps
       268812    Max AI traffic was 89 aircraft (Deleted 0)
       295469 === DLLStop called ...
       295469 === Closing external processes we started ...
       296469 === About to kill any Lua plug-ins still running ...
       296625 === Closing global Lua thread
       297625 === About to kill my timers ...
       297922 === Restoring window procs ...
       297922 === Unloading libraries ...
       297922 === stopping other threads ...
       297922 === ... Memory checking ...
       297922 === ... Button scanning ...
       298015 === ... Axis scanning ...
       298125 === Releasing joystick devices ...
       298125 ***ERROR C0000005 at 0F0A2095 DLLStop   [0x00000000, 0x00000000]
       298125 ***      Access violation trying to read address EE198B05
       298125 ***      EAX 00000000  EBX 1629589C  ECX 00000002  EDX 16295870  EDI 00550DDE  ESI EE198B05
       298125 ***      EIP 0F0A2095  EBP 0043F650  ESP 0043F620
       298125 ********** Modules List ***********
       298125 00440000-00443000 sfc.dll
       298125 00800000-00A9F000 fsx.exe
       298125 02420000-02493000 language.dll
       298125 05010000-050B9000 xuipc.dll
       298125 050C0000-05222000 d3d9.dll
       298125 090E0000-090EC000 XInput1_4.dll
       298125 09650000-0965E000 SimConnect.dll
       298125 0A400000-0B109000 nvd3dum.dll
       298125 0F080000-0F0B7000 DINPUT8.dll
       298125 0F230000-0F23D000 LINKINFO.dll
       298125 0F400000-0F4C9000 nvSCPAPI.dll
       298125 0F4D0000-0F541000 ObjectFlow.dll
       298125 0F590000-0F649000 nvldumd.dll
       298125 0F6E0000-0F81D000 steam.dll
       298125 0FAD0000-0FBF5000 gameoverlayrenderer.dll
       298125 0FC80000-0FC89000 dx10SimC.dll
       298125 0FCB0000-0FCE2000 msls31.dll
       298125 0FE60000-11296000 nvwgf2um.dll
       298125 1B4B0000-1B550000 A2A_Feel.dll
       298125 1D8F0000-1D969000 HyperGauge.dll
       298125 1D970000-1D9F3000 AS-FlightRecorder.dll
       298125 1DB50000-1E1ED000 FSUIPC4.dll
       298125 1E3C0000-1E3CE000 SimConnect.dll
       298125 1E590000-1E5FE000 as_btstrp.dll
       298125 20720000-2127B000 ieframe.dll
       298125 21280000-212F8000 DSREG.DLL
       298125 21700000-21710000 WLDP.DLL
       298125 21860000-21883000 srpapi.dll
       298125 23680000-2368E000 msimtf.dll
       298125 23690000-23B90000 d2d1.dll
       298125 23B90000-23DEB000 d3d10warp.dll
       298125 25E50000-261D5000 jscript9.dll
       298125 26BB0000-26D18000 uiautomationcore.dll
       298125 27310000-27335000 cryptnet.dll
       298125 279A0000-279DE000 UIAnimation.dll
       298125 2F3C0000-2F681000 Steam2.dll
       298125 38000000-38A9C000 steamclient.dll
       298125 3E780000-3E7D7000 vstdlib_s.dll
       298125 3EFA0000-3F0B7000 tier0_s.dll
       298125 45E50000-45ECD000 RICHED20.DLL
       298125 50B80000-50BFE000 DSOUND.dll
       298125 510C0000-510E9000 AccuFeelMenu.dll
       298125 510F0000-5117E000 XAudio2_6.dll
       298125 51180000-51DF0000 bglmanx.dll
       298125 51DF0000-51E15000 dinput.DLL
       298125 51E20000-51E27000 XInput9_1_0.dll
       298125 51E30000-51E58000 uiautomationcore.dll
       298125 51E60000-520AD000 gameux.dll
       298125 520B0000-52109000 d3d10_1core.dll
       298125 52110000-5213B000 d3d10_1.dll
       298125 52140000-52255000 D3DCompiler_34.dll
       298125 52260000-522B1000 d3d10core.dll
       298125 522C0000-523C7000 d3d10.dll
       298125 523D0000-523D6000 dx10SharedLib.dll
       298125 523E0000-52472000 dx10fixerlib.DLL
       298125 52480000-524ED000 reald3dx10_34.DLL
       298125 524F0000-52576000 sdkencryptedappticket.dll
       298125 52580000-528EF000 d3dx9_34.dll
       298125 528F0000-528F9000 d3dx10_34.dll
       298125 52900000-5292D000 window.dll
       298125 52930000-52985000 weather.dll
       298125 52990000-529C3000 visualfx.dll
       298125 529D0000-52A0D000 util.dll
       298125 52A10000-52AF4000 ui.dll
       298125 52B00000-52B16000 fs-traffic.dll
       298125 52B20000-52B50000 symmap.dll
       298125 52B50000-52C2C000 terrain.dll
       298125 52C30000-52C5F000 sound.dll
       298125 52C60000-52C8E000 simprop.dll
       298125 52C90000-52D68000 sim1.dll
       298125 52D70000-52DEF000 panels.dll
       298125 52DF0000-52E55000 multiplayer.dll
       298125 52E60000-52F32000 main.dll
       298125 52F40000-52F61000 livingwater.dll
       298125 52F70000-52F94000 gps.dll
       298125 52FA0000-530D0000 g3d.dll
       298125 530D0000-5317D000 g2d.dll
       298125 53180000-532DF000 fsui.dll
       298125 532E0000-53358000 flight.dll
       298125 53360000-53476000 fe.dll
       298125 53480000-534C3000 facilities.dll
       298125 534D0000-534E4000 demo.dll
       298125 534F0000-5352D000 controls.dll
       298125 53530000-53592000 atc.dll
       298125 535A0000-535CE000 acontain.dll
       298125 535D0000-5360F000 ai_player.dll
       298125 53610000-53663000 ablscpt.dll
       298125 53670000-537C0000 API.DLL
       298125 537C0000-537E6000 steam_api.dll
       298125 537F0000-5395A000 nvspcap.dll
       298125 539D0000-53A04000 MLANG.dll
       298125 53BF0000-53C1F000 XmlLite.dll
       298125 543C0000-54486000 ntshrui.dll
       298125 549B0000-549BC000 simscheduler.dll
       298125 549C0000-549CE000 MFC80ENU.DLL
       298125 549D0000-54ADF000 MFC80.DLL
       298125 54AE0000-54AE7000 DCIMAN32.dll
       298125 54AF0000-54BDD000 DDRAW.dll
       298125 54BE0000-54C5C000 AcSpecfc.DLL
       298125 54C60000-54CFB000 MSVCR80.dll
       298125 54E00000-54E66000 SS3DevProps.dll
       298125 57E90000-57EA7000 USP10.dll
       298125 57EB0000-57F37000 MSVCP80.dll
       298125 57FA0000-58065000 Windows.UI.dll
       298125 58070000-58147000 AUDIOSES.DLL
       298125 58150000-581AA000 MMDevApi.dll
       298125 58250000-58498000 DWrite.dll
       298125 5A390000-5A461000 wintypes.dll
       298125 5A470000-5A697000 CoreUIComponents.dll
       298125 5A6A0000-5A72F000 CoreMessaging.dll
       298125 5A730000-5A796000 msvcp110_win.dll
       298125 5AA30000-5AB66000 twinapi.appcore.dll
       298125 5AB70000-5ADC2000 d3d11.dll
       298125 5ADD0000-5AEBB000 dcomp.dll
       298125 5AEC0000-5AF03000 dataexchange.dll
       298125 5B240000-5B2C4000 mscms.dll
       298125 5E750000-5E757000 ksuser.dll
       298125 60000000-60021000 CSERHelper.dll
       298125 626B0000-63A34000 mshtml.dll
       298125 63FC0000-63FF9000 wdmaud.drv
       298125 65CC0000-65CC9000 msadp32.acm
       298125 66080000-66098000 MSACM32.dll
       298125 69B10000-69C3F000 MSXML4.DLL
       298125 6A8A0000-6A8A8000 midimap.dll
       298125 6B7C0000-6B7CA000 msacm32.drv
       298125 6C660000-6C871000 iertutil.dll
       298125 6CA90000-6CC02000 WindowsCodecs.dll
       298125 6CC30000-6CC91000 msiso.dll
       298125 6D0A0000-6D0BB000 ncryptsslp.dll
       298125 6D0C0000-6D0EC000 NTASN1.dll
       298125 6D0F0000-6D110000 ncrypt.dll
       298125 6D110000-6D120000 mskeyprotect.dll
       298125 6D120000-6D186000 schannel.dll
       298125 6D210000-6D21A000 HID.DLL
       298125 6D220000-6D3BB000 urlmon.dll
       298125 6D820000-6DA96000 AcLayers.DLL
       298125 6DAA0000-6DAB5000 ondemandconnroutehelper.dll
       298125 6DAC0000-6DACA000 Secur32.dll
       298125 6DBB0000-6DF57000 nvapi.dll
       298125 6DF60000-6DF69000 AVRT.dll
       298125 6DF70000-6DFD7000 TextInputFramework.dll
       298125 6E210000-6E2A3000 apphelp.dll
       298125 6E2F0000-6E300000 usermgrcli.dll
       298125 6E300000-6E308000 DPAPI.DLL
       298125 6E3D0000-6E45A000 dxgi.dll
       298125 6E4A0000-6E4C3000 dwmapi.dll
       298125 6EDF0000-6EDFF000 cscapi.dll
       298125 6EE50000-6EED6000 sxs.dll
       298125 6F000000-6F010000 sfc_os.DLL
       298125 6F110000-6F118000 WINNSI.DLL
       298125 6F120000-6F162000 WINSTA.dll
       298125 6F230000-6F251000 mdnsNSP.dll
       298125 712D0000-71390000 fastprox.dll
       298125 72160000-721AA000 fwpuclnt.dll
       298125 721B0000-721B8000 rasadhlp.dll
       298125 721C0000-7223F000 DNSAPI.dll
       298125 725D0000-72734000 PROPSYS.dll
       298125 727C0000-727D0000 WKSCLI.DLL
       298125 727D0000-727EC000 srvcli.dll
       298125 72820000-72888000 wbemcomn.dll
       298125 72890000-72896000 SHFOLDER.dll
       298125 728A0000-728CF000 rsaenh.dll
       298125 728D0000-728E3000 CRYPTSP.dll
       298125 72900000-72910000 wbemsvc.dll
       298125 72910000-7291D000 wbemprox.dll
       298125 72920000-72942000 DEVOBJ.dll
       298125 729A0000-729EE000 MSWSOCK.dll
       298125 729F0000-72A18000 ntmarta.dll
       298125 72D20000-72D2B000 NETUTILS.DLL
       298125 72D30000-72D55000 dbgcore.DLL
       298125 72E10000-72E88000 uxtheme.dll
       298125 72E90000-72EB2000 USERENV.dll
       298125 72EC0000-72F6D000 WINHTTP.dll
       298125 72F70000-730CD000 DbgHelp.dll
       298125 73100000-73266000 gdiplus.dll
       298125 73270000-73293000 WINMMBASE.dll
       298125 732A0000-732B6000 MPR.dll
       298125 732C0000-732D8000 bcrypt.dll
       298125 732E0000-7330F000 IPHLPAPI.DLL
       298125 73310000-736F3000 msi.dll
       298125 73700000-7378E000 COMCTL32.dll
       298125 73790000-737E6000 OLEACC.dll
       298125 737F0000-738DE000 MSVCR120.dll
       298125 738E0000-7394E000 WINSPOOL.DRV
       298125 73950000-739C1000 MSVCP120.dll
       298125 739D0000-739F4000 WINMM.dll
       298125 73A00000-73C0E000 COMCTL32.dll
       298125 73C10000-73ED1000 WININET.dll
       298125 73EE0000-73EE6000 MSIMG32.dll
       298125 73EF0000-73F03000 NETAPI32.dll
       298125 73F10000-73F1F000 WTSAPI32.dll
       298125 73F20000-73F28000 VERSION.dll
       298125 73F50000-73F5A000 CRYPTBASE.dll
       298125 73F60000-73F80000 SspiCli.dll
       298125 73F80000-73F87000 NSI.dll
       298125 73F90000-7410D000 CRYPT32.dll
       298125 74110000-74155000 powrprof.dll
       298125 74160000-742A6000 MSCTF.dll
       298125 742B0000-742F5000 shlwapi.dll
       298125 74310000-74428000 ucrtbase.dll
       298125 74430000-744C6000 OLEAUT32.dll
       298125 744D0000-7460C000 USER32.dll
       298125 74610000-74616000 PSAPI.DLL
       298125 74620000-746E0000 RPCRT4.dll
       298125 746E0000-74839000 gdi32full.dll
       298125 74840000-74A78000 combase.dll
       298125 74A80000-74A99000 imagehlp.dll
       298125 74B00000-74B25000 IMM32.dll
       298125 74B30000-74B87000 bcryptPrimitives.dll
       298125 74B90000-75ED8000 SHELL32.dll
       298125 75EE0000-75EF6000 win32u.dll
       298125 75F90000-75F9E000 kernel.appcore.dll
       298125 75FA0000-76017000 advapi32.dll
       298125 76020000-76099000 msvcp_win.dll
       298125 760A0000-76107000 WS2_32.dll
       298125 76170000-761B1000 sechost.dll
       298125 761C0000-761F9000 cfgmgr32.dll
       298125 76200000-76244000 WINTRUST.DLL
       298125 76250000-76271000 GDI32.dll
       298125 76280000-7628E000 MSASN1.dll
       298125 76290000-762A0000 profapi.dll
       298125 76300000-763F3000 ole32.dll
       298125 76400000-76984000 windows.storage.dll
       298125 76990000-76A13000 clbcatq.dll
       298125 76A20000-76AF0000 KERNEL32.DLL
       298125 76C60000-76CEC000 shcore.dll
       298125 76CF0000-76EB2000 KERNELBASE.dll
       298125 76EC0000-772DA000 SETUPAPI.dll
       298125 772E0000-7739D000 msvcrt.dll
       298125 773A0000-7748F000 COMDLG32.dll
       298125 77490000-7761E000 ntdll.dll
       298125 77890000-778F9000 MSVCP100.dll
       298125 783A0000-7845F000 MSVCR100.dll
       298125 90A10000-90AAE000 WiFiGO_HookKey.dll
       298125 ***********************************
       298125 EIP 0F0A2095 is in DINPUT8.dll, Base=0F080000
       298125 Stack EBP 0043F650->0F08842A, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F66C->0F0882EC, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F680->0F088640, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F69C->0F0884A2, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F6AC->0F088423, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F6C8->0F0882EC, which is DINPUT8.dll (Base=0F080000)
       298125 Stack EBP 0043F6DC->0043F9CC, which is  (Base=00000000)
       298125 Stack EBP 1DB76A54->FFFEFC45, which is  (BAD) (Base=00000000)
       298125 Stack EBP C710C483->00000000, which is  (BAD) (Base=00000000)
    
     
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" /> 
      <EventID Qualifiers="0">1000</EventID> 
      <Level>2</Level> 
      <Task>100</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2017-05-28T18:42:46.858311900Z" /> 
      <EventRecordID>10374</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>ORIGIN</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>fsx.exe</Data> 
      <Data>10.0.62615.0</Data> 
      <Data>559f9a9a</Data> 
      <Data>FSUIPC4.dll_unloaded</Data> 
      <Data>4.9.6.615</Data> 
      <Data>59103e64</Data> 
      <Data>c000041d</Data> 
      <Data>000c2a60</Data> 
      <Data>2774</Data> 
      <Data>01d2d7e164c9c4e1</Data> 
      <Data>D:\SteamLibrary\steamapps\common\FSX\fsx.exe</Data> 
      <Data>FSUIPC4.dll</Data> 
      <Data>cd36bdc8-15f3-4c74-a3b4-b176f56bcc3e</Data> 
      <Data /> 
      <Data /> 
      </EventData>
      </Event>

     

2017-05-28_11-52-33.png

Share this post


Link to post
Share on other sites

Just to be as minimal as I can, here's a log listing with the crash. The sequence of operations was:

  1. start FSX
  2. Load a flight (just parked cold and dark)
  3. Try to exit FSX (this tyime via the menu Flights/exit (equivalent to Ctrl-C)

The wait mouse cursor shows up, the shutdown sequence starts, and eventually it crashes. This did not happen with version C. The most directly relevant lines of the log seem to be:

 

 115094 === Closing session: waiting for DLLStop to be called ...
   142297 === DLLStop called ...
   142297 === Closing external processes we started ...
   143297 === About to kill any Lua plug-ins still running ...
   143453 === Closing global Lua thread
   144453 === About to kill my timers ...
   144656 === Restoring window procs ...
   144656 === Unloading libraries ...
   144656 === stopping other threads ...
   144656 === ... Memory checking ...
   144656 === ... Button scanning ...
   144750 === ... Axis scanning ...
   144844 === Releasing joystick devices ...
   144844 ***ERROR C0000005 at 0F0A21DB DLLStop   [0x00000000, 0x00000000]
   144844 ***      Access violation trying to write address 00620075
   144844 ***      EAX 00620069  EBX 000606EC  ECX 000606EC  EDX 93BFCFE0  EDI 00000006  ESI 93BFCFE0
   144844 ***      EIP 0F0A21DB  EBP 004EF3BC  ESP 004EF3BC
   144860 ********** Modules List ***********

 

the entire log follows:

********* FSUIPC4, Version 4.966n (8th May 2017) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
fsx.exe version = 10.0.62615.0
Reading options from "D:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 10
Module base=21550000
User Name="Arnon Moscona"
User Addr="arnon@moscona.com"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 28/05/2017 11:58:12
        0 FLT path = "C:\Users\Arnon\Documents\Flight Simulator X Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.62615.0
        0             api.dll: 10.0.62615.0
        0        controls.dll: 10.0.62615.0
        0      fs-traffic.dll: 10.0.62615.0
        0             G3D.dll: 10.0.62615.0
        0        language.dll: 10.0.62615.0
        0            sim1.dll: 10.0.62615.0
        0        visualfx.dll: 10.0.62615.0
        0         weather.dll: 10.0.62615.0
        0          window.dll: 10.0.62615.0
        0 ----------------------------------
       16 Trying to connect to SimConnect Steam ...
       31 FS path = "D:\SteamLibrary\steamapps\common\FSX\"
       94 ---------------------- Joystick Device Scan -----------------------
       94 Product= Saitek Pro Flight Quadrant
       94    Manufacturer= Saitek
       94    Vendor=06A3, Product=0C2D (Version 2.1)
      110    GUIDs returned for product: VID_06A3&PID_0C2D:
      110       GUID= {F6B633E0-27FB-11E7-8002-444553540000}
      110       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      110 Product= vJoy - Virtual Joystick
      110    Manufacturer= Shaul Eizikovich
      110    Serial Number= 2.0.5
      110    Vendor=1234, Product=BEAD (Version 2.5)
      110    GUIDs returned for product: VID_1234&PID_BEAD:
      110       GUID= {109593D0-2812-11E7-8002-444553540000}
      110       Details: Btns=64, POVs=(0, 18000, 27000, 9000), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      110 Product= Saitek Pro Flight Quadrant
      110    Manufacturer= Saitek
      110    Vendor=06A3, Product=0C2D (Version 2.2)
      110 Product= Saitek Pro Flight X-55 Rhino Stick
      110    Manufacturer= Madcatz
      110    Serial Number= G0000609
      110    Vendor=0738, Product=2215 (Version 0.86)
      110    GUIDs returned for product: VID_0738&PID_2215:
      110       GUID= {299EC5D0-3D62-11E7-8006-444553540000}
      110       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0
      110       GUID= {299EC5D0-3D62-11E7-8005-444553540000}
      110       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      110 Product= <not readable at this time: maybe device disconnected?>
      110    Vendor=046D, Product=C2AB (Version 0.1)
      110    GUIDs returned for product: VID_046D&PID_C2AB:
      110       GUID= {C8E21EE0-393D-11E7-8003-444553540000}
      110       Details: Btns=1, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z0
      110 Product= Saitek Pro Flight X-55 Rhino Throttle
      110    Manufacturer= Madcatz
      110    Serial Number= G0001570
      110    Vendor=0738, Product=A215 (Version 0.119)
      110    GUIDs returned for product: VID_0738&PID_A215:
      110       GUID= {337E3D10-3D62-11E7-8007-444553540000}
      110       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      110       GUID= {337E6420-3D62-11E7-8008-444553540000}
      110       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255
      110 Product= Logitech Dual Action
      125    Manufacturer= Logitech
      125    Serial Number= DCCA434C
      125    Vendor=046D, Product=C216 (Version 4.20)
      125    GUIDs returned for product: VID_046D&PID_C216:
      125       GUID= {D42E67D0-38D5-11E7-8007-444553540000}
      125       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X255,Y255,Z255
      125 Product= Saitek Pro Flight Combat Rudder Pedals
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0764 (Version 2.1)
      125    GUIDs returned for product: VID_06A3&PID_0764:
      125       GUID= {9AFCE820-3942-11E7-8004-444553540000}
      125       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U0,V0,X127,Y127,Z0
      125 -------------------------------------------------------------------
      125 Device acquired for use:
      125    Joystick ID = 0 (Registry okay)
      125    0=Saitek Pro Flight Quadrant
      125    0.GUID={F6B633E0-27FB-11E7-8002-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 1 (Registry okay)
      125    1=vJoy Device
      125    1.GUID={109593D0-2812-11E7-8002-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 2 (Registry okay)
      125    2=Saitek Pro Flight X-55 Rhino Stick
      125    2.GUID={299EC5D0-3D62-11E7-8006-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 4 (Registry okay)
      125    4=Logitech G13 Joystick
      125    4.GUID={C8E21EE0-393D-11E7-8003-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 8 (Registry okay)
      125    8=Saitek Pro Flight X-55 Rhino Throttle
      125    8.GUID={337E6420-3D62-11E7-8008-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 6 (Registry okay)
      125    6=Logitech Dual Action
      125    6.GUID={D42E67D0-38D5-11E7-8007-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 7 (Registry okay)
      125    7=Saitek Pro Flight Combat Rudder Pedals
      125    7.GUID={9AFCE820-3942-11E7-8004-444553540000}
      125 -------------------------------------------------------------------
      141 LogOptions=00000000 00000001
      141 -------------------------------------------------------------------
      141 ------ Setting the hooks and direct calls into the simulator ------
      141 --- CONTROLS timer memory location obtained ok
      141 --- SIM1 Frictions access gained
      141 --- FS Controls Table located ok
      141 --- Installed Mouse Macro hooks ok.
      141 --- Wind smoothing fix is fully installed
      141 --- SimConnect intercept for texts and menus option is off
      141 --- All links checked okay
      141 -------------------------------------------------------------------
      141 SimConnect_Open succeeded: waiting to check version okay
      141 Trying to use SimConnect Steam
      141 Opened separate AI Traffic client okay
     1078 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     1078 Initialising SimConnect data requests now
     1078 FSUIPC Menu entry added
     1078 c:\users\arnon\documents\flight simulator x files\KFHR runway default C172.FLT
     1078 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\C172\Cessna172SP.air
     7281 Weather Mode now = Theme
    26172 D:\SteamLibrary\steamapps\common\FSX\SimObjects\Airplanes\A2A_C182\C182.air
    26172 c:\users\arnon\documents\flight simulator x files\KSQL with A2A C182.FLT
    32719 User Aircraft ID 1 supplied, now being used
    32735 Aircraft loaded: running normally now ...
    32891 System time = 28/05/2017 11:58:45, Simulator time = 11:20:56 (18:20Z)
    32891 Aircraft="C182_N6182G"
   100500 Starting everything now ...
   100500 ASN active function link set
   100500 Ready for ASN WX radar
   101672 Advanced Weather Interface Enabled
   115094 === Closing session: waiting for DLLStop to be called ...
   142297 === DLLStop called ...
   142297 === Closing external processes we started ...
   143297 === About to kill any Lua plug-ins still running ...
   143453 === Closing global Lua thread
   144453 === About to kill my timers ...
   144656 === Restoring window procs ...
   144656 === Unloading libraries ...
   144656 === stopping other threads ...
   144656 === ... Memory checking ...
   144656 === ... Button scanning ...
   144750 === ... Axis scanning ...
   144844 === Releasing joystick devices ...
   144844 ***ERROR C0000005 at 0F0A21DB DLLStop   [0x00000000, 0x00000000]
   144844 ***      Access violation trying to write address 00620075
   144844 ***      EAX 00620069  EBX 000606EC  ECX 000606EC  EDX 93BFCFE0  EDI 00000006  ESI 93BFCFE0
   144844 ***      EIP 0F0A21DB  EBP 004EF3BC  ESP 004EF3BC
   144860 ********** Modules List ***********
   144860 00080000-000ED000 reald3dx10_34.DLL
   144860 001D0000-0025E000 XAudio2_6.dll
   144860 00400000-0040E000 SimConnect.dll
   144860 005F0000-005F3000 sfc.dll
   144860 00800000-00A9F000 fsx.exe
   144860 02790000-02803000 language.dll
   144860 06250000-063AF000 fsui.dll
   144860 063C0000-06469000 xuipc.dll
   144860 06470000-064A0000 symmap.dll
   144860 064B0000-06594000 ui.dll
   144860 065C0000-06722000 d3d9.dll
   144860 06730000-06A9F000 d3dx9_34.dll
   144860 090E0000-090EC000 XInput1_4.dll
   144860 09F60000-09F6D000 LINKINFO.dll
   144860 0B020000-0B0D9000 nvldumd.dll
   144860 0B2B0000-0B3C5000 D3DCompiler_34.dll
   144860 0BA40000-0C749000 nvd3dum.dll
   144860 0CC50000-0CC7B000 d3d10_1.dll
   144860 0CD80000-0CE49000 nvSCPAPI.dll
   144860 0CF90000-0CFB8000 uiautomationcore.dll
   144860 0DA10000-0DC5D000 gameux.dll
   144860 0F080000-0F0B7000 DINPUT8.dll
   144860 0F200000-0F307000 d3d10.dll
   144860 0F370000-0F402000 dx10fixerlib.DLL
   144860 0F510000-0F517000 XInput9_1_0.dll
   144860 0F520000-0F549000 AccuFeelMenu.dll
   144860 0F550000-0F5A1000 d3d10core.dll
   144860 0F640000-0F699000 d3d10_1core.dll
   144860 0F6E0000-0F81D000 steam.dll
   144860 0F930000-0F936000 dx10SharedLib.dll
   144860 0FAC0000-0FAC9000 dx10SimC.dll
   144860 0FAD0000-0FBF5000 gameoverlayrenderer.dll
   144860 0FC20000-0FC29000 d3dx10_34.dll
   144860 0FCB0000-0FCE2000 msls31.dll
   144860 0FD50000-0FDD6000 sdkencryptedappticket.dll
   144860 0FDE0000-0FE51000 ObjectFlow.dll
   144860 0FE60000-11296000 nvwgf2um.dll
   144860 18270000-18EE0000 bglmanx.dll
   144860 18FE0000-19080000 A2A_Feel.dll
   144860 1ABB0000-1AC29000 HyperGauge.dll
   144860 1EDB0000-1EE33000 AS-FlightRecorder.dll
   144860 1F130000-1F13E000 SimConnect.dll
   144860 1F1F0000-1F25E000 as_btstrp.dll
   144860 1F300000-1F33D000 controls.dll
   144860 1F390000-1F3CF000 ai_player.dll
   144860 1F520000-1F636000 fe.dll
   144860 1F6C0000-1F713000 ablscpt.dll
   144860 1F740000-1F750000 WLDP.DLL
   144860 1F750000-1F7B2000 atc.dll
   144860 1F8F0000-1F904000 demo.dll
   144860 1F910000-1F988000 DSREG.DLL
   144860 1F990000-1FAE0000 API.DLL
   144860 1FB30000-1FBA8000 flight.dll
   144860 1FC70000-1FD1D000 g2d.dll
   144860 1FDB0000-1FE15000 multiplayer.dll
   144860 1FED0000-1FEE6000 fs-traffic.dll
   144860 1FF30000-1FF5E000 acontain.dll
   144860 20030000-20053000 srpapi.dll
   144860 20060000-2009D000 util.dll
   144860 20130000-20173000 facilities.dll
   144860 20290000-202B1000 livingwater.dll
   144860 20340000-2034C000 simscheduler.dll
   144860 20370000-203A3000 visualfx.dll
   144860 203E0000-2040E000 simprop.dll
   144860 20410000-20540000 g3d.dll
   144860 20570000-20594000 gps.dll
   144860 20610000-206EC000 terrain.dll
   144860 20760000-20832000 main.dll
   144860 208E0000-209B8000 sim1.dll
   144860 209F0000-20A6F000 panels.dll
   144860 20A90000-20ABF000 sound.dll
   144860 20AD0000-20AFD000 window.dll
   144860 20C20000-20C75000 weather.dll
   144860 21550000-21BED000 FSUIPC4.dll
   144860 237A0000-242FB000 ieframe.dll
   144860 247A0000-247AE000 msimtf.dll
   144860 24DE0000-25165000 jscript9.dll
   144860 25C70000-25DD8000 uiautomationcore.dll
   144860 26A10000-26F10000 d2d1.dll
   144860 26F10000-2716B000 d3d10warp.dll
   144860 293F0000-29415000 cryptnet.dll
   144860 29A80000-29ABE000 UIAnimation.dll
   144860 2F3C0000-2F681000 Steam2.dll
   144860 38000000-38A9C000 steamclient.dll
   144860 3B0A0000-3B0C6000 steam_api.dll
   144860 3E780000-3E7D7000 vstdlib_s.dll
   144860 3EFA0000-3F0B7000 tier0_s.dll
   144860 45E50000-45ECD000 RICHED20.DLL
   144860 50420000-5050D000 DDRAW.dll
   144860 50B80000-50BFE000 DSOUND.dll
   144860 50CC0000-50CC7000 DCIMAN32.dll
   144860 537F0000-5395A000 nvspcap.dll
   144860 539D0000-53A04000 MLANG.dll
   144860 53BF0000-53C1F000 XmlLite.dll
   144860 54C60000-54CFB000 MSVCR80.dll
   144860 54D00000-54DC6000 ntshrui.dll
   144860 54E00000-54E66000 SS3DevProps.dll
   144860 57E90000-57EA7000 USP10.dll
   144860 57EB0000-57F37000 MSVCP80.dll
   144860 57FA0000-58065000 Windows.UI.dll
   144860 58070000-58147000 AUDIOSES.DLL
   144860 58150000-581AA000 MMDevApi.dll
   144860 58250000-58498000 DWrite.dll
   144860 5A390000-5A461000 wintypes.dll
   144860 5A470000-5A697000 CoreUIComponents.dll
   144860 5A6A0000-5A72F000 CoreMessaging.dll
   144860 5A730000-5A796000 msvcp110_win.dll
   144860 5AA30000-5AB66000 twinapi.appcore.dll
   144860 5AB70000-5ADC2000 d3d11.dll
   144860 5ADD0000-5AEBB000 dcomp.dll
   144860 5AEC0000-5AF03000 dataexchange.dll
   144860 5B240000-5B2C4000 mscms.dll
   144860 5C840000-5C84E000 MFC80ENU.DLL
   144860 5E750000-5E757000 ksuser.dll
   144860 5EAF0000-5EB15000 dinput.DLL
   144860 60000000-60021000 CSERHelper.dll
   144860 626B0000-63A34000 mshtml.dll
   144860 63FC0000-63FF9000 wdmaud.drv
   144860 66080000-66098000 MSACM32.dll
   144860 664D0000-664D9000 msadp32.acm
   144860 69B10000-69C3F000 MSXML4.DLL
   144860 6A8A0000-6A8A8000 midimap.dll
   144860 6B7C0000-6B7CA000 msacm32.drv
   144860 6C660000-6C871000 iertutil.dll
   144860 6CA90000-6CC02000 WindowsCodecs.dll
   144860 6CC30000-6CC91000 msiso.dll
   144860 6D0A0000-6D0BB000 ncryptsslp.dll
   144860 6D0C0000-6D0EC000 NTASN1.dll
   144860 6D0F0000-6D110000 ncrypt.dll
   144860 6D110000-6D120000 mskeyprotect.dll
   144860 6D120000-6D186000 schannel.dll
   144860 6D210000-6D21A000 HID.DLL
   144860 6D220000-6D3BB000 urlmon.dll
   144860 6D820000-6DA96000 AcLayers.DLL
   144860 6DAA0000-6DAB5000 ondemandconnroutehelper.dll
   144860 6DAC0000-6DACA000 Secur32.dll
   144860 6DBB0000-6DF57000 nvapi.dll
   144860 6DF60000-6DF69000 AVRT.dll
   144860 6DF70000-6DFD7000 TextInputFramework.dll
   144860 6E210000-6E2A3000 apphelp.dll
   144860 6E2F0000-6E300000 usermgrcli.dll
   144860 6E300000-6E308000 DPAPI.DLL
   144860 6E3D0000-6E45A000 dxgi.dll
   144860 6E4A0000-6E4C3000 dwmapi.dll
   144860 6EDF0000-6EDFF000 cscapi.dll
   144860 6EE50000-6EED6000 sxs.dll
   144860 6F000000-6F010000 sfc_os.DLL
   144860 6F110000-6F118000 WINNSI.DLL
   144860 6F120000-6F162000 WINSTA.dll
   144860 6F230000-6F251000 mdnsNSP.dll
   144860 712D0000-71390000 fastprox.dll
   144860 72160000-721AA000 fwpuclnt.dll
   144860 721B0000-721B8000 rasadhlp.dll
   144860 721C0000-7223F000 DNSAPI.dll
   144860 725D0000-72734000 PROPSYS.dll
   144860 727C0000-727D0000 WKSCLI.DLL
   144860 727D0000-727EC000 srvcli.dll
   144860 72820000-72888000 wbemcomn.dll
   144860 72890000-72896000 SHFOLDER.dll
   144860 728A0000-728CF000 rsaenh.dll
   144860 728D0000-728E3000 CRYPTSP.dll
   144860 72900000-72910000 wbemsvc.dll
   144860 72910000-7291D000 wbemprox.dll
   144860 72920000-72942000 DEVOBJ.dll
   144860 729A0000-729EE000 MSWSOCK.dll
   144860 729F0000-72A18000 ntmarta.dll
   144860 72D20000-72D2B000 NETUTILS.DLL
   144860 72D30000-72D55000 dbgcore.DLL
   144860 72E10000-72E88000 uxtheme.dll
   144860 72E90000-72EB2000 USERENV.dll
   144860 72EC0000-72F6D000 WINHTTP.dll
   144860 72F70000-730CD000 DbgHelp.dll
   144860 73100000-73266000 gdiplus.dll
   144860 73270000-73293000 WINMMBASE.dll
   144860 732A0000-732B6000 MPR.dll
   144860 732C0000-732D8000 bcrypt.dll
   144860 732E0000-7330F000 IPHLPAPI.DLL
   144860 73310000-736F3000 msi.dll
   144860 73700000-7378E000 COMCTL32.dll
   144860 73790000-737E6000 OLEACC.dll
   144860 737F0000-738DE000 MSVCR120.dll
   144860 738E0000-7394E000 WINSPOOL.DRV
   144860 73950000-739C1000 MSVCP120.dll
   144860 739D0000-739F4000 WINMM.dll
   144860 73A00000-73C0E000 COMCTL32.dll
   144860 73C10000-73ED1000 WININET.dll
   144860 73EE0000-73EE6000 MSIMG32.dll
   144860 73EF0000-73F03000 NETAPI32.dll
   144860 73F10000-73F1F000 WTSAPI32.dll
   144860 73F20000-73F28000 VERSION.dll
   144860 73F50000-73F5A000 CRYPTBASE.dll
   144860 73F60000-73F80000 SspiCli.dll
   144860 73F80000-73F87000 NSI.dll
   144860 73F90000-7410D000 CRYPT32.dll
   144860 74110000-74155000 powrprof.dll
   144860 74160000-742A6000 MSCTF.dll
   144860 742B0000-742F5000 shlwapi.dll
   144860 74310000-74428000 ucrtbase.dll
   144860 74430000-744C6000 OLEAUT32.dll
   144860 744D0000-7460C000 USER32.dll
   144860 74610000-74616000 PSAPI.DLL
   144860 74620000-746E0000 RPCRT4.dll
   144860 746E0000-74839000 gdi32full.dll
   144860 74840000-74A78000 combase.dll
   144860 74A80000-74A99000 imagehlp.dll
   144860 74B00000-74B25000 IMM32.dll
   144860 74B30000-74B87000 bcryptPrimitives.dll
   144860 74B90000-75ED8000 SHELL32.dll
   144860 75EE0000-75EF6000 win32u.dll
   144860 75F90000-75F9E000 kernel.appcore.dll
   144860 75FA0000-76017000 advapi32.dll
   144860 76020000-76099000 msvcp_win.dll
   144860 760A0000-76107000 WS2_32.dll
   144860 76170000-761B1000 sechost.dll
   144860 761C0000-761F9000 cfgmgr32.dll
   144860 76200000-76244000 WINTRUST.DLL
   144860 76250000-76271000 GDI32.dll
   144860 76280000-7628E000 MSASN1.dll
   144860 76290000-762A0000 profapi.dll
   144860 76300000-763F3000 ole32.dll
   144860 76400000-76984000 windows.storage.dll
   144860 76990000-76A13000 clbcatq.dll
   144860 76A20000-76AF0000 KERNEL32.DLL
   144860 76C60000-76CEC000 shcore.dll
   144860 76CF0000-76EB2000 KERNELBASE.dll
   144860 76EC0000-772DA000 SETUPAPI.dll
   144860 772E0000-7739D000 msvcrt.dll
   144860 773A0000-7748F000 COMDLG32.dll
   144860 77490000-7761E000 ntdll.dll
   144860 77640000-7774F000 MFC80.DLL
   144860 77890000-778F9000 MSVCP100.dll
   144860 783A0000-7845F000 MSVCR100.dll
   144860 79370000-793EC000 AcSpecfc.DLL
   144860 ***********************************
   144860 EIP 0F0A21DB is in DINPUT8.dll, Base=0F080000
   144860 Stack EBP 004EF3BC->0F0A212A, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF3D8->0F0A1D6A, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF408->0F08842A, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF424->0F0882EC, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF438->0F088640, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF454->0F0884A2, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF464->0F088423, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF480->0F0882EC, which is DINPUT8.dll (Base=0F080000)
   144860 Stack EBP 004EF494->004EF784, which is  (Base=00000000)
   144860 Stack EBP 21576A54->FFFEFC45, which is  (BAD) (Base=00000000)
   144860 Stack EBP C710C483->00FFFF00, which is  (BAD) (Base=00000000)

 

Share this post


Link to post
Share on other sites
17 minutes ago, arnonmoscona said:

Found that there is one entry in dll.xml that was related to the crash on start. It is the one named


Reality XP GNS WAAS Hardware

If I comment it out ( <!-- ... -->) then I no longer get the CTD on start.

That was one of the few I didn't know. 

19 minutes ago, arnonmoscona said:

Also I am showing the fsuipc4.log

10 minutes ago, arnonmoscona said:

144844 === Releasing joystick devices ...
144844 ***ERROR C0000005 at 0F0A21DB DLLStop [0x00000000, 0x00000000] 144844 *** Access violation trying to write address 00620075

Ah. That's a crash associated with a joystick device driver. Interesting. 

The location is in DirectInput:

13 minutes ago, arnonmoscona said:

144860 0F080000-0F0B7000 DINPUT8.dll

REgarding this:

27 minutes ago, arnonmoscona said:

Now to the bad part: whenever I exit a flight (not exit FSX - but exit a flight) I get a crash

Is there a log or Event information for this? the logs you show are all on exiting FSX or loading it. I don't see any reason for exiting a flight having anything to do with any of this.

The Windows Event you depict is in fact the one which the Loader's patch to the Registry fixes. It is "FSUIPC4_Unloaded" which means SimConnect tried to call FSUIPC4 but it hadn't been loaded, so causing the crash at the intended entry point (the address confirms this). SimConnect is buggy in that it loads modules then assumes they've loaded. very bad programming practice. it should give an error message instead.

In order to identify which joystick driver it is I shall look a loogging the separate Joystick Device closing actions. but that will be tomorrow now. Sorry.

Where's the csv file I asked for?

Pete

 

Share this post


Link to post
Share on other sites

Another point to note is that switching flights does matter. Tried the following:

  1. start FSX
  2. load a flight
  3. after loading the flight - used the flights/load to load the same flight again.
    1. Result: crash
    2. See fsuipc4.log with manually added comments around the flight loading events

 

From the system event log:

 

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.6.615, time stamp: 0x59103e64

Exception code: 0xc000041d
Fault offset: 0x000c2a60
Faulting process id: 0x2b84
Faulting application start time: 0x01d2d7ececf58ef3
Faulting application path: D:\SteamLibrary\steamapps\common\FSX\fsx.exe
Faulting module path: FSUIPC4.dll
Report Id: f67ae05f-27a1-4089-b2fe-33aa2b57a1f2
Faulting package full name:
Faulting package-relative application ID:

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-05-28T20:02:30.409236200Z" /> 
  <EventRecordID>10530</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>ORIGIN</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>fsx.exe</Data> 
  <Data>10.0.62615.0</Data> 
  <Data>559f9a9a</Data> 
  <Data>FSUIPC4.dll_unloaded</Data> 
  <Data>4.9.6.615</Data> 
  <Data>59103e64</Data> 
  <Data>c000041d</Data> 
  <Data>000c2a60</Data> 
  <Data>2b84</Data> 
  <Data>01d2d7ececf58ef3</Data> 
  <Data>D:\SteamLibrary\steamapps\common\FSX\fsx.exe</Data> 
  <Data>FSUIPC4.dll</Data> 
  <Data>f67ae05f-27a1-4089-b2fe-33aa2b57a1f2</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

 

FSUIPC4.log

Share this post


Link to post
Share on other sites

And now it started to crash on load again :-(

Went back to version c - does not crash on load, but continues to crash on getting out of a flight situation (eithe pressing "esc" or Ctrl-c - either way it now crashes consistently.

So no more stable config. And the only things being changed is around FSUIPC. Very frustrated. Now the sim is next to useless.

 

Share this post


Link to post
Share on other sites
3 hours ago, arnonmoscona said:

Oh. Here it is

FSUIPC4.JoyScan.csv

Okay. That shows the X55 stick as having tat GUID with both 8005 and 8006 (with 8006 being correct) and the Throttle as having both 8007 and 8008 with 8008 being correct. If you look back a few messages you will see how to use that information to make 4.966c work fine.

Not that i want you to abandon 4.966n because I'd like to get to the bottom of the problems. however, as I said, I very busy just now and may not give it sufficient attention for a few days. Meanwhile you can still fly ...

3 hours ago, arnonmoscona said:

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.6.615, time stamp: 0x59103e64

Exception code: 0xc000041d
Fault offset: 0x000c2a60

Okay. That's very useful, thanks. I'll take a look at that in the morning. 

In the log you added annotation

=====>>>>> now the system shows the "application stopped working" dialog and clicked "close application"

So, the "application stopped working" occurred BEFORE FSUIPC somehow closed down normally and THEN got the crash in one of the joystick drivers?

2 hours ago, arnonmoscona said:

Went back to version c - does not crash on load, but continues to crash on getting out of a flight situation (eithe pressing "esc" or Ctrl-c - either way it now crashes consistently.

And crash details or log from that?

There seems to be a common cause. Maybe you were just lucky before with 4.966c. 

It is starting to sound more and more like a corruption in the system somewhere, probably in one of the joystick device drivers. There's no way a freshly installed copy of FSUIPC is going to be different from the previously freshly installed copy. 

I'll try to do a quick logging addition tomorrow to see if I can identify the joystick which is causing the crash on termination, the one FSUIPC logs, and I'll also check that Windows crash report location.

Meanwhile you might like to try removing one device at a time from your system. Just unplug one at a time to check. FSUIPC will only deal with connected devices. If you locate it, use the Windows device manager to uninstall it fully, including drivers, then re-boot with it plugged in again, in the same place, so that Windows will reinstall it automatically, hopefully with uncorrupted drivers.

You're not using Saitek software with them too, are you? If so you might want to reinstall that, or just stop using it.

Pete

 

Share this post


Link to post
Share on other sites

Following on from above, I had a quick look, and most of the code i needed to identify exactly which joystick was causing the problem 9by ID in your INI) was already there, but disabled. I've re-nbaled it and adjusted it a little. Download this and try in -- change flights or just close down so the same datea as before gets logged, only this time there's a little more.

FSUIPC4966p_TEST.zip

I'm off to bed now, exhausested!

Pete

 

Share this post


Link to post
Share on other sites

Thanks I will try this. Before downloading, I can tell you that it still fails when exiting a flight even with all gaming devices disconnected> I'll download it, reconnect the dcevices and send you results.

Share this post


Link to post
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...

×
×
  • 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.