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

 

not sure how i would find out but it states in properties it was last modified. ‎20/‎01/‎2008 ‏‎21:24

 

Thanks for the other suggestions ill look through them soon

Rt-Clk on the name, choose Properties, Details, and look for Product version (middle of the box). :smile:

Rt-Clk on the name, choose Properties, Details, and look for Product version (middle of the box). :smile:

 

Brill.. its 6.0.6001.18000

 

and this is the last hang 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: 0

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

 

Thanks Steve

have you got any of the orbox sceneries installed like the nrm since i had the same problem as yours , ctd in canada at the same area found out it was the nrm was at fault installed the patch for it and havnt had any ctds at all.

I do have the whole of oz and the pnw demo, with a few airports. But my scenery should be up to date...i'lll run the Service Patches again to make sure.

 

I did a bit of flying around YQT again this morning and had no issues.....I'm scratching me head.

 

Ta

Wrong version, Steve: Here is the correct one. Just rename it and place it in the root folder. This version won't fail.

 

It may not fix the issue you have, but one ought to have it, as FSX on Win7 can fail when it calls any of the later versions.

 

Life is good

Make sure you have your Microsoft Visuals C++ Redistributables from 2005 to 2010 with all updates installed. FSX will not work without them. For SP2/Acceleration, you need the SP1 to 2005. Windows 7 and later OS's installs all versions of dotnet to make sure your old applications run properly. Vista and XP did not install dotnet automatically. The uiautomationcore.dll is part of the dotnet package. I still think the main problem here is overheating or an issue with the overclock (i.e., wrong memory settings, CPU voltages too high/too low).

 

Hopefully Paul has the solution with the proper version of the uiautomationcore.dll but my experiences show it rarely works, especially for AppHangs. It's more of a fix for menu clickings.

 

Best regards,

Jim

Make sure you have your Microsoft Visuals C++ Redistributables from 2005 to 2010 with all updates installed. FSX will not work without them. For SP2/Acceleration, you need the SP1 to 2005. Windows 7 and later OS's installs all versions of dotnet to make sure your old applications run properly. Vista and XP did not install dotnet automatically. The uiautomationcore.dll is part of the dotnet package. I still think the main problem here is overheating or an issue with the overclock (i.e., wrong memory settings, CPU voltages too high/too low).

 

Hopefully Paul has the solution with the proper version of the uiautomationcore.dll but my experiences show it rarely works, especially for AppHangs. It's more of a fix for menu clickings.

 

Best regards,

Jim

 

Cheers Jim....

 

What I can't understand though, if it is overclocking issues, why it never happens anywhere in the sim, no matter how long I have been flying, until I hit Canada.

 

I can do a 12 hour to Hong Kong and never experience an issue or massive rise in temps...

 

Wrong version, Steve: Here is the correct one. Just rename it and place it in the root folder. This version won't fail.

 

It may not fix the issue you have, but one ought to have it, as FSX on Win7 can fail when it calls any of the later versions.

 

Life is good

 

Thanks Paul, Ill give it a whirl

What I can't understand though, if it is overclocking issues, why it never happens anywhere in the sim, no matter how long I have been flying, until I hit Canada.

 

Certainly strange for sure but I only made a suggestion for a possible fix or where to look. Do you have addon scenery in Canada that is not compatible with FSX? FSX uses the CPU(s) more than the GPU's and fsx is a program that uses a lot of resources. Things start getting hot in there when you have a long flight as there's a whole lot of rendering and computing going on (especially if you're changing views a lot).

 

Best regards,

Jim

Certainly strange for sure but I only made a suggestion for a possible fix or where to look. Do you have addon scenery in Canada that is not compatible with FSX? FSX uses the CPU(s) more than the GPU's and fsx is a program that uses a lot of resources. Things start getting hot in there when you have a long flight as there's a whole lot of rendering and computing going on (especially if you're changing views a lot).

 

Best regards,

Jim

 

Thanks for your input.

 

I have no scenery add ons in Canada.

 

The last hang on a long haul I can remember started to hang as I changed view point. But the most recent just did it looking ahead in the cockpit. I have tried the newest automation.dll and will see how it goes.

 

Thanks for your advice

Hello.

 

First Major test since putting the new UIAutomation in. PMDG 747 EGKK to KLAS. Set off last night followed the plan route and went to bed expecting a hang message in the morning, but instead I was 80NM out of KLAS and all working well, so its one nil to the Randall at the moment. Ill do a EGKK to KBOS soon and see what happens.

 

Cheers

Another update.

 

For the first time in a long time, if not ever I have finally arrived at Boston. No hangs. Lots more testing to come but fingers crossed. I did do part of the trip on x2 so maybe not along as it normally is but the computer was still solid for 5 hours so the temps should have had a chance to rise.

 

Will see.

 

Thanks guys.

 

Steve.