hi everyone, its me again, no dont run away, i need a possible explanation. this is in relation to my earlier post yesterday. i loaded the fs9 md11 with the route egpf - kjfk. everything went well throught the flight with the autoflight and profile working in harmony. i reached the point when the aircraft was about to turn into final appproach to runway 31L with land armed when suddenly the system crashed to ctd. i have a high end computer with 8gb memory, i mention this thinking that memory may be to blame but i think 8gb should be more than enough for a flight of 2878nm and i had 11 tons of fuel for landing. i realise there could be a multitude of reasons, but has anyone had a similar experienced and solved it. many thanks in advance. richard welsh.

Something in the back of my mind about FS9 not capable of huge memory blocks, but there is a patch that fixes the executive to allow it. Someone else will have to provide the referrence or you can try an advanced search for the name of the patch.I assume it was a pure CTD, no messages? Hope my vague recall is of some value.

Something in the back of my mind about FS9 not capable of huge memory blocks, but there is a patch that fixes the executive to allow it. Someone else will have to provide the referrence or you can try an advanced search for the name of the patch.I assume it was a pure CTD, no messages? Hope my vague recall is of some value.

hi Dan, your very reliable for replies, i made a mistake about the 8gb of memory,it should read 4gb, my memory needs a kick. it was a pure ctd, no message. i think the patch you refer to is here at www.ntcore.com and it refers to x64 platforms whatever that is, i am on windows xp 32. thanks again Dan. richard welsh.

hi Dan, your very reliable for replies, i made a mistake about the 8gb of memory,it should read 4gb, my memory needs a kick. it was a pure ctd, no message. i think the patch you refer to is here at www.ntcore.com and it refers to x64 platforms whatever that is, i am on windows xp 32. thanks again Dan. richard welsh.

Yes Richard, I had the same thing when flying long haul or medium haule (sometimes) before.The only reliable cure for this is to change to a 64-bit system, which I did one years ago.Haven

Yes Richard, I had the same thing when flying long haul or medium haule (sometimes) before.The only reliable cure for this is to change to a 64-bit system, which I did one years ago.Haven

Maybe, but the most likely reason is an out of memory error. Sometimes scenery is loaded into memory and that space is not released for reuse, and the longer the flight the less you have available. Someone wrote up a good explanation of this many months ago. Look over the OOM error messages using the advanced search for some tips you might want to consider.

Richard,most definitely an out of memory error. The problem is, even though you do have 4GB of RAM, Win XP 32bit can only use a bit more than 3GB. Now that alone wouldn't be that bad for FS9, however XP 32bit does not allow for fs9.exe to use more than 2GB of your memory. With today's add-ons this limit can easily be reached.There is a windows "hack" you may apply to get fs9.exe to use more memory. However this modification can have severe side effects. A 64bit operating system would cure the problem once and for all with no side effects.Now if you don't have one lying around you should not buy a new one at this point. Windows 7 is coming in October and will be an amazing operating system for FS9 and FSX. So if you can wait for Win 7 64bit to be released, your OOMs will be gone then... If you can't wait, try the modification mentioned above or check eBay if you can find a cheap WinXP Prof 64bit.Regards,Markus

Markus,Would this issue cause the computer to reboot? A few weeks ago, I upgraded my 32bit XP system from 2GB to 4GB. As you noted I only get credit for 3.25GB. I was flying last night on FS2k4 and 3 hrs into the flight, the screen turned blue and my computer rebooted. No warnings, or anything, everything was fine. I've never had that problem before. I'm going to try again tonight and see what happens. Prior to last night, and since upgrading, I've been doing 1 hr flights with no problems. Thanks!Mike Franks

Hi,Some scenery leaks memory, and it is only noticeable when flying long haul as it takes that long for the leak to develop into a major issue.There is a problem with scenery when a landclass file is in a scenery folder with an associated texture folder. To fix it, put the landclass in a seperate scenery folder, WITHOUT a texture folder (none at all!!!) and then reference it seperately in the scenery.cfg file.Finding the bad landclass can be nearly impossible if you have many sceneries installed. Was a problem for me for a while until I found out the cause. Disabling scenery works to avoid it.HTH.Best regards,Robin.

Thank you Robin. I didn't think about a scenery issue. When this happened last night, I was flying from Guam to Narita. I over the Pacific getting ready to start my decent. I've made this flight before without any issues. Let me try a flight over land and see what happens after a couple of hours. If it does it again, I may just take out the 2GB RAM upgrade and go back to what worked.Mike Franks

I took the Queen up tonight and flew the route I had problems with yesterday. No problems, but I did fly it at 4x speed. Didn't want to invest alot of time for it to reboot on me. I'll keep an eye on it and see if it happens again. Thanks,Mike Franks

Hi,Robin is right, memory leak due to a "bad" LC file lurking somewhere where it shouldn't be, can eat all available memory on a long flight. I have 2Gb of memory, my FS9 is beefed up but can still fly both, the 747 and MD-11 to airports like KORD or EGLL with cca 150 AI aircraft around me and all sliders to max. Haven't had a CTD in a long time, ever since I found (hopefully) the last LC file in a wrong place. No hack needed. :( It really is worth it to investigate the scenery installed and hunt down offending files. I usually keep all LC files in a separate folder (and scenery.cfg entry), plus two folders for mesh, one is the "lower" level, covering huge areas, the other is for "higher" level mesh, all sorts of small mesh files that come with different sceneries. I am running Win XP, SP2, 2GB RAM, geForce 9800GT with 512Mb RAM - I didn't want a 1Gb card because of the way Win XP handles memory. Regards,Jure

Hi,Robin is right, memory leak due to a "bad" LC file lurking somewhere where it shouldn't be, can eat all available memory on a long flight. I have 2Gb of memory, my FS9 is beefed up but can still fly both, the 747 and MD-11 to airports like KORD or EGLL with cca 150 AI aircraft around me and all sliders to max. Haven't had a CTD in a long time, ever since I found (hopefully) the last LC file in a wrong place. No hack needed. :( It really is worth it to investigate the scenery installed and hunt down offending files. I usually keep all LC files in a separate folder (and scenery.cfg entry), plus two folders for mesh, one is the "lower" level, covering huge areas, the other is for "higher" level mesh, all sorts of small mesh files that come with different sceneries. I am running Win XP, SP2, 2GB RAM, geForce 9800GT with 512Mb RAM - I didn't want a 1Gb card because of the way Win XP handles memory. Regards,Jure hello everyone, and many thanks to all of you for the informative replies to my problem. i have the greatest respect for those of you who have the ability to get into the nitty gritty of computers something i regret not having, i have a fear of tinkering with something i dont understand therefore trying to fix the various items of scenery etc., is beyond me personally, but i will endeavour to sort things out. richard welsh

Mike,no, windows running out of memory does not produce a blue screen. Often blue screens are a result of driver issues or in severe cases defective hardware. Your recent memory upgrade could be a cause for this but does not have to be... The new RAM could have compatibility issues or could be defective.Regards,Markus

Thank you Markus and Jure for the reply and advice. I'll look at my scenery and LC files a little closer. I hope it's not the RAM, but if it is I have no problems taking it out. With Windows XP, I'll never get credit fo the entire 4 GB. I forgot to mention, I also upgraded my GeFORCE video card from 7600 to 9400. Not high end, but it works for me. As I said, I'll keep an eye on it and see if it happens again. I have my fingers crossed it's one of those freaky things that happen sometime with computers.Mike Franks