Jim Young
In Memoriam
-
Joined
-
Last visited
-
Jim Young changed their profile photo
-
Locked.
-
Thanks Paul. I will be updating it soon, hopefully to make it easier to use. -
This AVSIM Crash-to-Desktop (CTD) guide provides investigative techniques you can try when you get one of those dreaded crashes while loading the sim to your setup screen, during the loading to the flight, or during the flight. Most importantly, the guide includes tips on preventing crashes, probable causes, and you may see some actual fixes we found while searching the Internet and scanning forums throughout the flight simulation community. For the purposes of this guide, a CTD includes incidents where the simulation crashes, freezes up during a flight or you receive the nasty Blue Screen of Death (BSOD). Except for some rare known causes of crashes, each CTD must go through an investigative process and this guide will provide you with some tools to assist you in finding the cause and taking corrective actions. We have found some simple procedures you can take that fixes a majority of CTD’s but, if they do not work, we provide some procedures you can take to investigate the crash. You must be aware, what “fix” works for many, does not work for all as the crash could have been caused by an anomaly on YOUR computer system. We hope this guide will be sufficient and prevents you from the task of uninstalling/reinstalling your simulator, your add-ons, and/or your operating system. The following changes to previous versions of this guide were made: Updated and clarified the investigative techniques in the “How to fix Most Freezes/Crashes” section. Updated links within the document and to external website locations. Added detailed instructions for repairing FSX, FSX-SE, or P3D. Added instructions for deleting incompatible aircraft for MyTrafficX users. Added method for repairing Windows 7-10 without reinstalling Windows. Added information for fixing PMDG_737NGX_2.ddl. Fixed grammatical errors.
-
I will pin this but please be aware of our non-advertising policy in the AVSIM Terms of Service. No direct and live link to the stores. Thanks for your cooperation.
-
Hi Carl, In the menu above your post, there's an icon with a link. Click on it and paste your link into that. Best regards, Jim
-
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
-
I suspect the link to the site is here: http://secure.simmarket.com/tropicalsim.mhtml Best regards, Jim
-
Glad you might have found a fix. Be careful moving the old files over. Sounds like your System Registry was pointing to another user. I had to do this once before too. As far as the corrupted user redirecting you to Windows 10 support, it sent me to Windows 7. It has an option to indicate the Windows version. In any case, it is pretty much the same routine for Windows 7 and above. Best regards, Jim
-
I like the fact you can zoom way, way in and way, way out. There is also a camera for the front of the aircraft that can be zoomed in/out before going into the cockpit. I personally like the spot view when it is zoomed out to .30 (very realistic IMHO) but pretty neat when you can zoom it in too up to 510. Now you can zoom into those rivets on the aircraft and some of the eye-candy scenery at airports.
-
Thanks Jeff for correcting. I still do not understand why as they each stand alone but that's the the manual says so that's the way it should be done. It also states that in Rob's AVSIM P3D Guide on page 13!! Apologize Flavio for the confusion! Best regards, Jim
-
There is no order that matters. Just make sure you uninstall the old one first.
-
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
-
-
It's good you found the causes of your StackHash(es). The Buffer Overflow errors are quite common and mean nothing. Here's an explanation from one Source - http://www.howtogeek.com/school/sysinternals-pro/lesson4/all/ (scroll down to the Buffer Error section). I personally think you will get more StackHashes (it's not an error). I believe it is bad programming on the part of some developer that causes many of these issues. StackHashes occur and then go away for a while then they return. Another member, Ray Proudfoot, and I found a missing object in MyTrafficX caused a StackHash. Removed the object and the crashes stopped (they alternated between StackHash and the ntdll.dll error. I hope you did find the error because of missing winter textures. Were they loading or trying to load about when you got the StackHash? For me, the culprit has been the AI program and it was caused by the AI program looking for a flight plan for an AI aircraft and couldn't find it. I knew it was MyTrafficX as Process Monitor was processing AI aircraft when the freeze or the crash occurred. Best regards, Jim
-
Yes, I told you not to check this compatibility box and only the Administrative Mode should be checked. There is one other reason why I know FSX will not start up and that's if you do not have Microsoft.net 2.2 and Microsoft Visual C++ 2005 but I see those programs are installed. If you had MyTrafficX or MyTraffic6 installed, that would cause ntdll.dll errors too but at least you would be able load FSX-SE. Make sure you do not have any dll.xml or exe.xml left over from a previous installation left in your folder (they are located in the same folder as your fsx.cfg). Make sure you do not have the fsuipc.dll in your Modules folder (or anything in the Modules folder). Even if you had bad voltages and your system was overheating, FSX-SE would still load. You cannot get past the splash screen. So it is something in your fsx-se directory. Best regards, Jim
