+- AirSource Virtual Pilot Union Forums (https://forums.air-source.us)
+-- Forum: General Discussion Conferences (https://forums.air-source.us/forumdisplay.php?fid=3)
+--- Forum: General Discussions (https://forums.air-source.us/forumdisplay.php?fid=7)
+--- Thread: FSX fatal error (/showthread.php?tid=1906)
Pages:
1
2
Re: FSX fatal error - hooger4785 - 02-02-2012
Thanks, Lee, I'll try that!
Re: FSX fatal error - hooger4785 - 02-03-2012
*sigh*...reinstalled SP1 and SP2, downloaded a new uiautomationcore.dll, and STILL happening! Here's the latest installment:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: uiautomationcore.dll, version: 6.0.6001.18000, time stamp: 0x4791a76f
Exception code: 0xc0000005
Fault offset: 0x0001dd8f
Faulting process id: 0xf10
Faulting application start time: 0x01cce21e4f2407b7
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll
Report Id: 24066748-4e13-11e1-949f-dc0ea133044c
Getting frustrated here! :evil:
Re: FSX fatal error - JSkorna - 02-03-2012
Try changing to a different video driver.
Re: FSX fatal error - hooger4785 - 02-03-2012
Different video driver...now we're getting out of my realm of computer expertise. How do I do that?
Re: FSX fatal error - Leemazz - 02-03-2012
Also try searching your computer for the uiautomationcore.dll its defo giving you problems check the versions .
It could be some addon causing it to get worked up , install new video drivers also if your on an nvidia just go to there website and follow the driver links same thing with ATI
Re: FSX fatal error - TheDude71 - 02-16-2012
My experience with FSX and that same crash, with all the fixes mentioned already, if I use the menu bar, or even right click to bring up a menu too many times, bam, CTD. :evil: :evil:
Resolution: EZDok... http://www.flight1.com/products.asp?product=ezdockcam and a nice gaming pad I had. Problem solved!!
I start my flight and only use the menu to start FSInn and FSPassengers, then I hide the menu. I have set up my EZDok for all my views needed, plus have my QT lower buttons set for outside views too. No more crashes. Point here is to stay away from the menu as much as possible. Even with the UIAutomationcore.dll fix, I was still recieveing the CTD at differnts intervels of menu usage.
Good luck and hope this was helpful to you. With EZDok, you don't need a game pad, you can use your keyboard and set it up as you like, I just find the the game pad made it more comfortable for my setup and very easy and quick to navigate the cockpit.
P.S. Sorry, should of asked, are you clicking on the menu or right clicking for the drop down menu prior to your crash????
:mrgreen: