Jim Young

If you just installed P3Dv3.2 and nothing else (and absolutely nothing else) then it would be very difficult to understand the StackHash after an initial install. It would be best if you posted your AppCrashView report here or the Event Viewer report as requested by the AVSIM CTD Guide. Here's what the next version of the AVSIM CTD Guide says about this crash - StackHash – See also BEX and NTDLL.dll above. There is no module on your computer system named StackHash so no need to look for it. If the StackHash is shown as the faulting module, it will have four characters next to it like StackHash_0a9e. That represents the memory address of where the fault occurred. Do not try to look for it. You will not find it. There is no known solution to BEX/StackHash errors other than reinstalling Windows and your simulator but some have accidentally fixed their problem as follows - lower display driver settings rebuild the simulator’s configuration. This will lower settings and eliminate tweaks that might not be working properly change voltages/overclocking settings in the BIOS disable all scenery add-ons in the Scenery Library. Or, move your scenery.cfg to a temporary folder and let the config rebuilt with the default configuration. If error goes away, you will have to investigate which scenery was the cause. and/or shut down the simulator only in Windowed Mode and starting up in Windowed Mode but never in Full Screen. Here's what the next version of the AVSIM CTD Guide states about the NTDLL.dll error - NTDLL.dll – The following is a quote from Microsoft Techs - “Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures. When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future” (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu). The service is part of the Security Center service so you need to make sure this service is turned on. If the ntdll.dll is placed on the watch list, this information will be shown in the Event Viewer (Admin Events). See also Increase Heap Limitation in the Actions to Take to Prevent Crashes section of this guide. Several possibilities for the NTDLL.dll error are as follows: Most likely cause is outdated or corrupted hardware drivers. Run a driver update program as discussed in previous section. Use the System File Checker (sfc \scannow) to look for corrupt or missing system files. See previous section for details on running this program. Recently update video card drivers? Reinstall or install the previous version. System overheating. Check (not common but it can cause this crash). Wrong timings/voltages set for your installed RAM. Use the utility, CPU-Z, to check or look inside the BIOS (NOTE: With newer Mother Boards and Memory Simms, this issue is not as common as it was with earlier systems but it can still happen).CPU voltage too high or too low (only if you manually adjusted this in the BIOS). You might be able to fix by returning your BIOS to Optimized Defaults or lowering your overclock by one point from say, 4.4GHz to 4.3GHz. Remove the UIAutomationcore.dll from the main FSX folder, if installed (applies to FSX users only). A known fix (could be the wrong version placed in the FSX folder). Check your dll.xml for duplicate entries or entries where the software was removed but the entry in the dll.xml still exists. Fix. Disable User Access Controls (UAC) (see the section above for more information). Update hardware drivers for your computer (especially on new computer systems or if the Windows OS has been reinstalled or upgraded) (see Driver Update information in this guide). Disable MyTrafficX, v5.4c or MyTraffic6a in the Scenery Library to see if this program is the cause of the ntdll.dll error. It is believed to be caused by an AI scheduling programming error. For MyTrafficX go back to the 5.4b version or make sure no external AI program schedule is activated (i.e., the 2012 or 2013 Schedules on the developers website). The default schedule appears to be okay for most. Check the developers support forums for updated information and possible bug fixes. For MyTraffic6, some have fixed it by renaming the MyTrafficmil.bgl to MyTrafficmil.orig. Some have seen this error when changing to payware aircraft after using another payware or default aircraft. Best regards,

Sad to hear. Thoughts are with him and his family.

It is crashing because it does not like the Carenado entries in the dll.xml. Disable the following entry if it is in the dll.xml as follows: <Launch.Addon> <Name>CMeteoXml</Name> <Disabled>true</Disabled> Change this line from False to True as shown. <ManualLoad>True</ManualLoad> <Path>.\CMeteoXml.dll</Path> </Launch.Addon> There's another entry but it should be okay as long as the Carenigraph.dll is in the main P3D Directory. <Launch.Addon> <Name>Carenavigraph</Name> <Disabled>False</Disabled> <Path>.\Carenavigraph.dll</Path> </Launch.Addon> If the entry is there but the module is not there, then crash.... This topic belongs in the Carenado Support Forums so moving it there. Best regards,

Moved from the developers' forum as I think you'll get more viewers here. Best regards,

Great post Ray! Positive comments like yours are greatly appreciated and I think our membership will like the feedback! Best regards,

You may have corrupted your fsx installation by replacing the fsx.exe, g2d and g3d.dll's. I mean, this is FSX-SE that you have loaded and you just cannot do that to FSX-SE (or FSX) as the FSX.exe was changed when it was upgraded to SP1 and SP2 (and Acceleration). You have identified the problem - the FSUIPC.dll module. Have you installed the latest update? The version I have is 4.949h dated 3/2/2016. If you are networked with several computers at your house, then simconnect could be a problem but, if you just have one computer, simconnect is NOT the issue. You can try to reinstall FSX-SE. You will probably be told it is already installed and asked if you want to do a repair. Select that option. It will replace your FSX.cfg and scenery.cfg (but not your dll.xml as that is not a default file). So, if you want to return your fsx-se.cfg and scenery.cfg, you will want to back them up. The best solution for any crash is to return the sim to the default. That requires moving the FSX-SE, Scenery.cfg, and dll.xml to a temporary folder. Run FSX-SE. Runs okay? Then move the scenery.cfg back first. Runs okay? Then move the fsx-se.cfg back. You already know the fsuipc.dll will not load properly so you either update that or disable it from loading int he dll.xml. Hope this helps. Best regards,

The second crash belongs to ASN. It is not properly installed. Best regards,

Do you have any FSDT or FlightBeam airports installed? If so, download and run the latest Standalone Addon Manager. What is loaded when you first startup FSX? Answer: All of the modules in the dll.xml and any .dll located in your main fsx directory. Then your AI aircraft and flight plans for your AI aircraft. Of course, your FSX.cfg. Then all the licensing stuff for FSDT/FlightBeam airports. Then your scenery.cfg and all of the scenery is loaded. Any photoscenery that is enabled will load all of their scenery files (.bgl's) (that takes some time). Simconnect will load and so will the PMDG Interface located in the PMDG\dlls\ folder. That's about it. No aircraft will load as you haven't selected any yet in the setup area. So the problem is in your scenery.cfg, your dll.xml, or licensing for FSDT airports. I had this happen to me once a year or so ago and I discovered my FSDT scenery had somehow become unlicensed and the sim would not load and crashed after the splash screen. I downloaded the latest Standalone Addon Manager and that fixed the problem. I do not know what you have installed but, as I stated earlier, the problem with startups is in the dll.xml or scenery.cfg. You are out of options if you have moved your dll.xml and scenery.cfg to a temporary folder and the sim still does not start up. Well, you have one option left and that would be to completely uninstall FSX and your addons, make sure everything has been removed per the PMDG install/reinstall guide, run a registry cleaner to make sure nothing is left in the registry, and then reinstall. Best regards,

As I stated above: "In regards to Windows Error Report (.wer) reports that AppCrashView uses to compile a report, make sure it is turned on - http://www.laptopmag...porting-windows Best regards,

Go to Windows Logs>Applications in the Event Viewer and right click on Applications and select Properties and make sure "Enable Logging" is ticked. Do this for all Windows Events. Best regards,

You want us to read a 676 page manual? Heck the 33 page guide that comes with the Carenado Phenom 300 is long enough and much, much more understandable! Best regards,

It's there. You just cannot find it. I currently have 791 events recorded (aren't I special...)- Make sure you are looking in Custom Views>Administrative Events. Here, it will show you every event no matter what the source as a Windows Event could be causing the problems with your simulator application. In regards to Windows Error Report (.wer) reports that AppCrashView uses to compile a report, make sure it is turned on - http://www.laptopmag.com/articles/disable-error-reporting-windows Best regards,

Most scenery addons for any of the simulators can be installed outside of the respective simulator. Makes it much easier if you have to uninstall/reinstall your simulator. Some, like FSDT/FlightBeam and Orbx/FTX stuff, is installed inside the respective simulator. I have 90% of all of my scenery addons installed on another SSD on another drive and just direct the Scenery Library to the proper location. If you have old scenery you had installed in FS9 or FSX, you can try to use the P3D Scenery Library and link the folder(s) where the scenery is located. FSX and P3D came out with a new texture format (.dds) but many sceneries are backward compatible but may not work as well as if they were developed specifically for FSX/P3D. For those, you'll just have to wait until the developer upgrades his/her products or possibly suffer some anomalies or performance issues (and crashes). Best regards,

In some cases, yes, and in some cases no. V2 is like FS9 was several years ago. V3 is like FSX several years ago. Like a whole new sim. You could install some stuff from FS9 into FSX but not all of it and many had to wait until the developers figured out the FSX code and developed installers for FSX. Some goes with going from V2 to V3 and it will probably be the same when V4 is released a couple of years from now. Best regards,

Goto Windows\Microsoft.net\Framework and it will show you the list of dotnets installed. You should have v2.0.50727. Best regards,

Thanks for passing on the info. I was unaware it was fixed but we did do a maintenance and security update on Wednesday night so perhaps that fixed the problem. Best regards,

According to the manual, you have to go to the developers website where he has "Easter Eggs" for you to download for Orbx and FlyTampa sceneries. He cites KRDD - Redding; KORS - Orcas Island, and KBLU Blue Canyon-Nyack as examples. So you have to already own these products. For Orcas Island, he adds a landing zone in the scenery. For Redding, a race track. So, go to his website and click on "downloads" and you will get the rest of the story. Best regards,

All the scenery I had installed in FSX I am using in P3D by simply telling the P3D Scenery Library where the scenery is located. No reinstalling or anything. The aircraft are a different animal but most of the FSX developers have developed installers for P3D (some charging for it). If at all possible, I would stay away from EMT and doing "tricks" to fake out the fsx installers. Do you need it all installed right now? Today? Just take your time and try to use legitimate installers. Best regards,

I have the same monitor and have tried 1920x1200 resolution and saw no difference in fps (plus it looked ugly!). Best regards,

Good news! Thanks for the update! Best regards,

Is Java installed and running? Best regards,

If the airport is FS DreamTeam or FlightBeam, goto the menu and select Add-ons and then look for Couatl Settings and then Restart Couatl. If that does not work, click on Couatl Live Update and then check for Live Update, install if an update is available. Also click on Add-on Manager and then look for the airport and make sure it has been activated. I think many of the other commercial add-on airports do the same thing and remove buildings if the product is not properly activated. Best regards,

If you have a dll.xml in the same folder as your fsx.cfg, move that to a temporary folder and restart FSX. If it restarts, then you have a problem with a module in the dll.xml. When FSX first starts up it loads the modules in the dll.xml. The AVSIM CTD Guide, page 2, provides instructions on how to use the Event Viewer but basically, you search for Event and look up in your menu and click on Event Viewer. Once open, go to Custom Views and then Administrative Events. This provides you with every recent event that might have caused the crash. If you see a FSX entry, double-click on it and it will open up into a new Window. In the new Window, look down to the bottom left and you will see Copy. Press this button and the crash will be recorded to your clipboard. Come back here and in a new post, right click inside the post and select Paste. The crash will show up in the post. I don't know anything about the World of AI but that might be the problem and you may have to uninstall and reinstall it. Best regards,

No, I meant Virtual Address Space (VAS) which has absolutely nothing to do with RAM. Best regards,

Hi Luke, You would contact me. I will have to change your tag as a member to Commercial Member so members know you represent a commercial developer when posting. If you want to have your own support forum, I can set up a support forum for your product(s) and you can advertise your product(s) in YOUR forum and provide information about updates, etc. No charge for this. Once the forum is set up, you will be the moderator of YOUR forum and you can pin topics and do the normal moderating duties. Many post product details and then provide updates. As long as you maintain your official support forum for your product(s) and do not set up an official forum elsewhere, you would remain as the moderator. If you decide to set up your official support forum elsewhere, then I would have to remove your status as a moderator and we may or may not keep the forum here as an unofficial forum. I usually make exceptions to this policy if you advertise on AVSIM. Of course, you can also advertise your product(s) here. See Advertising Info under the Contact Us tab for more information. When you are ready, if you want a support forum, PM me and give me the name you want for your support forum. Otherwise, let me know when I should change your tag to Commercial Member. If you have further questions, please PM me. Best regards,