Win7 64 bit system with lots of overhead and getting the OOM and the skeleton from the selection menu....seems random though....looking forward to a fix. cheers

Getting a message stating 'Your computer has run out of available memory.'I am running Win XP 32bit, E6700 3.2Ghz CPU, 4gig ram, Ati Radion HD 5670 Graphics Card.Would appreciate any feedback.cheersJohn Cornish

Best solution is to run FSX with Windows 7 64 bit. However, in the meanwhile, still using Windows XP 32 Bit, you should be able to eliminate this "out of (Virtual memory) error" by using "The 3 GIG switch".This will increase the amount of memory addressable by each application. ( ie Give FSX more addressable memory ) Increasing from the default 2 Gigs, to 2.5 Gigs, should be sufficient. There is probably no need to opt for the full 3 gigs. http://technet.microsoft.com/en-us/library/bb124810(EXCHG.65).aspx WARNING: Be VERY CAREFUL when editing the boot.ini file. ( use Notepad, not a word processor !!)If you corrupt the BOOT.INI file, windows will not boot !! Geoff

Best solution is to run FSX with Windows 7 64 bit. However, in the meanwhile, still using Windows XP 32 Bit, you should be able to eliminate this "out of (Virtual memory) error" by using "The 3 GIG switch".This will increase the amount of memory addressable by each application. ( ie Give FSX more addressable memory ) Increasing from the default 2 Gigs, to 2.5 Gigs, should be sufficient. There is probably no need to opt for the full 3 gigs. http://technet.micro...(EXCHG.65).aspx WARNING: Be VERY CAREFUL when editing the boot.ini file. ( use Notepad, not a word processor !!)If you corrupt the BOOT.INI file, windows will not boot !! Geoff

Hello Geoff, Thanks for the reply. Checked the thread supplied but the /3G switch doesn't seem to apply to Win XP. 'The /3GB switch is supported only on the following operating systems:

• Windows 2000 Advanced Server
• Windows 2000 Datacenter Server
• Windows Server 2003 Standard Edition
• Windows Server 2003 Enterprise Edition
• Windows Server 2003 Datacenter Edition'

I find it strange that there is memory problems before any scenery is loaded. I am still at the Free Flight screen where the only demands on CPU, memory and graphics card is of the rotating model. I think that there is a fundamental problem with the way the 737NGX program handles system memory.. Thanks for your input.cheersJohn Cornish

DO ALWAYS USE 64BIT!!!!!!!i have not seen a OOM in fsx or fs9 in 2 years now since in get myself 6 gb kingston memory and a win 7 64bit

The 3 gig switch does apply also to Windows XP ( Sorry, I thinkI gave you a PRE XP OS MS link.) ieWindows XP ProfessionalWindows Server 2003Windows Server 2003, Enterprise EditionWindows Server 2003, Datacenter EditionWindows 2000 Advanced ServerWindows 2000 Datacenter ServerWindows NT Server 4.0, Enterprise Edition Chech out the later linkhttp://msdn.microsoft.com/en-us/windows/hardware/gg487508 I run it on one of my older "Compatability" development systems, and it is 100% sucessful. Another thing that can be causing "out of memory" to occur, is if your page File is FRAGMENTED or corrupt. If you have had enough of these issues, and want to try a solution, I would recommend. (1) Defrag the drive that has your page file on it. ( Typically the C drive).(2) Delete the page file on the C drive. ( If you have another drive, set a tempory page file on that drive).(3) Defrag the C drive again.(4) Delete the page file on the D drive,and set a new page file on the C drive. make sure is is a FIXED size, and not controlled by the OS. Use MAX recommended size as indiacted when you create it.(5) Re-boot (6) Edit the boot.ini file to include the 3 gig switch, with the option to use 2.5 gigs.(7) Re-Boot. (8) If FSX is not on your C drive, ,,make sure you defrag the FSX drive. Hopefully, this will correct your issue, and you will never get an OUT OF MEMORY error again ( I don't on the XP system) There is also a registry setting, that will make you computer "CLEAR" the "page file" on Shutddown/reboot.While this is mainly a SECURITY featue ( lost of stiff remains in the apge file between boots .. ie bank account Nubmers etc), the action of CLEARING the "page file" will help to keep it Defragmented. TAKE CARE EDITING THE REGISTRY !!!TAKE CARE EDITING the "BOOT.INI" file ============The above is just some advice. As you have done before, I recommend , given the above information, you do some futher research, before making any changes. ie Do not do changes just based on my sole recomendation. Geoff

Absolutely on 64bits system, Out of memories events are mostly fixed.

Fortunately you said "mostly fixed". I experienced the same message by using Win7*64bit and 16GB memory. Regards,Axel

Just a thought - those with out of memory issues - do you have more than one pagefile using two or more different hard drives ? Thanks,

Flying in the ORBX PNW area now, FSX's virtual size in Process Explorer is 3.8GB, so it's in the brink of crashing. I got a g3d.dll CTD in PNW earlier today too... maybe both are related EDIT: and just crashed: g3d.dll again

Hi Dario! I had also a severe memory leak in PNW KBFI and my virtual size was also around 3.8GB just staying at ground doing nothing!!! My solution was to remove a fps limiter named antilag and set the frames in FSX to unlimited. Virtual memory use was at about 2.4 after removing the d3d9.dll file from FSX root. BrgdsPatrik Soderberg

Just a thought - those with out of memory issues - do you have more than one pagefile using two or more different hard drives ? Thanks,

Hi Armen. I'm currently using a single fixed 4GB page file in the VRap. I can test different configs if you think that'll help, but the MD11 herself hits 3GB of VAS in the same situationI'm pretty sure it's just a matter of accepting FSX's limitations and lowering the sliders a bit in those uber demanding areas

Hi Dario! I had also a severe memory leak in PNW KBFI and my virtual size was also around 3.8GB just staying at ground doing nothing!!! My solution was to remove a fps limiter named antilag and set the frames in FSX to unlimited. Virtual memory use was at about 2.4 after removing the d3d9.dll file from FSX root. BrgdsPatrik Soderberg

Thanks Patrik. 2.4 is a lot less than what I see here. Must be different FSX settings I guess. I don't use the antilag limiter and my frames are unlimited too

I also just had a OOM in EGLL on approach rwy 27R for the first time in month. System is win7 64bitFSX SP2Aerosoft EGLLPMDG 737-800NGXHD5870 1GBRaptor 300GB drive Setting is High with autogen at Very dense Michael

Folks with 16 GB of RAM desktops exaggerating a bit in my opinion. What application needs or can handle such amounts of memory? I also used /set IncreaseUserVa 3GB switch in my Vista 32-bit to be able to run DCS A-10C. Now I've removed this option but "skeleton 737NGX" appears in both cases. I think if PMDG Team placed this issue on their tracking buglist ("Out of memory issues/32-bit issues") it must be a reason for that!

Getting a message stating 'Your computer has run out of available memory.' It then goes on to say that I need to tweak settings in scenery etc to reduce demand on memory. At this stage I haven't left the FSX Free Flight screen.So I have loaded FSX, walked away for a while and returned to find the memory message. I restarted and watched the whole process and the selected rotating 737NGX starts up in skeleton form then slowly the outer skin is drawn. After about a minute it returns to skeleton form and I get the memory alert.I have tried ******* Altuve FSX.CFG tweak but to no evail. I can run PMDG 747-400X and IFly 737 with no problems.I suspect 737ngx is very demanding on computer resources.I am running Win XP 32bit, E6700 3.2Ghz CPU, 4gig ram, Ati Radion HD 5670 Graphics Card.Would appreciate any feedback.cheersJohn Cornish

i have this same problem on win-7 64 bit operating system-exactly the same scenario and fsx shuts down,i have [email protected], 8 gb ram, gtx 590,cant fly ngx any more nowvivek anand

Just to clear up a technicality - the issue is not running out of memory (FSX can only access 2 Gb of memory by default), but running out of large enough contiguous memory space for the largest allocation requested at any moment. In a 32-bit system, that can only address 4 Gb of RAM total, this problem is encountered sooner than on a 64-bit system as the 64-bit system has much more memory it can play with, though the 64-bit system is not immune to this problem, especially if it has 4 Gb or less memory installed and a small or no swap file. More physical memory will fix this on 64-bit systems. All the /3Gb switch is doing is telling the OS to allow a 32-bit app access to 3 Gb of memory not 2 Gb (at the expense of kernel memory which is simultaneously reduced from 2 Gb to 1 Gb) but the 32-bit OS still hits it own 4 Gb limit eventually. Best regards,Robin.

I also experienced out of virtual memory error when FSX with 737NGX loaded was running on Vista desktop for a longer time period.

More physical memory will fix this on 64-bit systems.

More physical memory on 64-bit system will not fix the issue with respect to FSX. FSX is a 32-bit program, and will still have those limitations when running on a 64-bit platform. So regardless, FSX can only use 4GB. The advantage of the 64-bit platform is that additional memory can be used for the operation of the OS and other addon programs that run outside of FSX, whereas a 32-bit platform can only utilise 3-4GB max in total. I've had the OOM on my 64-bit system and it's simply a case of reducing the overhead by pulling back the sliders. Unfortunately, compromises have to be made. Chris