Dazz

Yes, you are correct I didn't describe the issue clearly . I was trying to highlight that the available RAM of around 1.4GB was very low on an 8GB system. Mine usually stays around the 3 - 4GB total when in FSX. Again the avaialble RAM shown is at a point in time, it could well have been lower when the Windows message appeared. Also it could be that FSX needed more than the available RAM at a particular point in time, but another app had used the available RAM not leaving enough for FSX to load into and hence the warning.

I still believe something else is utilising the RAM and not leaving enough for FSX to operate in.

It would be interesting to see if the available RAM is the same after a clean boot or after using something like game booster to free up resources.

Yes, I would use VMMAP to see what was happening in the VAS that could be affecting high RAM usage.

Thanks for your input.

pH

That's weird. I flew in and out of KLAX with NGX couple of times, my LOD is 6.5, never seen an OOM.

 

I would suggest using Process Explorer to view the Virtual Size of the FSX, thus really seeing what's going on, if it's really a classic OOM.

 

That's the issue for me at least... I end up doing this after I've already spent time usually in Orbx land with LOD 6.5... so the virtual memory is really taxed at that point.