I never wrote that the page file had anything do with VAS. Another poster made that connection.

 

Indeed, I specifically wrote that   the page file error "system running low on virtual memory” is not the same as the FSX error the FSX  error  “computer has run out of available memory”. 

 

 

Source:  Windows Internals, Sixth Edition, Part 2 Microsoft Page 279 by Mark Russinovich, David A. Solomon, & Alex Ionescu

Thanks Gerry but, and this is a big but, that's "virtual memory" and we are discussing Virtual Address Space which is only 4GB's at the max. Lack of VAS is causing the OOM's most of the time as FSX eats it up very fast especially if you have Autogen turned on. In some instances, wrong page file (virtual memory) settings can cause crashes too. I'm not sure if it would cause an OOM but it could be the cause of ntdll.dll crashes. This is what PMDG (and Word Not Allowed) are trying to tell everyone in the PMDG 777 Intro Guide which I mostly quoted above. That the page file (virtual memory), VAS, and system RAM are different things and many get them confused.

 

Best regards,

What slider settings do you use to run that lot?

 

I have

 

autogen off,

 

water textures on high x1

 

dx10

That's mainly where I get my OOM's too is LAX with FSDreamteam's wonderful work they did on LAX its a shame you can't get to enjoy it like we should be able too..

 

 

I also don't have any PMDG aircraft at the moment & I still end of getting the OOM's upon arrival there..  I plan on getting PMDG 777

 

I do my best to take care of my FSX computer, keeping it clean & I only have stuff FSX related on it.. So I don't have any other games or such on this computer only FSX & related material.. My planes, REX4, ASN, UT2, FS Flight Keeper & as well as my scenery from different providers.. I even only have active Airports that I am flying from & to & possibly my Alternate if it happens to have an addon other wise everything else is off or unchecked in the FSX scenery selection screen.. I have like all my ground traffic like cars ,boats & such set to only 20 % & Airport traffic set to zero..  So I am doing what I can to limit the resources that I am using but I guess LA is just too much for FSX, it still gives out on approach..

 

 

Gateway

 

Windows 7 64 bit

 

Intel Core i5 Processor 650  @ 3.20 ghz

 

1GB GDDR DIRECTX11 with 3D Vision  NVIDIA GeForce GTX 550 TI

 

8GB DDR3 Ram

 

1TB Hard Drive

 

I guess next time I plan on flying to LAX, I'll have to try to select that Direct X 10 but I believe the reason I stopped using it is it was making the terminals looked whited out like.. 

That the page file (virtual memory), VAS, and system RAM are different things and many get them confused.

 

Yes but I made point that point very clear originally - "the page file error "system running low on virtual memory” is not the same as the FSX error the FSX error “computer has run out of available memory"

 

Yes but I made point that point very clear originally - "the page file error "system running low on virtual memory” is not the same as the FSX error the FSX error “computer has run out of available memory"

Okay, cool.  Thanks!  I'm just trying to keep this most complicated subject as uncomplicated as possible as there are several members who are obviously confused.  Thanks for your help as you have been very helpful in the past.

 

Best regards,

If you see that the VAS is nearing 4 GB (mostly on final), what can you do to lower the VAS

.

Save the flight, end flight and after that load the saved flight, didn't lower the VAS very much.

Save the flight, shut down FSX and restart it and than load the saved flight, lowers the VAS very much, but than you loose you IVAO connection.

After reloading the flight and connect again to the network is very annoying for ATC.

 

Is there a better solution for this problem?

 

Wener Verwaal

If you see that the VAS is nearing 4 GB (mostly on final), what can you do to lower the VAS

Unfortunately, VAS usage goes the other way. You start out with about 3.3GB's and, by the end of your flight, you should be around 1GB of VAS left. When it gets to about 500MB's, then the FSUIPC utility will start 'dinging' in the background warning you that you are about to run out of memory. If you run that FSUIPC utility for measuring VAS, you can have details of the amount of VAS used during the whole flight and will see it fluctuating down and then back up and then back down and maybe some 'out of memory' error messages in the FSUIPC.log. A tip for everyone: Goto the FSX/Modules folder and send your fsuipc.log to your desktop. This way, at the end of a flight you don't have to go looking for it in Windows Explorer and can just double-click it and see what the log tells you. Sometimes it will tell you it saved you from crashing and, of course, if helps prevent the G3D.dll crash.

 

Best regards,