Crash Loading P3Dvhttp://forum.simflight.com/topic/82599-crash-loading-p3dv34-reporte-fsuipc4dll/3.4 reporte FSUIPC4.dll

[Pete Dowson]

On 12/24/2016 at 0:26 PM, wlix261 said:

I am having crash when trying to load P3Dv3.4, and I get a windows crash report that lists the fault module name as FSUIPC4.dll.
...
Sig[7].Name=Exception Offset
Sig[7].Value=0001f044

Offset 1F044 happens to be the address of the function called initially by SimConnect just after it loads FSUIPC4, so FSUIPC hasn't even started. In fact, if it is crashing there, it means that the loading of the DLL failed to happen, yet SimConnect is still trying to call the function where it would have been!

This points to a problem in SimConnect or the DLL.XML file(s). Unless I can reproduce it here I can't really help further on that crash. Others here seem to be getting a hang instead, but I guess that might depend upon what rubbish was present to that address when execution is attempted, so maybe it's the same thing ...

Hoping to be able to reproduce it, somehow ...

[LATER]

I'm wondering if something has been changed in SimConnect that somehow stops the auto-decompression of FSUIPC after Windows loads it. Maybe one or two volunteers here would test and uncompressed copy of the DLL for me, just to check this. Send me an email -- petedowson@btconnect.com. I don't want it to be made available generally for security reasons, but if this is the problem I'll need to look for a solution or ask L-M what's changed to do this.

Pete

 

 

[quasar07]

Good afternoon Peter, it happens to me only in the first load of the day, it takes about 6 minutes to boot, the home screen, once loaded, all other loads do well, until the next day when it happens again the same.
If the first load does not start AS16, sometimes it starts fast, and then the others no longer matter because it does them well. It is only the first time after being turned off.
A greeting.

[B773ER]

Pete,  I can test it for you but won't be until Saturday afternoon, probably around 1900Z. Hopefully someone else will be along to test before then.  If not I will email you if you'd like? 

[Pete Dowson]

16 minutes ago, quasar07 said:

it happens to me only in the first load of the day, it takes about 6 minutes to boot, the home screen, once loaded, all other loads do well, until the next day when it happens again the same.
If the first load does not start AS16, sometimes it starts fast, and then the others no longer matter because it does them well. It is only the first time after being turned off.

Hmm. Another variation -- perhaps the opposite of most of the others. Curiouser and curiouser ...

Has anyone here asked L-M to check this at all? If not I might have to, because it must be something they've changed.

Pete

 

[Pete Dowson]

10 minutes ago, B773ER said:

If not I will email you if you'd like? 

I'll need to get it tested before then. don't worry.

Pete

 

[Pete Dowson]

Okay. The first test result with FSUIPC uncompressed got exactly the same problem. FSUIPC is simply not getting loaded, and it is never actually run. SimConnect crashes by calling it when it isn't there!

It's looking like time to call in L-M support on this.

Unfortunately I cannot repro it here at all, so can you guys please report the problems and what I've said about it. I'll look for the new thread there and add to it if needed.

Pete

 

[quasar07]

I made a video so you see the first load and the next two, this accelerated X5 but you can see the system clock,
Greetings.

 

Edited January 6, 2017 by quasar07
video borrado

[Pete Dowson]

Just now, quasar07 said:

I made a video so you see the first load and the next two, this accelerated X5 but you can see the system clock

Sorry, I don't see the point of a video. Are you assuming I don't believe you? I prefer proper descriptions and readable data.

Pete

 

[quasar07]

No, not much Peter, but you know the saying ... more worth a picture than a thousand words and more with my English, translated.
Sorry

[Pete Dowson]

Are you all using LINDA? There have been reports of problems with LINDA, reported elsewhere. There's a workaround I think..... I'll see if I can find the details..

[LATER]

Ah, no. It was different -- to do with closing problem (http://forum.simflight.com/topic/82312-timeforluaclosing/#comment-496245)

Pete

 

[quasar07]

Yes, I'm using Linda, Peter.
Thank you.

[Pete Dowson]

Just now, quasar07 said:

Yes, I'm using Linda

Does it still fail if you stop LINDA loading?

Pete

 

[Pete Dowson]

Can you all check that you don't also have FSUIPC4 being loaded by the DLL.XML in the ProgramData folder! This has been reported once already, and removing it has fixed it --- so far.

If so we need to identify what it putting it there, as FSUIPC's installer certainly doesn't!

Pete

 

[quasar07]

Okay, Peter, I've disabled Linda and normal load, first time I start the computer.
Thank you very much.

[von]

Just for Info:
5/Jan/2017 13:15
All ok here with FSUIPC 4.959 / Win7-64 / P3D 3.4.18.19.475

**
FSUIPC loaded near / first (top/ I always move it/put it there) in DLL.xml:
C:\Users\Vaughan\AppData\Roaming\Lockheed Martin\Prepar3D v3

example:
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>dll.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
        <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.18.19475\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>PMDG HUD interface</Name>
        <Disabled>False</Disabled>
        <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>

**
FSUIPC not present:
C:\ProgramData\Lockheed Martin\Prepar3D v3

**

I do not use Linda

 

[Pete Dowson]

Quote

FSUIPC loaded near / first (top/ I always move it/put it there) in DLL.xml

Very odd. It usually gives more problems with interaction with other modules when it is loaded early. Is the only thing after it the PMDG HUD? Not sure if your ".." means you omitted other entries.

Pete

 

[von]

28 minutes ago, Pete Dowson said:

Very odd. It usually gives more problems with interaction with other modules when it is loaded early. Is the only thing after it the PMDG HUD? Not sure if your ".." means you omitted other entries.

Pete

 

It was just example to show top portion.

With every software install or update I check the exe and dll xml.
I move FSUIPC back to the top protion above my addon aircraft e.g.,.. for years now FSX and P3D.
Years ago I had a problem with it at or near the bottom ... never (so far) have I had any problems with it higher up.

Here are mine files for FSX and P3D today
*****************************************

FSX
***

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>ObjectFlow.dll</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>AFXModule</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>F:\AFX-v108\AFXModuleFSX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Object Placement Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Visual Effects Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>VRS_TacPack</Name>
    <Disabled>False</Disabled>
    <ManualLoad>True</ManualLoad>
    <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Flight Recorder</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Flight1SoundStream</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Flight One Software\Flight1 SoundStream\Flight1SoundStreamFSX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>VistaMare Core</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>VistaMare\ViMaCoreX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Level-D Simulations</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Modules\LVLD.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Fly the Maddog</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>F:\FSX\Modules\LeonardoSH.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>CMeteoXml</Name>
    <Disabled>False</Disabled>
    <Path>.\CMeteoXml.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Carenavigraph</Name>
    <Disabled>False</Disabled>
    <Path>.\Carenavigraph.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>XMLTools</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>XMLTools.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>

 

P3D:
****
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>dll.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
        <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3 SDK 3.4.18.19475\Environment SDK\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>PMDG HUD interface</Name>
        <Disabled>False</Disabled>
        <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>
        <Name>ObjectFlow_P3D</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Carenavigraph</Name>
        <Disabled>False</Disabled>
        <Path>.\Carenavigraph.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>XMLTools3D</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>XMLTools3D.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
    <Launch.Addon>
        <Name>as_connect</Name>
        <Disabled>False</Disabled>
        <Path>as_srv\as_btstrp.dll</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>VRS_TacPack</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
    </Launch.Addon>
</SimBase.Document>

 

[Pete Dowson]

5 hours ago, von said:

With every software install or update I check the exe and dll xml.
I move FSUIPC back to the top protion above my addon aircraft e.g.,.. for years now FSX and P3D.

Interesting to see FSUIPC4 loading before PMDG_HUD. That was one of the problem DLLs others have isolated -- that and RAASPRO.DLL. But I am loading RAASPRO (though I had to go find and update).

Pete

 

[B773ER]

7 hours ago, Pete Dowson said:

Can you all check that you don't also have FSUIPC4 being loaded by the DLL.XML in the ProgramData folder! This has been reported once already, and removing it has fixed it --- so far.

If so we need to identify what it putting it there, as FSUIPC's installer certainly doesn't!

Pete

 

Is this the fix for P3D minimizing to the task bar? 

[B773ER]

8 hours ago, Pete Dowson said:

Okay. The first test result with FSUIPC uncompressed got exactly the same problem. FSUIPC is simply not getting loaded, and it is never actually run. SimConnect crashes by calling it when it isn't there!

It's looking like time to call in L-M support on this.

Unfortunately I cannot repro it here at all, so can you guys please report the problems and what I've said about it. I'll look for the new thread there and add to it if needed.

Pete

 

I submitted the post just above this before seeing this. So no fix until LM troubleshoots? 

[wlix261]

Quote

 

After the P3D Crash,

This is what comes out of the DLL.XML file located at

c:\User\me\AppData\Roaming\Lockheed Martin\Prepar3D v3

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>FSX-Join</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSX-JoinD.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>IvAp</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files\IvAp v2\ivap_fsx_bootstrap.dll</Path>
    <Commandline>
    </Commandline>
  </Launch.Addon>
  <Launch.Addon>
    <Name>CMetroXml</Name>
    <ManualLoad>True</ManualLoad>
    <Disabled>False</Disabled>
    <Path>.\CMeteoXml.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Carenavigraph</Name>
    <Disabled>False</Disabled>
    <Path>.\Carenavigraph.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>
</SimBase.Document>

Regards

Alvaro Escorcia

 

 

 

 

[Pete Dowson]

5 hours ago, B773ER said:

Is this the fix for P3D minimizing to the task bar? 

Sorry, you seem to have omitted something here. Is "what" the "fix"? Why would P3D minimise?

5 hours ago, B773ER said:

I submitted the post just above this before seeing this. So no fix until LM troubleshoots?

 

Many users other than myself also have no problems at all. Some process of elimination is needed to see what is common between those who do have the problem. so far I only seem to have got one user to cooperate with going through a process of elimination to see which add-on is causing the DLL loading problem.

 

Pete

 

(Not sure where that orange bar comes from, but I can't delete it!)

 

[Pete Dowson]

3 hours ago, wlix261 said:

After the P3D Crash,

This is what comes out of the DLL.XML file located at

c:\User\me\AppData\Roaming\Lockheed Martin\Prepar3D v3

That's what it would look like after a reinstall also, so the reinstall is making no change whatsoever.

Pete

 

[Joerg Alvermann]

Well, for me it looks indeed like LINDA - specific linda.lua - is triggering the P3D crash. P3D stops crashing when I remove 'linda.lua' file from the Modules folder. Though I have to check whether removing 'linda.lua' from the Modules folder is sufficient IF the P3D crash already happened once, or a new run of FSUIPC Installation is required too.

The odd thing however is that after running the FSUIPC installation routine, once i move linda.lua back into the Modules folder, it will run once without problems. Only from the 2nd P3D start onwards it triggers the crash.

P.S: linda.lua is triggered by ipcReady.lua which - of course - needs to be present as well, and is NOT causing any issue if it remains present in the Modules folder

 

LATER after further testing: 

Fresh FSUIPC install, LINDA present: P3D start as normal, BUT P3D crashes when it's closed. This is a known (LINDA-) issue and had happened since P3D 3.4 without effecting subsequent starts of P3D. This seems to have changed with HF2 where LM also has changed some exception handling (according to Beau Hollis in the LM forum). The P3D crash on exit seems to leave the system in an unclean state which causes the crash on the next attempt to start P3D.  Removing linda.lua from the Modules folder does not help if P3D already crashed once on exit, but removing linda.lua before the first (after FSUIPC install) P3D run prevents P3D to crash on exit, i.e. the system remains in a 'clean' state when closing P3D.

Obviously the Installation routine of FSUIPC however seems to 'resets' the system to a clean state, which - according to everything above - points to the DLL.XML (in AppData Roming) file again.

Joerg

Edited January 6, 2017 by Joerg Alvermann

[Pete Dowson]

2 hours ago, Joerg Alvermann said:

The odd thing however is that after running the FSUIPC installation routine, once i move linda.lua back into the Modules folder, it will run once without problems. Only from the 2nd P3D start onwards it triggers the crash.

I could understand this better if LINDA was changing the state of some hardware or driver and this was causing the crash on the next load, but then you would get a crash on the second and sunsequent load in any case, whether you ran the Installer or not. After all, the Installer is actually changing nothing at all.

2 hours ago, Joerg Alvermann said:

The P3D crash on exit seems to leave the system in an unclean state which causes the crash on the next attempt to start P3D.

Ah, so could the apparently successful sessions actually be crashing on exit without you noticing? Can you check the Event Viewer logs in Windows to see? On a successful run, is the FSUIPC log file complete with the end summaries?

2 hours ago, Joerg Alvermann said:

Obviously the Installation routine of FSUIPC however seems to 'resets' the system to a clean state, which - according to everything above - points to the DLL.XML (in AppData Roming) file again.

Well other folks have tested this and proved there's no change to that file before and after. They are character-for-character identical! I don't know what else the Installer could be doing to "reset" anything.

Incidentally, ever since FS2002 days I have always started each new flight with a clean PC re-boot. It doesn't take long and you are then assured of exactly the same start conditions. I most especially don't trust any Windows based system after any crash.

Try a re-boot instead of an FSUIPC reinstall.

Pete