Please help. I'm not very computer literate so please bear with me. When I am running FS9, flying the PMDG 747 & FS2crew occassionaly the program freezes and I get an error message saying that the system does not have enough virtual memory and will close up FS9. It also says to free up some memory on my hard drive using diskcleanup. Well I ran diskcleanup and I still get the message. Any ideas. Thanks in advance.Gateway GT5056AMD Athlon 64 X2 Processor Dual Core2046 MB RamRadeon X1900 GT 256 MBSB Audigy 4

How much free space do you have on your C: drive?I assume you run WinXP. Are you letting WinXP manage your swapfile settings? RhettAMD 3700+, eVGA 7800GT 256, ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, etc. etc.

I have 81% free space. I not sure how to check to see if xp runs my swapfile settings.

re: swapfile settingsI'm not much of a computer whiz but this one is fairly easy.Right click "properties" on your "my computer" icon.Go to advanced then then click "performance" then "settings".From "settings" go to "advanced". It's the "virtual memory" that you are looking for there to see what it is and change if necessary.There are different opinions on what to set it for, I think 1 1/2 times your memory size is often considered pretty good. I think Windows defaults to 1 X memory size. Either way you won't get into trouble at all with 1X which I think should be a bare minimum. What is yours set for? I don't think it's a great idea to set it for Windows to manage the size, give it some good hard figures. If you have two hard drives, each has it's own page file, then you get different opinions. Many people say use the drive that your FS9 is NOT on for the whole system page file so as to spread the work load around. Until you learn more you might just forget that for now and the important thing is to see just what your page file is set for compared to your sysems memory.I'm sure others can expand on this but first check to see what yours is set for. You really can't get into any trouble if you stick with the page file memory size of 1 or 1 1/2 times your system memory size. If you have a small hard drive this reserves/takes a pretty good chunk out of your hard drive space BTW but that's just reality. If the page file is too small it creates lots of problems with a memory intensive application like FS9.If you make a change be sure to hit that "set" button when you are finished, pressing just OK does not change the setting. Then hit OK.BTW a search for "page file settings" on the web will find you all kinds of clear and concise information that's not overly technical or hard to grasp. In fact it's a good thing to learn a bit about and not intimidating at all, thats why I'm responding to this thread.Edit: I should have mentioned that if you have a system that is inherently low on sytem memory that page file should be even larger as a percentage. What it is doing is using your hard drive in place of the system memory (that you are low on) and even though it works much slower than system memory it at least gets the job done.

fireman, go to swapfile settings, as neslesman details below,and make sure that Windows is controlling your swapfile.Then retest to see if you still get out-of-memory (OOM) errors.I assume you've applied the FS9.1 patch, too.RhettAMD 3700+, eVGA 7800GT 256, ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, etc. etc.

thank you, i will try all this. i do have the fs9 patch installed also.

Okay, tried all that and it still gives me an error. I did a flight from Ksan to Kden in the PMDG 747 w/ ASV6 and FS2Crew running and it still ocurred. Any other ideas. It seems it only occures when running the PMDG 747-400. Thanks in advance.

******Point #1:Are you checking on your memory usage during your flight? That's what I would do. You can do this by right-clicking on your taskbar, and selecting "Task Manager". Then look at the "Performance" tab.Where it says "Physical Memory (K)" see the figure for Available and see if that goes down to zero or near it. WinXP SHOULD be swapping data to the disk so it should not hit zero.Also on that screen is "Commit Charge", and where it says, "Limit" that is your max amount of kilobytes of data your system can handle. That is a sum total of your physical memory sticks and the size of your swap file. When you're flying your PDMG plane, cruising along at 35,000 feet over the Rockies or wherever, pull up Task Manager and see what your numbers look like. WinXP should be automatically increasing your swap file size to account for the heavy mem use PDMG plane, and so forth. I'd think your Commit Charge Limit should go to 4,000,000 or higher.*****Point#2:Otherwise, you might run a program called MemTest (google for it) to see if you have a bad memory stick.*****RhettAMD 3700+, eVGA 7800GT 256, ASUS A8N-E, PC Power 510 SLI, 2 GB Corsair XMS 3-3-3-8, etc. etc.