February 10, 201115 yr Hi all,I'm getting OOM issues (out of memory), which is very strange considering I have HD5970 (2gig) and 8 gigs of ram. I'm using Windows 7 64 bit, my .cfg has been modified by Bjote's auto-tweak tool, not sure if this would have anything to do with it.Is there a free software I can download that can monitor my ram and cpu usage for a period of time? Thank you.
February 10, 201115 yr I delt with this too, probably causes are anything from corrupted textures, scenery, bad fsx.cfg entry, memory going bad, overclocking settings wrong, duplicate acfad2 file. Good luck! It's a pain. What was the last 2 things you installed? Fly in a different area, do you still get them?
February 10, 201115 yr Author I did recently overclock my HD5970. I am going to revert my overclock. It happened yesterday when I was on approach in Paris, there was lots of traffic and my frames were low.I do have memfix on my .cfgDoes anyone know of a software that allows me to monitor my cpu and ram usage?
February 10, 201115 yr Moderator No, an OOM?. Never heard of such a thing. Only a gajillion times. :( I got 220 results in the FSX forum alone! Google OOM with reference to FSX.There you shall find the answeres to the questions you never found.No kidding! OOM is almost always triggered by insufficient VAS (Virtual Address Space) for FSX, which has absolutely nothing at all to do with physical memory......what confuses the matter is that there are multiple causes of VAS exhaustion. The real chore is finding out which is causing the problem (leaky scenery, VAS table too small, etc.) :( Fr. Bill AOPA Member: 07141481 AARP Member: 3209010556 Avsim Board of Directors | Avsim Forums Moderator
February 10, 201115 yr No kidding! OOM is almost always triggered by insufficient VAS (Virtual Address Space) for FSX, which has absolutely nothing at all to do with physical memory......what confuses the matter is that there are multiple causes of VAS exhaustion. The real chore is finding out which is causing the problem (leaky scenery, VAS table too small, etc.) :(--------------------------------------------------------------I triggered an O.O.M. when bringing up 2D pop-up instruments a number of times inflight. I've had no other O.O.M. episode by doing or running anything else. Just pop-up 2D intrument panels from the V.C. and in full-screen mode. I believe they don't release the memory locations from the Memory Stack.
February 10, 201115 yr Does anyone know of a software that allows me to monitor my cpu and ram usage?If you want to track the cause of OOM, then you have to configure Process Explorer (http://technet.microsoft.com/en-us/sysinternals/bb842062) to show like this:Notice the Virtual Size showing as a column. That shows you your memory usage that is relevant to OOM error (VAS, as mentioned in another post). If it crosses 4GB, you are screwed. This way you can track what's causing the trouble. You can notice when it starts climbing and that way start excluding stuff on relevant places and searching for either a file or scenery or whatever else causing it. Pain, I know, I did it... but it's the only way short of reinstalling everything.
February 10, 201115 yr Bill & KostaI'm with you. The VAS can be exceeded by a multitude of processes, etc even .NET Framework can cause FSX to exceed the 4GB Limit!! Physical RAM, unless faulty, is rarely an issue in today'd modern PC's.One of my theories is that the OOM problem may have something to do with "Heaps", "Stacks" and "Handles" which may be caused by some unidentified issue with a third party addon. In some cases the way that the code interacts with the FSX VAS may prevent the Windows garbage collector (GC) from working effectively and eventually an OOM happens. I have never seen an OOM on a 64-bit OS with a plain vanilla FSX SP2 install with no overclocked hardware. The original FSX files are mainly quite small and I do see that some 3rd party addons have huge file sizes and again that might cause some issues wrt Windows GC in certain circumstances. I have noticed that the number of "handles" in FSX increases significantly prior to an OOM, but I do not have the knowledge to pin point the cause or causes.Ah Well! I guess its time to write to Mark Russinovich the sysinternals guru and see if he can offer some advice on how the sysinternals suite could help identify the OOM errors.RegardsPeterH
February 11, 201115 yr Moderator I have noticed that the number of "handles" in FSX increases significantly prior to an OOM, but I do not have the knowledge to pin point the cause or causes.Peter, if you see the number of "handles" continuously and regularly increasing, it's a fair bet that you have a gauge loaded that's causing a looped event to fire (aka: race condition).The most common cause of this is sloppy or careless programming. When an event fires continuously at an ~18Hz rate, it leaves no time for other events to get through, or at best delays them from getting through. Normally, after an event has fired and been processed, the handle for that event is destroyed (released). But, if there's a race condition, no time is left for the handle to be destroyed, and......every unreleased handle takes up a block of VAS! Fr. Bill AOPA Member: 07141481 AARP Member: 3209010556 Avsim Board of Directors | Avsim Forums Moderator
February 11, 201115 yr Hi BillGood possibility re gauges! I wrote to Mark Russinovich yesterday via his blog site, so if he is not too busy we might get some tips and tricks on this OOM issue. I also forgot about 'threads' which can also be quite important.RegardsPeterH
Create an account or sign in to comment