Near the end of a flight from Kansas City (KMCI) to San Francisco (KSFO)I got an error saying my computer ran out of physical memory. I got the error about 15NM from SFO while on approach. I would say about a 3+ hour flight.Here's my setup and background:CPU info: Dell 3.2 ghz P4 Dimension XPS with 800mhz fsb, 2gb dual channel sdr ram, ATI Radeon 9800 xt pro 256 mb ddr dna drivers, Raid 0 240gb (2 X 120's), Sound Blaster Audigy 2, Direct X 9.0c, WinXP pro, All drivers (fs and puter and OS updated).Most programs in background turned off, etc.FS Info: using PMDG 737 and Active Sky.I wonder what caused the error? There is probably some easy solution for this I forgot or am overlooking. I suspect that there is an add-on writing files to the hard drive along the way but not sure about that.Any ideas here? Thanks.

What scenery add-ons do you have?-John

I have the FlyTampa SFO, but it wasn't being displayed at the time of the crash. This wasn't an FS crash as far as I'm aware but an actual puter crash. I do also have the FSG mesh though.

I had the same problem with basically the same system as yours. The only thing I had recently done was upgrade my ATI drivers so I uninstalled and reinstalled them and haven't had the out of memory problem since. I would be interested to know if you also receive a CTD when you open any kneeboard and click on the screen. This was happening to me too along with the out of memory errors. Reinstalling the ATI drivers fixed my problem(s). I will add that I thought my drivers were properly installed. The device manager indicated all drivers were installed and there were no problems. DirectX diagnosis indicated all drivers installed and no problems either. However, I think there was an old ATI entry in my registry that failed to be removed and was conflicting with my video card drivers. Since you probably recently updated your ATI drivers, I would suspect this as your problem. Good luck.Jim

I've been using the DNA drivers for a while now. I do get an FS CTD though when I try changing back and forth between full screen and windowed mode.

Sometimes a scenery error will be caused by scenery even if you're outside of the area where it's displayed. I had the exact same issue some months ago after installing some odd add-on--all I remember is it was freeware. You could try disabling the FlyTampa in your scenery.cfg to see if that stabilizes things. -John

I've never had problems with any add-on scenery before.