Sign in to follow this  
Bruce50010

FS9/Win7 Crash when selecting aircraft

Recommended Posts

I recently updated my computer to Windows 7 and installed FS9, Radar Contact, and Wilco 737 PIC.

 

From the FS main menu, or in a flight, I get a "Microsoft Flight Simulator has stopped working" every time I try to select an aircraft in create a flight, or change an aircraft when in an existing flight.  It does not matter what aircraft I am selecting -- an included FS9 aircraft or the Wilco add-on.  I've had no crashes from any other menu options, only the aircraft selection.

 

I've tried running as administrator, running in compatibility mode, running in full screen and windowed mode, and my video drivers are updated -- still crashes every time I try to select an aircraft -- really hoping someone has seen this before.  Thanks in advance for any help.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Please do not use compatibility mode other than to make sure it states at the bottom that the program should always start up in admin mode for all users.

 

When you installed the Wilco 737 PIC, did you right click the installer and select, run as administrator?  Did you have UserAccessControls (UAC) disabled?  Was any anti-virus program running during the install.  Many anti-virus programs will look at old programs like the Wilco 737 PIC and give false positives indicating there's a trojan or virus.  There is no trojan or virus and it is safe to install it.  So any anti-virus program should be disabled during the installation of known products, like the Wilco 737.  You might look in the quarantine section and see if a file or registry entry was quarantined.  Malware programs like MalwareBytes will find "Malware" too and quarantine what it thinks is malware.  So you need to disable any malware program too.

 

Look in your Event Viewer for an Event.  See page 2 of the AVSIM CTD Guide (link in my signature) for instructions.  You can also download and run AppCrashView and it will show you all of your crashes since you installed Windows.  See page 1 of the guide for the link and instructions.

 

Best regards,

Share this post


Link to post
Share on other sites

Thanks for the quick reply.  From the Event Viewer there are at least three different events...two appear to be related to 737 PIC as shown below.  I will try uninstalling and re-installing as an administrator with virus protection disabled.

 

Most common errors  related to 737 PIC --

 

Clipboard01.jpg

 

 

Clipboard02.jpg

 

 

Clipboard03.jpg

 

Clipboard04.jpg

 

The only one that does not appear to be related to 737 PIC is this one --

 

Clipboard05.jpg

 

Clipboard06.jpg

 

Share this post


Link to post
Share on other sites

Per the AVSIM CTD Guide:

 

NTDLL.dll – Several possibilities as follows:

  • 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.
  • System overheats or you have wrong timings/voltages set for your installed RAM or CPU voltage. 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.
  • Check your dll.xml for duplicate entries or any corruption.  Some have fixed the NTDLL.dll CTD by removing duplicate entries and/or old software entries where the software is no longer on your system.
  • Disable User Access Controls (UAC) (see the section above for more information).
  • Update hardware drivers for your computer (especially on new computer systems) (see Driver Update information in this guide).

I can cause an NTDLL.dll crash to occur 100% of the time if I raise my overclock above 4.3GHz.  Lower to 4.2GHz and the crash goes away.  I used the auto settings for the overclock and obviously, my CPU or DRAM voltages were too high or too low.  Some have also fixed this crash by lowering some of their settings.

 

Your other errors regarding the gauges was probably caused by not having the proper permissions to use them.  You should always start up FS9 with Admin Privileges.  You can do this by going into the FS9 main folder and right clicking on FS9.exe and selecting properties.  Once open, click on the compatibility tab and look near the bottom and make sure it states to start up the application with admin privileges for ALL users (not just you).  You should also look up each one of those gauges and right click the gauge, select properties and make sure it shows that the gauge can be shared.

 

Next, you need to make sure your user access controls are disabled.  The new operating systems have tons of security and they prevent certain files from loading.  If your aircraft is calling for a gauge and your system won't let you have access, then there's a problem.

 

I would uninstall the aircraft and then reinstall it.  Make sure when you reinstall it that you right click the installer and select "Run as Administrator".  Make sure any anti-virus program and the UAC have been disabled too.

 

Best regards,

Share this post


Link to post
Share on other sites

Just curious, I notice your FS9 still says version 9.0 in one of the event logs.  Don't know for sure, but don't the Wilcos require 9.1 update version?

 

Perhaps that could be it.

 

Randy

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this