I think I have found a way to cure the out of memory errors I have been getting and this may help those that are still getting them. I increased my Page File setting from the default 1533MB to by 500MB to 2033MB. Since then when flying into say Simflyers PHX which usually took like 10 seconds to load or would crash with an out of memory error, it loads up in like 2-3 seconds now...and no out of memory errors. Now for the computer gurus out there....is this safe to do?Under the Virtual Memory menu, it says Space Available as 278560MB. I have the initial size at 2033MB and maximum size at 4090MB. The XP recommendation is 1533MB for the initial size. Am I assuming correctly that we can make the intial size anything we want up to 4090MB? Are there any downsides to increasing it by 500MB like I did? I hope not as by me doing this, I so far (fingers crossed) have not run into the "out of memory" error yet.

Initial size is just the min size of the swapfile. If XP needs more memoery it will increase the size to the max value at most. When it does this resizing of the file it is sometimes possible that the system/FS will crash. I prefer to have Min and Max set to the same value to stop it from resizing however this requires a good setting so that you never run out of memory.BTW I'm surprised you run out of memory with a 1533 MB swapfile. When I run FS9, memory allocation is never above around 500MB. Unless that scenery is really inefficently designed, having a memory usage of over 1.5GB sounds very strange.

surprised or not, let me add a trickle to this stream... definitely something spooky going on after 9.1: texture-heavy environments began to crash left and right like pigs. massive memory-related problems, as far as my humble-yet-not-at-all-mean programming experience tells me...any other crash stories?

Stable as can be here--and my MSFS desktop has it's challenges. Until I landed in the hospital this year, I was going to build a new system and just use the desktop as an imaging system. I put that off until my plate's a little less full. But still, the system has only 384 megs and 98SE to boot, and it's handled 9.1 very well.The only time I ever caught an out of memory error was a load once of a bad bgl under 9.0. I can't recall if it was an Afcad bgl, mesh, landclass--it's been too long. Oddly enough, I was getting the error miles away from the area the bgl was supposed to update.But no issues in version 9.1. I don't discount that with the numerous add-ons, changes from 9.0 to 9.1 may show a problem that causes either the add-on or MSFS to crash. -John

too poor and too lazy here to have numerous add-ons :-)ok, let's narrow the postulate down: xp sp2, 1 gig of memory, fixed-size swap, increase in texture/memory-related fs crashes from "zero" to "frequent" after installing fs update 9.1

A few other things to try...Make sure all the time/datestamps of the dll's in your modules folder are greater than 6/1/04. Any module without a time/datestamp greater than that is likely left by an add-on, and may need an update by that developer.Other thing to try--the 9.1 update modifies the display.cfg. It may be some odd setting there that your video card and/or DirectX doesn't like. In the "Backup Folder" you should have an older version of the display.cfg. Go ahead and backup the newer display.cfg, and restore the older one from the backup.Also, is your startup aircraft one of the defaults? If it isn't, and your startup aircraft launches a custom set of gauges, it's possible the startup aircraft isn't liking the 9.1 update.Last, you never know if the sim landed the new dll's on a marginal series of sectors on your HD. One of them could simply be corrupt. A disk defrag and cleanup might clear that problem.I agree though--it's odd that it's smooth sailing before 9.1 and out of memory afterwards... I hope you get a better answer than any I've given..-John

The out of memory errors I get are when using the PMDG737 or the Eaglesoft citation X and going into Simflyers sceneries of ORD, ATL and PHX. This is also with Activesky 4.5 going as well. I also have FS Genisis's 38m terrain for all the US. I don't have any errant LC files either. My total page file is in the 900's when running FS9. Of course this also includes the other 30 processes that are running in the background.I have the 9.1 update and XP SP2 with of course Direct 9.0c. Maybe its time to reinstall FS9 minus the update?

john, thanks a lot. i'll try all of these... eric, don't lose hope, 9.1 has done a lot of good to the visual aspect of the sim, it would be a pity to give it up... let's keep trying

Hey Eric.... Let me save you the trouble.... I've just completed a complete reinstall Windows XP, Hard drive, Not so complete FS 9.1 (updated) but I do have PMDG 737-800, Activesky 2004.5, simfliers Atl and Pho and Eaglesoft CitX,default scenery except ATL, I have already experienced shutdown just about over 85 and 285 junction near Peachtree Dekaulb flying PMDG 800 W/FSCrew.... Hope this helpsSteve

Really to figure this out, you'd have to reinstall, and install each add-on, fly a few days, then the next, and so on, until you hit the shutdown. If you just reinstall and load all the addons at the same time, then it's really hard to isolate the add-on causing the problem. If you can do that, then you can work with the developer to get their add-on in complete synch with FS2004 9.1. If however you have issues with a clean, plain vanilla install, then the add-on isn't the problem.-John

I have shutdowns flying INTO Simflyer's KATL with the PMDG too although not all the time. I'll give Eric's suggestion a try. I've found that if I'm turning knobs and clicking buttons at the time KATL starts loading (about 15 miles out), then I stand a better chance getting shut down. However, this is hard to do avoid when you're trying to set up a final approach.

What is odd gentlemen is that I have never got these errors anywhere else EXCEPT when going into certain Simlyers airports and once going into Imaginesim's DEN (but that developer is a former Simflyers designer and as such, uses the same design techniques). Fly-Tampa's stuff...never ever had a problem with that scenery...works like a charm. I guess something with the way SF has their scenery does not digest well with FS9. I found this in another forum. You guys may want to give this little program a try while FS9 is running:Hello,You can try to "trace" the problem by using this small and great program http://www.sysinternals.com/ntw2k/source/filemon.shtmlwhen analysing the results I did find on whitch file FS9 was looping (and crashing !)You can set up the filter to only monitor the FS9 folder (and it will monitor everything inside of it). Just use the filter option and type in the path to FS9. Go under Options, then Filter, then put that text under the included line.

Okay, I think I can definitely associate this error with SimFlyers. #### me off!

Preston,Do you have the PMDG stuff onboard? I did an experiment last night and found that as soon as I unistalled all my PMDG stuff (dll files included), I gained back 300MB over what I was getting and that was with using other payware aircraft. I did not start getting these errors till post FS9 patch. I think something is amiss with the patch and PMDG's plane and/or dll file.

Yep, all the while flying the PMDG. I've set my virtual mem to match yours but haven't tried a flight with the new setting yet.