I never got this error before, and the only thing I can think of is that I've been leaving my computer on all evening when sleeping lately. Although I didn't do that last night. What could be the culprit?

I never got this error before, and the only thing I can think of is that I've been leaving my computer on all evening when sleeping lately. Although I didn't do that last night. What could be the culprit?

Search for OOM errors on this forum..

If it says that you're running out of virtual memory, check your hard drive to make sure that you've got plenty of free space available. Windows uses your hard drives like RAM to cache data from your program while your flying and if there is less space available than it thinks it needs, you will get a message that you are running out of virtual memory. Free up as much space as you can by deleting temp files and any unnecessary files that you find.

Also, you can check and adjust the amount of virtual memory you have. There is some disagreement on this but I let Windows set my amount of virtual memory. seems to work well. If you don't know how to set virtual memory, tell me what OS you have and I can get you started.Bob

If it says that you're running out of virtual memory, check your hard drive to make sure that you've got plenty of free space available. Windows uses your hard drives like RAM to cache data from your program while your flying and if there is less space available than it thinks it needs, you will get a message that you are running out of virtual memory. Free up as much space as you can by deleting temp files and any unnecessary files that you find.

I don't think so... Virtual memory problems with FSX tend to be an address space issue

What type of error are you receiving and what are your system specs?

I don't think so... Virtual memory problems with FSX tend to be an address space issue

That may be so, but it's always good to check the basics first and it never hurts to keep your hard drive slim and trim (no unneeded files, defragged). Personally, I have my virtual memory set to 2.5 times physical RAM (8 GB) with the initial and maximum sizes set to the same value. 1.5 times physical RAM is usually considered a good starting point to find the right size for your system.

That may be so, but it's always good to check the basics first and it never hurts to keep your hard drive slim and trim (no unneeded files, defragged). Personally, I have my virtual memory set to 2.5 times physical RAM (8 GB) with the initial and maximum sizes set to the same value. 1.5 times physical RAM is usually considered a good starting point to find the right size for your system.

Nothing wrong with keeping your system slim and trim... but this goes to show how different definitions can become a constraint over time, even when you expect them to be plenty big..Definition of Virtual Memory in the OS, physical space on the hard drive, and last but not least:available virtual address space for FSX to run in.. Any of these can be a bottleneck.

Virtual memory is the page file on the disk - Windows will write to it if it runs out of physical RAM to use. User address space is different, it's part of the kernel's protected mode system (which is essentially how the OS prevents one program's crash from taking down the whole OS). User address space also gets called "virtual address space" - perhaps that's what you're thinking of Bert?To the OP - it's important which exact message you're seeing. Does it actually say "virtual memory" in it or does it just say "out of memory"? If it actually says virtual memory, then you need to look at the size of your page file (increase it or set it to Windows managed) and make sure there's plenty of free space on the hard drive for the pagefile to grow into. If it just says "out of memory", that's a user address space error and it means you need to upgrade to a 64-bit operating system most likely. 32-bit versions of Windows are limited by default to 2GB of user address space and FSX+addons can easily exceed this and cause the error message. It has nothing to do with how much physical RAM you have either by the way, this is an internal thing in the OS - you can see an OOM error on a system with 12GB of physical RAM if the user address space is limited.

Virtual memory is the page file on the disk - Windows will write to it if it runs out of physical RAM to use. User address space is different, it's part of the kernel's protected mode system (which is essentially how the OS prevents one program's crash from taking down the whole OS). User address space also gets called "virtual address space" - perhaps that's what you're thinking of Bert?To the OP - it's important which exact message you're seeing. Does it actually say "virtual memory" in it or does it just say "out of memory"? If it actually says virtual memory, then you need to look at the size of your page file (increase it or set it to Windows managed) and make sure there's plenty of free space on the hard drive for the pagefile to grow into. If it just says "out of memory", that's a user address space error and it means you need to upgrade to a 64-bit operating system most likely. 32-bit versions of Windows are limited by default to 2GB of user address space and FSX+addons can easily exceed this and cause the error message. It has nothing to do with how much physical RAM you have either by the way, this is an internal thing in the OS - you can see an OOM error on a system with 12GB of physical RAM if the user address space is limited.

...and if you are running a 32 bit OS, you can increase this space by using the /3GB flag... :(

Another cause for the "Your system has run out of available memory" message could be a result of either scenery "leak" or a misbehaving/poorly coded gauge that "eats handles..."A diagnostic method is to open the Task Manager's Performance tab and watch the System Handles display. If you see it continuously increasing in nearly constant "chunks" is a fair bet you've got a "leaky scenery" or "misbehaving/poorly coded gauge" problem.In that case, load a default a/c (such as the Trike or C172) and check again. If the number of System Handles continues to increase, it's probably the scenery currently loaded.If the System Handles remains fairly constant, then it's most likely the a/c you had previously loaded.

...and if you are running a 32 bit OS, you can increase this space by using the /3GB flag... :(

True but that can cause it's own set of problems if you start taking up so much of the available space that the video card's memory doesn't have address space room etc... I've seen all kinds of weirdness come from that setting, CTDs, bluescreens etc - it's very system specific as to whether it works or not. The for sure way to fix it is going to 64-bit.Not sure why you're doing the roll eyes at me, I've probably got more experience with these errors than anyone here - I deal with it every single day at support.

I'm getting those same messages, in win7 64bit, in Orbx NA Blue

Not sure why you're doing the roll eyes at me, I've probably got more experience with these errors than anyone here - I deal with it every single day at support.

Sorry, bad choice of smiley.. :( Agree that a 64 bit OS is the ultimate fix.

If you use a fixed-size page file you probably should look at task manager while running FSX and most intense addons such as weather programs and complex aircraft and monitor committed memory vs the system commit limit to make sure you aren't getting close.scott s..