Now I don't see anymore OOM but when approaching pay ware sceneries like Imagine, Fly Tampa, Aerosoft, DreamTeam, the screen goes all black and freeze. I have to reboot and try again. sometime it work sometime it goes back all black. I amusing two screen.Al

Now I don't see anymore OOM but when approaching pay ware sceneries like Imagine, Fly Tampa, Aerosoft, DreamTeam, the screen goes all black and freeze. I have to reboot and try again. sometime it work sometime it goes back all black. I amusing two screen.Al

Did you check the virtual size of FS9.exe in Process Explorer just before it crashes? I would also suggest in running windowed mode to simultaneously monitor FS9 with the Process Explorer. If virtual size exceeds 2GB, you are doomed.

Solrry I feel very stupid to ask but how do you do that?Al

Solrry I feel very stupid to ask but how do you do that?Al

OK, quick tutorial:Download http://download.sysinternals.com/Files/ProcessExplorer.zipStart it, got Menu, View, Select ColumnsDeactivate ALL but default ones like Process Name and PID and in Process Memory activate Virtual Size.Best to sort after Virtual Size in main window, just press onto Virtual Size to get the arrow pointing down, that way is FS9 going to be always on top.Monitor this number as you use FS9 in the windowed mode, just put it beside the window.Good luck!

I am thinking of switching over to a 64bit OS to help free up my FS9 as I have over 200 add ons and I am unable to run all the versions on France VFR scenery. However I have been advised that some external drives such as those used on CH products yoke/pedels or for Saitek throttles may not work on the new 64bit OS. Has anyone tried it and how do they work..??

Hi,As I got some also lateley, with heavy aircrafts, I read about it a bit, and it seems that 64 bit wouldnt help. Its about the adress space, what runs full.. a sort of table, but not the memory itself. Hence the pagefile what is not used a lot when the OOM appears.The number 1 suspect is landclass scenery! I tried on several airports, and no OOM whatsoever, even on a long flight, but add a bad landclass scenery part, even flyover, and the memory leak starts.. and builds up.. until you are in a 40 nm radius to your destination, what will be loaded then, but no memory available.. OOM.With a heavy (read complex aircraft) and heavy scenery, the adressable overhead is not big, but normally just enough. With the LC trouble it bleeds off very fast away.Johan

Hi,As I got some also lateley, with heavy aircrafts, I read about it a bit, and it seems that 64 bit wouldnt help. Its about the adress space, what runs full.. a sort of table, but not the memory itself. Hence the pagefile what is not used a lot when the OOM appears.The number 1 suspect is landclass scenery! I tried on several airports, and no OOM whatsoever, even on a long flight, but add a bad landclass scenery part, even flyover, and the memory leak starts.. and builds up.. until you are in a 40 nm radius to your destination, what will be loaded then, but no memory available.. OOM.With a heavy (read complex aircraft) and heavy scenery, the adressable overhead is not big, but normally just enough. With the LC trouble it bleeds off very fast away.Johan

Johan, sorry, but I have to completely disagree with you. Apart from tests of AES on Aerosoft forums (as mentioned before), my tests have shown that running 64bit gives you just enough overhead to even have landclass errors on the landing airport AND on the way, to be able to protect yourself from getting an OOM.I have tested on different OS's with the same FS9 installation, and concluded that simply, when the memory is attempting to grown, on 32bit will just fail close to 2GB... with 64bit the overhead goes up to 4GB, and I have never seen FS9 go much over 3GB virtual size.Since when I have the 64bits, I have also been trying to keep my landclass from each scenery I installed in a separate folder, just to prevent any landclass errors.And since then, I have barely had any really big build ups, though it can happen that it goes just over 2GB through the use of heavier addons, like PMDGs 747 and MD11, and this is exactly the point where 64bits are important, that it just doesn't crash on the small thing.Important thing is to keep FS9 clean, have an overhead and just enjoy your flight, with 99% assurance that it won't crash on landing :)

Johan, sorry, but I have to completely disagree with you. Apart from tests of AES on Aerosoft forums (as mentioned before), my tests have shown that running 64bit gives you just enough overhead to even have landclass errors on the landing airport AND on the way, to be able to protect yourself from getting an OOM.I have tested on different OS's with the same FS9 installation, and concluded that simply, when the memory is attempting to grown, on 32bit will just fail close to 2GB... with 64bit the overhead goes up to 4GB, and I have never seen FS9 go much over 3GB virtual size.Since when I have the 64bits, I have also been trying to keep my landclass from each scenery I installed in a separate folder, just to prevent any landclass errors.And since then, I have barely had any really big build ups, though it can happen that it goes just over 2GB through the use of heavier addons, like PMDGs 747 and MD11, and this is exactly the point where 64bits are important, that it just doesn't crash on the small thing.Important thing is to keep FS9 clean, have an overhead and just enjoy your flight, with 99% assurance that it won't crash on landing :)

Hi Word Not Allowed,I only said; it seems.. on what I was reading. I tried to resolve my landclass problems, and can make the troubled route with PMDG and some heavy sceneries without the OOM.The LC is priority number one to check them out.Is there any tool you know of what can identify LC files?Johan

Hi Word Not Allowed,I only said; it seems.. on what I was reading. I tried to resolve my landclass problems, and can make the troubled route with PMDG and some heavy sceneries without the OOM.The LC is priority number one to check them out.Is there any tool you know of what can identify LC files?Johan

Oh, its ok, sorry that I misunderstood.I was wondering myself of some tool, I am having hard time indentifying LC files. I heard about searching for LC*.bgl and WC*.bgl files, partially something with the word terrain... intuition is more the way I am using.I would also like to have a tool which would recognize LC files.

Thanks for the tip on the texture folders Mark. I was seeing OOM hits quite predictably when flying from Chilliwack to the Vancouver area (or the other way around). It seemed tied to the amount of time more than anything else. I downloaded Process Explorer as suggested near the end of this thread and watched the working set of FS9. It very gradually, but very persistently, grew from the area of 400 megs, after loading, to about 1.7 gigs when it crashed. I looked for empty texture folders and found only about two in the Addon Scenery folder. I got rid of them and tried the same flight with the same aircraft and the same addons (not much, BCMesh9d from Holger Sandmann plus Abbotstford Airport and Southwestern BC Landclass both from Russel Dirks). No more OOM at all and for that matter it loaded in about 256 megs rather than near 400 and never went above around 400 at the very worst point. After returning to Chilliwack and letting it just sit there for a while FS9 could be seen returning the memory it had been using until it was back to where it was when I first started it. That just amazed me. If anyone is having this problem, START with the texture folders. You may save yourself weeks of wasted effort. BTW, I am running Windows 7 RC, 32bit. No complaints about it at all. I purchased the 64 bit version because of the fact that it would allow me to access all of the 4 Gigs of memory I put in this machine, but there are some things I want to run that won't run in 64 bit yet. And seeing this machine running with 2.6 gigs free while running FS9, REX and it's Weather engine and using an ATI 5770 (supposed to be 1 gig), I may just go buy the 32 bit version of Windows 7 and stick with it. I am seeing about 3.3 gigs available out of the four. Don't know how that works when the video card is 1 gig, but that is the way it is. Much better than the dire predictions I had heard would have made me expect. Gord

Okay!!So if what I have read is correct you have done all that has been suggested and you are still having problemsBefore you start down the road of trouble shooting which is a PITA Have a little look in your addon scenery files or any scenery file that you have added and see if there are any empty texture folders.What is worth a try is to turn off 50% of your Add on scenerys and try a flight that you know will give you an OOM If you still get one at least you know it is not that 50% of your add on scenery :( It is a tedius job and at times it seems it would be quicker just to re install BUT if you go down that road you may install the same problematic addon again .There are several recent posts about this problem and good ideas about trouble shooting them.The short answer is , there is no short answer , I guess your left with trouble shoot or a 64bit OSMark

I tried that and still same problem on long flight to an airport with nice pay scenery like aerosoft.Any other suggestion? I am getting frustrated.ThanksAl

HelloDid you also patch the FS9.exe to be 4gb aware?, the boot.ini switches on their own won't work

It all fine now I installed window 7 pro 64 bites.ThaksAl

It all fine now I installed window 7 pro 64 bites.ThaksAl

Blimey after all that grey matter burning,what an anti-climax. :( Andy

Honestly I've flown FS9 since release day and have never had a crash which wasn't ultimately caused by bad scenery and/or duplicate afcads. I recently re-installed with Win7 and suddenly was getting crashes around the Florida area. I uninstalled all scenery in the area and the problem was solved. I did a little trial and error until I found the offending entry. You've got to be completely paranoid with everything you add to the sim. I keep a database of every single scenery package I install. Don't install something until you actually plan on flying there. I've been installing airports which I never get to. Also, I've always used the fs9.exe patched to 9.1 which came from MS. Who knows what issues are caused by other "versions". Maybe I've been lucky, but this has been my experience for quite a few years now. I also reinstall my Windows OS + FS9 every 1-2 years. With external drives the process is 100 times easier than it used to be. External drives are dirt cheap and you can back up anything you need quickly. All it takes is one little missing texture file, or a million other problems that can creep in with scenery. Sometimes, I find stuff in the library and don't immediately even see there's a patch out for it.

Is there a link with more detailed instructions (for dummies) on adding the 3gig switch to windows AND fs9? I'm fine with editing the boot file, just not exactly what to put in. I got brand new 2x2 sticks coming in, so I'll try out the switch.