Very recently I started to get CTDs. It doesn't happen all the time and it is not plane specific. Normally CTDs about 5 - 15 mins into the flight, around KSEA and KJFK so it's not just one area. Does this sound like it's related to corrupted AI textures? What would be your first suspect?Is there a tool that can scan corrupted files? How do you track down a corrupted texture file?Thanks in advance.

Well, like always...need more info first.Have you changed, installed, edited, something recently? Anything?What are your PC/Add-on specs?Do you get an error message, or is it jsut a Crash to desktop?, freezes at all?If you do think its a corrupt file, im not sure if there is a program that actively scans for corrupt files, but you can use something like FileMon to see what files are being read during CTD.Like wise, if its something with the system, you can go to Event Viewer under admin tools and see if theres a message with details on crash.

Hi Red thanks for the reply. First thing first, in event viewer of all the CTDs I had in the past few days some point to d3d.dll and the rest to rxpsrv.dll. All the error reports also included scenery.cfgI can't say I didn't change a thing in my FS recently although I only do very small changes to it these days. For example I installed HDE v2 and also played with the bloom effect, I also installed a new level-d livery. I have since backed out of everything I could remember that I did recently and couldn't determine that the CTDs were caused by any of them. Here I want to say that it is definitely not the HDE v2. CTDs happen to me with or without these textures.So far the biggest lead I have is those two dll files and scenery.cfg, but they don't give me a definitive answer either. The basics of my PC and FS setup is windowsxp pro 32bit, E8400 o/c'ed to 3.78ghz, 4gig ram no 3g switch used, 275GTX, case clean and well ventilated, 4 case fans and an after market CPU fan keep everything cool. FS9 kept fairly clean and neat with very few addon scenery, UT canada and US, FSGlobal mesh, GE pro, latest FSUIPC registered, both RXP GPS, custom AI traffic, and an fair amount of aircraft addons.Using filemon to monitor is a good idea. I've just started to do so although I have not been able to reproduce a CTD since. It seems to happen less now, although I'm not convinced that it will not come back again.

Hi Red thanks for the reply. First thing first, in event viewer of all the CTDs I had in the past few days some point to d3d.dll and the rest to rxpsrv.dll. All the error reports also included scenery.cfg

It is very hard to pin down things like this when FS gives you a range of causes, the following may help. It is probable you only have one issue but this is upsetting the others.1. d3d.dll is a DirextX driver and not specific to Flight Simulator, it could be worth checking your DirectX is fully up to date.2. rxpsrv.dll relates to Reality XP addons, gauges I think. Some of these are known to cause problems in Flight Simulator although they generally attribute the problem to util.dll . It would be worth checking to see if your failures only occur when using these gauges.3. scenery.cfg errors are something I have been reading about just recently but have no personal knowledge of. It is suggested that entries may have become corrupt or wrongly numbered to cause this. It could be worth (after taking a backup) whittling the scenery.cfg down to your basic FS entries and testing it in that form. If that's OK, try adding your add-ons a few at a time (using the scenery library, not by hand) and this should help a) check if any specific sceneries are causing your issues, and b) ensure the library is numbered correctly.Best wishes,John

Hi,Do you run FS9 in full screen mode? I always had random CTDs when I used FS in windowed mode but it seemed to stop when I used full screen mode. This is pretty irregular as thousands of people run it in windowed mode with no problems.Dave

http://www.adventure-unlimited.org/faultfinding.phpCheers!

That link is very informative thanks.Yes I always run FS9 in full screen mode.So far as I can remember this always happened in my RXP GPS equipped planes. I have a lot of them. I'm not yet to say the GPS is the root cause but certainly is part of this. I had like less than 20 rather simple airport scenery addons. I have since removed and deleted most of them and cleaned up the scenery.cfg file. That seems to have helped the most. I flew two flights last night without being about to induce a CTD. I will report back if and when I get another one. Thanks guys.

Another CTD. This time it's sim1.dll. My sim1.dll is the original without any mod. Filemon shows that the last files FS9 was accessing include the basemap.bin of the RXP 530 and some scenery files of a particular airport addon I have installed in that area. Filemon shows no error in access those files but then the nvidia services and directx went nuts according to the list and that's when my FS crashed.