Hello all.

 

For a while now I have had a problem with FSX which before today I have just shrugged off. But its about time I got to the bottom of the issue, which is this:

 

I fly for a virtual Airline. I can do Medium and short haul flights without issue. I can do Long Haul from Heathrow to the Far East. My problem occurs when Im long haul and going West.

 

I fly for hours without a hiccup. But, in the last two days I have tried EGLL to KBOS, twice, as soon as I reach the coast of Canada and two days running at point YQX FSX just freezes and hangs. The sound is there but the whole thing is frozen.

 

I also tried EGLL to KLAS yesterday but when I hit Canada it froze again.

 

I have, for as long as I can remember had this problem. Anywhere or anyway else I seem to manage to complete the flight. When ~I head west I have to stop FSX through the task manager due to the freeze.

 

I run lots of add ons, but no scenery anywhere near the West.

 

I made a copy of this mornings error:

 

 

Description:

A problem caused this program to stop interacting with Windows.

 

Problem signature:

Problem Event Name: AppHangB1

Application Name: fsx.exe

Application Version: 10.0.61472.0

Application Timestamp: 475e17d3

Hang Signature: f7fc

Hang Type: 2048

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 2057

Additional Hang Signature 1: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 2: 8513

Additional Hang Signature 3: 8513bb159fb6924f0924c89d62f39254

Additional Hang Signature 4: f7fc

Additional Hang Signature 5: f7fc88831a14516a1a53b7dc654b9c89

Additional Hang Signature 6: 8513

Additional Hang Signature 7: 8513bb159fb6924f0924c89d62f39254

 

Any suggestions would be appreciated.

 

Many Thanks

 

 

Steve.

 

FSX on 64 bit installed in its own C:

i5 O/C 3.6ghz

4GB Ram

GTX 260 Graphics Card.

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

What aircraft were you flying or loading at the time of the crash? This crash is usually due to FSX looking for a texture or a module or a gauge and cannot find it. One person who had this exact same crash uninstalled Aerosim's AirbusX. Not saying there's a problem with this aircraft. Just saying it may have not installed correctly. There have been issues with FSInn too if you have that installed. Renaming your FSX.cfg to fsx.old and restarting FSX and letting the sim rebuild your FSX.cfg has fixed problems in the past too. If it doesn't, simply go back and rename the fsx.old to fsx.cfg. Hopefully one of these suggestions will work.

 

Best regards,

Jim

Sounds like our old friend - the UIAutomationCore.dll issue again, Jim.

 

All the best,

 

pj

Set up a flight in a default a/c. Start it in mid flight somewhere just before it usually crashes. If it crashes around the same spot, you're probably looking at some sort of scenery corruption. Sometimes having two texture folders in the same area, etc. It just might narrow down your search a bit.

 

Vic

Sounds like our old friend - the UIAutomationCore.dll issue again, Jim.

 

All the best,

 

pj

 

You might be right Paul and that's an easy 'fix' to check out but let's see how he does with the new fsx.cfg, FSInn issue, or a bad aircraft install. It could also be a corrupted logbook.bin too. Just so many possibilities. I had an AppHang once before and it took me a long time to figure it out. Actually turned out to be faulty memory settings in my BIOS even though I had my settings tested for stability and they passed testing every time. Hopefully you and Vic will linger and help me out on this one if my first recommendations don't work.

 

Best regards,

Jim

All.

 

Thanks for all your replies. Sadly I have hit a busy period at work audit maybe a week or so before I get to test your suggestions. I did a bit of research prior to posting and noticed the UiAutomation thing. I think I downloaded it correctly and placed it in the root folder of fsx but still the game froze.

 

This normally happens long Hal and the only aircraft I fly that distance is the PMDG 747x.

 

Is Shall try the suggestions above and report back.

 

Thanks

If you are getting long haul crashes, look at overheating issues, especially if you are overclocked.

 

Best regards,

Jim

A very quick update as i have only had 30 mins testing. I did a search for fsinn on my system and i don't think i have it installed. I started a flight in the pmdg 737 nix. And put myself 33000 above cyqx. The sim froze after about 30 secs of flying. It had a very similar hang error message that ill post later. I dont believe overheating is an issue as this was immediatley after turning the computer on. I do monitor the temps with an app and they are normally in an ok range. More testing to follow.....

Allmost sounds more like a VAS deal.

If it happens when you approach a certain area, then it could be scenery corruption or errors, I've encountered this behaviour on a couple of systems that needed scenery updates or an FSX Repair.

.....

Allmost sounds more like a VAS deal.

 

Whats a VAS deal.

.....

 

Whats a VAS deal.

 

http://#####.wordpress.com/2012/09/24/oom-out-of-memory-helperfix/

Just checking - what version of the UIAutomationCore.dll did you download, Steve?

Check out Nye Jones update to the UIAutomation issue on FSN:

http://www.flightsimulatornetwork.com/topic/3598-uiatomationcoredll/#entry19708