After purchasing of a new computer a year ago:Dell Duo Core 2.66 1333FSB4gigs RamNVIDIA GeForce GTS 250 w/1gig Memory I'm finding the same issue I saw with my old 2.66HT model I bought with when FS9 first came out. This nagging CTD issue when flying into or over the New York area especially KLGA. On my old box I had AI down to 50%, the new box has AI set to 95%. Here's a list of Add-ons for the area:Imaginesim's KEWRImaginesim's KLGALago's Manhatten SceneryFSDreamteam's KJFKI have a mixture of World of AI and Ultimate Traffic with the appropriate airlines disabled in UT for the newer WOAI traffic. I've tried everything from turning off scenery to totally shutting down AI and still the same issue. If I leave out from New York there's no issue but flying to and/or over the area can cause CTD's. The CTD's don't happen in the same spot and what surprised me on a flight the other day was I was approaching the area not yet near or over NYC and had a CTD. This makes no since and it's hard to find a answer for it. So I'm just wondering has anyone else had issue with the New York area in turn we all could put our heads together with various things we've seen and figure out once and for all what the heck is going on...

Up until you mentioned it wasn't in the same spot I was thinking bad AFCAD after suffering the same problems in KMEM.Changing the AFCAD solved my problem.Could it possible be a texture problem?I have the same addons as you with the exception of Lago's Manhatten Sceneryand have no problems in NYC.I know there was an article I recently read about duplicate textures causing CTD's.Maybe worth a shot.

Finding a bad texture is like looking for a needle in a hay stack. I saw a post on FSDreamTeam's site about the issue with their scenery but they have since released replacement, lower sized textures to solve the issue. I have those newer textures installed. Yesterday I wasn't even facing KJFK when FS9 crashed, the day before I was, the day before that on approach to the NYC area I had a CTD in which KJFK hadn't even came into my field of view yet.

I don't have Imaginesim sceneries, but I get CTD in the NY area sometimes, and like you only when I approach that area......I've the free KEWR, and free Manhattan, none of them are the cause, and none of your scenery are your cause.CTD to me happens only if I flight to that area with some type of aircraft, I had the posky 777, and with Alitalia texture and other, first i get a blurried texture then the CTD, with other aircraft I never get CTDs, neither with alitalia posky 777 out of the NY area.I guess there is something wrong with the base scenery or because the area is crowded of objects... not sure only guessing, but when I have to fly to NY I am always scared about random CTDs... only that area....

Finding a bad texture is like looking for a needle in a hay stack. I saw a post on FSDreamTeam's site about the issue with their scenery but they have since released replacement, lower sized textures to solve the issue. I have those newer textures installed. Yesterday I wasn't even facing KJFK when FS9 crashed, the day before I was, the day before that on approach to the NYC area I had a CTD in which KJFK hadn't even came into my field of view yet.

Sounds like you may have a bad AI texture. This will cause a CTD when the offending texture is within range, regardless of which direction you are facing. If it involves an airline with a light schedule into the NYC area, it would explain why you are sometimes seeing the CTD and other times are not.A quick test would be to move all of the WOAI folders and any other schedules you have in the world\scenery folder. Test and if you CTD, then it must be an AFCAD, scenery texture, or user aircraft texture. If not, it's an AI texture.I know it's a PITA to find the texture because I'd had to do it with hundreds of AI schedules. You can zero in very quickly by working with halves. Add half back in and test. If OK, add in half of the remaining and test. When you get the CTD, remove half of the set you added and test. Continue until you are down to the schedule causing the CTD. From there, it's a matter of finding the aircraft(s) causing the problem.In one instance I had 2 separate schedules causing the CTD at one airport. After that episode, I carefully screen the AI textures to make sure they are good before I install.Bruce

After purchasing of a new computer a year ago:Dell Duo Core 2.66 1333FSB4gigs RamNVIDIA GeForce GTS 250 w/1gig Memory I'm finding the same issue I saw with my old 2.66HT model I bought with when FS9 first came out. This nagging CTD issue when flying into or over the New York area especially KLGA. On my old box I had AI down to 50%, the new box has AI set to 95%. Here's a list of Add-ons for the area:Imaginesim's KEWRImaginesim's KLGALago's Manhatten SceneryFSDreamteam's KJFKI have a mixture of World of AI and Ultimate Traffic with the appropriate airlines disabled in UT for the newer WOAI traffic. I've tried everything from turning off scenery to totally shutting down AI and still the same issue. If I leave out from New York there's no issue but flying to and/or over the area can cause CTD's. The CTD's don't happen in the same spot and what surprised me on a flight the other day was I was approaching the area not yet near or over NYC and had a CTD. This makes no since and it's hard to find a answer for it. So I'm just wondering has anyone else had issue with the New York area in turn we all could put our heads together with various things we've seen and figure out once and for all what the heck is going on...

To you have Ultimate Terrain installed BTW?

I carefully screen the AI textures to make sure they are good before I install.Bruce

Just curious how you go about this?regards,Joe

If it involves an airline with a light schedule into the NYC area, it would explain why you are sometimes seeing the CTD and other times are not.A quick test would be to move all of the WOAI folders and any other schedules you have in the world\scenery folder. Test and if you CTD, then it must be an AFCAD, scenery texture, or user aircraft texture. If not, it's an AI texture.Bruce

At this point CTD's are not a 'sometimes' affair, it's all the time when flying into NYC. I switched from using my Maddog 2008 model to Feelthere's A320 and the problem still persists. With the A320 I at least get to the terminal versus the CTD on approach. Both birds are suceptable to the CTD on approach to the NYC area.Another thing like what was said above in order to test all the WOAI files I would have to remove a bunch, jump in and fly in real time to NYC and then see if the sim crashes. I can load up NYC and sit there for hours without a single CTD. I can fly out of NYC for the most part and have no issue. I can even slew to NYC and not experience a CTD. I really hate problems like this that's why I'm hoping it's not a AI texture file. Another thing to note even if it was I should have this problem at other airports. I'm only seeing this around the NYC area.

To you have Ultimate Terrain installed BTW?

Nope... Didn't like what it did to Hawaii...

AI texture corruption is an always affair if the exact same conditions can be replicated. It either occurs because the bad texture spawns at a local airport, or the aircraft is in the local proximity to your location, either as an overflight or an arrival at an airport.You say you only get the crash when flying into NYC and not when starting from NYC. Also, crashes occur at various stages of landing. What I don't see in your descriptions are confirmations that the exact same time of day on the same date was tested in each scenario. Even if you tested one day apart at the same time of day, you may not see the same AI traffic as some airlines do not fly daily schedules.If you don't want to mess with your AI files, the easiest test is to save a flight on approach to NYC when you have not crashed. The saved flight will then allow you to test under identical conditions other than aircraft type. If you get inconsistent results under those settings, then it's not an AI texture issue, but more likely a scenery issue, either AFCAD or scenery texture being loaded.

Thanks Bruce... I think I'm leaning towards something wrong with one of those WOAI packages. The add-on scenery for the area seems fine after some testing... I CTD's with or without all add-on scenery active.

Looks like these CTD's all depend on the area I depart from. From a high intensity airport add-on like FSDreamteam's KORD there's most certainly a CTD in the New York area upon arrival especially when an add-on like Leonardo's Maddog 2008 is used. At times I may make it with a lesser add-on like Wilco/Feelthere's A320 but a CTD is always possible from KORD no matter what aircraft I use. Taking off from airport's like Blueprint's KMSP or CYYZ there's no issue in the New York area again especially with add-ons like the aforementioned Airbus or E-Jet series. From high intensity areas like the Los Angeles bason from KBUR (JetBlue Wilco/Feelthere A320) there can be a CTD especially with the arrival time is at dusk or heavy weather. I also found on occasion flying over intense airports can cause CTD's. When I fly from KRSW on my way to KMSP when flying over KORD I get a CTD on arrival at KMSP (right after landing or before). Now in context I feel the KRSW problem is unrelated to the New York problem just the same I may be on to something. Can anybody confirm a flight from an intense airport into the New York area causes problems? I found KJFK not to be as intense of an issue like KLGA because of the proximity to Lago's Manhatten and KEWR. So a flight form EGLL to KJFK may not be a problem in most cases. It's flights from locations like KATL to KLGA that pose an issue (maybe one day FSDreamteam's KDFW to KLGA). I need to test a flight from Simflyers KIAH to KLGA and see if there's an issue. Either way it's interesting to see an airport thousands of miles away saved in upper memory can affect a location like the New York area. In a way it's like when taking off from New York affects the ground textures at many other airports. Upon landing there's texture ripping as if the flatten switch stopped working for the scenery all because the flight originated in New York. For some reason the New York area more than any other location seems to be a real problem child in Flight Simulator (both FS9 and FSX).I'm currently testing a flight from KATL to KLGA to see if I have an issue...

Can you identify the DLL responsible? This would help analyse the situation considerably.If you are not sure how to, please see http://www.adventure-unlimited.org/faultfi...php#Identifying .John

Can you identify the DLL responsible? This would help analyse the situation considerably.If you are not sure how to, please see http://www.adventure-unlimited.org/faultfi...php#Identifying .John

I'm going to use either 'Process Monitor' or 'File Monitor' to see what's going on. As of now I've nailed down this is caused by taking off from a location heavy with traffic and flying to NYC. The system as of now just locks up. There is no option to restart FS9 and/or the window like you've shown above. A few minutes ago I had to hard power down my system to get going again. The whole system was frozen. Other times I get an out of memory error but that's about it. I'm curious to know which one of these programs will actually point to the culprit 'file':Process MonitororFile Monitor

Do you have all of those add-ons active in the NY area all the time? My suggestion would be to isolate the issue by starting with one add-on at a time in NY and go from there. If there is no testing methodology then you are pretty much hoping for the needle in the haystack. So KISS (In Computer Troubleshooting terms Keep It Simple Stupid) and start with the lowest common denominator. That is one of the first things you learn in IT. Can you disable the add ons and fly to NY? If so great, if not it is a default or base level issue and you are really going to have a tough time tracking it down. If you can then add back a single airport and fly to all 3... All good, Disable that one and add the next lather rinse repeat. I have all of the same add-ons but only activate the two add-on sceneries I am using prior to my flight to help keep FS lean... So I never have JFK, KEWR and LGA active at the same time. All of my add ons are disabled unless in use... Once you change your thinking with FS to only use what you need at any given point opposed to load everything under the sun your probability of error decreases exponentially. At least that is my experience.Good luck with your troubleshooting.-Paul

I'm going to use either 'Process Monitor' or 'File Monitor' to see what's going on. As of now I've nailed down this is caused by taking off from a location heavy with traffic and flying to NYC. The system as of now just locks up. There is no option to restart FS9 and/or the window like you've shown above. A few minutes ago I had to hard power down my system to get going again. The whole system was frozen. Other times I get an out of memory error but that's about it. I'm curious to know which one of these programs will actually point to the culprit 'file':Process MonitororFile Monitor

OK, fair enough, but you have described this as a "Crash to Desktop" throughout whereas you are now saying that everything freezes up.If you are getting occasional Out Of Memory errors this could well be related to large amounts of add-on scenery rather than AI traffic. But I am confused as to your descriptions - you have said it always occurs approaching NYC and also that it is caused by is caused by taking off from a location heavy with traffic and flying to NYC.I would be looking at temporarily disabling all add-on scenery in the area (including mesh and landclass) and all AI traffic to try and pin the circumstances down.John