Noncon

I get this occasionally on my 3-series gpu using the Nexus mod - usually after shifting views. If I go into MSFS graphic settings and toggle the frame gen mod (off/on), return to the cockpit in it is smooth again.

I bet he still finds a way to help many of us even from heaven! My condolences to his family, strength be with you. KJ

I had that problem when I tried to run FS Force to get the force feedback working on my joystick on Win7 64. I had to uninstall that software to cure the problem. Mine would also freeze during takeoff, going from taxiway, to the runway. A few more suggestions: video card driverssystem over heatingWindow 7 power management settingsAs a last resort, update to the latest BIOS <--this worked for me with another fs9 freezing problemKJ

Its a problem in your registry. Specifically something about the pathway to FS9 in one of the registry entries is off. I had the same problem with the PMDG, and had to search my entire registry before finding one entry that had the pathway (.../Microsoft Games/Flight Simulator 2004) that was incorrect, can't remember the location. In hindsight, I probably could have run a program like CCleaner and let it fix registry errors.KJ

I can't tell if you did re-installed fs9 from the CD, or copied the files from another computer. However, try going to the Sound folder in fs9 root directory, and replace both the *.gvp files. You will have to copy them from the fs9 CD. Both are located on Disk 2, one is in MSGAME4.CAB the other MSGAME5.CAB.KJ

What type of frame rates are you seeing? The delay could be the result of low-end system performance. KJ

I'm not sure what process you are referring to. When you close FS9, is the task (as seen in Task Manager) still running? Either way, there is no connection between a hanging process and a fragmented hard drive. KJ

Start with the default Cessna, turn everything off except the Avionics switch. Then switch to the PSS, and if you want you can save the flight at this point and use it as you default PSS Cold and Dark flight. KJStart with the default Cessna, turn everything off except the Avionics switch. Then switch to the PSS, and if you want you can save the flight at this point and use it as you default PSS Cold and Dark flight. KJ

In CCC try setting key command to turn on AA. Back when I had a ATI card, in some cases I could set AA from CCC, but it would reset in 3D. The work around was going into the game, then use the key command to turn on AA. KJ

You really should start fs9 then select the desired flt. Especially using Windows 7 with its oddities of installing outside Program Files, Run As Admin, UAC etc. By the way I tried the same thing, got same corrupt message. I'm using Win 7 64. KJ

Active Camera use to cause double fs.exe to run. There was an update that fixed this years ago. If you use AC make sure it is the latest version. KJ

That is because Nvidia cards (for the most part) won't enable AA in Flightsim, via its Control Panel without nHancer. Even then, it won't work using the Default profile in nHancer, you have to create a new profile for FS.If you are using the newest Nvidia drivers, you need to install the Nvidia software (the name escapes me) instead of nHancer. KJ

If both ASE and ASA are on the same system, I suggest un-installing both. Then install ASA and see if it runs, if so install ASE. Perhaps the two programs don't play well together on the same system.KJ

Try increasing the Null Zone for the joystick. On some Wilco planes, even when it seems like the Autopilot is engaged, it will wander off course if the joystick isn't perfectly centered. Better yet, try disabling the joystick during flight to eliminate it as a possible source. KJ

In Control Assignment, make sure the entry for the Rudder says something like "Combined Pedals"KJ

Try renaming your fs9.cfg file. Upon startup, fs9 will rebuild this file. KJ

IMO, Yes. KJ

Looks good, but it is missing RWY 11/29, but an updated AFCAD here in the library should take care of that. KJ

You might see some benefit from an upgraded video card (e.g. GTS 250). KJ

Try updating/changing your video card drivers. KJ

If the blue screen keep occurring, you might need to bump up your memory voltage. I would suggest going to your memory mfg help forum, give them your configuration, and they can tell you if you need to make some voltage adjustments in the BIOS. KJ

Not sure if the above included making sure you don't have any empty Texture folders in the Addon Scenery folder. KJ

I would suggest you calibrate in FSUIPC, just to make sure you are getting full-travel from rudder. KJ

The first thing to do, is to create/save a Flight using something like the default Lear. This flight should be saved just prior to where the CTD occurs, so you can repeat the flight while troubleshooting the problem. After that, it is process of elimination. Start by turning the Graphics down to the minimum, this troubleshoots Autogen scenery problems.If it still CTD after this, try going to Addon Scenery Library and disabling all but the basic Addon SceneryIf it still CTD after this, try renaming the Scenery folder in Addon Scenery, this will troubleshoot a bad AFCAD file. It starts getting ugly after this, when you have to try to Troubleshoot a bad Module in the Module Folder, or something in the Aircraft folder. Reinstalling and carefully exporting the old files to the new installation till you find the problem works too. KJ

Is there an error message?Check your fs9.cfg file for "SITUATION=" and see if what is entered there is a valid path. I believe the default location is C:\Users\<your name>\Documents\Flight Simulator FilesMake sure you are start fs9 in Administrator mode. Just in case it is a permissions issue, where it can't write to the folder location. KJ