Disable the scenery in the scenery library and try another identical approach at the same day/time. This should help to prove if it is scenery or AI that is the problem. A new computer wont help.

 

If you still crash then it is likely AI texture.

Ok I think I might have solved the problem. I just finished a 1 hour flight from PAlma de Mallorca to LEMD and everything went fine, the FS did not crash.

 

What I did - I looked through ! all ! the AI aircraft folders in search for mistakes in aircraft.cfg files. I found in a few that sometimes the [flightsim.x] sections were not in proper order or the number were duplicated.

But I don't think that these mistakes were causing the problem, because I'd been flying without any problems with these cfg files.

 

What in fact might have caused the problem - In CRJ900 folder there were 5 texture folders (adria airways and air nostrum). The [flightsim.x] section in aircraft.cfg was one big mess. The numbers were duplicating - I think it was like 0,1,1,2,2 - and in addition, there were mistakes in the sections 'texture=x'. The names of the folders with textures that were entered into 'texture=x' were totally wrong. I think I put 'texture=air nostrum' while in fact the texture folders with nostrum liveries were called "texture.air_nostrum castillo' and "texture.air_nostrum galicio". So FS9 could not find such folders as just "air nostrum".

Apparently when you put the proper texture folder name in 'texture=x' but bmp files in this folder are corrupted, or there are multiple bmp files there, the FS won't crash, the texture will just not load and the aircraft will be grey. (Happened to me many times when installing new traffic - the game didn't crash but I was seeing just models of airplanes flying, w/o liveries).

But if you put a wrong texture folder name in 'texture=x' FS will be crashing.

 

Summing up: I THINK the problem is solved. But soon when I have time I will make a longer flight to Madrid, say from Manchester or Amsterdam, so flights in which FS9 was crashing lately and will inform you if the problem is totally fixed

What in fact might have caused the problem - In CRJ900 folder there were 5 texture folders (adria airways and air nostrum). The [flightsim.x] section in aircraft.cfg was one big mess. The numbers were duplicating - I think it was like 0,1,1,2,2 - and in addition, there were mistakes in the sections 'texture=x'. The names of the folders with textures that were entered into 'texture=x' were totally wrong. I think I put 'texture=air nostrum' while in fact the texture folders with nostrum liveries were called "texture.air_nostrum castillo' and "texture.air_nostrum galicio". So FS9 could not find such folders as just "air nostrum".

Apparently when you put the proper texture folder name in 'texture=x' but bmp files in this folder are corrupted, or there are multiple bmp files there, the FS won't crash, the texture will just not load and the aircraft will be grey. (Happened to me many times when installing new traffic - the game didn't crash but I was seeing just models of airplanes flying, w/o liveries).

But if you put a wrong texture folder name in 'texture=x' FS will be crashing.

 

Those errors, while being a pain in the behind, should not cause FS9 to CTD or OOM. You would get what you have already seen, ai aircraft appearing in the default no texture color (bad texture folder naming or incorrect texture naming). If the [fltsim.xxx] section is incorrectly numbered you will have ai that simply do not appear and can hurt performance a bit as FS9 looks for the AC called for in the flight plan, but no CTD or OOM. What will cause the problems is a corrupt texture, either landclass, scenery, or ai aircraft. A landclass bgl that calls for a nonexistent texture. A scenery folder with a empty texture folder. A very badly configured scenry.cfg file. Duplicate AP files or very poorly designed AFCADs that are compiled with fatal errors that are not resolved. Last but not least a aircraft gauge that can cause data to be stored during its use and not properly purging said data causing to much to be stored in RAM (buffer overflow I think it is called?)

 

Regards,

Mel

What will cause the problems is a corrupt texture, either landclass, scenery, or ai aircraft.

 

As far as the first two first are concerned I am not sure if they may be the reason in my case, because I have been flying with all the add-ons for a long time without any problems, and I didn't modify anything in the last couple of weeks. As far as the latter one is concerned, what do you mean by corrupt ai aircraft? Corrupted model file?

 

A very badly configured scenry.cfg file.

 

Could you be more specific on that?

 

Today I am going to force FS to a very hard work, I'm going to fly from Barcelona to Paris Charles de Gaulle and back to Madrid in one 'session' and without reloading anything in FS. If the game doesn't crash, I'll consider the problem solved...

The problem with a faulty AI texture is you may have installed it years ago, but only now made an appearance at a particular airport at a particular time when you happened to be there. That is why i advise you to do the flight to same airport/same time as when you had the crash.

The problem with a faulty AI texture is you may have installed it years ago, but only now made an appearance at a particular airport at a particular time when you happened to be there. That is why i advise you to do the flight to same airport/same time as when you had the crash.

 

Exactly! However, you usually get a .dll error message I believe. Sorry I can't recall which module (.dll) for sure. Fe.dll maybe?

 

Could you be more specific on that?

 

As you add, move and remove scenery the numerical order of [Area.xxx] can become disordered and will cause problems if severe enough.

 

As far as the first two first are concerned I am not sure if they may be the reason in my case, because I have been flying with all the add-ons for a long time without any problems, and I didn't modify anything in the last couple of weeks. As far as the latter one is concerned, what do you mean by corrupt ai aircraft? Corrupted model file?

 

AI texture file not the model file. Something that just came to me is that in your original post you mention a specific aircraft and livery. It is also entirely possible that if the livery has a or some faulty texture(s), for instance the wrong texture format or missing alpha channel might be the cause. This is sort of a long shot, just trying to be thorough.

 

As far as how long your add on files have been installed doesn't matter. A system (computer) glitch while a file is being handled can on rare occasions damage the file.

 

One more possible cause might be that you are having some mild hardware problem that only shows under certain conditions. You might try a long flight with a different aircraft, well away from the area that you normally fly like PANC - KSEA just to see if you have the same problem.

 

Hardware: faulty RAM, faulty GPU or to much heat.

 

Regards,

Mel

I'll take a look at the scenery.cfg.

 

You might try a long flight with a different aircraft, well away from the area that you normally fly

 

I've tried that, wherever I fly there is no problem, it only occurrs in Madrid. The longest flight I've done in a couple of weeks was 4 hours, Manchester - Gran Canaria, no problem at all.

 

hat is why i advise you to do the flight to same airport/same time as when you had the crash.

 

Not dependent on the time of the day, it was crashing no matter what hour I was landing at.

 

Yesterday I flew the route Barcelona - Paris Charles De Gaulle - Madrid without any reloading etc. Everything was going smoothly until like 5 minutes before ToD to Madrid - I was switching something in the weather radar, FS went black, I heard a sound like you hear when disconnecting pendrive for instance and game over

I restarted FS, moved the plane to the, more or less, point at which FS crashed, made the descent to LEMD and no problem appeared.

So I will need to test it once again soon..

You will do well to rule out AI aircraft first. So do the same flight with AI turned down to 0% If you still get the crash then it is most likely scenery problem.

I've tried that, wherever I fly there is no problem, it only occurrs in Madrid. The longest flight I've done in a couple of weeks was 4 hours, Manchester - Gran Canaria, no problem at all.

 

And;

 

You will do well to rule out AI aircraft first. So do the same flight with AI turned down to 0% If you still get the crash then it is most likely scenery problem.

 

After you have shut down the AI traffic ((0%) as pschule - Peter? says)). Try the problem flight / destination - Madrid, with a default jetliner. If you have the same problem then that leaves nothing else but the Madrid area scenery that you are using. If you have no problem, restore the AI traffic and redo the flight again with the default jetliner. If you have the problem then it is a AI problem. If you still don't have a problem then it is something related to the B738 (PMDG?) and the Madrid area scenery such as a airport file, a duplicate AP file (AFCAD) or bad NAV data that the PMDG doesn't like. From my point of view it is seeming that the more I learn from you the more I believe it is scenery related.

 

In case you don't have it download and run ScanAfd. It will find any duplicate AFCADs if you have any. *** NOTE *** Some scenery uses a 'stub' airport to provide taxi signs, these are not a problem and can be disregarded if and when the show in ScanAfd as a duplicate file.

 

http://library.avsim.net/search.php?SearchTerm=ScanAfd&CatID=root&Go=Search

 

Regards to all,

Mel

Your best bet is to switch to Windows 7 64bit. :wink:

 

 

jime

Your best bet is to switch to Windows 7 64bit. :wink:

 

 

jime

 

FS9 runs superbly on Win7 64 bit, but if the OP's problem is ai texture or scenery related it wont matter a jot what system he is running he will still get a crash through OOM errors.

 

Peter

This is an automatic message.

 

This topic has been moved from "The FS2004 (FS9) Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.