Just installed FSX on a new Windows 7 machine, and we've run into quite a problem.

 

Whenever we run 'Kiosk Mode', FSX will crash after about a minute of flight time, and display the "A fatal error has occurred" message box.  FSX seems to run just fine by itself - no crashes so far.  

 

We've placed a new "UIAutomationCore.dll" file in the FSX folder, and we've tried compatibility mode - no luck so far.

 

I've attached the error that shows up in the application log:  

 

Any thoughts?

And here's the error as reported by AppCrashView:  

And here's the error as reported by AppCrashView:  FSX Error - appcrashview.txt

 

Tell us something more about mashine - CPU(overclocked or not), GPU and RAM?

 

Anyway, update direct X and libraries and check that you have the right version of UIAutomationCore.dll, not all versions works.

 

Direct X: http://www.microsoft.com/en-us/download/details.aspx?id=35

dorect x sp1: http://www.microsoft.com/en-us/download/details.aspx?id=5582

 

 Install just "ENU (vcredist_x86.exe)" here: http://archive.msdn.microsoft.com/KB961894/Release/ProjectReleases.aspx?ReleaseId=2067

 

And here is the right version of UIAutomationCore.dll: https://www.dropbox.com/s/adxsx0mxb6wztil/UIAutomationCore.rar

 

Update your FSUIPC, just to exclude all posibilities: http://forum.simflight.com/topic/66139-updated-modules/

 

And disable UAC: http://www.mydigitallife.info/how-to-disable-and-turn-off-uac-in-windows-7/

 

If you still get crashes, disable DEP too using second metod in command prompt: http://windows7themes.net/disable-windows-data-execution-prevention-in-windows-7-vista.html 

Disable DEP only if you have antivirus softvare, othervise your PC will be vulnerable. You can use  free "avast" anivirus for example, just google for it... There are many opinions on this, i prefer to have DEP disabled all time and i never had a problem becouse of this.

 

Well, that should be all. I hope you have enough RAM, I've seen before this exception code on systems with no enough RAM....

Agree with above except for the following:  A BEX with no faulting module usually indicates issues with insufficient memory to process FSX.  FSX settings need to be reduced.

 

The uiautomationcore.dll should be removed.  It only fixes fsx menu crashes and, as you can see since you got a crash, it does not work for any other types of crashes.  I have never had it installed in my main fsx folder and have never had a menu crash.

 

You have the latest Microsoft Visual C++ 2005 so disregard the link and directions to install it (DO NOT Install just "ENU (vcredist_x86.exe)" here: http://archive.msdn....?ReleaseId=2067).

 

Try this fix - http://support.microsoft.com/kb/947246.  (Fixes the heap limitations).

 

Best regards,

Jim

I was able to try everything suggested (except FSUIPC - blocked by the web filter here at work), but still didn't have any luck.  FSX is still running fine by itself - but launching from Kiosk mode causes issues.

 

The PC isn't overclocked.  Here's the rest of the configuration:  

 

 

The same missions are also in FSX do not sure why you are running in Kiosk mode.  Your logbook could be corrupted too.  You can try renaming the logbook.bin to logbook.old and see if this fixes the problem.  If fsx does not crash, then it was a corrupted logbook.  The logbook is located in your My Documents\FlightSimulatorXFiles.  There's also a FSX Logbook Recovery program (FSX Logbook Recovery v1.1 by Daniel Van Os) that analyses and fixes the logbook.  But you want to check first whether it is corrupted.  The logbook has all of your rewards, etc., for completing a mission.

 

Other than that I'm lost.  A BEX crash indicates you had a Buffer_Exception_Overrun and that most likely indicates high FSX settings that FSX cannot handle.  The AMD A8-5500B APU really isn't all that powerful and competes maybe with the i3 or the i5 Intel CPU's.  It may be just as simple as turning down your settings in FSX.

 

Best regards,

Jim

Hi Jim, 

Thanks for your help so far.  I tried running with all of the graphics set to their lowest settings, and still had the same issue.  Haven't tried the logbook fix yet.

 

Since this PC will be set up in a museum display, we need to stick with kiosk mode.