From my previous posts regarding FSX crashing I spent a great deal of time searching for answers through other Forums such as Avism who have an excellent CTD Thread.
All my crashes came up with various causes such as Appcrash - Bex - UIAutomationcore.dll - AI_Player.dll - ATC.dll and finally MSVCR80.dll so you can imagine how frustrating this was for me not being able to pinpoint the actual cause of the trouble and seriously began to think that it would be best just to not bother with FSX any more as every flight I did was affected.
Pleased to say that FSX is now running sweet and smoothly with not even a stutter. The reason for all my problems was that I had simply not updated FSUIPC to the latest version for FSX!! When I did after reading about possible fixes to my problems there were no more crashes!!
Nigel.
I used to be an optimist but with age I am now a grumpy old pessimist.
It does doesn't it? On my varied searches for a cure I came across one thread that mentioned to ensure that FUISPC was kept up to date and seeing that mine was of the older version did just that, after finding that my crashes were no more I reverted back to the original FUISPC and the CTD came back!!
I can only assume that by updating FUISPC helped enormously and can offer no other explanation. Apart from that I am back flying and enjoying the experience even more now that my computer is upgraded to i5.
Regards
Nigel
I used to be an optimist but with age I am now a grumpy old pessimist.
I, on the other hand, have the latest FSUIPC and still get "stutters", the sim wil go into "not responding" mode for almost exactly ten minutes at random times/locations.
UIAutomationcore did not cure it either.
Any ideas
(FSX Gold, Win7 64bit Home Premium - very high spec system)
Old pilots never die, they just run out of runway.
This may be total baloney in today's environment, but:
Some years back, Windows used to gobble up a bit of memory every time an application was opened.
Even when that application was closed, it left a bit more memory tied up.
So, if an operator opened Excel, then closed it while doing word processing, then re-opened Excel, repeatedly, it only took a couple of hours to totally clog up the memory, and the workstation would freeze.
Do any of our hardware specialists have insight into whether something similar happens on long-haul FS flights?
Could autogen be continually piling data into memory, and never completely flushing it out after use, so that eventually it can't process any more?
All my flights are relatively short, and to date, IIRC, I've NEVER had FS lock up on me, regardless of detail, number of aircraft flying etc.
Despite the fact that FSX should release scenery (AFAIK).. I don't believe it does. May be wrong though and NOT for the first time
As mentioned in another thread.. I often fly Culdrose to Gib and in a variety of models (only one per flight though). If I fly in something that goes like stink.. I can usually make the other end without problems. If I fly something less speedy.. chances are I'll either hit display problems as I reach the other end or it will freeze. I generally use 'live' weather on these flights so no two flights are exactly the same. The only constant is the scenery I fly over. For me.. this seems to be a time issue. The longer I take, the greater the likelihood of problems. The faster I am, the less chances there are of problems. FSX.. as real as it gets
ATB
DaveB
I've also been trying to get to the bottom of this "freezing" problem, like Nigel I read a lot of stuff on Avsim, one post seemed to accept this as NORMAL for FSX!!...is it "Normal"??, if so I'm wasting my time trying to achieve a long haul flight with a heavy!, I've just set up with PMDG T7 but even the tutorial flight only gets 30 minutes into the flight and FSX freezes.
How do you ever complete a VA flight?...at the moment I'm testing my setup with absolutely minimum settings, only flying at night with no weather, traffic etc, using the Realair V2 "Duke", not too heavy on fps, didn't have a freeze last night after 3 hours of flying around checking out the UK2000 Xtreme airports I bought during the Flightstore sale last month.
I was seriously considering upgrading my system AGAIN to a top of the line processor, not quite sure what to do now?.
Its coming back to me now. I think there were a few things. There was a problem with an AI BGL file and there was also a problem with a piece of add-on scenery, and I'm buggered if I can remember what it was. There was also something to do with sound. I'm wondering if it was actually the sound gauge used in the Trident and VC10 etc (I think there is a compatibility issue with it on Windows 7 and later) It was a third party sound gauge written by Doug Dawson that was really common in loads of FS9 aircraft. I know I re configured quite a few models to use the newer version of the sound gauge which was designed for FSX. I think that may have been the one that fixed it for me.
With regards upgrading to faster hardware. Why? FSX is a 9 years old. If you were upgrading just for FSX, I'd be asking why, as it cant really utilize the newest hardware properly.
Just trying to get reasonable fps, example, I just finished a flight with the Duke V2 into Luton, shut down, cold and dark, I'm only getting 6 fps...ASN, UK2000 VFR airfields, no traffic selected, I'd like to do a bit better than that if possible!.
Glad you're sorted though 
On my varied searches for a cure I came across one thread that mentioned to ensure that FUISPC was kept up to date and seeing that mine was of the older version did just that, after finding that my crashes were no more I reverted back to the original FUISPC and the CTD came back!! 
