I am my wits end...

3 hours ago, Jim Young said:

When you first purchase P3D, the installation program will install a dll.xml and place it in the same folder as your scenery.cfg.  There will be nothing in it other that the header at the top.  . Lockheed Martin put it there so that add-on developers could use it to place an entry for their modules so the modules would load at startup of P3D.  The FSUIPC module is one of them.  When it is installed, they install a new dll.xml and place it in the old default location where the P3D.cfg is located.  ActiveSky places their entry in the old location too.  As you reported above, FSCrew installed RAASPRO in the default dll.xml.  So did PMDG.  It doesn't make any difference which dll.xml is used by an add-on developer but it is preferred they all be located in the default location in the same folder as the scenery.cfg.  The dll.xml creates the Add-on Menu you see when you startup P3D.  When you click on the Add-on Menu, it will show options where you can open up FSUIPC or RAASPRO and make some changes. 

When I told you to backup the dll.xml's and rename them to dll.off, this effectively stopped the loading of any modules when you first start up P3D. When you start up P3D, it creates a new default dll.xml and there is nothing in it other than the header information at the top you mentioned.  There is no new dll.xml created in the same folder as the P3D.cfg.  You can go into that folder and rename dll.off by just removing .off.  This will allow the FSUIPC and ActiveSky entries to be loaded again.  You can then do another flight and see if the crash occurs again.  If it does, then your suspicion that FSUIPC may be at fault may be correct.  In that case, you would have to go to the FSUIPC site and see if there is an update, download, and install it.  But first, you want to run a flight and see if you get a CTD.  If not, then it is not the fault of the FSUIPC or ActiveSky. 

You will have to delete the new dll.xml created in the same folder as the scenery.cfg.  Once done, rename the dll.off by removing .off.  This will activate the entries in this dll.xml.  Run the flight again and see if you get the crash.  If so, then you know one of the modules in this dll.xml is causing the crashes.  You do this by opening up dll.xml using Notepad so you can edit it.  Here is one of your entries:

<Launch.Addon>
        <Name>RAASPRO</Name>
        <Disabled>False</Disabled>   This is the line you edit.  Change False to True such as  <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>.\RAASPRO\RAASPRO.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>

After you edit as above, this module will no longer load when you start up P3D.  When you run the flight again, if there are no crashes, then you know RAASPRO was the culprit.

Hope this helps!

Best regards,

Jim

Thank you for taking the time to help, it has helped Jim.