Came across this website earlier, on it is a handy RAM useage tool showing what is being used with installed RAM and virtual memory.Just click on screenshot on bottom of page. It might help us with OOM messages.http://www.whiz-tech...-vista-xp-2000/Here is an example

Edited February 7, 201214 yr by paul123

PaulSorry but this has nothing to do with OOM errors - they are due to an issue in the Virtual (process) address space.This is reporting Physical RAM plus Virtual Memory aka paging file - neither causes OOM errors in FSX.VMMAP is the best tool for the VAS and intepreting OOM errors.RegardsPeterH

Ok Peter, does this apply to computer OOMs as well when using fsx ?

Edited February 7, 201214 yr by paul123

Hi PaulIt depends what the computer OOM is - I've never seen just an OOM message for a PC ie one that was dependent on the OS. If it is a hardware issue then I guess you might see an OOM, but OOM's in software are usually associated with the VAS, eg FSX. FSX is a 32-bit program and when running under Win 64bit it has a max 4GB Virtual (process) address space to load into and if this VAS is fragmented or deplted then you will see an OOM error in FSX.See P Taylor's Blog: http://blogs.msdn.com/b/ptaylor/archive/2007/06/15/fsx-and-win32-process-address-space.aspxThe VAS has nothing to do with the Physical RAM and the VAS is used (simply) by Windows OS to load a program into a virtual space to protect the OS from crashes due to faults in the software, etc, and it is the OS that passes instructions from the VAS to the cpu which then utilises the Physical RAM, etc.If you are running out of Physical RAM and/or paging file the system will usually first slow down quite drastically, then you may get a message similar to, The computer has run out of available memory (this message is software dependant - FSX would give a similar message, and it may also be due to a faulty paging file or not even having a paging file at all) and if you totally deplete all available memory ie Physical RAM and paging file you can get a BSOD sometimes with an obscure exception code. As I say I have never seen an OOM error due to the system itself, but I've had quite a few BSOD's in my time. I run Photoshop CS5 64-bit (which has a huge VAS if LAE is set - we are talking terabytes here) and the other day I had a large number of big bmp images open (from FSX) that I was editing - on a machine running win 7 64-bit but with only 4GB Physical RAM plus a Windows managed PF. Suddenly the whole PC crashed with a "black" screen and no message. The next time I started the OS I experienced a BSOD with meaningless (to me) exception codes with dire warnings of impending doom, but the OS finally started after another warm boot. Now I feel that crash was due to the fact that I had depleted the physical RAM - just a theory and because the VAS was large I did not experience an OOM error in Photoshop.RegardsPeterH

Yeah, one thing is FSX running out of VAS and crapping out with an OOM, and another thing is to hit the system's commit limit (both RAM and page file exhausted)First one will only crash the app and has nothing to do with physical memory, second is an indication of low RAM or that you should increase the size of the page file (not enough physical memory) for that workload and will lock the entire system

Edited February 8, 201214 yr by dazz

Really confused now, can you clarify Dazz (if you can ) which one is causing my error "Your computer has ran out of available memory, please restart FSX with different settings .... . Is it physical memory or VAS ?" I get no freezing, graphic spikes just suddenly that message. I have uploaded a picture of the windows task manager, the memory useage when it crashed was really high, 6GB out of the potential 8GB on my system.Is that the cause ?Also I took Peters advice and used that VMAPP, a screenshot is also attached , even though I have not got a clue how to interpret it.....

Really confused now, can you clarify Dazz (if you can ) which one is causing my error "Your computer has ran out of available memory, please restart FSX with different settings .... . Is it physical memory or VAS ?" I get no freezing, graphic spikes just suddenly that message. I have uploaded a picture of the windows task manager, the memory useage when it crashed was really high, 6GB out of the potential 8GB on my system.Is that the cause ?Also I took Peters advice and used that VMAPP, a screenshot is also attached , even though I have not got a clue how to interpret it.....

That's FSX running out of VAS, as you can see in VMMap, hitting the 4GB limitLike Peter said, you can't see that in RAM Usage Monitor.

Thanks for the reply Dazz, how do you suggest I try and resolve it ? Do you get it on your system ?

Thanks for the reply Dazz, how do you suggest I try and resolve it ? Do you get it on your system ?

No , I don't get it. You'll have to follow an elimination process, with settings, addons, etc...

Edited February 8, 201214 yr by dazz

OK I will try and trigger it, what I did notice with Vmapp is that it does not constantly adjust itself, so do I open the programme when I get the error and then save the screen shot ?

You can manually update with F5, or open fsx in trace mode in the tab "Launch and trace a new process" and it will take VM snapshots periodicallyDoes it happen with any addon in particular?

Edited February 8, 201214 yr by dazz

Triggered the failure Dazz, just been flying the default 737 in dawn conditions over UK, here is that file hopefully

Interesting.... I'd like to monitor my VAS usage next time I fly.

Edited February 8, 201214 yr by benorg

Triggered the failure Dazz, just been flying the default 737 in dawn conditions over UK, here is that file hopefully

Wow, OOM with a default a/c. Doesn't seem right.

Paul & DazzI haven't seen that with a default plane before - Was the UK scenery the default scenery or were you flying in an add-on scenery area.Any changes from a default fsx.cfg like LOD, FFR etc? Any other flight sim exe files running such as weather, etc.Any other exe files running in the background?Anything logged in the event viewer at the same time?Looking at the page table I would guess from the unusable figure 74 MB there is quite a degree of fragmentation, It could be depletion with 3.7GB committed and only 190Mb free. Not sure on this one.There's lots of small chunks of data being allocated 4K which is what I see when I get defragmentation in FSX and I guess that small chunks will be always inherent in FSX.I would try the same scenario following a clean boot (Google this to see what I mean it is not a plain reboot) which will turn off a lot of services if the crash still happens then it is not a background program causing the issue. If you have the trace file saved form VMMAP, I could have a look to see what's going on the some of the other parameters such as the heap etc. I can only offer an educated guess based on your screenie. We really need to see the Thread stack to determine the 32+64 bit thread size needed (eg 1 thread in note pad needs 1.2MB free contiguous VAS) We then look at the free flag and see the largest free block if this is less than the 32+64bit thread size we have defragmentation and an OOM.Can we also get a screenie of the fragmentation view just to confirm that - Viewfragmentation viewAs I say this is an educated guess!!RegardsPeterH

Edited February 9, 201214 yr by peterhayes