Finally I have my new hardware system for flying the PMDG 737 ngx with good frame rates. I am very pleased with it but today, a week after installing everything, I suddenly (after 2 hour flight) get a 'run out of memory error' and fsx was shutting down. On the G15 keybord monitor it tells me that I only use 30% RAM. On the same moment of the chrash  the CPU was 50% active. 

 

 I also have a few moments last week, that when I am (FSX-PMDG747ngx-REX wheater-FSC9) running my flight it stops and a pop-up tells my  FSX does not respond. After approx 4 min the system runs again fine. 

 

My system specs: Windows 7 64 bit, i7 3770K (oc 4.2 Ghz), Asus Radion HD7970 3072 MB, 16 GB RAM, Mobo Asus P8Z77. FSX and other software is installed on a Samsung 500 GB SSD in a separate C.FSX directory.

 

Please assist me to find the solutions with me for this problem. Many thanks.

Errol

 

Try adding HIGHMEMFIX=1 under [Graphics] in the FSX.cfg.

And if this does not help,

maybe you could also try to set the IncreaseUserVA to 3072, allowing FSX as a 32bit application to use 3GB. You can read about that in my other thread over here: http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/

 

All the best,

Christian

I've had this (FSX reporting OOM) only once in a year-and-a half flying the NGX. It has nothing to do with CPU/GPU load. On modern systems FSX doesn't really push these very hard at all. From all of the reading I've done over the past few years about FSX, the following is the most likely explanation.

 

I see you have 16GB of system memory, but my understanding of the way FSX works is that it doesn't utilize all of that RAM. It operates within about a 3.5-4GB memory space, and most of your addons (the aircraft, complex scenery, weather engines like REX and AS2012) must operate within that memory space. Recently when FSDT released their CYVR scenery, quite a few users complained that they were getting OOMs there, and it seemed that most of these same people also had demanding ORB-X regional scenery installed as well. As FSDT explained it this was not the fault of their scenery, but the result of trying to cram too many addons into that 4GB memory space. Eventually FSDT did release an update that allowed for installing less-demanding textures and this seemed to fix most users' problems.

 

When I had the OOM I immediately suspected the problem was caused by all of the REX HD textures I was using. I made some adjustments in my REX settings, flew the exact same flight several times with the same weather, and the problem did not reoccur.

 

But, you know, we may never really know exactly what caused the OOM unless it's repeatable under the same flight parameters which, with so many different addon variables, is nearly impossible to recreate. For now, I'd chalk it up to a fluke. If it happens again under similar circumstances then you can begin assembling a theory about what's causing it and try making some adjustments in the demands your addons are making on that very limited FSX memory space.

 

Also, try Athena's suggestion about adding the HIGHMEMFIX=1 line to your FSX.cfg file. If you don't know how to do this, just ask.

EDIT:

Also consider adding UIAutomationCore.dll to the FSX main folder (reference the AVSIM FSX Hardware and Software Guide).

And if this does not help,

maybe you could also try to set the IncreaseUserVA to 3072, allowing FSX as a 32bit application to use 3GB. You can read about that in my other thread over here: http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/

 

All the best,

Christian

 

Does not apply to a 64 bit OS... <_<

 

Also consider adding UIAutomationCore.dll to the FSX main folder (reference the AVSIM FSX Hardware and Software Guide). 

 

This has nothing to do with OOM errors..

 

This has nothing to do with OOM errors..

My apologies. I suppose my understanding of its usage was inaccurate. 

Do you have any Orbx stuff installed? Even if you're no flying in the area it can take up to 500MB of RAM so deactivate if you have it installed and aren't flying in that part of the world. The himem fix is a must have if you don't already have it.

Very important for fixing OOM and it's for win 7 64bit, just install "Fixit": http://support.microsoft.com/kb/947246

 

I never had OOM after this. I used this on some friends computers, and it works excellent for them too.

 

Again, this is for Windows 7, 64bit only!

 

This has nothing to do with OOM errors..

 

True, but it will help with other crashes, worth installing.

 

 

My apologies. I suppose my understanding of its usage was inaccurate. 

Nevertheless a good advice. See above.

And if this does not help,

maybe you could also try to set the IncreaseUserVA to 3072, allowing FSX as a 32bit application to use 3GB. You can read about that in my other thread over here: http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/

 

All the best,

Christian

This work's great for 32bit windows, i remember when i had XP 32bit

 @(the topic starter)has windows 7 64bit which use up to 4gb already. That actually can do some harm, it's step back for him(to 3gb). And win7 anyway has excellent VAS usage management by default.

What i posted above is for Windows 7. Here is original thread: http://forum.avsim.net/topic/384873-out-of-memory/

Zeljko,

as far as I know increasing IncreaseUserVA to 3072 (3GB) is not a step back. To my knowledge, 64bit systems like Vista,Windows 7 or Windows 8 will asign a total of 4GB of virtual memory to a 32bit process. And when a system makes use of virtual memory, then the kernel also uses virtual memory. Normally Windows will use the upper 2GB of VM for its own (for the Kernel and other things). By setting the IncreaseUserVA you are !not! reducing the total available virtual memory. The only thing you are doing is, that you are altering the distribution of the 4GB VM. Instead of 2GB/2GB (User Program/Kernel) you are shifting this ratio to 3GB/1GB (User Program/Kernel), so your user program (in this case FSX) is actually getting 1GB more of virtual memory than before.

So this is really not doing any harm. The only thing you have to keep in mind is that if you are on a 32bit System or a 64bit System with only 4GB RAM in total, you need to reserve a little bit more memory to the kernel. Therefore, most of the people propose a value of 2560 here, which results in a ratio 2,5GB/1,5GB (User Program/Kernel).

You have to try for your own what is the best way for your system. If there is any strange bahaviour in FSX, like crashes, you need to rise the Kernel memory (lowring the IncreaseUserVA value), then you should be fine again.

 

Best regards,

Chris

FSX comes with the Large Address Aware flag set since SP1 (I think) so it can access a full 4GB in user mode on a 64b OS. The IncreaseUserVA tweak is completely useless in this case

I don't have the IncreaseUserVA tweak but when I go into Process Explorer it shows 4gb available to FSX. So I don't think it's necessary for a 64 bit OS.

Like with the most tweaks/settings, they are strongly related to the system configuration you are using. So what might be helpful for the one system needs not to be helpful in the same way for the other system. As i have written before, windows is still assigning 4GB of memory for a 32bit application like FSX, but a certain amount of this memory is reserved for the windows kernel and is therefore not accessible through FSX. That is always the case! With the IncreaseUserVA parameter you do not set the total available memory to a 32bit application. It will still be 4GB, you are just changing the ratio between the memory the application can access and the memory the Kernel gets.

And yes, FSX comes with the Large Address Aware flag. That's the prerequisite that this change works at all. But it does not help that the application has the ability to access the memory, when the system does not provide it.

 

So in short:

- You still will have 4GB memory assigned for FSX

- IncreaseUserVA only changes the ratio how these 4GB will be distributed to FSX and the kernel.

- This works on 32bit and 64bit systems, because it is related to 32bit applications and not to the operating system itself

 

You can read more about this on the Microsoft Technet sites.

 

 

Best regards,

Christian

 

 

PS: For me [Win8 64bit, 12GB RAM] , and of course also for others, the IncreaseUserVA setting was the solution to a whole bunch of problems regarding FSX and the PMDG. I checked this again and again on a very clean installation without any side effects from other programs, addons or hardware. If you are interested in that I would suggest you also read my other thread here in the forum: http://forum.avsim.net/topic/402872-pmdg-737ngx-crash-to-desktop-when-choosing-end-flight-even-on-a-fresh-and-clean-windows-installation-some-interesting-facts-i-found/