Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Memory Ran Out

Featured Replies

I recently built a new computer and I hadn't had any problem the last few times flying, but I just had a Ran out memory error occur. I have a AMD Phenom II X6 3.3GHZ processor, 12GB RAM, ASUS Sabertooth 990FX MOBO and a AMD Sapphire ATI Radeon 6850 vid card. The error occured before I even took off from KLAS. I had to do a complete OS install and it loaded fine. I do get a invalid key now though for the my WIndows 7 64 bit Home Premium program. I don't think that should have anything to do with it though. I had the computer taken to a computer store to have hardware tests done and everything passed. The computer processed all 12 GB of memory. Any ideas what could be the cause of this?

Josh Scholl

I do get a invalid key now though for the my WIndows 7 64 bit Home Premium program.
This might be the problem as your OS may not be properly installed. Out of memory errors normally occur in 32 bit OS's and they are rare with 64 bit systems. However they do occur with 64 bit systems because no matter how much memory you have installed, FSX can only 'see' 4 GB and, if you have your sliders set in your FSX settings too high, you'll get the out of memory message. Is the system overclocked? This has been a cause too for this error as your memory may be overheating or the voltages are too high. But most likely, it's your fsx settings are set too high. If you run FSX with the default settings (ugh!) does the OOM still occur? That will give you a hint. Hope this helps.Best regards,Jim

We actually need to see the OOM error as its probably nothing to with Physical RAM but to do with the 4 GB of Virtual Address Space (MAX) that FSX loads into in a 64-bit OS. If this becomes drefragmented or depleted you will get an OOM error, that's why we need to see what the error is. It's easy to fragment or deplete the VAS using complex scenery or complex planes. The VAS is part of the OS and the Physical RAM is part of the hardware on a PC they interact but they are different.RegardsPeterH

  • Author

I haven't had anymore errors for memory but I do notice some of the scenery flickering like the sky sometimes flickers or the runway looks like it is layed over the taxiway. I do PMDG 747-4 and 8, Airbus X, LevelD 767, Captain sim 707, Turbine Duke, VRS Superbug and REX. I built the computer though to handle the stress of FSX. I have seen computer with less hardware than me and they have max settings and no issue. I have used the venotubo tweak config to help with my FPS. I get good FPS though its just the scenery flickering and small things like that, that cause frustration. I had to turn off my shadows because it looked jagged. Is there anyway around the 4GB max? I do not have it overclocked. I don't want to take the risk of damaging the motherboard so I leave it at its 3.3 GHZ. I have seen online people getting it to 4.3 GHZ with no problem but I just don't want to take the risk. I spent enough money on building the computer. I did get the OS activated with no problem so I don't think it could be the OS? I do get an exception error sometimes when FSX crashes. I don't know it off the top of my head but it says something about "H-Result." I built the computer for Microsoft flight but that sounds like a bust so I guess it will be for FSX.

Josh Scholl

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.