Hi,If you know that you have PAE enabled in XP-32 then you should remove it, as it is a cause for massive system instability and performance problems. Again, there may be a fix itself by enabling a LargeAdressAware flag in FSX.EXE (which one can do by editing the exe with Visual C++'s, editbin.exe utlitiy.) This has fixed similar problems in Stalker and Supreme Commander. Unfortunately I still haven't tried it yet, but when I do I'll let everyone know if it fixes the issue.Best regards,Mark.

I too have had the same problem only mine have been with FSX and FS9. I am currently running a Core2 Duel 6800 extreme with a 7950 1 gig video card and 2 gigs of corsair 8500 ram.I believe there is a problem but it's not the memory at all. I believe that Flight sim is throwing up a generic error message. The problem is deeper than just a memory leak. When I get the out of memory error, I still have lots of memory. I still don't know what could be cause this problem but I am hoping soon there will be a fix. Another common element to my problem, it mostly happens when I do the flight online. very strange.It could be a video driver issue (nvidia) for us. Maybe fsx or fs9 can't handle that much video memory and it's simply getting it's self caught in a death loop.just my thoughts.:-wave

>Hi,>>If you know that you have PAE enabled in XP-32 then you should>remove it, as it is a cause for massive system instability and>performance problems. >Hi Mark,I removed PAE by disabling Execute Disable Bit in the BIOS, and removing the /noexecute=optin line from the Boot.ini file. I believe this is related to DEP, which when enabled results in PAE being enabled automatically.Anyway, unfortunately I get exactly the same out of memory problem with PAE removed. It should be noted that I've had no other instability or performance problems with anything else on this system - with or without PAE.After further testing, I think I've tracked the problem down to the autogen scenery in FSX. I seem to get this problem only when autogen is set to max. When I set to normal, the out of memory problem didn't occur. I could get it to happen every time with autogen at max.I still can't decide if this is a video memory or system memory problem. I need to test some slightly higher autogen settings to see if it trips up when I go over my video card's 512MB limit.

Hi everyone,FSX SP1 seems to have fixed the problem for me. I no longer CTD in any of the spots I routinely did before, and I was able to fly for a long period of time w/o issue. Please let us know if SP1 has also fixed your CTD problems as well.Mark.

>Hi everyone,>>FSX SP1 seems to have fixed the problem for me. I no longer>CTD in any of the spots I routinely did before, and I was able>to fly for a long period of time w/o issue. >>Please let us know if SP1 has also fixed your CTD problems as>well.>>Mark.It hasn't completely eliminated the problem for me, but it is much improved. I have to purposely stress the system to make it happen now - by changing views, spinning the spot view round and round etc.Anyway, before SP1 came out, I realised that turning my autogen down slightly seemed to get rid of the problem. In any case, if I run max autogen in SP1, I get artifacts and floating trees in some places.

Phil Taylor from Aces says that this problem is caused by a problem in DX9, something about how it only uses a 2 gb memory space, and that it needs to be modified to allow for a 3 gb memory space. Something like that.In the Fall I believe MS is going to release a DX10 download to enable Vista to fully use DX10, perhaps that will circumvent the problem for Vista users, but I hope that MS also finds time to repair DX9.There's an FSX user w/ XP Pro who has OOM problems also, he says that all he does is turn down the sliders a little and the problem goes away.There's going to be an SP1 coming out for Vista, but I don't know when or what issues it addresses.

IMHO and just do a quick search on my screen name here and at the UT and PMDG forums to see ALL of the testing I have done on this... It is an MS issue.We saw this with FS9 in the latter days with a lot of add-ons and now we are seeing it with Vanilla FSX. MS can not seem to write an application that correctly manages its own memory within the confines of a Microsoft operating system. Amazing!MS develops XP and Vista as 32-bit with CLEAR memory limitations and then other divisions of MS develop things like FS and Exchange that can't seem to keep themselves within those limits...Like I said, IMHO this is a BUG in MS applications or Operating systems in general, Exchange has this issue, IIS has this issue, its not just FS. If you write the O/S to a 32 bit spec then you should Da*n well make sure your applications can abide by it!!!The ONE thing that would have got me to drop FS9 completely was a fix for the dreaded OOM. Seeing people are getting it with default FSX will prevent me from dropping a penny into add-ons for FSX. Why pay for add-ons when the vanilla app can't even manage its own memory to confine itself to the memory the O/S allots!Just my .02,-Paul

Ifyou have that problem then try this fix:http://forums.avsim.net/dcboard.php?az=show_mesg&forum=121&topic_id=399256&mesg_id=399256&listing_type=searchNo warranty given but I have not had it since.

Yeah there is an MS flaw, Phil Taylor has said that it is in DX9. If I recall he said that it only has a 2 gb virtual memory allowance and it needs to be 3 gb's? So I guess whenever that is exceeded then you get the OOM. This will probably be fixed for Vista users when they get the DX10 patch, but what about us XP users, I hope they give us a patch for DX9!I spoke to MS the other day about the end of support for XP. They said that XP will be warranteed until 2009, but it will still be supported until 2014, I believe that's what she said. I think that is good news for XP fans.One nice thing about FSX (I still haven't gotten it yet) is that a new X-15 payware aircraft can attain about 385,000 feet in FSX, whereas annoyingly it can only reach 100,000 feet in FS9. Not complaining about FS9 though, it is a classic, I just installed my 2nd unit of FS9 on another computer. Need to buy more. Not to criticize the author of that X-15 because it looks good, sounds like some good detail has gone into it, but in the real plane Mach 6.7 was not its' speed limit, that was the speed it attained at half throttle, same goes for the max altitude attained 354,700 feet if I recall. With max throttle (never used, too scary) the X-15 was estimated to reach Mach 9.5+, and it was considered to be capable of possibly as much as an orbit or two. It's just disappointing when a flight simulator X-15 only reaches Mach 4.6 or altitude of 385,000 using maximum throttle.