Any explanation on this problem

have you been able to reproduce this error?did you add any new aircraft, panels and/or scenery recently?--

>have you been able to reproduce this error?nope>did you add any new aircraft, panels and/or scenery recently?nope....it happened very suddenly while on simmingthanks

this may not be what you wish to hear ...in order to nail down a problem that challenge must happen often, and tied to a specific aircraft, or time in flight, or location in the FS 'world'.FS is a processer hungry application - meaning that it is asking our PCs to work 100%. errors happen (them little bits get confused or don't switch 'on and off' as expected); and the chance for this increases the closer one gets to 100%. CDTs are to be expected ... rarely. and yes, it should be upsetting (especially after spending 15 minutes programming the FMS, or 5 hours on a cross country flight). i've CDTed my computer many times over my years of simming. i find FS9 to be the most stable of the 'modern' FS versions (FS7, 8 & 9 ... i'm not yet a FSX user as my machine doesn't have the correct specs).--

okay...thanks for your thought!but what make that happened if any of these addons are added recently; aircraftpanelssceneryBTW...my last scenery addon was added last two week...is that probably the cause?

Did you have FS9 running for a long time?It sounds like something has a memory leak, whether it's an add-on file , a stock one or a missing one causing problems.You can hit ctrl-alt-delete while in windows to bring up the task manager. Go to Processes and you can see which processes use how much memory. While flying in FS9, occasionally check back with this to see what process memory is increasing. It could even be something outside of FS.

the cuases for a crash are many. as some have stated: memory leak, power surge, bit loss on a chip, etc. etc. don't worry about what happened unless the issue reappears.--

It happened less than 10min

Mardley,I think that the message refers to "Virtual Memory" rather than "Physical Memory". Check your "Virtual Memory" setting.

My virtual memory is always set using;Custom size:Initial size (MB) 2560MBMaximum size (MB) 2560 MBThis is based on;RECOMMENDED PAGEFILE SIZETweakingCompanion_3.2.pdf www.tweakguides.com

At last this could be the answer I'm looking for :-)http://support.microsoft.com/kb/892610

>My virtual memory is always set using;>>Custom size:>Initial size (MB) 2560MB>Maximum size (MB) 2560 MB>>This is based on;>RECOMMENDED PAGEFILE SIZE>TweakingCompanion_3.2.pdf >www.tweakguides.com>>>That is no longer good advice. New advice: LET WINDOWS HANDLE IT.Allcott