I got several Out of memory erros when I fly with the great Alphasim SR71 longer distances. Sometimes the error occured five minutes after takeoff. The error occured under SP1 too.So I tried a solution I found for make STALKER ready for run with Windows Vista. The solution seems to work with FSX too. I got no error on flights which crashed before regulary with OOM.Try this only if you have at least 2 GByte of RAM and at your own risk.First download the explorer from http://www.ntcore.com/exsuite.phpNext make a copy from fsx.exe. Than start "CFF Explorer" and open the orginal fsx.exe file.Now go to NT Header/File Header and click File Header. Ther you find a button labeld "click here". Click it. And select the mark at "App can handle> 2gb adressest " Save the modified EXE, overwrite the orginal one (You have youre copy saved?).If you run Windows Vista 64 or Windows XP 64 youre ready and didnt need to read on. The rest is only for Windows Vista 32 or maybe Windows XP.Now make Windows Vista (32-Bit) ready to support more than 2 GByte.Open a command prompt with Administration rights. You find it under "Programs->Accessories->Command prompt" click right and select "run as administrator".Enter "bcdedit /set IncreaseUserVA 3072" (without quotes) in the command window and press enter.After that restart windowsFor Windows XP there is a similar setting for the boot.ini, but I have no Link to it, should be found be google.For me it solve the problem.Too reset the Increased User Adressspace just start the commandline prompt with Admin right again and enter "bcdedit /set IncreaseUserVA 2048"Please post youre results here, so we can see if this is a solution or a workaround only.

MarkusI'll give it a try.Vista Home Premium 32 bit4GBIntel x6800 Core2 XtremeI followed your instructions and didn't have any problems. The bcdedit said 'completed successfully'. Changed FSX.exe and ran the Windows memory diag and it reported no errors. Checked FSX to see if it still works and it does. Took a restore point before this.Prior to this change I have done about 8 real flights and quite a few short 'load saved flight' tests. All with the stock C172. Out of the 8 real ones I have had 1 OOM. 6 of the 8 were from and to small airports and the one that got the OOM was on approach to a larger ap, ENGM Gardermoen.Someone else here mentioned OOM's on approaches also. At the time of the OOM, I had both ai sliders set to 100%. Do you think that the OOM has anything to do with heavy slider settings or more dependent on sim run time, or both?This morning, before your post, I turned down some of my settings including the ai to 15%, took off from ENGM, did a flyaround of the Oslo area for about and hour and landed back at ENGM. No problems.For testing this change, I will put the ai back to 100%.Did some searches on MSDN and there are quite a few items about IncreaseUserVa. I only looked at a few, but will look at more later;MS Knowledge Base, also.I believe it was on Phil's blog that it was mentioned that this is a memory allocate error and they don't know it will happen till it happens, so will this patch merely give FSX another 1 Meg to use up?It sounds like it.We'll see how it goes.

Flew the C172 around Tokyo for a bit over an hour. This is one of my saved test flights and I could always make this one blurry out if I tried to.FPS purposely set to 20 with mid to high sliders. I won't list them, but they're mostly 2/3rd's, no ground shadows, no bloom, etc.4.5 LOD radius.AI both at 100.Flying at about 5000 altitude.I did change the FIBER_FRAME_TIME_FRACTION to 0.60 to see if that would help with 'super blurry'/CTD event that would inevitably occur with this saved flight if I stressed it. ie: rapid panning, zoom in at RJTT, pan while banking, etc. This is the only cfg mod that I currently have and I think it worked. There would be some 'late fills' of textures and autogen, but no blurries.The FPS would on occasion reach 20 but most of the time would be in the teens with some predictable stuttering. Towards the end of the flight I maxed the scenery complexity, autogen and terrain mesh sliders which dropped the FPS to around 8 to 10 but still no blurries or OOM.Landed at RJTT and parked. No OOM. So far, so good.Side note:FSX appears to be much smoother at low FPS than FS9 is. I don't think I was ever able to make a smooth landing in FS9 at 8 FPS. It would get the 1 or 2 second stutters and the next time I seen the runway it would be somewhere else other than the last time I saw it. This didn't happen in this test.The max commit count reached about 1.6 meg in Resource Monitor.

Markus,I made the changes as you suggested. I loaded my 100% positive OOM config settings and then loaded a flight from LAX to SFO. I usually receive an OOM msg about 10-15 minutes out of LAX. I did not and was able to fly completely to SFO w/o incident. Scenery textures seemed to load much faster and I hardly saw any blurries (weather was loaded too so clouds/haze may have affected any blurries). Received great FPS all the way. I did everything I could to cause an OOM crash or, at least make everything begin to blur just before the OOM. Everything in the cockpit and on the ground remained normal.For me, this may have been an additional fix to my OOM problems. I read somewhere this AM on a forum (cannot recall - I visit many), that the beta NVIDIA drivers 160.03, fixed the OOM errors. I have dual NVIDIA 8800GTX cards in SLI configuration. I installed them this morning, ran FSX as above with my known OOM config settings, and was able to get to SFO without an OOM. However, there was a lot of blurry textures on the ground but they seemed to render quickly -- quicker than previous NVIDIA drivers. Upon landing at SFO, my aircraft panel suddenly began to blur but I was able to still operate the aircraft and I received no OOM. I was able to close FSX normally. So I think NVIDIA has fixed the OOM problem with the 160.03 drivers but not completely. I have always thought the video card drivers were the cause of FSX OOM's as several others on this and other FS forums. I certainly appreciate your efforts in researching and finding this modification of the FSX.exe and the system RAM problem w/computers w/over 2 gigs of memory. I think it will go far in ultimately fixing this problem some are experiencing. I'm going to do some further testing of your "fix" in the morning after golf as this test was done quickly to provide you some early feedback. I'll advise if any of the results I provided above change. Best regards,Jim

JimI have Radeon x1950 Crossfire and got the OOM also, so if it is a video driver problem it's not only nvidia.

I have a Vista / 8800gtx / Dual Core 2 / 3 gig 800 Ram build and used to get the oom error all the time. I did this fix some time ago and it completely solved the memory problem and improved overall loading times. I just can't believe that FSX and Vista, both being Microsoft hasn't addressed this yet in a patch, makes me lose some faith in the overseers.

MarkusTried the same scenarios again, only this time I took out the FIBER_FRAME_TIME_FRACTION=0.60, so my FSX.cfg is now entirely stock with no mods. In fact, except for some key assignments, the FSX >2GB address set and slider adjustments my entire FSX install is stock.The blurries are gone, so the fiber frame apparently is not a factor.The improvement therefore must be your solution. I wonder if both the blurry issue and the OOM are in some way both related to memory.One thing that I think everyone familiar with FS knows is not to jump to conclusions, but this looks extremely promising.Edit:See post by mickslick which was posted while I was doing this.

I wonder if there is any downside. For instance, just as in the days of 640K limit if you had 1 MB installed and maybe a LAN adapter and/or a specialized video card, the memory map would backfill from 1MB and could conceivably use up some of the 640K.I think this is similar, except instead of 640K and 1Mb it is 3Mb and 4Mb. Is it possible that with enough memory mapped hardware the backfill could eat into the 3Mb used by the application and possibly cause a memory overlay?I don't know. Perhaps MS is playing it safe.

I might try Markus's fix if I get an OOM again.I'm using the 158.43 beta drivers for Vista - and it seems like it has cured the OOM problem for me. I haven

"I have Radeon x1950 Crossfire and got the OOM also, so if it is a video driver problem it's not only nvidia."BobZ,I stand corrected. All the OOM threads I read had the user using a NVIDIA card, especially the 8800 (and VISTA). I can't understand why the 160.03 NVIDIA drivers did not cause an OOM whereas their latest WHQL driver did. Now I really hope Markus' "fix" works!Ciao,Jim

I just tried the same Tokyo stress flight as last night with the stock FSX.exe but left the Vista IncreaseUserVA at 3072 and it OOM'd in under 5 minutes.mickslick seems pretty matter of fact about it and it raelly looks like a solid fix.Look here at MS Technet and search for increaseuserva.[http://www.microsoft.com/technet/support/default.mspx]

Hmm - those beta drivers did not help. If I turn the autogen up to "insame" level - I get the OOM again. Reverting to the old drivers - and I'm going to try you fix. :)

I agree - I apears to have helped me as well. I had an area where i would force the OOM all the time. This fix has me flying around the area without any problems!!!If this turns up to be solid - I owe you a big one!!!Vista Ultimate 32 bitCore2Duo E6700Geforce 8800 GTX/768Mb.4 GB Corsair DC2 800 ram.

Markus,I ran another flight and the flight performed flawlessly. Textures were also crisp throughout the flight. I really believe this "fix" will help those who are suffering from the blurries too. I recommend your original thread be placed in the FS Tips and Tweaks section so it won't get lost. Thanks again for fixing my system!Best regards,JimIntel DuoCore Extreme CPU X6800 OC at 3.46GHz4GB DDR2 SDRAM at 667MHz30" Monitor (3007WFP)Dual 768MB NVIDIA 8800GTX Video CardsSATA2 harddrives in RAID0 configVista Home Premium, 32 bitCreative X-FI Extreme Music sound card

It was Markus who posted it, not me. But I did bravely volunteer to try it. LOL