Hi Pete,As I noted above, Adam did tell me that it is possible for FSX to run out of memory. I am no expert on memory access, but apparently it is possible for FSX to ask for more than 2GB of memory, and there's nothing that can be done to stop it. It's not a memory leak issue, it is a limitation of the 32 bit OS.For the benefit of others, as I assume you are aware of this Pete - The fix is not simply turning a switch so it compiles 64 bit, there's quite a bit of work involved in creating a 64 bit version, and I imagine the number of people running 64 bit OS is not a large enough market at the moment.**********************For the user who is doing lots of task switching, you are causing windows to page FSX to disk. Windows has long been known to not be super efficient once data starts being paged to disk. There is nothing FSX can do to fix it, this is an OS issue.If you don't want to get the slowdown, I suggest not running other programs at the same timy you are running FSX.Thomas[a href=http://www.flyingscool.com] http://www.flyingscool.com/images/Signature.jpg [/a]I like using VC's :-)N15802 KASH '73 Piper Cherokee Challenger 180

>I am no expert on memory access, but>apparently it is possible for FSX to ask for more than 2GB of>memory, and there's nothing that can be done to stop it. It's>not a memory leak issue, it is a limitation of the 32 bit OS. Thomas, I don't buy this as an explanation of the problem. As Howard indicates in the post just before yours, he's using 4 GB of RAM and still encountered the problem. I can also attest to this as I boosted my RAM to 4 GB as part of my troubleshooting, and it made no difference at all. Furthermore, I would check my RAM usage throughout my dozens and dozens of test flights and, as I indicated earlier in this thread, "my indicated memory usage for FSX is about 1.2GB with the rest of the machine using about 250MB. This leaves about 500MB to spare when getting the frame rate drop or the out of memory error."Robert

Similar proble has occured a couple of times but not very recently.

Hi,I encountered the same problem. Shortly after starting the Paris airshow mission the display got wild and there was stuttering sound. Any input except for pressing Escape was making it worse.I did what was suggested in previous answers. I removed the entry "PoolSize=5000000" in the section "BufferPools" which I had added at the beginning of my FSX installation and configuration according to some tuning tips I found in the internet.Now that I have done some flights I have to say that the problem is gone. Well, that could be an explanation: If the buffer pool size is too high the sim collects scenery data faster than the hardware can handle. Now it depends on the actual place where you start your flight (scenery complexity), how much physical resources are in your computer and how the settings are. Sooner or later the sim collapses.rgdsliloAMD Athlon 64 3800+, 2 GB RAM, 2 x 150 GB HDD, ATI Radeon X800 XT with 256 MB

The usual cause of the video slowdowns are not becauseof system ram. It's a runout of *video* ram. IE: texturestorage.. Heck, I only have *1* gig of ram, and a 128 megvid card,and have no problems at all unless I overly crank the scenery settings and overload the video. I can fly around the world 20 times over for hours on end, and not slow down.MK

Had my first ever out of memory message today. Mind you I was pushing the system to its limits. How much video memory does FSX want?

>Had my first ever out of memory message today. Mind you I was>pushing the system to its limits. How much video memory does>FSX want?If you get an error message, it's quite possible you ran out of system ram. I've never had a message from overloading the video, although I guess it's quite possibleif part of the system ram is also used for texture. IE: AGP aperature settings, etc...In general those I've heard that bombed out on an errorran out of system ram. Myself, when I overload my video on purpose, it's blursand slows down, but it doesn't crash.. And usually onceI leave the area that overloaded things, it returns backto normal once it can handle what is thrown at it. The video memory requirements can vary drastically according to location, density of scenery, clouds/wx, resolution, etc... Natually if you run high res, you aregoing to be much more likely to tap out the video. You are pushing many more pixels. Actually, it's quiteeasy to tell when the video is on the edge.. If you getthe blurries on some land textures, while some are sharp, you are borderline. If your panel blurs to a lower res, over a certain scenery, you are nearly tapped out. Thingsare getting bad if the panel lowers it's res. MK

>Had my first ever out of memory message today. Mind you I was>pushing the system to its limits. How much video memory does>FSX want?My ATI X1600 Pro with 512 MB seems adequate. Most of the time the video memory hangs around 350-400 MB.Occasionally it has peaked at 506 MB.HOWEVER, I changed my "BufferPools" to 50000000 or 100000000 a few days ago and also added some new scenery elements. ( 50 or 100 million )I noticed that my video memory was maxing out after 1/2 to 1 hour .All 512MB on the card plus the 256 MB of the aperture. I fly in windowed mode and I noticed I lost my SHFT+Z readouts when this occured.I started removing things one at a time and re-testing.It was when I dropped the BufferPools down to PoolSize=25000000 that my video memory usage returned to "normal"... Paul

Paul, your problem mirrors mine to a "T." It's been suggested above that the BufferPools setting might be at fault and I tried it but didn't notice much of a difference. But with so many variables it's often hard to know for sure. In light of your experience, I'll definitely give a BufferPools reduction a try.Thanks, Robert