Using boxed version of MD-11X with latest patch, FSX patched, Windows XP (SP3), 2 Gig ram, 8800GTX, Intel core 2 quad 6600 @2.4; nothing overclocked.Freeze occurs with oom error message in tutorial flight about 5 minutes after takeoff.Hope you can help.ThanksRichard

Freeze occurs with oom error message in tutorial flight about 5 minutes after takeoff.

There are no known memory leaks in the MD-11 software.However, it's much more "memory intensive" than your typical add-on (or default MS airplane, for that matter). Therefore, any memory leak (regardless of its source) will become more evident.That said: There are known issues with buggy scenery, and other third party add-ons.What do you have installed, above and beyond the base FSX install?

Using boxed version of MD-11X with latest patch, FSX patched, Windows XP (SP3), 2 Gig ram, 8800GTX, Intel core 2 quad 6600 @2.4; nothing overclocked.Freeze occurs with oom error message in tutorial flight about 5 minutes after takeoff.Hope you can help.ThanksRichard

I imagine you've already checked this, but do make sure you've given yourself enough virtual RAM (ie, a big enough swapfile). If I were you, I'd start by checking that you're letting the system take complete control over virtual RAM. If this still doesn't work then I'd try setting a really big swapfile manually (6Gb) to see if that helps. Remember to re-boot between each change you make. You should easily find detailed instructions on this by googling.As you only have a total of 2Gb, you are unlikely to benefit by enabling the physical address extension (PAE) option in XP (usually accompanied by the /3GB switch option for those with 4Gb of RAM or more). But if nothing else works, you might give it a go anyway. Again, you should easily find detailed instructions by googling.Otherwise you should just bite the bullet and add another 2Gb. The cost should be pretty low these days. I must admit I'm be quite impressed that if you can get FSX to run properly with complex add-ons at more than very basic settings on as little as 2Gb. I see that the minimum spec for the MD-11 is 1Gb - but presumably this would need everything turned down to its absolute minimum setting to work at all. On my PC, the "commit size" (judged by the Task Manager) frequently exceeds 1.5Gb and regularly exceeds 2Gb. Same with the working set and other memory-related variables. So I have always assumed that 4Gb of system RAM is necessary as a sensible minimum: ~2.5Gb for FSX and ~1.5Gb for the OS and services etc. Tim

There are no known memory leaks in the MD-11 software.However, it's much more "memory intensive" than your typical add-on (or default MS airplane, for that matter). Therefore, any memory leak (regardless of its source) will become more evident.That said: There are known issues with buggy scenery, and other third party add-ons.What do you have installed, above and beyond the base FSX install?

Hi Melkor and thanks for replying. I have no scenery add-ons but am running the PMDG 747, LDS 767 and the demo version of FSPassengers.Richard

I imagine you've already checked this, but do make sure you've given yourself enough virtual RAM (ie, a big enough swapfile). If I were you, I'd start by checking that you're letting the system take complete control over virtual RAM. If this still doesn't work then I'd try setting a really big swapfile manually (6Gb) to see if that helps. Remember to re-boot between each change you make. You should easily find detailed instructions on this by googling.As you only have a total of 2Gb, you are unlikely to benefit by enabling the physical address extension (PAE) option in XP (usually accompanied by the /3GB switch option for those with 4Gb of RAM or more). But if nothing else works, you might give it a go anyway. Again, you should easily find detailed instructions by googling.Otherwise you should just bite the bullet and add another 2Gb. The cost should be pretty low these days. I must admit I'm be quite impressed that if you can get FSX to run properly with complex add-ons at more than very basic settings on as little as 2Gb. I see that the minimum spec for the MD-11 is 1Gb - but presumably this would need everything turned down to its absolute minimum setting to work at all. On my PC, the "commit size" (judged by the Task Manager) frequently exceeds 1.5Gb and regularly exceeds 2Gb. Same with the working set and other memory-related variables. So I have always assumed that 4Gb of system RAM is necessary as a sensible minimum: ~2.5Gb for FSX and ~1.5Gb for the OS and services etc. Tim

Hi Tim and thanks for your suggestion. I have increased the virtual ram and will try again tonight but I will also order additional ram.Richard

Hi Tim and thanks for your suggestion. I have increased the virtual ram and will try again tonight but I will also order additional ram.Richard

Richard,Extra ram is always good but 2 gig of ram should be sufficent to run the MD-11. I run the MD-11 and PMDG 747 on up to 15 hours flights with no OOM and only have 1 gig of memory. As stated it has to do with how much eyecandy you use within FS. Granted I don't use FSX but FS9 but memory use is still extreme on the MD-11 even in FS9. Just my input,Sean

http://www.pcwintech.com/node/145 download and install this program, it really is th

http://www.pcwintech.com/node/145 download and install this program, it really is th

PLEASE NOTE: This section is for anyone who sees out of memory error while using FSX. It applies to ALL circumstances.To clear up confusion about this change.. the amount reserved for the cache is NOT and DOES NOT have anything to do with the amount of memory in the system or how much memory you are allowing access to the system!!This change only tweaks the address space, relieving the OOM error. The 32bit system will use the physical memory installed up to 4GB regardless! ONLY FSX SP2 HAS THE ABILITY TO ADDRESS MORE THAN 2GB OF SYSTEM MEMORY. THE DVD AND SP1 VERSIONS CAN ADDRESS MORE THAN 2GB HOWEVER IT REQUIRES MANUAL EDITING OF THE DVD OR SP1 FSX.EXE FILE USING SPECIAL SOFTWARE WHICH WILL ALLOW >2GB SUPPORT.The method of removing out of memory and other errors on a 32bit Operating system and allow fsx access to memory amounts greater than 2GB is listed here:For XP:disable hidden files and folder, then on the root C:\ you will find a file named: boot.ini Open it in notepad and add the follwoing to the end of the OS boot line: /3GB/Userva=2560 EXAMPLE LINE EDIT:multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows XP Professsional" /fastdetect /3GB /Userva=2560 <---- add it heresave and close the filerebootto set that back to default, simply remove the editIf you are using XP SP2 and are running a dual, quad, OR a single core Intel HYPERTHREAD processor, make sure this update is appliedhttp://www.microsoft.com/downloads/details...;displaylang=enXP SP3 users do not need that update

PLEASE NOTE: This section is for anyone who sees out of memory error while using FSX. It applies to ALL circumstances.To clear up confusion about this change.. the amount reserved for the cache is NOT and DOES NOT have anything to do with the amount of memory in the system or how much memory you are allowing access to the system!!This change only tweaks the address space, relieving the OOM error. The 32bit system will use the physical memory installed up to 4GB regardless! ONLY FSX SP2 HAS THE ABILITY TO ADDRESS MORE THAN 2GB OF SYSTEM MEMORY. THE DVD AND SP1 VERSIONS CAN ADDRESS MORE THAN 2GB HOWEVER IT REQUIRES MANUAL EDITING OF THE DVD OR SP1 FSX.EXE FILE USING SPECIAL SOFTWARE WHICH WILL ALLOW >2GB SUPPORT.The method of removing out of memory and other errors on a 32bit Operating system and allow fsx access to memory amounts greater than 2GB is listed here:For XP:disable hidden files and folder, then on the root C:\ you will find a file named: boot.ini Open it in notepad and add the follwoing to the end of the OS boot line: /3GB/Userva=2560 EXAMPLE LINE EDIT:multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows XP Professsional" /fastdetect /3GB /Userva=2560 <---- add it heresave and close the filerebootto set that back to default, simply remove the editIf you are using XP SP2 and are running a dual, quad, OR a single core Intel HYPERTHREAD processor, make sure this update is appliedhttp://www.microsoft.com/downloads/details...;displaylang=enXP SP3 users do not need that update

I had another freeze and oom error this evening but I am running XP Professional and cannot find boot.ini in my C:\ drive; I also did a windows search and still could not find it.Richard

I had another freeze and oom error this evening but I am running XP Professional and cannot find boot.ini in my C:\ drive; I also did a windows search and still could not find it.Richard

Go to system properties, "startup and recovery" section, select settings, and then you will see a system startup section with a big edit button. Click on edit and you will see your boot.ini file. You can edit it right there using notebook.

Go to system properties, "startup and recovery" section, select settings, and then you will see a system startup section with a big edit button. Click on edit and you will see your boot.ini file. You can edit it right there using notebook.

Richard, by all means give these fixes a go and see what happens. But there is continual confusion on the forums about what these changes actually do. As I said in my first post, I am afraid that they are unlikely to help in your particular situation. Without going into the ins and outs of it, what they do is tell XP and FSX to address RAM above the first 4Gb of memory space and try to squeeze the OS/services into less space than they would ordinarily occupy, leaving more room for applications. These fixes are unlikely to help you unless and until you add another 2Gb of physical RAM. In your current PC, the amount of physical RAM you have installed (obviously) CANNOT account for the use of more than 2Gb of available memory addresses, so this is most unlikely to be the bottleneck in your case. To the techies out there, I appreciate that this is a bit of a simplification and it is not my intention to start a long debate about exactly what is achieved by these switches as that would be of no assistance to the OP. I just want to explain to Richard that if these fixes don't work, he shouldn't be surprised. The best long-term fix - and, if time counts for anything, probably a lot cheaper than fiddling around with the settings - is to install more RAM and enable PAE etc.Tim

Richard, by all means give these fixes a go and see what happens. But there is continual confusion on the forums about what these changes actually do. As I said in my first post, I am afraid that they are unlikely to help in your particular situation. Without going into the ins and outs of it, what they do is tell XP and FSX to address RAM above the first 4Gb of memory space and try to squeeze the OS/services into less space than they would ordinarily occupy, leaving more room for applications. These fixes are unlikely to help you unless and until you add another 2Gb of physical RAM. In your current PC, the amount of physical RAM you have installed (obviously) CANNOT account for the use of more than 2Gb of available memory addresses, so this is most unlikely to be the bottleneck in your case. To the techies out there, I appreciate that this is a bit of a simplification and it is not my intention to start a long debate about exactly what is achieved by these switches as that would be of no assistance to the OP. I just want to explain to Richard that if these fixes don't work, he shouldn't be surprised. The best long-term fix - and, if time counts for anything, probably a lot cheaper than fiddling around with the settings - is to install more RAM and enable PAE etc.Tim

Thanks Tim and everyone who has replied. I have ordered another 2 Gb of ram, but excuse my ignorance; what is PAE and how do you enable it?Richard

Did you apply the change that I suggested? It worked for me and my rig is virtually the same as yours.

Thanks Tim and everyone who has replied. I have ordered another 2 Gb of ram, but excuse my ignorance; what is PAE and how do you enable it?Richard

Richard,To stop me (or anyone else) getting you (or me/anyone else) into a muddle, I suggest you take it from the horse's mouth, here:http://www.microsoft.com/whdc/system/platf...PAE/PAEmem.mspxThis page will also show you how to add the necessary "/3GB" switch to your boot.ini file.If you still get OOM errors after you have done this (and assuming you have added the extra 2Gb of RAM), then try adding this further switch after "/3B": "/Userva=2560". If you still get errors - and you should not, assuming your swapfile is set up correctly - then trying experimenting with the 2560 slightly. But that, I suggest, is as a last resort.Finally, make sure you are running FSX SP2: without this service pack, FSX cannot make best use of the extra RAM without further tweaking. (I have heard that SP1 is also sufficient and this may be true: but my - dim - recollection is that on my PC, SP1 did not by default have the necessary feature enabled (namely, the "Large Memory Address Aware" flag in the NT Header for the FSX.EXE file)).Tim