Jim Young

Whenever you install GSX and SODE and FSDT airports, part of the installation will be to place entries in your dll.xml and exe.xml.  There are currently two folders that could contain the dll.xml and exe.xml and the required entries for FSDT and SODE.  One is in the same folder as where your P3D.cfg is located.  The other is the same folder as where your scenery.cfg is located for P3D.  Both are hidden folders.  On page 5 of the AVSIM CTD Guide, I show the location of these hidden folders.  Rob Ainsworth just published the AVSIM P3D Guide and he has the location of these folders and entries too.  The standard installation folder FSDT uses for the dll.xml is the folder where the scenery.cfg is located (which is the new location for P3D).  You want to make sure you do not have the entries in the dll.xml and exe.xml in the folder where your p3d.cfg is located and also in the dll.xml and exe.xml where your scenery.cfg is located.
 
If the entries are not in the dll.xml or exe.xml then you can try to fix it by downloading the latest Standalone Addon Manager.  Just go to the Products and select GSX and then click on Addon Manager and install it.  It will make sure your installation was properly done.  According to Image 1, SODE is properly installed.  Image 2 - List index out of bounds - see the following link at FSDT Forums - http://www.fsdreamteam.com/forum/index.php?topic=14306.0.  Image 3 - Adding Addon Manager to dll.xml file, indicates to me it is adding the file or checking for the file.  Again, just run the Standalone Addon Manager again.
 
These issues are not really P3D issues.  If you cannot get it resolved with my suggestions above, I would go to the FSDT Forums, sign in and post your problem there.  The developer is extremely helpful IMHO.
 
Best regards,
Jim

The AVSIM CTD Guide provides locations of all of the files too, including the location of the hidden folders (right after the guides intro).  The dll.xml goes in the same folder as the fsx.cfg.  When you uninstall FSX-SE, this folder will not be removed and you have to manually remove it.  If you do not manually remove it, the fsx.cfg will be overwritten but not the dll.xml when you reinstall FSX-SE.  So, if there is a dll.xml still located there, it will load when you first startup FSX and try to load modules.  If it cannot find the modules, it will crash (in some cases).  The reason I asked for you to check to make sure fsuipc.dll is not installed in the modules folder or on your computer, is that the version installed may not be compatible with your brand new installation of FSX-SE.
 
This is about it.  One more suggestion - You don't want to reinstall Windows and I don't blame you.  The guide provides a way where you can fix a corrupted User and this would definitely wipe out any remnants of your current user file.  Look on page 21.  Click on corrupted user profile and it will take you to the Microsoft website to provide you with instructions on how to fix a user profile.  Look under 'Repair and Recovery'.  I did it once and it give my system a breath of fresh air like a new installation.
 
Best regards,
Jim

That thread was removed by the late AVSIM CEO as AVSIM has a FSX Configuration Guide and a CTD Guide (see links in my signature).  Our hardware forums provide the best information regarding hardware.
 
Best regards,

You need to check out the AVSIM CTD Guide and there's a download you can get and run and it will give you a good idea as to what caused the crash.  See link to guide in my signature.
 
Best regards,

The uiautomationcore.dll in your System32 folder caused the crash.  Did you put a version in the main FSX folder?  If not, recommend you do.  See the AVSIM CTD Guide, page 7, for the only two versions that can possibly be placed in your main fsx folder (see link to the AVSIM CTD Guide in my signature).  The Guide has links to the locations where you can download the version you want. 
 
If you do have a version in your FSX folder, remove it by moving it to a temporary folder.
 
ADDED:  I would also run the System File Checker to look for and fix corrupted or missing files - https://support.microsoft.com/en-us/kb/929833
 
Best regards,

It's obviously caused by the Estonia Migration Tool (maybe, perhaps).  P3D works great out of the "box" and then you begin to add addons that were not made for P3D and P3D freezes or crashes (whichever comes first).  IMHO, you should never ever fly a 10 hour flight with a product that was added using the EMT.  Not even a flight longer than 2 hours as you will be frustrated.  If there was no event in the Event Viewer, then that means it was caused by your computer system.  Your system cannot handle what is being thrown at it.  It cannot render textures fast enough.  It does not have the virtual address space to accomplish a task.  Of course there will be no Event as there was no memory available for your computer to record the event.
 
You simply ran out of VAS and the AVSIM CTD Guide provides some solutions for running out of VAS like turning down all of your settings.  You had everything running for 10 hours with no problems whatsoever so you can be almost assured none of your addons, alone, caused your crash.  You just ran out of VAS.  I run out of VAS after 2-3 hours as I begin my descent about two hours out and I'm flying into a storm and hi res airport scenery.  I get an OOM 99.9% of the time.  There is no fix for this problem for me other than to turn off ASN and use a default weather setting and turn down my P3D.cfg settings.  I have REX too and you cannot use 32 bit textures with much success as it can bring your system to its knees pretty quick.  There is currently no computer in the world that can run P3D or FSX for any length of time with high settings and lots of eye-candy like addon scenery and commercial weather engines.  I think you should only use ASN for local area flights to place flying in rough weather but never any long flights.  Again, this is not P3D's issue, this is a computer system issue and it occurs in FSX and FSX-SE too.  Microsoft only provides 4 GB's of virtual address space (VAS) with their operating systems.  When VAS runs out or gets very low, your application will freeze or crash.  You can monitor the amount of VAS usage by following the instructions in the AVSIM CTD Guide using a freeware utility called FSUIPC.
 
Best regards,

The initial installation of the PMDG 777 for P3Dv3.1 had a bad RAASPRO dll.  It caused a crash at startup but there was an error message.  I've never heard of anyone successfully adding entries to the dll.xml manually.  At least you were able to diagnose your issue and determine the problem was the dll.xml.  You should disable each entry in the dll.xml as discussed in the AVSIM CTD Guide.  For example, the line in red below would be changed from false to true.
 
<Launch.Addon>
    <Name>RAASPRO</Name>
    <Disabled>False</Disabled>
    <Path>.\RAASPRO\RAASPRO.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
 
You change all of the entries to True except for one, restart P3D and see if the freeze occurs again.  If not, change another entry from True to False and do this until the culprit is found. 
 
Best regards,

Until they come up with an installer you will have to select "Browse" and then navigate to the P3Dv3.1 folder then click okay and it will begin the installation program.  When finished, the aircraft won't be installed in P3D.  You will find the installation files over at C:\Program Files (x86)\Carenado Installer.  Now all you have to do is move the installation to the appropriate folders.  For instance, you'll see a Carenado Navigraph folder.  Move or copy it to the main directory of P3Dv3.1.  In the Carenado Installer folder, open up Carenado folder and you will see a couple of files that should be copied or moved to the main directory of P3DV3.1.  Once that's all done, then you need to open up your dll.xml file (located in the same folder as your P3D.cfg) and enter the following:
 
<Launch.Addon>
    <Name>Carenavigraph</Name>
    <Disabled>False</Disabled>
    <Path>.\Carenavigraph.dll</Path>
  </Launch.Addon>
 
That's it.  Start up the sim and load the Phenom 300 and you should have the 2013 version of the Nav data installed.  If you want to update the NavData by using Navigraph FMS Data Manager you can but make sure you tell the Navigraph program where P3Dv3.1 is located otherwise it will create a P3Dv3 folder and install the navdata there.  That's okay but you will then have to move it over into the P3Dv3.1 folder.  Fun stuff!
 
There is no installer for P3Dv3.1 yet and no one, including JustFlight, has the installer yet.
 
Best regards,

See the on-going discussions in the Library Forum about this issue - http://www.avsim.com/forum/522-the-file-library-general-forum/
 
Best regards,

This BSOD is caused by a too high or too low cpu voltage setting.  I know you said your CPU is not overclocked, but check your BIOS and make sure the settings at at the Optimized Default settings.
 
Best regards,

So disable the entry in the dll.xml for fspassengers and that should do it until fspassengers can find a fix.  That way fspassengers will not load and it will be inoperable.  Is this the latest version of FS Passengers or the really old one?
 
Best regards,

We are in Performance Mode as something is hurting the sites performance.  It's a temporary glitch.
 
Best regards,

It's not too late Rick. The problem has been fixed.
 
Best regards,

If you have the UTX utility, opening this utility and then closing it will fix this problem (guess it fixes the entries in the terrain.cfg.  If you do not have the UTX installed, then it must be another issue.
 
Best regards,

The AVSIM CTD Guide provides some probable causes for ntdll.dll errors.  For me, I could reproduce it 100% of the time with my overclock.  I had my overclock at 4.4GHz and changed it to 4.2GHz and the crashes went away.  I moved it back to 4.4GHz and the ntdll.dll crashes started again.  Probably had wrong voltages although I had them set to auto for my ASUS board which worked for JJ when he first promoted the board for ASUS a couple of years ago.  It might have also been a combination of high settings and the high overclock but think it is most likely just the overclock.
 
Best regards,

You waypoints disappear as your FMC has a discontinuity(ies) plus you need to make sure the STAR is activated after it is selected. Goto the Dep/Arr page and select your runway and STAR. Click on Activate. Go to Legs page and check your waypoints and make sure there are no discontinuities.
 
Best regards,

Perhaps the following link will help - http://escenariosfsx.blogspot.com/p/fsx-lezl.html
 
I found this via Googling lezg fsx.
 
Best regards,

That should do it!  I have the Corsair 850 PSU and have had no problems with it since I got it two CPU's ago (rebuilt system twice w/same PSU).  When FSX or P3D are running, they take up a lot of resources.  I personally think FSX is a better benchmark program than some of the programs specifically made to check system stability.
 
Hopefully it works.  Your latest Event Viewer log does not indicate anything.  I like the AppCrashView program as it provides more information about a crash (see page 2 of the AVSIM CTD Guide for the link).
 
Best regards,

You will need to buy another copy of FSX or get the original DVD back from your buddy.  FSX can be installed on two separate computers but the last installation is the one that shows the hardware configuration.  So, when you get it back from your buddy, you will have some problems because he overwrote your original activation setup and the activation will not work.  Contacting Microsoft to help you with a reactivation will not work either.  It is very difficult to find the DVD version of FSX or Acceleration or FSX Gold so it does not look good for you.
 
You can purchase and download FSX-SE though!!

You should definitely state you want to run this software.  These are the User Access Controls in your computer system which is trying to protect you from evil, evil people who try to install something in your computer without your approval.  It is most important that you tell your computer that the PMDGSounds can be trusted.
 
Best regards,

Here you go! http://forum.avsim.net/topic/461767-p3d-v24-ctd/
 
Best regards,

See page 9 of the CTD Guide regarding this error.
 
Best regards,

Fixed.  Should have gone to the support site in the first place!  http://www.fsdreamteam.com/forum/index.php/topic,10451.0.html.
 
Best regards,

You do not have to use the suggested configs in the Addon Manager for any of the FSDT airports.  Since I don't use tweaks and I like my LOD_Radius 6.5 and Texture_Max_Load 4096, I don't allow the modifications suggested by FSDT.  Just open up the FSX.cfg, find the 'reject small radius parts' tweak by commenting it out (placing two slashes in front of the parameter - //reject small radius parts=).  It won't load the next time you start up fsx.
 
Best regards,

This happens with IE10 or 11 users.  You have to hit that little BBCode Mode button, then paste the link in your post.  Same goes if you try to quote a post, nothing will show up in your reply.  IE10 and 11 users have to use the BBCode Mode and turn it off.
 
 
 
 
The Microsoft Visuals are used by developers to make sure your application runs as intended.  At least it was updated to the proper version.  The 6195 version was suppose to be included with Acceleration but the program was released too soon.  What was the other faulting module?
 
There are thousands of reasons for fsx to crash.  The faulting module only provides a clue to a fix but it does not always fix the problem.  A fix for the faulting module will work for 8 out of 10 users but not for the other two.  It mostly comes down to system configuration.  The Exception Code you listed in your OP shows up in almost every crash, whether it be fsx or Microsoft Office or Internet Explorer.  It means there was a memory accession violation. 
 
I would try removing the logbook.bin in the MyDocuments/FlightSimulatorX Files.  Move it to a temporary directory so that it will be rebuilt.  If that fixes the problem then you had a corrupted logbook.  The logbook contains every flight you have ever flown plus all of your missions and awards received.  So, if the logbook was corrupted, you want to fix it or else none of your completed missions will show up as completed anymore.  AVSIM has a FSX Logbook Recovery tool in the AVSIM Library.
 
Ah, let's see what else I might have up my sleeve.... 
 
Best regards,

I don't use tweaks so cannot advise on the BufferPool tweak. The FSX Configuration Guide located to the right of this forum under Hot Spots provides some guidance. Of course there are those who love this tweak to death and will give you their advice. I do not use tweaks as I have a very powerful system (i7 4770K w/780GTX video card).
 
Best regards,