Today my 2gb of ram had came. I added it onto my pc which the ram then totaled 4gb from the 2gb previously. all seems well but the then the erros which says : "fsx has run out of memory ". I dont understand i added 2gb of ram?

If this is the error:

Your computer has run out of available memory" error message when you start Flight Simulator

then this may help: http://support.microsoft.com/kb/892610. Did you make any changes to the paging file?

Regards

pH

i think now its something to do with my hard-drive because i have 300mb free intsead of 500

Maybe this helps: http://pcflightsimnews.blogspot.nl/2012/08/ntcore-4gb-patch.html?m=0

WOW, if you get to a point of only having 500MB free on your hard drive, buying memory is least priority...

Get that hard drive upgraded to an SSD drive ASAP...

All of this has NOTHING to do with physical ram, swap file or HDD size. It is a 32bit O/S limitation.

 

It has been discussed to death over the years.

 

This post explains the situation...

 

http://blogs.msdn.co...ress-space.aspx

 

The best thing to "reduce" OOM errors is to get a 64bit O/S and use FSUIPC (it has a warning dong when you're reaching the limit of VA space.

I have windows 32bit ? could that possibly be the problem?

I have windows 32bit ? could that possibly be the problem?

 

RAM wasn't the issue.

 

As "RCITGuy" mentioned above, when your hard drive has only 500MB free space, Windows cannot swap programs correctly, and it leads to all sorts of strange errors.

 

Start by cleaning C: drive, and make sure you've got at least 5 or 6 GB free space.

 

Probably too many temporary files eating up valuable space.

WOW, if you get to a point of only having 500MB free on your hard drive, buying memory is least priority...

Get that hard drive upgraded to an SSD drive ASAP...

 

An SSD is nice, but it's not going to keep you from running out of memory is it?

if you have 32bit windows there is a switch that can help you.

This post explains the situation...

 

http://blogs.msdn.co...ress-space.aspx

 

The best thing to "reduce" OOM errors is to get a 64bit O/S and use FSUIPC (it has a warning dong when you're reaching the limit of VA space.

Al Stiff

 

 

I have win 7 64 bit and I run into OOM.

 

I read this from that link you posted

 

"Games under 64 bit Windows would only run into this issue if they use the IMAGE_FILE_LARGE_ADDRESS_AWARE flag. 32 bit executables with this flag get 4GB address space in Win64, while those without the flag continue to have only 2GB."

 

So does anyone know how to turn on that flag under Win 7?

 

MAnny

 

HAs anyone done this in win 7?

 

"Any 32-bit application that has IMAGE_FILE_LARGE_ADDRESS_AWARE in its process header, can be given up to 3 G RAM by typing bcdedit /set IncreaseUserVA 3072 at a command prompt and a following restart. The memory share will then be 3G app /1G system instead of the usual 2G app/2G system. The IMAGE_FILE_LARGE_ADDRESS_AWARE setting is given by the application (or not), not by the user."

Things are being mixed up here. If as I say in my second post if the error is "Your computer has run out of available memory" error message when you start Flight Simulator then that has everything to do with Physical RAM, Paging File and HDD space. I was surprised to see the OP was talking about 3/500 Megabytes being left in free space on his HDD. Lets look at that every HDD needs 5 - 10% to carry out file maintenance and if it doesn't have that space then you will get this error irrespective of the OS 32 or 64 bit. Any conventional HDD with less than 40% free space will cause performance issues and less than 20% will start to throw up all sorts of errors including this one. (A SSD can take up to being 90%+ full)

 

Now if this was the 'usual' OOM error for FSX then as many posters have said above it is a VAS error. The OP runs 32-bit OS and if he is running FSX+SP2 then the large address aware flag is set in FSX and it can now access 4GB VAS max. But in a 32-bit OS you can only utilise 2GB VAS (2GB for system/kernel) until he sets the /3GB switch in the Boot.ini or using bcedit Vista and Win 7. He can the access up to 3GB VAS leaving only 1GB for the system (Not to be used ina 64-bit OS which already has 4GB VAS for FSX and 8TB for the OS).

 

We need to know which type of error the OP is experiencing as there are 2 very different solutions, but it does look like his HDD is the issue. From the MS link I give above: "When you start Microsoft Flight Simulator, you receive the following error message:

 

 

Your computer has run out of available memory. Flight simulator will now exit. You may not have enough free space on your hard disk drive. Run disk cleanup to free up space, and then try running Flight Simulator again."

 

So once we kmow which error we are dealing with we can help fix it.

Regards

pH

I have windows 32bit ? could that possibly be the problem?

 

No... See below:

 

An SSD is nice, but it's not going to keep you from running out of memory is it?

Actually, yes it is, doesn't have to be an SSD drive, but a hard drive upgrade is the fix, but what do I know, only been fixing this same problem hundreds of times for parents, their kids, and businesses all over London stuffing their drives with games, apps and pictures until full, calling me asking "How much to upgrade the memory" due to this exact same error, when its not the RAM that's causing this.

 

As he says, his hard drive is down to 300/500mb free space, and any mechanical hard drive that goes below 50% free does start to incur a performance hit, with it getting worse, the closer you get to 100% full until you get this "Out of memory" error. Its to do with how windows handles your page file, and Win7 manages it automatically by default, thus if your out of space, or almost out of space, there is no room left to manage the page file.

 

On a 32bit O/S, the page file is 1.5x the physical RAM size, so a 32bit O/S with 2GB RAM will typically have 3.5GB page file, so windows sets aside 3.5GB space for the page file...

 

So, Husman "had" a 3.5GB page file on his hard drive, and "had" 500mb free space.. No problem..

Now he introduces another 2GB memory, and windows see's it and wants to increase the page file to 1.5x 4GB, which equals 6GB, (2.5GB more than before) but it cant, he only has 500mb free, thus, "Out of memory"...

 

As I said, a mechanical hard drive upgrade will resolve this, but, it will need to be a minimum of 3x the size of his current drive, in order to ensure he stays below the 50% capacity mark to maintain performance, whereas an SSD, you can fill it to 90%+ with NO performance hit at all on speed or read/write times, AND your page file act's far more like real memory due to an SSD being 10x+ faster than a mechanical drive... Oh, and an SSD drive doesnt need a defrag, EVER In fact, trying to defrag an SSD should be avoided, as SSD drives are rated by read/writes, not hours of use like mechanical drives are, so defraging them regularly actually makes things worse.

 

So if current drive is 120GB, then a minimum of 360GB+ should be aimed for...

Page file will be happy to read/write all day long, and no more "Out of memory" problems.

Actually, yes it is, doesn't have to be an SSD drive, but a hard drive upgrade is the fix, but what do I know, only been fixing this same problem hundreds of times for parents

 

What you say makes sense and I'm guilty. I believe I have got over 50% full on my harddrive. Will it help if I have an SSD installed for the operating system and a separate harddrive for FSX?

 

One question though...If this is the case, then why doesn't my X-Plane 10 run out of memory also?

Don't know, I'm still a bit of a newbie to FSX, so I don't know how it runs/installs onto separate hard drives and works with all the "god knows how many add-ons there are for it"..

I have 2 x 450GB SSD drives running in RAID0 on my system, giving me 850GB of SSD space, which I use as 1 drive, almost doubling the SSD speed as each drive only has to do 50% of the reading/writing..

 

If I load up a flight like a 737-800, with flight plan from Heathrow, and click the "Fly now" button, it takes just under 5 seconds before it all pop's up on my 3 x 24" screens ready to go @ 5760x1200 resolution..

 

Whoever gave me that "reputation" point for my post... Thanks, much appreciated :biggrin:

if you have 32bit windows there is a switch that can help you.

 

I have win 7 64 bit and I run into OOM.

 

I read this from that link you posted

 

"Games under 64 bit Windows would only run into this issue if they use the IMAGE_FILE_LARGE_ADDRESS_AWARE flag. 32 bit executables with this flag get 4GB address space in Win64, while those without the flag continue to have only 2GB."

 

So does anyone know how to turn on that flag under Win 7?

 

MAnny

 

HAs anyone done this in win 7?

 

"Any 32-bit application that has IMAGE_FILE_LARGE_ADDRESS_AWARE in its process header, can be given up to 3 G RAM by typing bcdedit /set IncreaseUserVA 3072 at a command prompt and a following restart. The memory share will then be 3G app /1G system instead of the usual 2G app/2G system. The IMAGE_FILE_LARGE_ADDRESS_AWARE setting is given by the application (or not), not by the user."

 

Manny, you do not need to do this with 64bit...(and the FSX EXE is patched LAA by default with SP2). You're already all set and ready to go...