Hi all,I recently got my system to the FPS and smoothness levels that I have been looking for, and begun conducting some flights in the Level D 767. I'm using ASE w/ REX 2OD for weather, RC4 for ATC, and TrafficX @ 60% for traffic. I've been receiving Out of Memory errors shortly after touchdown, usually right about as I turn for the taxiway. This has happened twice between FSDT KLAS and Flightbeam KSFO w/ Megacities LV and SFO enabled, but also between FlyTampa TNCM and KTPA (two lower autogen areas). I'm running FSX Acceleration on Windows 7 64-bit Home Premium, w/ 8GB of Corsair Dominator GT 1866 CAS 8. I have HighMemFix=1 in my .CFGIs there anything I can do to avoid these messages? Will running ASE and RC4 through WideFS over the network help? What sliders can I adjust or what additional .CFG tweaks might be effective?I appreciate any and all help or opinions on the subject.~Andrew

I thought you had CTD's. If you experiencing OOM's it's normally because FSX is heavily loaded (or perhaps there's a memory leak in one of your addons). There's really nothing you can do other than turn down settings - it's occurring because the virtual memory is overloaded. It's not specifically the physical memory causing the problem. You'd have to google virtual memory or "out of memory" error to get the specifics.I used to get those when I flew with LOD of 6.5 and normally with Orbx PNW and payware planes.

I thought you had CTD's. If you experiencing OOM's it's normally because FSX is heavily loaded (or perhaps there's a memory leak in one of your addons). There's really nothing you can do other than turn down settings - it's occurring because the virtual memory is overloaded. It's not specifically the physical memory causing the problem. You'd have to google virtual memory or "out of memory" error to get the specifics.I used to get those when I flew with LOD of 6.5 and normally with Orbx PNW and payware planes.

Which settings do you think I should back off of? I know it's because I'm running out of VAS space, but I'm not sure exactly is causing me to run out. I stupidly installed FSGenesis, RC4, and ASE at the same time. I would think that because ASE and RC4 are running outside of FSX, they should be able to make use of the other 4GB of RAM the system has available. This would seemingly isolate the mesh as the source of the problem. If I back off of the mesh LOD do you think that will eliminate the OOM's? I don't know how much RAM mesh, or autogen, or traffic, or texture detail each take up.Does anybody on here know the answer, or is trial and error the only option for fixing these?

Does anybody on here know the answer, or is trial and error the only option for fixing these?

This is the method I used...Did you get these when you ran a vanilla installation?

Which settings do you think I should back off of? I know it's because I'm running out of VAS space, but I'm not sure exactly is causing me to run out. I stupidly installed FSGenesis, RC4, and ASE at the same time. I would think that because ASE and RC4 are running outside of FSX, they should be able to make use of the other 4GB of RAM the system has available. This would seemingly isolate the mesh as the source of the problem. If I back off of the mesh LOD do you think that will eliminate the OOM's? I don't know how much RAM mesh, or autogen, or traffic, or texture detail each take up.

RRThe 4GB VAS is totally different to your Physical RAM, ASE and RC4 may well run in their own VAS but it is their interaction with FSX in its own 4GB VAS space is were the problems may arise. Is it possible for you to post the OOM or look in the event viewer to see what is causing the OOM error. If it is a Windows Reportable error then there will an ID of the error module (usually a dll) with other error location id codes, etc. We may get an idea of what is causing the error if we have this info.RegardsPeterH

PeterH,After your suggestion of checking the event viewer, it's like a revelation. It looks like the OOM's I've been receiving have been triggered by the D3D9.dll. I researched this, and it appears that alot of people find crashes related to this .dll cease when they run FSX in windowed mode, rather than Full Screen mode. With this information, I decided to conduct a test. In windowed mode, I flew from KSFO to KLAS, and rather than crashing shortly after contact with the approach controller, I was breezing all the way through, and was on short final when I decided that I would look out the 1st class window to see the strip. When I did this FSX experienced a fatal error, and crashed to the desktop.The event viewer indicated that this was caused by the UIAutomationcore.dll. I know that this is a notorious problem with FSX. I shall research it further to see if there are any known fixes. Do you have any suggestions? I fear that this may be just a different symptom of the same problem, and that I'm not actually solving anything.

Ahhhhh, UIAutoomationcore.dllHere, download this file UIAutomationcore.zip (it's a Vista one because the Win7 version causes these errors in FSX - uploaded by me so there's no virus or anything lol)Place the dll in your root FSX folder.https://skydrive.live.com/?cid=408ca931940d5e3c&sc=documents&uc=1&id=408CA931940D5E3C%21121#

RamRGlad you got it sorted!PeterH