Jim Young

You should see a major difference if you disable Texas and look out the cockpit window as you will be seeing the default scenery for the area. When you enable the scenery, it will be MSE Texas and the scenery outside the cockpit window should look drastically different. If you hit the F12 key, you will get a completely different resolution as the scenery appears to be much farther away and not sure why it looks crispier. Not sure what the elevation is after hitting the F12 key but zooming in and out (using the plus and minus keys might help). I use those keys frequently especially when using MSE scenery. But you are not going to get the same resolution in the cockpit unless you are at the same elevation and same zoom factor. How that is done is not known as I have never used the F12 key but I have used the zoom in/zoom out keys which dramatically change resolutions.

I think some of these top down views are at higher resolution (zoom factor around 30%) for realism. Other cockpit views do not have the zoom factor and cannot be increased to say 30% as it will distort the VC. I don't use 2D cockpits but those you might be able to change the resolution a little. In wing view (for the PMDG 737 for instance), I always change the resolution to 30%). Get better fps and clarity and the sim looks more realistic. Not sure why this is not done by default by MSE. I think MSE is best viewed at 30-40% resolution as it makes things much crisper and clear (also suggested by MSE). Best regards, Jim

Story here - http://aviationweek.com/commercial-aviation/joe-sutter-father-747-dies-95 He certainly lived a good life. An Aviation Giant. My thoughts and prayers to his family and friends. Rest in peace! Jim

It could mean something that is related to your subsequent crashes with P3D and the only way to find out is to fix it. Some of the errors found in the Event Viewer are okay and Microsoft will usually tell you if the error is by design but I would do some Google searching to see if there's a fix for the error. The AVSIM CTD Guide, page 24, has a link to the Microsoft.net Repair Tool and more information about Microsoft.net's. Best regards,

The d3d9.dll and ntdll.dll crashed your FSX but it does not mean FSX did it. You have the Windows 10 versions installed and, since I don't have Windows 10, cannot verify the versions are correct. As I stated above, d3d9.dll is part of the DirectX 9 runtime program. Some members here use a hacked version of the d3d9.dll and, according to the AVSIM CTD Guide, it causes a crash of FSX - D3D9.dll – This is most likely caused by installation of SweetFX or the ENBSeries Modules. Remove the D3D9.dll modules (there are several) from your main FSX folder. These two hacks of DirectX files have been popular to many users but found to be the source of several CTD’s. Most likely the module is not configured properly for your computer system and you should conduct some searches on AVSIM (the AVSIM SweetFX Forum) and elsewhere for the best configurations. Several members have been successful in getting these modules to work properly. The following ENBSeries files are installed in the main FSX directory and should be moved to a temporary directory if you are seeing crashes or graphics anomalies: D3d9.dll, D3dx9_40.dll, D3dx9_26.dll, and ENBSeries.ini. SweetFX installs the following files that should be moved to a temporary directory if problems occur: D3d9.dll, D3d9.fx, Dxgi.dll, Shader.fx, and the injector.ini. D3D11.dll You state you do not have SweetFX or the ENBSeries hacks installed but did you have them installed at one time, maybe several years ago? Your FSX directory will still have remnants of the hack if all of the files are not removed. There's an initiator (.ini) file that loads whenever you startup FSX. Just covering all bases with this as you do not provide a lot of information. The ntdll.dll is a well-known error. There is no known "one" fix that works for all. The following is quoted from the CTD 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." If you want to know how to use programs like the System File Checker, details are in the AVSIM CTD Guide. Best regards, Jim

I am having a hard time understanding your problem. You do not provide any information whatsoever about your issue other than it takes [something] about 4 minutes to come up, and it does every time you fly. You should move your dll.xml to a temporary folder and see if this fixes the problem (whatever it is). The dll.xml is loaded at startup of FSX. You should also check your main FSX folder and look for d3d9.dll there. If it is there, then you have a hacked version in the folder. Delete it. Best regards,

The d3d9.dll is part of Windows and located in your Windows\System32 folder. It is part of DirectX. You can try checking for errors to DirectX by going to the Run command and typing in dxdiag or you can go to your Windows search bar and type in dxdiag and then look for errors. If you cannot resolve it you can Google the file on the Internet and download it or go to the Microsoft DirectX website and download the latest version of DirectX (most likely already installed). PMDG usually installs DirectX too when installing any of their products. If none of the solutions above work, then you will have to reinstall Windows. Best regards, Jim

The kernelbase.dll is discussed on page 32 of the AVSIM CTD Guide (no known fix) - Kernelbase.dll – No known fix but some have solved this problem by - Updating or reinstalling their video card drivers. Scanning your system for corrupt/missing files. Disable startup programs by typing msconfig in the Windows search box. When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer). User Profile Corrupted – last resort, fix possible corrupted user profile. Further details in the guide (see link to the guide in my signature). The sound.dll CTD is rare and I can find no solution on the Internet. I would suspect it is related to the kernelbase.dll error. You installed P3D in the default locations and maybe that is causing your problems. Do you have UserAccessControls (UAC) disabled (see page 23, AVSIM CTD Guide)? You can also try moving your p3d.cfg to a temporary folder and restarting P3D and letting the config rebuild. Could be a tweak or setting in the config that P3D does not like. Best regards, Jim

Respectfully, that's impossible. An Event has to be recorded. AppCrashView deciphers Windows Error Reporting that occur when something happens to your computer system or a software application crashes. It provides more details. If there is no AppCrashView or Event, then there is absolutely nothing anyone can do to help you. Best regards,

Welcome back. Hope you have fully recovered from your health issues (although, at 84, a new one seems to crop up after one goes away). I golf with individuals in their 80's and they sometimes hit the ball further and more accurately than me (at 71). I hope they can continue for many more years and I hope your health and quality of life improves. Many have no problems running FSX or any of the other flight simulators on Windows 10. AVSIM does have a forum set up just for Windows 10 users. Windows 10 does include additional security as many Windows users over the years have complained to Microsoft their operating system did not stop malware or viruses from being installed on their computer. Microsoft decided it was time to protect you from evil people around the world who attempt to compromise your computer system. Windows Vista and Windows 7 were enhanced with additional security features but they mostly did not affect the operation of any of the flight simulators. Windows 8.1 had even more stricter security and now Windows 10 has arrived with even more (and updates even add more security!). When Windows 7 was released, AVSIM and many other developers and computer experts informed us on how to properly uninstall and install FSX and P3D. The rules are simple.... Disable UserAccessControls (UAC) Disable any Malware/Anti-virus program when installing a flight simulator and/or make sure you exclude those programs from scanning your FS directories. You will also want to make sure Microsoft Essentials (the freeware anti-malware program) is not scanning and messing up your files too! Do not install the FS program in the default directory. Instead, install in a directory such as C:\FSX or E:\FSX (or P3D). Enjoy using FSX or P3D. One of my favorite guides for installing FSX was developed by tech experts at PMDG - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx. The guide can be used for FSX-SE and P3D installations too. AVSIM also has the AVSIM CTD Guide which also provides valuable information on installing and running FSX on the newer Windows platforms. Best regards, Jim

Make sure the C172 aircraft.cfg has the following entry: [fltsim.4] title=Cessna Skyhawk 172SP G1000 sim=Cessna172SP model=G1000 panel=G1000 sound= texture=G1000 kb_checklists=Cessna172SP_check kb_reference=Cessna172SP_ref atc_id=N700MS atc_id_color=0xffffffff ui_manufacturer="Cessna" ui_type="C172SP Skyhawk G1000" ui_variation=" Glass Cockpit" ui_typerole="Single Engine Prop" ui_createdby="Microsoft Corporation" description="A stable and trustworthy plane, most pilots have logged at least a few hours in a Cessna 172, since it's the most widely available aircraft in the rental fleet, and is used by most flight schools. Since the first prototype was completed in 1955, more than 35,000 C172s have been produced, making it the world's most popular single-engine plane. One of Cessna's first tricycle-gear airplanes, the 172 quickly became the favorite of a growing class of business pilots. Its reliability and easy handling (along with thoughtful engineering and structural updates) have ensured its continued popularity for decades." Make sure you have a folder under C172 entitled: model.g1000 and panel.G1000 and texture.G1000. Best regards,

99.9% of all BSOD's are caused by a hardware failure of some sort. Most likely cause is a corrupted or bad driver. I cannot see how any software program like P3D can cause a BSOD. The only possibility is with high settings and that will cause a BSOD with the 0124 bugcheck. A software program that places a lot of resources on the system settings like FSX/P3D will trigger a too high or too low CPU voltage setting or another setting in any overclock. It is impossible for me to overclock my system higher than 4.4GHz and I have found the stable setting at 4.2GHz. Overclocks will not allow you to push your computer to its limits. Maybe for 2 or 3 sessions with P3D but it is going to bite you eventually. There are many computer experts (of which I am not one) who have succeeded to defeat my theories on overclocking. I have run all kinds of benchmark tests to try to get my computer to BSOD with an overclock set at 4.6GHz and it refuses to crash. I load FSX (haven't tried it with P3D) and my computer crashes with a BSOD (again, a computer system problem, not a software problem). Your images are very difficult to read. Best regards,

The ntdll.dll error and the StackHash are covered extensively in the AVSIM CTD Guide (see page 36) (link to guide in my signature). There is no known one thing that causes these two errors but the guide provides some "fixes" that worked for others (we googled the Internet to look for solutions and these were what was found). I doubt the aircraft you were flying caused the crash but, like the PMDG aircraft, more resources are being used. Make sure the aircraft is compatible with P3D as that could cause the crash too. Once other possible fix that is not in the AVSIM CTD Guide is a possibility that the mytrafficmil.bgl located in MyTraffic6\Scenery may be causing the errors. When individuals disable this .bgl, the errors go away. Hope this helps. Best regards,

AA does not work well in FSX at all. A known fact. You can reduce the jaggies but not completely eliminate (although mine appear to be perfect). If the AVSIM FSX Configuration Guide did not eliminate the jaggies, then you have a tweak or something else happening that is causing an anomaly. For one thing, you cannot set all of your settings to the max and expect no jaggies. FSX evidently was not programmed properly to allow that to happen. You MUST enable AA in FSX for it to even work. So, why my AA has no jaggies and yours does is definitely a mystery. I do not use tweaks at all so this might be your issue.

If you have the ENB Series or SweetFX hack installed, this could be the cause. DX10 has issues with those hacks. DX9 does not. There is no known solution that works for everyone. Some have found that recent security updates to Windows or Windows Updates have caused the problem. They uninstall them and everything works again. If it happened when you start up FSX, there could be an incompatible module being loaded in the dll.xml. You can move the dll.xml and exe.xml to a temporary folder, restart FSX and see if this fixes the problem. If not, move the dll.xml and exe.xml back. Some have fixed this problem by moving their fsx.cfg to a temporary folder and restarting FSX. FSX.cfg will be rebuilt. You may have a tweak or other corrupted setting in the fsx.cfg. Happens frequently. Hope this helps. If not, try some of the suggestions in the AVSIM CTD Guide (see link in my signature). Best regards, Jim

I suspect you are referring to the file in our AVSIM Library - http://library.avsim.net/esearch.php?DLID=196456&CatID=fsxmisc. Just stating this so everyone will know what you are talking about (okay, I was a little confused about your subject). Best regards, Jim

The machine_check_exception BSOD indicates you have a major hardware problem - https://en.wikipedia.org/wiki/Machine-check_exception. Same goes with the clock_watchdog_time_out BSOD. See page 14 of the AVSIM CTD Guide in regards to updating your hardware drivers (link to the CTD Guide in my signature). In regards to the FSL_A32XX.dll error, see the following link for the fix - http://forums.flightsimlabs.com/index.php?/topic/7178-installation-instructions-for-v101172-fsx/. You evidently had your anti-virus program running. Best regards, Jim

Let's lock this one up. OP had another username here too (similar) so I merged them. It is strange the developer has offered to assist and the individual all of a sudden is too busy to receive support.

I think this topic has run its course and has been discussed enough. Topic closed.

I have decided to unlock this topic. Apologize for the inconvenience. Best regards, Jim

In the same folder as your FSX.cfg, there should be a "dummy" default scenery.cfg. This should never ever be edited, moved, or deleted. If you should accidentally delete your "working" scenery.cfg located in C:\Program Data\Microsoft\FSX, then FSX-SE will rebuild using the one the "dummy" default scenery.cfg. If somehow, FSX-SE was not installed properly and you have no C:\Program Data\Microsoft\FSX-SE folder, then it cannot rebuild the file. So, you need to look in C:\Program Data\Microsoft\FSX-SE folder to see if there's a scenery.cfg located there. If so, move it to a temporary folder. The one that is located in the same folder as your fsx.cfg will then be able to rebuild it. Right now it simply cannot rebuild it as the one in the C:\Program Data folder is corrupted and cannot be read. The folder holding the fsx.cfg and dummy scenery.cfg is hidden. So is the folder in C:\Program Data. See the AVSIM CTD Guide, pages 5 and 6 on how to unhide these hidden folders. A link to the AVSIM CTD Guide is in my signature. Best regards,

The AVSIM CTD Guide has information on how to fix BSOD's. BSOD's are related to hardware issues and mostly are caused due to bad or incompatible drivers for a piece of hardware. Best regards,

48 hour flash sale - http://www.justflight.com/product/flightsim-commander-9

It's how I learned to tell others. High overclocks like your 4.8GHz can sometimes become very unstable. I have my OC down to 4.2 GHz and have seen no problems for a super long time and no ntdll.dll errors. I personally do not see any performance improvements with major overclocking. Just more frustrations. Best regards,

The AVSIM CTD Guide provides possible solutions to the kernelbase.dll error (see link in my signature). Best regards,