Hi,Two weeks ago I switched into new system (i7-950, p6XT, 12gb RAM, 460GTX, 2xWD300 Raptors, Win-7 Ultimate 64-bits) reinstalled FS2004 from the scratch with all my addons and noticed via Process Explorer that Virtual Memory size usage increased by ~2GB (from 1.5 average to 1.7 average). Yesterday, while boarding at 19:00 GMT at AI Aerosoft EHAM with iFly-738 (UT Europe, Custom made Traffic, GE, REX) I had almost 1.93GB usage of Virtual Size barely doing nothing, just watching AES movements with 46FPS.The question is - should I expect OOM soon and what I can do to prevent it? I do not use 3GB switch (there is no need for that on 64-bit systems). I also read the reports that some people (such as Word Not Allowed) have >3.5 GB usage of Virtual Memory on their 64-bit system.An finally, could someone please confirm one thing regarding Process Explorer. Am I correct that OOM usually happens when Private Bytes number exceeded Virtual Size number, not just when Virtual Size simply hit 2GB plank.Thanks for youur thoughts and help

Also,For a long time, I had been a strong opponent of patching FS9.EXE. It seems like now the time has come to reconsider my views. I found this topichttp://forum.avsim.net/topic/293216-dreaded-out-of-memory-error-in-fs9/page__p__1812190__hl__3gb+switch__fromsearch__1#entry1812190Am I correct that if I have W7 Ultimate 64bit system, does it mean that the only step I should implement is the Step 2 (i.e. patch fs9.exe).STEP 2 -Now to modify to the fs9.exe (thanks to Markus and Stu):Try this only if you have at least 2 GByte of RAM and at your own risk.First download the explorer from http://www.ntcore.com/exsuite.phpNext make a copy from fs9.exe. Than start "CFF Explorer" and open the orginal fsx.exe file.Now go to NT Header/File Header and click File Header. Ther you find a button labeld "click here". Click it. And select the mark at "App can handle> 2gb adressest "Save the modified EXE, overwrite the orginal one (You have youre copy saved?).Following the above procedures will fix the OOM error on 32 bit OS's as a band aid as I stated above but to REALLY REALLY CURE the ROOT CAUSE You Must Move to a 64 bit OS Once and For All You still still need to do step number 2, but you don't have to worry about ANY of the Boot.ini garbage and your machine can now see and use more memory more efficiently...32 bit OS's are dead...TadaPaul Solk Thank you

>>Am I correct that if I have W7 Ultimate 64bit system, does it mean that the only step I should implement is the Step 2 (i.e. patch fs9.exe).<<Thank you

You are correct...DJ

You are correct...DJ

Thanks DJ. Any negative graphic effects on addon scenery been noticed? Is AES OK?

Thanks DJ. Any negative graphic effects on addon scenery been noticed? Is AES OK?

It should not affect anything except stopping OOM errors in Win x64 - certainly I haven't had any issues under Win7 x64. AES should run OK in this enviroment; I believe that there were issues with it using the switch in XP x32 but have seen no complaints with x64 systems.DJ

Thank you DJ.Last question (perhaps to all of W7U-64 owners).What is your average Virtual Size file during the flight session in heavy airports with sophisticated planes, AI, REX, UTE\UTUSA, GE, ASV? What was the maximum size as far as your remember?ThanksDmitriy