FS9.1 is 'crashing' on a saved flight close to Seattle. Within 10 seconds of loading it the sim 'crashes' but unfortunately the error report cannot identify the file or event responsible.I'd heard of FileMon being helpful in these cases but it's no longer available. Process Monitor has now replaced it. I've installed it and have filtered for just FS9.1 events. I have a saved log which hopefully someone will help me with. I can't upload it unfortunately.Two entries that stands out are: -FAST IO DISALLOWED relating to a file in Username\Local Settings\Temp. BUFFER OVERFLOW with a Registry address shown.If, with someone's help, I can identify the files that are causing the problem I hope things can be fixed. My FS9 installation is over 5 years old and has so many addons I dread to think how long it would take to reinstall everything. This 'crash' is easily reproduceable and I only have this problem around Seattle. I'm hoping it's just a corrupt file.Thanks for any help.Process Monitor can be downloaded from here. http://technet.microsoft.com/en-us/sysinte...s/bb896645.aspx

FS9.1 is 'crashing' on a saved flight close to Seattle. Within 10 seconds of loading it the sim 'crashes' but unfortunately the error report cannot identify the file or event responsible.

Have you tried with a fresh flight? Saved flights can sometimes cause a problem if there have been changes made to the setup since the flight was saved.John

Have you tried with a fresh flight? Saved flights can sometimes cause a problem if there have been changes made to the setup since the flight was saved.John

Hi John,The problem originally occured on a flight from Honolulu to the UK. I setup a flight out of KSEA and headed WNW. Within 10 minutes I had the crash. I reflew it and saved the flight just before the crash to make reproducing it as easy as possible.My guess is that it's a bad (texture) file and I was hoping Process Monitor might point me to it but to my untrained eye it hasn't. I have flown Heathow - Singapore without problem so this is a problem in a very specific area.Process Monitor is a great tool but without the knowledge of how to read its output my analysis is a bit limited. I'm hoping an expert can come to my rescue.

Hi John,The problem originally occured on a flight from Honolulu to the UK. I setup a flight out of KSEA and headed WNW. Within 10 minutes I had the crash. I reflew it and saved the flight just before the crash to make reproducing it as easy as possible.My guess is that it's a bad (texture) file and I was hoping Process Monitor might point me to it but to my untrained eye it hasn't. I have flown Heathow - Singapore without problem so this is a problem in a very specific area.Process Monitor is a great tool but without the knowledge of how to read its output my analysis is a bit limited. I'm hoping an expert can come to my rescue.

If it is bad texture, Flight Simulator will normally identify the fact. Without knowing the dll file that caused the crash it really is impossible to guess what the problem is.Are you actually getting a Flight Simulator error message or is this one of those meaningless messages generated by Vista? If Flight Simulator exits without any error message of its own, the problem is usually attributable to something external - software or drivers.John

If it is bad texture, Flight Simulator will normally identify the fact. Without knowing the dll file that caused the crash it really is impossible to guess what the problem is.Are you actually getting a Flight Simulator error message or is this one of those meaningless messages generated by Vista? If Flight Simulator exits without any error message of its own, the problem is usually attributable to something external - software or drivers.John

Hi John,Yes, I get the standard "FS has encountered a problem" message but when I click on More Info it say's "unknown" against the source of the problem. All the scenery files for the area seem to have been loaded as Process Manager lists the areas loaded a few seconds prior to the crash.The fact that it always happens around Seattle whether after a few seconds of flying with a saved flight or hours into a long-haul suggests a problem with FS - not with drivers etc. It's extremely frustrating and I really don't want to resort to a rebuild for the sake of one bad file which you would think could be identified by Process Mgr.For now I'm just avoiding Seattle. BTW, I'm still with XP.

Hi John,Yes, I get the standard "FS has encountered a problem" message but when I click on More Info it say's "unknown" against the source of the problem. All the scenery files for the area seem to have been loaded as Process Manager lists the areas loaded a few seconds prior to the crash.The fact that it always happens around Seattle whether after a few seconds of flying with a saved flight or hours into a long-haul suggests a problem with FS - not with drivers etc. It's extremely frustrating and I really don't want to resort to a rebuild for the sake of one bad file which you would think could be identified by Process Mgr.For now I'm just avoiding Seattle. BTW, I'm still with XP.

Thanks Ray. It is very difficult to know what to suggest is causing it, but you could certainly try disabling all add-on scenery in the area, disabling all AI traffic, disabling any add-on mesh or trying the same situation with a different aircraft (one each at a time) to try and narrow down the problem. It is possible that any one of these may be clashing with a driver. I would certainly check the video driver for updates and DirectX too, to make sure they are fully up to date. You could also experiment with that saved flight using a different screen resolution.Hope this helps,John

Thanks Ray. It is very difficult to know what to suggest is causing it, but you could certainly try disabling all add-on scenery in the area, disabling all AI traffic, disabling any add-on mesh or trying the same situation with a different aircraft (one each at a time) to try and narrow down the problem. It is possible that any one of these may be clashing with a driver. I would certainly check the video driver for updates and DirectX too, to make sure they are fully up to date. You could also experiment with that saved flight using a different screen resolution.Hope this helps,John

Hi John,It's a real pain and thanks for your suggestions. There has to be something unique about this area because I fly extensively to different continents and haven't encountered this elsewhere.I didn't mention it earlier but I also have FSGlobal 2005, Ultimate Terrain and Ground Environment installed. IIRC these replace the default ground textures and mesh which makes the problem all the more baffling. I did reinstall GE a year or so back after other FS crashes but the error message clearly pointed to a FS-related file. This problem doesn't.If I was getting the crashes elsewhere I would suspect drivers etc. but it's just around Seattle. Changing aircraft and disabling Ai is easy enough so I'll certainly try doing that, thanks. I have DX9.0c which I believe is the latest version for FS9.Whilst having a program like Process Monitor is great it's not much use if you can't decypher what it's reporting! :(

Hi John,I've registered on Microsoft's SysInternals forum and posted my log. Hopefully someone will be able to spot the problem.What I think I'll do is to fly towards this point NW of Seattle from all 4 directions to try and ascertain the size of the area affected. Once I have those coordinates there might be a way of identifying which file or files cover than area. That might give me my 'bad' files.More during the week.

Here's a depiction of the 'crash' area using FSNavigator to define 4 points in space where the crashes occur. It's such a small area. Could it be just one rogue file? The named 'waypoints' are just the heading of the aircraft at the time of the crash.

Do you have WOAI airlines installed? I'm having the same problem in the New York area all but preventing me from landing at KLGA with certain aircraft. I've never been able to figure it out. Another thing to look at is your departure airport. Try flying to Seattle from different locations and see what happens. Your area is Seattle, another area mentioned by someone else is Rio, mine is the New York City area. This is becoming a real problem and if the general consensus turns out being WOAI aircraft at least we all can collectively pin down where to start looking... Right now it's anybody's guess as to what's going on.On a side note you 5 year old install of FS9 has nothing to do with it. I just reinstalled FS9 a year ago when I bought my new machine. The problem that was there before is here again. Something is going on and it's going to take an effort from everyone who's seeing this to figure it out. Again I'm leaning toward some of WOAI's airlines as being the problem.

Hello. Regarding WOAI, although I do do not have any of their packages installed so I'm not completely familiar with the aircraft models used, I would like to share a observation from a while back. When flying into or around KDEN I would get a CTD, no error message, nothing. After a serious amount of checking and testing I finally located the problem. My particular GPU, enhancer and FS9 setup would crash anytime I came into visual range of a 'old' Project Ai DH8, but only if the Ai paint on the model was in 32 bit format. Frontier / Lynx Flight plans with the DH8C 32 bit textures, crash to desktop. When I changed the textures to DXT3 no problem. With the newer TFS DH8's either seem to work well. Since there is no new DH8a-b yet, who knows? Just a thought.A few additional thoughts:Check scenery for proper scenery and landclass layering and check for duplicate AFCADs (SCANAFD, available here on AVSIM)If you have disabled all add on scenery and all AI traffic that leaves you with only a few causes. If you have terrain mesh for the KSEA area installed, please try temporarily removing that (possibly corrupt BGL). Next make a backup of the FS9 main texture folder and a backup of the FS9 Scenery\World\Texture folder and temporarily replace them with the default files from your FS9 disks. Try your KSEA flight with a default aircraft and no additional FS programs running. If you have no problem then just start one support program at a time and test again. Then one texture folder and test, then the next. This will help you by process of elimination to isolate the file(s) causing the crash.I hope this helps you out some.Good luck, Mel

Silly question time.Do you have VOZ installed and if so what version?regards,Joe

Do you have WOAI airlines installed? I'm having the same problem in the New York area all but preventing me from landing at KLGA with certain aircraft.

Sorry, no. I have Ultimate Traffic, about 5 years old. I haven't flown into this area with no Ai enabled but I don't think it would cause the crash. It would be strange indeed if one livery caused the problem that never existed in any other major US airport. And looking at that area it's outside KSEA. If it wasn't then I'd be very suspicious.

On a side note you 5 year old install of FS9 has nothing to do with it. I just reinstalled FS9 a year ago when I bought my new machine. The problem that was there before is here again. Something is going on and it's going to take an effort from everyone who's seeing this to figure it out. Again I'm leaning toward some of WOAI's airlines as being the problem.

But my 5 year install has involved 3 different PCs. :( I installed a skeleton version on each new PC, renamed it and then moved my monster install to the new PC. But everything works. I suspect a FSGlobal texture. I might reinstall that or if I can identify which files populate that part of the world just replace those.Good luck with your problem but I think it's a different one to mine.

A few additional thoughts:Check scenery for proper scenery and landclass layering and check for duplicate AFCADs (SCANAFD, available here on AVSIM)

I have ScanAFD and have no duplicate airports. Good idea though, thanks.

If you have disabled all add on scenery and all AI traffic that leaves you with only a few causes. If you have terrain mesh for the KSEA area installed, please try temporarily removing that (possibly corrupt BGL). Next make a backup of the FS9 main texture folder and a backup of the FS9 Scenery\World\Texture folder and temporarily replace them with the default files from your FS9 disks. Try your KSEA flight with a default aircraft and no additional FS programs running. If you have no problem then just start one support program at a time and test again. Then one texture folder and test, then the next. This will help you by process of elimination to isolate the file(s) causing the crash.I hope this helps you out some.Good luck, Mel

I haven't disabled all scenery in my most recent tests. I did do something along those lines when this first starting happening a year or so ago but got fed up and decided to avoid the KSEA area. But it's like having an itch so although it's not causing serious inconvenience I would like to get to the bottom of it. And with over 150 scenery layers it would be a big job to disable, test and then enable / disable repeatedly.I have no 3rd party airport scenery for that area. The only thing that is different is GE and FS Global. I doubt it's Ultimate Traffic as any bad aircraft would crop up elsewhere.The problem of running without any extra FS programs is there are quite a lot of modules that I've added over the years. But if it was these why would they not cause crashes elsewhere? Same goes for disabling the world scenery. This is a very small area and I suspect it's a single tile - either mesh (FS Global) or terrain (Ground Environment). I reinstalled GE when I had problems elsewhere in the world so I'm sure that is okay. And those error messages were quite different to this one.I'm going to make a backup of the entire FS9 and then reinstall FS Global unless I can identify which files make up the mesh in that area. I'll write to the FS Global support team first and if that doesn't help then I'll reinstall FSG.Thanks.

Silly question time.Do you have VOZ installed and if so what version?regards,Joe

The name rings a bell. Is it the Australian scenery? I did have it for a while but uninstalled it as it wasn't possible to install for the whole of Oz. Is that known to cause problems thousands of miles from the area it covers?

Ray,In Process Monitor, look for anything that says "NAME NOT FOUND" along with a *.bmp associated with it. That would be your missing texture that will cause a CTD. I've had it a few times in Southern California and traced it to a missing road texture using Process Monitor. No more CTD after fixing the problem!! ;)If it isn't a missing texture, the last loaded *.bmp file will be the corrupted file causing the crash. This helps finding a bad AI texture (in most cases).