The other day I flew into KASE from KJFK, and on short final FSX crashed, telling me it had run out of memory. I found that very hard to comprehend, considering the fact that I have 6 gigs of ram. Is this due to a memory leak perhaps? Does anyone have an idea? I formated my computer a week ago, its not bloated full of stuff i dont need or anything. i7 Bloomfield6 gigGTX260Saitek x52pDual sound cardsW7 64FSX SP2Maddog 2008 with service packUTXGEXREXWorld of AI (around 50 packages used for online traffic)FSInn / FSCoPilot

wimsYou didn't run out of physical RAM you actually exceeded (somehow) the Virtual Address Space - 4GB - that FSX loads into. Every program in Windows 7 loads into its own Virtual address space, so that if it 'crashes' it doesn't bring the computer down with it. Now FSX is a 32-bit program so it can only utilise 4GB of VAS. Having complex scenery, aircraft and any 3rd party software, a video card with large amounts of VRAM can exceed this 4GB limit which is NOT dependent on physical RAM. If you had used all of your RAM then your computer would have crashed not just FSX. Its all to do with how 3rd party software is written and how it interacts with FSX. If its written 'badly' or doesn't interact well with Virtual memory it can cause the VAS to be overloaded resulting in a OOM error. IMHO, too many objects (from complex add-ons) can fill up the VAS and the inbuilt 'Garbage Collector' cannot free up any more RAM and this results in the dreaded OOM error If you type event viewer in the start menu and look for the crash time it will indicate what caused the error - but its not always easy to detect what caused a particular OOM issue. [For more info Google Virtual address space and windows 7 64-bit]A "cure" - reduce the sliders in the display settings in FSX will sometimes help! :( RegardsPeterH