Sign in to follow this  
Fsxsimmer758

P3D Crashing to desktop while loading

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

Try with deleting the Prepar3d.cfg. To be safe, keep a copy of this file somewhere else to reintroduce your tweaks if you have P3D up and running again.

Share this post


Link to post
Share on other sites

(Always make a copy of the Controls folder when deleting P3D.cfg to avoid bad surprises with joysticks ;-)

Share this post


Link to post
Share on other sites

When this occasionally happened to me, it was a broken .dll or a wrong entry in my dll.xml. Disable your dll.xml and see what happens.

Share this post


Link to post
Share on other sites

I have periodically been facing the same problem lately but normally after 100% loading of the flight. I have checked the windows event viewer and have found that at different times different .dll files are listed as the source for failure. I have tried many fixes and none seemed to work. I unplugged the machine and left it for a couple of days and all of a sudden things were fine. It worked flawlessly for a couple of days and now I face the problem again. My machine is unplugged for a few days. I will follow this thread in the hopes that you find a solution, one that perhaps will also work for me.

Best of luck! 

Share this post


Link to post
Share on other sites
MY DLL FILE

 

<?xml version="1.0"?>

<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>Migration Tool Plugin</Name>

    <Path>MigTool.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>Addon Manager</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>bglmanx.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>C:\P3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>VistaMare Core</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>VistaMare\ViMaCoreX.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>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>

Share this post


Link to post
Share on other sites

Disabe FSUIPC and as_connect and see what happens. I would also remove the Migration Tool section completely.

 

When as_connect is the culprit uninstall and reinstall it. This helped me several times.

Share this post


Link to post
Share on other sites

    VistaMare Core

    True

    False

    VistaMare\ViMaCoreX.dll

 

 

 

This might be worth a look 

 

http://www.avsim.com/topic/487699-bex-error-p3d-ctd-when-starting/#entry3412670

 

 

    Migration Tool Plugin

    MigTool.dll

    module_init

    module_deinit

  

 

What Software are you Installing using the Migration Tool?  There are easy work around's for most non compatible Software.  

 

Do you have FSX as well?    When you are getting these Crashes, is the Migration Tool enabled or disabled,  With both FSX and Prepar3D installed it can get Tricky 

 

The bottom line is unless you know what you are doing,  Get rid of the Migration Tool,   it can add a whole host of headaches to a Sim.

 

-------------------

 

As the rest have said disable each Entry in your dll.xml file,  Either that or move the entire dll.xml file to a separate folder and then try start Prepar3D  

Share this post


Link to post
Share on other sites

Get rid of:

 

<Launch.Addon>
    <Name>VistaMare Core</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>VistaMare\ViMaCoreX.dll</Path>
  </Launch.Addon>

Share this post


Link to post
Share on other sites

Make sure this one is up to date (fsdt manager)

  <Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>

Share this post


Link to post
Share on other sites

Since it crashed while loading weather, I would suspect a problem with ASN.  But that's just me.  Lots and lots of recommendations for sure.

 

I will send this to the right forum.

 

Best regards,

Share this post


Link to post
Share on other sites

Looks like the WEATHER.DLL

 

Faulting application name: Prepar3D.exe, version: 3.2.3.16769, time stamp: 0x56df48ce
Faulting module name: weather.dll, version: 3.2.3.16769, time stamp: 0x56df4838
Exception code: 0xc0000005
Fault offset: 0x00010955
Faulting process ID: 0x11c0
Faulting application start time: 0x01d1a178be69c72d
Faulting application path: C:\P3D\Prepar3D.exe
Faulting module path: C:\P3D\weather.dll
Report ID: 410563b8-0d6c-11e6-813e-d43d7eba3cc7
Faulting package full name: 
Faulting package-relative application ID: 

Share this post


Link to post
Share on other sites

I get it occasionally and a computer restart always solves it, but I'll take the other tips into account

Share this post


Link to post
Share on other sites

 

 


Looks like the WEATHER.DLL

 

According to the AVSIM CTD Guide (see link in my signature):

 

Weather.dll – delete wxstationlist.bin and default .wx file associated with your default flight.  They will be rebuilt.  This crash can be caused by FSX/P3D settings too high or bad tweak (BP tweak mentioned most often). If you have a commercial weather program that has cloud textures or a program that furnishes cloud textures such as REX, FEX, then lower settings and make sure DX5 compression is used and textures are 512 or 1024.  This coupled with high settings FSX/P3D may produce this crash.

 

Best regards,

Share this post


Link to post
Share on other sites

A very important point : if your \Texture folder is corrupted (or even missing), you will ALSO get a crash due to weather.dll during flight load (tested and verified multiple times on my side).

Share this post


Link to post
Share on other sites

Thanks Jerome.  I will add to the new CTD Guide.

 

EDIT:  How do you know your texture folder is corrupted?  Only way is to do a repair install or uninstall/reinstall the sim.  Will not be added to new CTD Guide as I do not know how you determined the texture folder was corrupt (w/o totally reinstalling the sim and, if you reinstalled the sim or repaired it, how do you know it fixed the texture folder?).

 

Best regards,


Still no good, I'm thinking of just re-installing P3D 

I do not think just reinstalling P3D will do it unless you make sure all of your P3D files are removed as the cause is possibly in the hidden folders too.  Here's what I found for FSX (P3D is the same as FSX) - http://forum.simflight.com/topic/73367-fsx-crash-with-weatherdll-as-long-as-fsuipc-is-loaded/

 

Best regards,

Share this post


Link to post
Share on other sites

Jim and all....

 

I just solved my CTD problem. My case may be an "outlying data point," but I want to be sure people know about this. My error log was all over the map. But basically, when P3D started to load, it would CTD.  I could restart the sim, same problem, I could restart the computer, sometimes it would work ok. Basically random reasons from the Error Log. I am using Windows 10.

 

Microsoft Support (chat/screen control) spent 2 hours working on this and came to the conclusion they couldn't fix it. Then the lady said, "before we go, lets try one more thing."  She made me a new profile for Windows 10, Then we ran P3D. It worked!  So we tried it again and again ... no problems. We migrated my user files over to the new Microsoft Profile. (Lost some things and had to reinstall, which she told me would happen), but once everything was back ... NO PROBLEMS!!!  It wasn't P3D, it was the Microsoft Profile for Windows 10 that had somehow become corrupted.

 

I had re-installed P3D 4 times, I had re-installed all the ORBX files ... literally started from scratch and that did not help ... after all that work, the same problems.  I cannot tell you why a corrupted Win 10 profile makes P3D (or FSX) CTD.  I have a friend who solved his problem the same way, by changing the Microsoft profile ... he was using FSX with Win 10.

 

I am sure, the fixes above this in the thread are good ones for people with those specific problems. I tried them all, nothing helped.  If you have tried everything else, re-installing, making all the changes advised above and you still have a problem and  if you are using Win 10, change your profile and try running the sim ... it may work for you.  I've been error-free for 1 full week (and that's with 3-6 hours a day on the sim. I'm enjoying the hobby again.

 

To test it, make a new Microsoft Profile, then log in to it and try running your sim. (Don't worry about the addon's at this point, they probably won't work). If the sim works as it should, then you have the problem I had. Then get ready for some not-so-fun time reloading and reinstalling.

 

I'm no 'maven' at this like Jim and the other folks here, but I wanted to share this with folks in case they have the same problem. I can't tell you "why." But this got me functional again ... after 5 months of errors! At this point, I wouldn't just jump on this as the final solution. I think it needs to be discussed so we can understand the "why".  But it sure is a good clue for the problem if you are using Windows 10.

 

Doug/RTMM

  • Upvote 1

Share this post


Link to post
Share on other sites

 

 


She made me a new profile for Windows 10, Then we ran P3D. It worked!

 

This "solution" is in the AVSIM CTD Guide, page 21.  I once had an "unsolvable" CTD and ran across this solution (I have Windows 7) and the fix worked for me.  It is better than reinstalling Windows. 

 

I am surprised you had "lost some things" and had to reinstall.  I did not but I know it is easy for it to happen.  You just have to be sure you move the folders from the older profile over to the new once you get FSX working again.

 

Thanks for the providing the community with the solution to your problem.  I'm sure it will help someone.

 

Best regards,

Share this post


Link to post
Share on other sites

You Bet, Jim. And thank you for all you are doing.  It is a confusing maze out there, you are giving us a way through it.  I saw that for Win 7, but didn't think it would apply to Win 10, so I didn't try it. Just wanted to contribute what I could. 

 

Doug

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this