Getting back in the saddle again after several months--Problem: I have the terrific KPDX scenery from Flightzone but it's causing consistent CTDs generally at 10nm out and around 3000 feet. I have all the UT patches and KSEA patch. I run KPDX (#2) right below AES (#1) and above KSEA/then SEA photo. I've messed with the order etc, and no luck. CTD applies to all aircraft. Memory is good. I run scan AFCAD and have no duplicate KPDX AF2.bgls.

 

No problems if I start in KPDX and depart out. Only happens on approach.

 

I've searched previous posts and most conclude it's likely a duplicate AFCAD--which I've checked for.

 

Any solutions?

 

THanks!

 

System specs: Intel i7 at 3.8ghz, 6GB DDR RAM, NVIDIA GTX 285, Raptor HD 10000rpm. Vista 64-bit.

Have you tested this with all AI turned off? Sometimes CTD's can be caused by bad AI aircraft textures.

I don't use any AI. I use VATSIM (squawkbox) exclusively.

 

RP

Hi. Try to use procmon to see what is missing. I don't have any problems with KPDX.

 

Sent from my MT15i using Tapatalk 2

 

 

Edin

 

Thanks...what is procmon? Is it a utility for FS9? Where can I find it?

 

Thanks!

 

Rich Perry

The only time I had a CTD from this software was when I put in an updated AFCAD. I removed the new AFCAD and didn't pursue the problem. It has been fine since then.

Sounds like you have a corrupted texture in "World Texture" folder. Try reinstalling those textures from the FS9 cd4 disc.

What is the error message? Do you have the FS9.1 patch installed?

 

Go into your Windows Control Panel and get into Admin Tools. Look for the Win Event Manager. See if you can spot any errors about the the time of the Win Crash.

 

Another question is are you switching com frequencies at that point? In some situations a repeated earlier same com frequency can cause an FS crash. This was supposedly fixed in FS 9.1.

 

With VATSIM you are not using any utilities that render AI around you, correct?

 

Can you successfully approach an airport nearby in the same area? Can you land at KPDX without using VATSIM but using the same approach path? If not then there could be a texture or other modelling issue as more detail gets rendered as you get closer.

 

FS9 AI atc is always running in the background even if not selected. If you happen to be a registered user of FSUIPC3 you can turn it off by adding to the general section of FSUIPC.ini (back it up with a safe copy outside of FS first):

 

//RemoveATC=Yes//

 

but with out the ""//" pairs that make it ineffective. This was added for VATSIM users and other third party ATC apps like RC.

 

procmon is a very techie thing that stands for process monitor and creates a log of running Win process events I believe. It is free at:

 

http://technet.microsoft.com/en-us/sysinternals/bb896645

Hi.

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.

You can download from http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Check also this forum:

http://forum.aerosoft.com/index.php?/topic/19147-ooms-ctds-and-maybe-more/

You should make a filter to only check fs9.exe and include = FILE NOT FOUND.

Usually when You have missing texture, You will have memory leak which will result with CTD or OOM message.

Sorry for late reply.

If You send me email (on PM) I can check my settings of Proc mon

 

Regards

 

Edin

I reinstalled KPDX from Flightzone and no more CTDs on approach. As suggested, I believe a file must have "gone missing" or duplicated somehow, but the reinstall cured the problem. Thanks for the procmon info--that will be very helpful in the future.

 

Rich Perry