There's 2 reasons. One is FSX does not cleanup after itself as efficiently as it could. For example it was shown that scenery from the origin was still allocated in VAS at destination. The other issue, is VAS must also be contiguous. So for example say FSX requires 50MB address space for data, and you have 300MB free, but the largest contiguous space you have available in that 300MB is 48MB, then FSX will still OOM. This is why most OOM's occur toward the end of the flight, when a large amount of data, for the destination airport/AI is loaded, usually on approach or just after landing, and VAS is at it's most fragmented state.. This can be managed to a point by freeing up unnecessary space up front. The way I do it is to set ManualLoad to True to all my optional startup dll's in the dll.xml file. Usually the dll's for aircraft addons (No sense loading Captain Sim DLL's when I'm flying a PMDG aircraft). When FSX starts it will then ask which dll's you want to load, say no to all that are not being used. With our craving though for High 4096 Res scenery (The SDK specifies FSX only officially supports a max 1024 res graphics) and high detailed complex system aircraft, somethings gotta give. You can't get away with sticking 10 pounds in a 5 pound sack for long with out it coming back to bite you once in a while.