Just to let you know my system is:Window XPIntel® Core 2 Duo [email protected] GHZ3.00 Ghz, 3.25 GB RamNvidia GE Force 8800 GTX (32 bit)\What should I do?ThanksAl

Mark, I turn off most of my sceneries and AES and when I arrived in New York, same problem again OOM. I guess the only solutionis to go with 64 and reload everything?Al

You say you turned off most of your sceneries , did you leave any addon scenery active ?Also Are you using AI traffic ?What aircraft are you using to test?There are still options for finding this problem , but if you are prepared to opt for a 64bit os then that is no bad thing, though it may be worth doing a search to make sure you are not going to encounter issues of another sort Mark

If you're having OOMs with the /3GB switch and with most of your sceneries off then it sounds like either something is royally fubared or you have a memory leak of epic proportions. Try your flight in windowed mode with process explorer with the process explorer runing and observe the memory, how fast does it go up and at what point (value) do you OOM? Could be that your /3GB implementation isn't working for some reason.

Hi for OOM errors with FS9 on 32 bit system: 1- set the pagefile size to system managed2- apply the 3G switch AND enable the FS9.exe to use more than 2Go of virtual address space look at my posts in this thread for more explanations on OOM and how solve them (in the PMDG forum but what it said there is independent of add-ons you use)how to :http://forums1.avsim.net/index.php?showtop...39523&st=86About the userva : http://forums1.avsim.net/index.php?showtop...9523&st=116 About UT :http://forums1.avsim.net/index.php?showtop...39523&st=91I definitely agree that a complete post should be made about OOM errors and how to solve them and this topic should be pinned on top of the FS9 forum !hope it helpsJulien

There are only three solutions to OOM problems and these have already been listed above, but just to reiterate and emphasize, they are as follows:1) Implement the /3GB /userva swtiches (where userva = system ram - 768Mb - video ram; otherwise excessive paging will occur); or2) Upgrade to a 64bit operating system; or3) Reduce the complexity of the scenery environment.There are no other solutions that will yield a resolution to these problems, with the caveat that the 3rd option is pretty much a stop-gap measure and any new complex airliner, additional AI planes (if any) or a detailed airport may upset the balance. Keep in mind that all these also have their downsides. The 3GB switch messes up AES and may cause issues with other software installed on the system, while moving to a 64 bit system can cause compatibility issues and so on and so forth. Personally, I'm currently running XP 32bit SP3 with 4Gb of RAM and the /3GB switch enabled and haven't had an OOM event since implementing it.

Hi people,I had also the same problems. OOM's but now with my new XP 64bit system, made a flight yesterday, from EHAM (cloud9) to EGLL (aerosoft) with a PMDG MD11 and still get the OOM. out of memory.I also asked it in another topic here, if you are running XP64bit, do you still need to apply the 4Gb patch our 3Gb switch? I tried to apply the 4Gb patch on the FS9.exe and this resulted in a not starting FS9.Is there something i don't know our what can it be?Peter

I am using PMDG 747 with aerosoft KJFK and Manhathan. Michael who is an expert in Flight Sim from LA fixed my FS to oipen with FS auto start which shut down unnecessary things. Last night he installed SCM2004 because my sceneries were all screw up. Today I am testing and I got freezing screen until I turned off Aerosoft Manhatan and JFK. Then it worked fine but I am doing more testing.Al

I had also the same problems. OOM's but now with my new XP 64bit system, made a flight yesterday, from EHAM (cloud9) to EGLL (aerosoft) with a PMDG MD11 and still get the OOM. out of memory.I also asked it in another topic here, if you are running XP64bit, do you still need to apply the 4Gb patch our 3Gb switch? I tried to apply the 4Gb patch on the FS9.exe and this resulted in a not starting FS9.Is there something i don't know our what can it be?Peter

The problem is that if there is a memory leak somewhere, a 64bit OS will only postpone symptoms and not fix them. It will just make more memory available to FS9, but if something leaks, given enough time, it'll probably chew through that additional resource as well.I don't think there's a need to patch FS9 with a 64 bit OS, at least I don't recall anything being posted on that topic. I'm sure a little googling will yield a result.

I've been at it for the last 7 hours. I used PMDG 747, World of AI, Ultimate traffic, AI Smooth, Radar contact, AVS weather, FS real time. Each time I am on final approach to JFK it freezed. I try several plane all the same.Al

The problem is that if there is a memory leak somewhere, a 64bit OS will only postpone symptoms and not fix them. It will just make more memory available to FS9, but if something leaks, given enough time, it'll probably chew through that additional resource as well.I don't think there's a need to patch FS9 with a 64 bit OS, at least I don't recall anything being posted on that topic. I'm sure a little googling will yield a result.

I also emailed NTcore and they replied verry short with the message there is no other way than makin FS9.1 knowing that there is 4GB then with the patch. But after almost a day (yesterday) googeling on the question, i did not read anything about it. It should work. I will test the memory with memtest. mayby there is something wrong. And i removed Ground Enviroment. Mayby this will cause the leak. No still using FS Global 2008.I will keep it updated here if mayby someone in the future will have the same problems.Thx. so far for reply.Peter

I hate to bring back this topic but after lots of flight I found that if I fly long flight with nice paid sceneries like Aerosoft, fly tampa, imagine and FS Dreamteam with payware plane like PMDG, Level D and Wilco. O get teh OOM or when on final the screan goes all black. I did the same flight with the planes more simple payware Overland and no problem at all. Any comment or help on this?ThanksAl

I hate to bring back this topic but after lots of flight I found that if I fly long flight with nice paid sceneries like Aerosoft, fly tampa, imagine and FS Dreamteam with payware plane like PMDG, Level D and Wilco. O get teh OOM or when on final the screan goes all black. I did the same flight with the planes more simple payware Overland and no problem at all. Any comment or help on this?ThanksAl

Did you change to 64bit OS?

No too expensive and too much trouble. Plus some told me that 64 bits did not do any difference.aL

No too expensive and too much trouble. Plus some told me that 64 bits did not do any difference.aL

Well, then, I'm afraid you are going to have those out of memory errors further... and you might alternatively try the /3GB switch. Plus whoever said that 64bit don't do any difference for memory for FS9, knows exactly jacksh**.One another thing, if you are a user of AES, you might also look into that. I was reading on AES forums that if flying from non-AES'd airport to an AES'd airport, you have a good chance of getting an OOM (or g3d.dll error for that matter) if you are using /3GB switch.

Thanks Word Not Allowed and you are right I amusing AES. I will check the forum.ThanksAl

I can confirm what Word Not Allowed says about AES.Even on very short flights from non AES airports into AES enabled ones I got OOMs all the time, but not on other airport combinations (AES to AES, non AES to non AES, AES to non AES). Ever since I disable AES before starting a non AES into AES airport flight those crashes are gone ... go figure.Oliver