Hi all,FSX look sgood and my pc is strong enough.However after being in flight for 45-70 minutes I get a small message window saying that Flightsimulator does not work anymore and that is has to be closed.When clicking ok Fs shuts down.My settings are medium high and 20 fps I even get when being at a busy airport.The message appears in flight when I am at 15000-30000 ft.Framerates up there are good.Beside FSX I use PM MCP , Aerosoft MCP , ASX.Help is appriciated.

Check out the CTD- crash to desktop forum

Hi Gerard,I'm wondering with all of the overclocking your system is subjected to, is the northbridge/southbridge receiving enough cooling and are voltages in the BIOS sufficient to run that way constantly?It could be a heat issue that surfaces after running FSX for a while.Regards,Jim Karn

After trying and testing I am getting the feeling that the message appears when ASX is running.I just finished a flight where I first flew for 1 hour without ASX and then I started up ASX.After half an hour I FSX hung with a small message window that says "FSX stopped working. Vista is searching for a solution. When it is found we will let you know."I am running with framerate set to 20 and everything else to medium high.A second test I did was at busy airport ( Eham ) and I started slewing around a lot.No problem.Then I started up ASX and got back to slewing.Within 2 minutes FSX hung with the known message.But no stuttering or bad fps before hangingMy system is overclocked, but when FSX is hanging Vista is not.I can startup FSX again or do other things.So bad cooling I count out.With my board the North-and Southbridge are cooled by a cupper pipeline with small fans at one end.A a cooler is blowing cold air towards the fans.In the Bios the CPU temperture is just 29 degrees.The mobo teperature is around 42 degrees.Looks fine to me.I am looking to ASX ; perhaps when FSX is very busy with detailed scenery and very detailed and complex cloudlayers pop in this gives an issue.Or when ASX is updating FSX with very complex weather.Surely there must be someone who has/had the same error message.A solution would be very welcome.