Hello,I have built an core I7 965 system with 12 gigs of triple channel ram and two gtx285 video cards. I am running 3 wide screen 24 Inch 1900 x1200 monitors. Overall I am getting fairly good frame rates with running the 3 monitors. (25-30 FPS). Over Vancouver , my frame rates suffer and drop to 12-15 fps. I am running Jon Holger's Vancouver X as well as UTX REX and My TrafficX.Today while flying over Vancouver, I received an memory error, "FSX is out of memory. Please restart FSX"My operating system is Vista 64. The 12 gigs of ram show up in the operating sytem. I have checked the system resources manager when running FSX and it shows that the computer is using almost 4 gigs of ram. How is this possible with a system that runs 12 gigs of ram? Is there any tweaks that I can do to make FSX use more of the available ram?Regards Rod Hamilton.

You did not say what OS you are running.If 32 bit you can have all the memory you want installed, but the OS will only use a little over 3 gig of your ram.IF 64 bit your OS can use it all but FSX can only use 4 gig or so... don't quote me on that.Based on your report of out of memory I assume you are running 32 bit OS and there are many topics as to what you can try to get around this error.

Actually, the OP did state "Vista 64..."But, the problem isn't really physical memory related. The "error message" is misleading folks." The problem is running out of memory addresses. The solution is the same irrespective of the OS in use. You need to increase the Virtual Address Space (VAS) allocation for FSX by at least another 512KB.

How do add virtual memory in FSX ?Sorry, I mean Virtual Address Space (VAS) allocation for FSX Rod Hamilton.

See if this helps. http://forums.flightsim.com/vbfs/showthread.php?t=179112May help Bill by not having to write the explanation again.

Okay, I read the thread.Where do I find the boot.ini file, to add the /3GB switch ?

Okay, I read the thread.Where do I find the boot.ini file, to add the /3GB switch ?

Vista does not use a boot.ini file.I'm confused as to why Bill Leaming told you that you needed to increase your Virtual Address Space when in the very same post he knew you had Vista 64.Nothing in his posts at the site linked above is necessary when running a 64 bit operating system.You said "I have checked the system resources manager when running FSX and it shows that the computer is using almost 4 gigs of ram." I believe the FSX.exe will only use the first 4GB of physical memory regardless of your total amount of RAM in your system. Someone correct me if I am wrong. It sounds like FSX really ran out of memory on your system since you noticed your system resources was at 4GB.Todd

Thank You Todd.I just spent the last 30 minutes looking for the boot ini and could not find it. Obviously this tweak does not work for Vista 64.Thank you for responding. Rod.

Thank You Todd.I just spent the last 30 minutes looking for the boot ini and could not find it. Obviously this tweak does not work for Vista 64.Thank you for responding. Rod.

RodI would have a read of this http://support.microsoft.com/kb/940105 excerpt:"On a modern operating system such as Windows Vista, applications run within their own private virtual address space. Typically, the size of the virtual address space is fixed at 2 gigabytes (GB) for 32-bit applications. How much virtual address space is available is not related to how much physical memory there is on the computer. Many people confuse the VAS with Physical RAM but they are not really related, and if you deplete the VAS that FSX needs, for any reason, you may get OOM errors but that is unusual on a 64-bit OS. I would suspect some artifact of overclocking or an intermittent hardware fault. Have you tried your graphic card as a single card? What is the size of your paging file and when was it last defragged? You are correct the /3G switch DEFINITELY does NOT work on a 64-bit OS.PeterH

I had this problem with Windows7x64 Ultimate.I also have 12Gigs of triple channel RAM and couldn't figure what was going on.I went into the Computer Properties and to Advanced then to Performance>Settings>Advanced and "Virtual Memory". Here mine was set to "System managed size", so I changed it to "Custom size" and for "Initial size (MB)", I put 18419, or 1 and 1/2 the total amount of RAM in my computer. Then for the "Maximum size (MB)" I set 36837, or approx. three times the total RAM in my computer.Next I reduced the amount of AI aircraft in my UT2 to 25%.This seems to have helped a lot. I haven't had any more OOMsBob

Hi peter,Yes i have my system overclocked to 4 ghz. My ram is also overclocked to 1800 with ram timings of 7-8-7-7-20 . ( Dominator 1800 triple channel ram). i have also changed the system management size to 18419. Perhaps my ram timings are out. In any event thanks to everyone who have replied.Kind regards Rod Hamilton.

Hi peter,Yes i have my system overclocked to 4 ghz. My ram is also overclocked to 1800 with ram timings of 7-8-7-7-20 . ( Dominator 1800 triple channel ram). i have also changed the system management size to 18419. Perhaps my ram timings are out. In any event thanks to everyone who have replied.Kind regards Rod Hamilton.

RodI would suspect the o/c. The paging file increase may help - needs defragging if not on its own separate partition.RegardsPeterH

FSX is a 32-bit application, and as such, it has to stay within a 4GB address space--no more. When it asks the OS to allocate even one byte beyond 4GB, you'll see an OOM. You could have 128 gigs of RAM on the machine, and that will not change that.Bad overclocking will not cause an OOM--the kinds of errors it produces are blue screen crashes, lockups, and CTDs.The disk cache on a system with a 64-bit OS and 12 GB of physical RAM is absolutely irrelevant--something is very, very wrong if that cache is getting hit at all during a FS session. With 12 GB of physical RAM, FSX is getting 4GB of dedicated physical address space to work in, and the OS is all in physical RAM as well--virtually nothing should be getting paged to disk.It is possible to produce an OOM in heavy traffic situations in complex scenery, especially if a bunch of that traffic is planes made for flying rather than AI (i.e. 20 instances of the PMDG MD-11 trying to blast off out of Memphis at the same time). AI aircraft tend to have much lower polygon counts and make use of mip-mapping to reduce the memory footprint when the objects are distant, as opposed to a non-AI plane with 32-bit textures that's still hitting your memory hard even when it's but a speck miles away. It's also possible to run yourself out of address space over time if one or more programs has a memory leak--in other words it is not releasing RAM back to the OS after use.My recommendation is to take a good look at what planes you are allowing your AI program to generate as AI traffic, and try to limit it to acft designed for AI, and a limited number of those by reducing the traffic percentages as well. If you've got a whole lotta add-ons, you may want to tailor your configurations so that unneeded modules are not loaded (i.e. the PMDG dlls when flying the LDS 767). Unlike FSX on a 32-bit OS, you can have a whole lot out there without hitting the memory wall...but the address space is not unlimited. You said that your memory usage was near 4GB when the OOM occurred...that tells me you had a legit OOM from too much stuff...the proverbial 10 lbs of doo-doo in a 5 lb bag.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I just spent the last 30 minutes looking for the boot ini and could not find it. Obviously this tweak does not work for Vista 64.

Why would you look for a boot.ini file when the article stated quite clearly that this applied only to WinXP?The method for Vista users is to use the BCDEdit.exe utility, as described in the next section of the article.FSX is a 32bit application. On a 64bit system it will be run in a virtual WOW64 session, which is basically a 32bit emulator. As such, it's VAS allocation is subject to precisely the same rules that apply to FSX running on a 32bit operating system.That is why I suggested increasing the USERVA by 512MB.

For that matter Vancouver+ will bring systems to their knees - it's hyperdetailed. You can cut out some of the extra detail, reduce ground traffic, etc. for more system overhead. There is so much custom detail in the scenery, it almost qualifies as FS11. Jeff ShylukSenior Staff ReviewerAVSIM