I inquired about this issue about 5 weeks ago, and still Im getting these Out of Memory error messages.

Specs:
Vista32
Gigabyte EX58 Extreme Motherboard
i7-940 Chip 2.93Mhz
6Gigs Corsair 1600+ DDR3 Lat8
Ultra 8800 Graphics Card

As Im running FSX, Im monitoring the Task Bar Memory usage. Typically from the beginning of the flight to Descent its showing around 2300 to 2400 MB used. When I get the out of message error, its typically around 20NM to the airport on approach. I did notice before the error message poped-up the memory usage was at 2550 MB.

I did do Nicks suggestion by adding IncreaseUserVA 2560 to startup. So how or can this be fixed? Would it benefit me by going to Vista64?

Also, I have been overclocking the computer to 3.53Mhz and monitoring the CPU and System temps, still using the stock CPU cooler. The CPU temp is around 60 to 67 C // 140 to 156 F. Is this an acceptable range? Or is the temp getting way too high?

Thanks everyone

Right...I totally understand that. Thats why Im asking if Vista64 will benefit. Is there a difference between "see" or "Use" all memory? If Vista32 only uses 4g but see's 3.3G (other .8 used by OS) is Vista64 going to allow me to use all 6 gigs and not get those error messages, or is there a limitation to how much FSX can use?

First of all, yes you need vista 64-bit. Your is currently recognizes there are 4 gigs but is only using about 3.3 gigs of the six. Second of all, do you have User Account Control on? If it is, turn it off. Then when you go to run fsx, instead of double clicking the shortcut, right click and click run as admin. This memory error is usually solved that way.

FSX is 32 bit application and has a hard limit of 4GB (100% avaliable and useable) in a 64bot OS as long as FSX SP2 and/or Acceleration is in use, or, the FSX DVD/SP1 fsx.exe file has been manually edited for the LARGE_ADDRESS_AWARE marker allowing >2GB access

Just because FSX is limted in that respect does not mean the last 2GB go unused.. on the contrary, that simply means FSX has full and total use of 4GB where other processes in the OS will map above that leaving FSX a clean and clear path of 4GB

A user needs to be on a 64bit OS with >4GB of memory, period



Most OOM FSX crashes related to a 32bit OS even with the cache edit in the system stem from instability in the 32bit OS or a addon in FSX. Many times there is simply no workaround and a 64bit OS is the only move that will fix the isse


Any 32bit program will have a full 4GB of memory available to it in a x64 OS where in a 32bit OS that program must not only share with the OS and video card in VM, the user is lucky if FSX actually gets 2.8GB to the application and remain stable