Hello everyone!

If possible, could anyone explain me why I’m having OOM erros with my VAS (monitorized in process explorer) around 3900000KB (3.8GB)? Shouldn’t it happen after the 4GB mark?
In my previous system, I remember the ding coming from FSUIPC when FSX was about to crash, but now I’m having OOM errors even before that. Really out of ideas here…

I have Win7 x64 and installed that MS Fit it tool that changes 768 to 1024 in the sharedsection entry.

Regards,
Daniel

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Do you have HighMemfix=1 in your FSX.cfg?

3.9 is WAY too close to the edge. VAS in FSX is not static or stable or predictable. Chances are one of yous addons is pushing FSX over the limit. Frequent culprits are photoscenery products like MegaSceneryEarth, Ultrares Airports like FSDT, weather programs such as ASN or REX especially those that insert highly detailed AI or scenery components.

 

Your best bet is to turn off as much AI as possible, set clouds or ground objects no higher than 1024x1024, load only as much photoscenery as you're going to be flying over. Remember also that busy airports like KJFK or KLAX can randomly punch huge amounts or AI and are known cuprits in the VAS wars. To make your system relatively stable you should never exceed 3.0 (and 2.8 is even better) when you're in cruise mode knowing that approaches are going to blitz your system.

 

Hope this helps, plus there are many, many posts on this issue in the CTD forum.

VAS of over 3.8 GB is likely to result in an OOM with FSX.  It has been better explained elsewhere, but in a nutshell, FSX uses its VAS in blocks, when approximately 3.8 GB is filled and FSX needs another large block to load something, it cannot find an empty block of sufficient space and will OOM.  FSX seems to be poor at memory management.