{yawn yawn -- sorry } Bottom line is you probably will have to reduce the amount of memory needed, by either turning down sliders, or by not running some of the other addons you have running in FSX. -- Or Update to Windows 7 64 Bit. You migt get some mileage from using one of the many "Real time" Memory defragmenter.I have had some good success with these, when running FSX is heavily loaded with addons, ob a 32 bit OS. Geoff

Thanks Geoff, no need to appologise for trying to help out mate!Like the OP I do have Win 7 64-bit. Will try out a some sort of memory utility, do you have any recommendations? There are a lot of them out there...

Hello, I also have these bloody OOM's, also with other "heavy" planes. Of course, it has something to do with the add-ons you'r flying with (like for EHAM approaches: if you installed Aerosofts Amsterdam together with NL-2000 fotoscenery).I have Win 7 64bit, so I thought, I can install more RAM. Now, I've 12 GB RAM installed. Still have the OOM's. Somewhere, I read a couple of posts, telling me, that since FSX is a 32bit program: FSX can only adress roughly 4 GB RAM, not more. When I did read this messages, I was quite frustrated with my 12 GB. On the other hand, it seems logical though.If it's really true, then we have to blame Microsoft's FSX in the first place, and not the producers from demanding add-ons. Regards, Henk

Not necessary! FSX was released almost 5 years ago. Maybe ACES Studio thought 1024x1024 resolution textures would be enough for this Flight Simulator version and thus they did not care much about manage large volumes of memory, 64-bit architectures and so forth. Anyway now FSX add-on developers want to take advantage of today's hardware capabilities but FSX is not good platform for that. Remember, 737NGX is only an add-on - not completely independent game! All of us should think a bit about it...

I actually think that this is being caused by a memory leak . PMDG should investigate

Not necessary! FSX was released almost 5 years ago. Maybe ACES Studio thought 1024x1024 resolution textures would be enough for this Flight Simulator version and thus they did not care much about manage large volumes of memory, 64-bit architectures and so forth. Anyway now FSX add-on developers want to take advantage of today's hardware capabilities but FSX is not good platform for that. Remember, 737NGX is only an add-on - not completely independent game! All of us should think a bit about it...

You're correct only for a small part.You will remember, that FSX was developed for computers with one core, although lots of us had already dual core processors. They upgraded that with the service-packs.When FSX was issued, they had already a 64bit OS developed, but, indeed, most of us used WinXP 32bit in those days. They should have upgraded FSX to 64bit later. Finally you can run a 64bit program in 32bit mode (and not reversed).That's why I blame Microsoft for bringing out FSX as a 32bit program without looking then a little bit more in the very near future.........and I'm sure, they knew this all. Henk

I have the same problem on W7 64, no matter what I do, even if I decrease resolution, pull down sliders, unistalled AI traffic etc.. sooner or later I will get OOM error, which really sucks for 70USD addon, that is not usable atm.. hope PMDG will release the patch real soon. martin

I am in that club also and OOM is 100% in EGLL from Aerosoft with the NGX. Did someone state that it is only happening when FSX adress more than 4GB or can it get OOM at 2GB for instance? Here is a thought. Why is it that FSX is better and smoother with the Autogen on Extremely Dense. This is contraversial with the above problem Michael

For those interested (I couldnt find the answer). The above recommendation (bcdedit /set IncreaseUserVA 2048) works on W7 x32 as well as Vista x32. I made the mistake when I upgraded my computers innards to stick with x32! I'm hesitant to upgrade to x64 as it seems people running x64 are also suffering from OOMs...... unfortunately the NGX is pretty much useless for me even at a default airport. Did a quick flight between YBAS-YAYE and it died after landing (plane freeze while FS continued to run) followed by the OOM. Tried to load up the NGX at YMML with Orbx scenery and I got the OOM pretty much as it finished loading..... Intel i7 8704GB DDR3 RAMGeForce 460 1GB

Ok decided to go through the tutorial flight and crashed with an OOM error just sitting there typing entries per the tutorial into the fmc.Before this I have just been handflying the NGX over my Megascenery Earth scenery with no problems up to a few hours at a time.Now just sitting at the end of the runway and reading the tutorial and making a few entries and poof! This is not good.I run XP with 4gb and the 3gb switch.I have followed the manual to the jot and tittle on system setup.i have used the .cfg tool at venetubo.com as per the manuals recommendation.My FSX rig runs perfect with XP and every other add_on.So whats next?Chris S

Guys and Gals IMPORTANTHaving tested now quite a bit and having spoken to some gurus at work here a few hints that can help us further Start FSX and Task ManagerGo to processes and click on view then Select ColumnsAdd the followingUser Objects , GDI Objects, paged pool and NP Pool That should doNow fly like hell do everything to get an OOMNow the important partOnce you have an OOM DO NOT CLOSE ITLeave it and check the task manager and check the data there and write it down and send this data in a ticket to PMDG maybe that helps themto identify where the problem lies. I will leave more info on this as it becomes available.I have seen a lot of you writing ' this is unacceptable' This might beBut we need the data to carry this forward and help others the same as ouselves to get this sorted.The chances are high this could be a problem generated by the NGX and if so there is no need to shout at PMDGIn general they have done a fantastic Job.So thereNow let us ask them to help us with our problem in a nice fashion. No need to make remarks of $100 and it wasn't even a 100 if was only 69.99 Lets be professional about this and take this forward..Thx guys and gals

Ok decided to go through the tutorial flight and crashed with an OOM error just sitting there typing entries per the tutorial into the fmc.Before this I have just been handflying the NGX over my Megascenery Earth scenery with no problems up to a few hours at a time.Now just sitting at the end of the runway and reading the tutorial and making a few entries and poof! This is not good.I run XP with 4gb and the 3gb switch.I have followed the manual to the jot and tittle on system setup.i have used the .cfg tool at venetubo.com as per the manuals recommendation.My FSX rig runs perfect with XP and every other add_on.So whats next? Chris S

ChrisDid you try this with the Task Manager?

The chances are high this could be a problem generated by the NGX and if so there is no need to shout at PMDG

I believe the chances are very low that it has anything at all to do with the PMDG NGX.I am running Windows7 64bit and have been plagued with OOMs for the last year with FSX.I started realizing it while flying the Super80Pro.The shop that built my computer suggested that I turn off SuperFitch, so I did and that helped a lot, but I still had OOMs.When flying the NGX, I again got OOMs after going about 400 miles. The OOMs would occur on decent into my destination.My FSX was installed in Program Files(86). Ryan suggested that I install it directly in the C: drive.I uninstalled FSX and re-installed it in C:I tweaked my FSX.cfg with "Bojote's" tool.I set my nVidia GTX480 with Inhancer.I installed FPS limiter. I have UTX, GTX, Orbx and REX Overdrive.Last night I took off from KSEA using real updated weather from the REX weather engine, heading for PANC with my fuel tanks almost full, but I fell asleep and forgot to set TD Pause.The NGX passed PANC and went on deep into northern Russia before it ended up in an empty field.When I woke up, expecting to do the decent, I seen the NGX just sitting there, alarms going off and with no fuel. I checked the MAP and could see the route it flew to northern Russia.FSX and the NGX were both still running perfectly.There is nothing wrong with the NGX that is causing OOMs. If you are running out of memory, check your configuration or check to see if you are having an overheating problem.The problem is in your computer, but the NGX is demanding and is requiring the best from your computer, so if it is not configured correctly, you will have OOMs. Bob

ChrisDid you try this with the Task Manager?

Not sure I'm following you on the task manager,One thing I did find though, if I put the plane on 08R at EGKK, then walk away from the computer for an hour or so, then come back and start programming the FMS, it willl OOM by the second or third data entry.If I start programming immediately after placing the plane there, I can get as far as final approach. Chris S

Not sure I'm following you on the task manager,One thing I did find though, if I put the plane on 08R at EGKK, then walk away from the computer for an hour or so, then come back and start programming the FMS, it willl OOM by the second or third data entry.If I start programming immediately after placing the plane there, I can get as far as final approach. Chris S

Chris Start your FSX and also the task manager. Leave the task manger open in the back ground. Now wait for the OOMThen look in the task manager and see what it says for the FSX as said before at the top add the other parts whichc are the interesting onesUser Objects , GDI Objects, paged pool and NP Pool Thx Ian

Chris Start your FSX and also the task manager. Leave the task manger open in the back ground. Now wait for the OOMThen look in the task manager and see what it says for the FSX as said before at the top add the other parts whichc are the interesting onesUser Objects , GDI Objects, paged pool and NP Pool Thx Ian

Ok roger that.Thanks Ian Chris