Hi everyone, I have a problem. everytime I run either the Maddog or tonight the AribusX I am getting a OOM error either at the beginning or the end of flight which is exacly what happened with the AirbusX, on approach after about an hour in the air. It was to fly Tampa's KBUF. Before this my machine would just freeze and I had to hard reboot. However I heard the same ding sound as tonight, so I assume it was the same thing, but without the actual OOM error on the screen. I have Windows 7 pro 32bit with 4 gigs of ram. If I run the this 3GB switch I have read about, will that help me, and how hard is this to accomplish? Thanks for your help in advance. :)Warm regards, Jeff

Hi everyone, I have a problem. everytime I run either the Maddog or tonight the AribusX I am getting a OOM error either at the beginning or the end of flight which is exacly what happened with the AirbusX, on approach after about an hour in the air. It was to fly Tampa's KBUF. Before this my machine would just freeze and I had to hard reboot. However I heard the same ding sound as tonight, so I assume it was the same thing, but without the actual OOM error on the screen. I have Windows 7 pro 32bit with 4 gigs of ram. If I run the this 3GB switch I have read about, will that help me, and how hard is this to accomplish? Thanks for your help in advance. :)Warm regards, Jeff

As best I know, the /3GB switch works for all 32 bit operating systems and should help with OOM errors.Search for instructions on this forum - I know how to do it for Win XP but not for Win 7..It basically involves typing in a few commands, not hard to do..

I am getting a OOM error either at the beginning or the end of flight Before this my machine would just freeze and I had to hard reboot. but without the actual OOM error on the screen. I have Windows 7 pro 32bit with 4 gigs of ram. If I run the this 3GB switch I have read about, will that help me, and how hard is this to accomplish? Thanks for your help in advance. Jeff

I don't think there's a boot.ini to edit with Win7, Jeff. Also - if you're not getting the OOM message - you're not getting an OOM.More likely it's the UIAutomationCore.dll which is causing the crash/hang/black screen.Check if you have this file in the root folder of the flight sim:- UIAutomationCore.dll If it's there - right-click on it and check that the version is 6.0.5840.16386. If it's not there - or if the version is different - go here, download it and put it into the root of DSX. DON'T put it anywhere else!Vista UIAutomationCore.dllhttp://www.search-dll.com/dll-files/download/uiautomationcore.dll.htmlversion 6.0.5840.16386Yes - it's the Vista version, and it prevents the hangs and black screens.

Hi everyone, I have a problem. everytime I run either the Maddog or tonight the AribusX I am getting a OOM error either at the beginning or the end of flight which is exacly what happened with the AirbusX, on approach after about an hour in the air. It was to fly Tampa's KBUF. Before this my machine would just freeze and I had to hard reboot. However I heard the same ding sound as tonight, so I assume it was the same thing, but without the actual OOM error on the screen. I have Windows 7 pro 32bit with 4 gigs of ram. If I run the this 3GB switch I have read about, will that help me, and how hard is this to accomplish? Thanks for your help in advance. :)Warm regards, Jeff

See http://forum.avsim.net/topic/231974-out-of-memory-with-vista/page__p__1479857__hl__bcdedit__fromsearch__1#entry1479857 for how do do what you want to do. The thread is about Vista, but Win7 works the same way.DJ

See http://forum.avsim.net/topic/231974-out-of-memory-with-vista/page__p__1479857__hl__bcdedit__fromsearch__1#entry1479857 for how do do what you want to do. The thread is about Vista, but Win7 works the same way.DJ

These are indeed the right instructions.Disregard the part about having 4 GB of memory etc, start with 2560 as a safe value.However, make sure you are running FSX SP2 or Acceleration (includes SP2) for this to work.

Hi everyone, thanks for tour replies. Paul, I think I will have a look for that file first, then if it is the correct version, I will look into doing the switch. I was scared to do this as I've read that if the values are not set correctly you can make your machine un-bootable, unless you boot into safe mode and make adjustments. I honestly would like to avoid screwing anything up too much as about a month ago, I really messed things up by diabling a service, rendering my machine usless. Luckly I was able to restore from an automatic restore point as I have system restore turned off. I will most likely not get to this untill Monday or Tuesday. I will report back everyone. Thanks again. :)Warm regards, Jeff

Well, here is an update and I hope you can make sense of this. Not sure what's going on anymore. I tried the UIAutomationCore.dll. Shortly after that I started getting CTD's which I did not have before like this. One was gd2.dll and another was BEX.dll. I read after researching that this particular UIAutomationCore.dll causes problems. Instructions said to remove it from my system all together. I first removed it from FSX, then I found out that there was another version all along in my Windows system32 folder. OK after that, now I started getting OOM errors constantly, instead of once in a while with any complex add on like PMDG JS41 and also the AirbusX which I want to use both of them more than any other... it figures :( OK, I then did the 3GB Switch. It said to open run, then put the code in there. I did that to the letter. Guess what, next flight OOM error!!! How is this possible I thought to myself! I then did further research and on another forum the instructions showed to open the command prompt as admin and put the code in there. I did that, loaded the AirbusX at KDPX and let it just sit running for 30 minutes, then took off and flew around 10 minutes with no error. However all of my OOM errors before this occurred at KPHL which I am terrified to go there again and try it. I NEVER had problems like this before the AirbusX was installed. The only OOM or freeze of FSX was with the Maddog 2008pro which I don't use anymore. I've flown the PMDG JS41 for hours without a single problem. Now after a few minutes in the air...Bang..OOM with the JS41!! Other than that, not one single problem. Now I am starting to wonder if the AirbusX did something to my system if that's possible?? Anyway, Being I did not get a OOM error last flight ( but not at the same KPHL area ) I have to test more I guess. Can anyone shed any light as to what could be the *&)($^# problem? I am beyond frustrated now and afraid to touch my sim. It ran without any issues before and I am thinking of doing a system restore point from before the AirbusX. The only problem there is that FSX is installed on my "I" drive, not "C" so will the restored point fix the issue? I'd prefer no to do this as I love the Airbus as it runs very nice and smooth. One more thing.. Can having DEP turned on cause OOM errors? Windows7 won't give me the option of disabling it so I am stuck there. Sorry for going on and on. Just trying to find a a solution without losing any AC or reinstalling anything. Thanks a million in advance. Ok...deep breath now...... ahhhhhhhhhh Was I ranting or having a bad dream??? Thanks for listening everyone!Warm regards, Jeff

then I found out that there was another version all along in my Windows system32 folder. OK after that, now I started getting OOM errors constantly, instead of once in a while

Oh my! You should NOT have removed the stock UIAutomationCore.dll from the ..\Windows\System32 folder! That .dll is use by Windows itself...The advice to place the Vista version of UIAutomationCore.dll in the ..\FSX folder is sound. Windows will use that instance of the .dll instead of the "default version..."

Thanks, Bill. There's another post here, yesterday - by FlightSimGuy - http://forum.avsim.net/topic/321253-fatal-error-crash-in-fsx/ who is pointing to a Microsoft fix-it site - which advises that one removes the .dll from the WOW64 and System32 folders - he claims "it fixed mine". I don't know who writes this stuff.FSX will look for the UIAtomationCore.dll in it's own folder first! That's where to put the dll. Please - Don't put it anywhere else, and please - don't delete those system dll's.

I did have a quick question, but first, my system rebooted and works fine without the dll in my windows system32 folder. I have the dll backed up in a folder on my "I" drive. I will put the vista version back into my FSX root folder and see what happens. My main question is when the 3GB switch is applied, do you have to do it everytime you reboot windows, or is this a permanent thing until changed otherwise? That is the only confusion I have with the switch. Thanks in advance guys.Warm regards, Jeff

I think my last question got lost here. Anyone who knows the answer to the following, if you might be able to help me? I think I've got the OOM issue at bay now. (Hopefully) When applying the 3GB switch, does this setting stay after rebooting or does this need to be applied whenever I reboot? From what I've read between the lines, it seems to stick unless changed. Thanks for any advice. As a follow up for anyone following my OOM issues, I still need to test my flights around KPHL as that was where my OOM errors were happening. I did complete some tests around KPDX with success, however I wonder if it is something that possibly got corrupted in my scenery around KPHL that can cause this? It is the default scenery other than GEX installed. The good news is that I've loaded the PMDG JS41 at KPDX and let it sit for almost 45 minutes to 1 hour with the external power on. I then proceeded to take off and fly for a good 40 minutes and had no problems. I did the same for the AirbusX. I just need to know if the 3GBswitch setting sticks or not after a reboot? I now have to get up the courage to go back to KPHL to test things out. I live in the "burbs" near KPHL and that's why I fly there a lot. Not that I would mind moving to the west coast and making KPDX my home airport! Thanks in advance and I appreciate all of your help everyone. :)Warm regards, Jeff

The setting "sticks," so you won't have to be concerned about it again... ;)

Bill,Thanks for your reply. I just want to take a minute to say that you are one of the nicest, most helpful individuals among the many in the community. You have always been kind and very patient even when sometimes we... well, I go off on a explosive long winded tangent when things go wrong in the flight simulator. Your work and knowledge here and through your work at Eaglesoft is appreciated more than words can express. Thank you and I wish you and yours a very happy and safe holiday season. :)Warm regards, Jeff

I'm so angry with this sim, I run 64bit win7 with 6gb ram and I'm getting OOM errors now, even with highmemfix=1 in the fsx.cfg file and a default system managed page file. What gives??!??!