This event seems to occur routinely while flying the MD-11. I can fly for hours in the NGX without issue, but have always had a problem with the MD. Below is the event viewer readout for the event. I don't it can really tell us much about what happened, but maybe point towards a solution.

 

When this happens, FSX simply stops responding. No movement, no looking around/viewchanges. No sound. Sometimes it comes back after a few minutes. OTher times, it can go on for hours. I've tried every help hint I could find on here and applied them all. It helped to a point. The issue happens less frequently, but it still occures on about 40% of my MD-11 flights.

 

I have W7, i5-2500k, 16gigs of RAM, Asus P67X mobo, nVidia GTX470.

 

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-18T04:50:53.000000000Z" />
<EventRecordID>17252</EventRecordID>
<Channel>Application</Channel>
<Computer>a0jwn7V41</Computer>
<Security />
</System>
- <EventData>
<Data>fsx.exe</Data>
<Data>10.0.61472.0</Data>
<Data>16f4</Data>
<Data>01cdf51e21e8ffd5</Data>
<Data>280</Data>
<Data>C:\FSX\fsx.exe</Data>
<Data>9d5c30be-612a-11e2-aa87-f46d04e8aba2</Data>
<Binary>55006E006B006E006F0077006E0000000000</Binary>
</EventData>
</Event>

 

I also found this: (Not sure if it's different info or not)

 

Fault bucket 952671711, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0
Problem signature:
P1: fsx.exe
P2: 10.0.61472.0
P3: 475e17d3
P4: 385f
P5: 0
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\Dave\AppData\Local\Temp\WER5BFB.tmp.appcompat.txt
C:\Users\Dave\AppData\Local\Temp\WER62EE.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Dave\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_fsx.exe_45744d573e4e7688b727d1ce7753f687e1529c7_03556de5
Analysis symbol:
Rechecking for solution: 0
Report Id: 9d5c30be-612a-11e2-aa87-f46d04e8aba2
Report Status: 0

 

 

Anything popout at anyone? This happens nearly every flight, all over the world.Sometimes it recovers and is gone. Sometimes it recovers only to show up again later in the flight. It's got me pretty frustrated as I don't know what else to do.

Hi there, I started with the MD-11 last night so no relevant experience with that, but, what are your temperatures?

 

When the fault is so random, could it be that ambient temperature also had something to do with it?

 

Regards,

Morten

Hi Dave,

 

I believe your issue can be fixed by installing the Vista version of UIAutomationcore.DLL in your root FSX folder, without it the sim will freeze/crash after switch and dial movements.

 

This is from Avsim's Tutorial's page "Software & Hardware Guide."

 

MENU CRASHES AND FIX AKA UIAUTOMATIONCORE.DLL-FIX

 

There is a know bug in originally installed FSX, when you click into menus a lot, or click around the cockpit, or right click, that FSX is going to freeze and/or crash.

The problem is known to get fixed by saving a Vista UIAutomationcore.dll file into FSX folder. Just by placing it there, FSX seems to use that file and not crash FSX any more by those clicks.

Link to the file

 

The second fix is to add the following to your [Graphics] section HighMemFix=1 of your FSX.cfg. You can find all the relevant info in the guide.

 

Good luck.

I believe your issue can be fixed by installing the Vista version of UIAutomationcore.DLL in your root FSX folder, without it the sim will freeze/crash after switch and dial movements.

 

I forgot to mention that I've also made that change. I'm not really sure where to go from here. It's pretty frustrating when it happens on approach after a 8+ hour flight.

Hi Dave,

 

Sorry to read about your continued frustration. I cannot remember what causes the apphang issue.

 

Before you do anything see if you can find the error's reported when the CTD occured in the Event Viewer, go Start and type Event Viewer, double click (expand) Custom Views then double click Administrative Events and find all the relevant errors associated with the FSX CTD.

 

Then head over to the FSX CTD Forum and copy your first post a start a new topic there, or you can simply press the report button and a mod will move it to the other forum for you.

 

Pete's FSUIPC module has proven to be a vital addition to FSX and has virtually eliminated most CTD's related to graphical glitches. Also, If you have a registered copy of FSUIPC you can select autosave and return to your flight after a CTD it does not remedy it but at least you can continue from where you left off.