Jim Young

FS2004 can only be run on a PC. The Kolb Firefly is just an addon and not a flight simulator.

The AVSIM CTD Guide provides for fixing freezes after takeoff. The Majestic Dash 8 Q400 uses a lot of resources so, if you have settings set high and the sim runs out of resources, it will freeze up. On page 9/10 of the AVSIM CTD Guide, it tells you how to fix most freezes/crashes. Other than that, you need to investigate what's happening on YOUR system as it does not occur to everyone. The AVSIM CTD Guide also shows you one location in the Event Viewer where you will see every event, whether associated with FSX or your system activity. I even included pictures. Freezes/hangs have shown up in other cases like the one you described but it usually will show an unknown error caused the B1 Hang. So, in your case, looking at the Event Viewer, even if it shows the events, will probably be useless. However, if your system was scanning your HDD or SSD or running some other type of event during your flight, this could have taken up enough resources to bring FSX to its knees. So it is always good to look at it. You will probably be shocked to see all of the errors happening on your computer system as everything is recorded. The AVSIM CTD Guide can be found by going to the link in my signature or clicking on the link on the right sidebar under Hot Spots. Best regards, Jim

If the sim is crashing (sounds like it freezes as you have to use the task manager to end the process) while programming the PMDG MCDU, then that indicates to me it is a problem with the PMDG 737 installation. Recommend you go to the PMDG website and submit a trouble ticket - http://support.precisionmanuals.com/kb/root.aspx. You have to register for support and then complete the trouble ticket. You can also check out the AVSIM CTD Guide (see link in my signature), page 9, How to fix Most Freezes/Crashes. This section contains instructions on how to fix most freezes by moving your p3d.cfg, dll.xml, scenery.cfg to a temporary folder, restarting P3D and letting P3D rebuild the p3d.cfg and scenery.cfg and to see if this fixes the problem. If so, there is a problem with one of these files. Best regards,

Check out the AVSIM Hardware forum regarding multiple monitor setup. There are several members here who have posted in the monitor forum and you should receive help there.

Please see the AVSIM CTD Guide, page 30, freezes during flight. Windows 10 introduced more security at the request of many customers. You must make sure UAC is turned off and you have set compatibility to all users. See page 10 of the AVSIM CTD Guide for fixing must freezes/crashes. Whenever you have freezes/crashes, you must return your FSX back to the default configuration to make sure it is not the configuration that is causing your crashes. Page 10 shows you how.

I found over 300 repaints by the author Maik Voight in the AVSIM Library - http://library.avsim.net/search.php?SearchTerm=Maik+Voigt&CatID=root&Go=Search

Be a member of the AVSIM Team!! AVSIM is in need of more volunteers as Library Managers starting immediately (there will be a brief training period). More details, including requirements, duties, and how to apply at the following link - http://www.avsim.com/topic/488217-new-positions-available-for-library-managers/.

Thanks Shiner! I'm sure this troubleshooter will be helpful to many.

I hope I did not recommend you turn off your anti-virus program, just exclude the FSX/P3D folders from being scanned. Sorry for the poor communications. I have never used an anti-virus program since at least 2000 and never been hit by a virus. Malware, yes, but no virus. Windows has a very reliable firewall and, if you ever turn that off, accidentally or on-purpose, you will most likely be hit with malware or a serious virus. My sister living far, far away from me turned hers off even though I told her never to turn it off and she had a virus within 20 seconds and had to call in the geeks at BestBuy to fix it (uh, reinstall Windows). Will an anti-virus program stop malware from hitting your computer? No but the chances of getting a virus or malware will be drastically reduced. What are you going to do about any new virus or malware that the developers of anti-virus programs do not even know about yet. It will hit your system and maybe in a day or two later, you will be informed there's a new virus and you need to update your virus definition. So, keep your anti-virus, anti-malware programs and your Windows firewall enabled while cruising the Internet and downloading stuff. When it comes time to install the product you just downloaded from Lockheed, make sure the folder where it will be installed, say, drive D, is excluded from scanning by your anti-virus or anti-malware program during the installation. You can also disable the anti-virus program temporarily as you still have your firewall protecting you during the installation and you will not be on the Internet as long as you know the software you downloaded came from a trusted website (how do you disable your anti-virus program anyway? I think they only have one method and that is to exclude the program or folder or drive from scanning) I had one software program (i-fly 747) that did not install properly because I did not exclude my malware program from scanning during installation. So it is all just a recommendation. Didn't the OP post a link to the solution? Just report the false positive to Microsoft and make sure you do not allow scanning of the install program or the installation folder during any installation. Best regards, Jim

The dll.xml is in the same folder as you fsx.cfg but it only exists if you have addons installed, like fsuipc or fsdt airports, PMDG products. Laptops are nice when you need a computer at another location but I don't think all that great for FSX/P3D. Still many use a laptop to run FSX and P3D as they don't have the luxury of owning a desktop and laptop and I-Pad/Phone and/or SmartPhone all at the same time. Personally, I would keep the laptop and purchase a desktop with at least the i7 2600K CPU and the 780GTX. With my desktop, I purchase the latest CPU, MB, GPU, and memory about every 3-4 years. I keep my Cooler Master case and take the old stuff out and replace it with the new usually at a cost around $1200. So a computer costs me about $250 to $500 a year. With my current system (see specs below), it's hard to discuss upgrades as it works so well for me. But, the new CPU's, memory and GPU are getting faster and running FSX/P3D a lot better. I just have to figure out how much better. After I get a new system, I may add another SSD or HHD but mostly I just keep the old ones. The biggest costs for a new system is the CPU and GPU. You might want to check our Classified section for some good deals our members are trying to sell. I also like E-Bay as you have a lot of idiots like me.... err, people like me :smile: who buy a new system every two years or so and get the latest and greatest and then sell their "old" system at bargain basement prices. Best regards, Jim

Hi Aharon, That's an old KB and I remember getting recurring problems when using IE11 in Windows 7. I'm almost sure Microsoft fixed the KB but some members might still have it on their system so why it is still considered a threat. I solved my problems by disabling IE11 and installed FireFox. Did you try renaming your dll.xml as I mentioned above? FSX startup problems are easy to fix as it is either in the dll.xml or another module in your main FSX directory as every .dll loads at startup. Finding the offending module being loaded by the dll.xml is the hard part if you do not know much about computers. I forgot to mention above that you need to look at what you just installed (FSX related or system related) before this error began. The d3d11.dll is part of the DirectX runtime program. You can check to see if you have any problems by typing dxdiag in the search bar of Windows 7 (or 8.1 or 10) and hitting the return button. It could be a bad video card driver installation. Nvidia just updated the video driver a couple of days ago and maybe it started after installing the update? I still have Windows 7 installed but thousands are successfully using Windows 10 with FSX (see our Windows 10 Forum). Sure there are problems with any new OS and figuring out how to disable UAC and doing basic things like you did in Windows 7, but it appears to be stable. I have it installed on my laptop but not on my desktop. Best regards, Jim

Is enhanced haze simulation under visibility options enabled?

It sometimes occurs if you have SweetFX installed. Evidently not compatible in some cases with that hack. Any modules, like the d3d9.dll hack that are in your main FSX directory load at startup. If something is amiss, FSX will not start up. Same goes with the FSUIPC. If you do not have the latest installed, it may crash FSX at startup. The dll.xml and exe.xml load at startup. Suspect one of those modules not loading properly at startup. Wish Microsoft error reporting would state something like, "one of your modules, specifically the fsuipc.dll, in your dll.xml did not load properly. Please check for an updated version". If you move your dll.xml over to a temp folder or rename it to dll.xml.off, you can see if this caused the problem.

When you open up FSX, click on Settings and then Scenery Library. Look down to see if the scenery is enabled. If it is enabled in the Scenery Library, it was installed correctly. I put all of my MSE stuff on a separate drive from FSX and then link the scenery to the Scenery Library. I think what you are seeing when you hit the F12 button is actual or realistic scenery around the airport. It looks like photo scenery but is not but what FSX thinks is the landclass in the area. When you go to photoscenery, it will look very realistic and you should be able to identify buildings and things if you live in the area. The zoom level is at 80% and when you go back to the VC it zooms to around 60%. So a slight variation in the distances.

May explain why many get crashes and others, like me with the same scenario does not. I never use 2D panels and always fly with the VC. Glad you were able to find a solution. I may try to get your "fix" in the next rendition of the CTD Guide with a link to this topic. There are so many configurations it is difficult to pin down a solution that fits everyone. Computers systems, games, and humans do not match.

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