I'm starting a 2nd "thread" on this because this reply might get lost at the bottom of the 1st thread I wrote a couple of days ago. I'll take the blame. On re-reading my first post I did NOT mention that my new OS system WAS Windows 7(64 bit) and not Windows XP (not on my new computer anyway). If I tell you that it is a duel boot system ( which it is) that will just cloud the issue. My new computer was custom made and it was made to run FS2004 and FSX on Windows 7 (64 bit) and not Windows XP. I have been, without much luck, trying to understand all of this "memory" stuff for years but it just doesn't seem to sink in.I think most of the answers and advise that you guys spent time giving me a few days ago was for a system running Windows XP. Now it's Windows 7 (64bit). So now with Windows 7 (64 bit), am I still open to be able to receive OOM errors ?( I did, twice) Is there any fix for this problem with Windows 7 (64) or do I just have to live with it? As I said before I loved what UT 2004 did for my scenery BUT my 1st ever OOM error came after installing UT 2004 after flying without it for about 8 years!!! Thanks for your help. jerrycwo4

Jerry, really not sure why you started another thread... There were already responses regarding W7. Please go back and re-read the original thread as everything written there about needing to make FS9 largeaddressaware REGARDLESS of OS and all other suggestions are still completely relevant.Also, do some searching within the forums, this has been discussed to death and usually it is the same group of us giving the same advice over and over...Run a 64 bit OSMake FS9 largeaddressawareCheck AI texturesCheck AfcadsCheck Empty texture directoriesGood luck!

I'm starting a 2nd "thread" on this because this reply might get lost at the bottom of the 1st thread I wrote a couple of days ago. I'll take the blame. On re-reading my first post I did NOT mention that my new OS system WAS Windows 7(64 bit) and not Windows XP (not on my new computer anyway). If I tell you that it is a duel boot system ( which it is) that will just cloud the issue. My new computer was custom made and it was made to run FS2004 and FSX on Windows 7 (64 bit) and not Windows XP. I have been, without much luck, trying to understand all of this "memory" stuff for years but it just doesn't seem to sink in.I think most of the answers and advise that you guys spent time giving me a few days ago was for a system running Windows XP. Now it's Windows 7 (64bit). So now with Windows 7 (64 bit), am I still open to be able to receive OOM errors ?( I did, twice) Is there any fix for this problem with Windows 7 (64) or do I just have to live with it? As I said before I loved what UT 2004 did for my scenery BUT my 1st ever OOM error came after installing UT 2004 after flying without it for about 8 years!!! Thanks for your help. jerrycwo4

Go to this page: http://www.ntcore.com/4gb_patch.php , download the 4gb_patch, run it and point it at FS9.exe in your main FS directory, tell it to patch large address aware. Save a copy of the FS9.exe first (just for luck). You're all done. Don't need to worry about the fine points.DJ

As stated Jerry, you need to make that FS9.EXE LAA. It's a 32bit application and it needs the LAA flag set to it so it knows it can look beyond the 32bit limit. It's as simple as doing what UBERSU said.

Jerry, read my reply on the previous thread. I have a similar system W7 64 bit with 12 GB of ram, and I was having the same OOM errors. and in my case was problems with textures, and some empty texture folders in the add on sceneries. You have the answer in your latest posting, you said that your problem started after you installed UT 2004. Start looking there. Uninstalled it then fly for a few hours and see what happens.DJ, I believe that is not the issue, I have the 4 gb patch installed. and it did not crashed until I started adding sceneries and AI aircraft with texture issues. Juan

Jerry, read my reply on the previous thread. I have a similar system W7 64 bit with 12 GB of ram, and I was having the same OOM errors. and in my case was problems with textures, and some empty texture folders in the add on sceneries. You have the answer in your latest posting, you said that your problem started after you installed UT 2004. Start looking there. Uninstalled it then fly for a few hours and see what happens.DJ, I believe that is not the issue, I have the 4 gb patch installed. and it did not crashed until I started adding sceneries and AI aircraft with texture issues. Juan

Right but regardless of whether it cures his OOM or not what is the point of running a 64 bit system with all that memory and not making a 32 bit application LAA?\That should be step one of installing FS9 in ANY 64 bit OS or you may as well have stayed 32 bit...Make the change recommended by so many different people already...-P

Jerry,Sorry to hear about your problem. I agree with what someone said above: that the most likely culprit is some rogue add-on scenery or something similar. I also run FS9 on a humble W7 64-bit Vaio laptop Core i5 M430 with 4GB RAM and have never experienced an OOM with it. No large-address-aware mod (I read the thread linked above and it almost caused brain explosion), wouldn't know how to go about it. BUT the same was also true with my previous XP SP2/SP3 set-up, and it didn't have the 3GB switch (whatever THAT was). There was only one exception: the only time I've ever had an OOM in the last 6 years of simming in FS9 was just once when I installed a particular add-on freeware scenery (can't remember which) in XP. I uninstalled it and the problem went away, never to return. So while I acknowledge that there are those out there with very many more techno-smarts than me (and I guess that there are probably some who are reading this), I'd go with the 'keep-it-simple' approach and think about your scenery add-ons first, if you're not happy with LAA and all that stuff. So, scenery and associated textures, empty scenery folders, that kind of thing. Uninstall all your scenery additions one by one and it's my guess you'll eventually come across one that's causing the problem.Here's another thought that maybe the techno guys could comment on: maybe making FS9 large-address-aware doesn't actually cure the root problem of OOMs; it just gives more overhead so that you're no longer aware of it happening, even though it's still there? Kind of treating the symptoms rather than curing the disease? I can only go by what I've found, which is that 32-bit FS9 can run perfectly happily in W7 64-bit (4GB RAM) with no OOMs and no LAA tweaking - unless of course W7 is so phenomenally unstable that OOM occurrences vary from machine to machine.;)

PsolkI agree you need the "FS9.EXE LAA". And I do have it in my configuration, but I was still getting the OOM errors. All I am saying is that in my specific case with one of the best system around (I7 930 extreme, 12 GB of RAM, GE FORCE GTX480, Twin velociraptor drives)and the best configuration possible, I was getting shot down by texture issues related to AI aircraft textures,and addon sceneries duplicated AFCADS and textures.Juan

Jerry, read my reply on the previous thread. I have a similar system W7 64 bit with 12 GB of ram, and I was having the same OOM errors. and in my case was problems with textures, and some empty texture folders in the add on sceneries. You have the answer in your latest posting, you said that your problem started after you installed UT 2004. Start looking there. Uninstalled it then fly for a few hours and see what happens.DJ, I believe that is not the issue, I have the 4 gb patch installed. and it did not crashed until I started adding sceneries and AI aircraft with texture issues. Juan

There is no evidence whatsoever that he has texture or afcad issues. UT is known for memory usage, and has caused OOM's in already stressed fs setups on many occasions (mine included until patched). The patch is easy, and should be made anyway in order to take full advantage his system. If he continues to get OOM's then he can march through sceneries and folders until he's blind. I doubt if it is really necessary at this point.DJ

Thanks for the link, DJ. I've downloaded it for future reference, just in case.If it ain't broke...;)

I would try running ACA2005V1.6 and get shut of any errors that that shows up.Last time i had OOM errors was when i had two conflicting sceneries in the sim.I could remove any one of them and everything would run OK,but have both in the sim at the same time and OOM errors would start again.MSFS will run OK with one or two small errors but gives up when there are multiple errors.

Go to this page: http://www.ntcore.com/4gb_patch.php , download the 4gb_patch, run it and point it at FS9.exe in your main FS directory, tell it to patch large address aware. Save a copy of the FS9.exe first (just for luck). You're all done. Don't need to worry about the fine points.DJ

Thanks DJ. This was incredibly easy to do and it's a nice "insurance policy" to have. Not sure if Opa will see this thread but it would be a good bit of information to share with the community with his "tips and tricks"BTW, it is worth downloading the freeware ScanAFD program. It checks for duplicate AFCAD files. I run it from time to time and it's not that infrequent to find one has snuck in there somehow.Ian

Thanks DJ. This was incredibly easy to do and it's a nice "insurance policy" to have. Not sure if Opa will see this thread but it would be a good bit of information to share with the community with his "tips and tricks"BTW, it is worth downloading the freeware ScanAFD program. It checks for duplicate AFCAD files. I run it from time to time and it's not that infrequent to find one has snuck in there somehow.Ian

Ian,I can't imagine life without ScanAFD - it is one of the most useful utilities I've encountered in FlightSim...DJ