Hi

 

I have recently installed Windows 8.1 as the OS for my new PC and I am having a problem with FSX .  During a flight, occasionally the flight 'freezes' and I get a message,  'A Fatal Error has Occured.  Windows is searching for a Solution.'   Does anyone have the same problem or what might be the cause of this error?  Someone did suggest inserting 'UlAutomationCore.dll' in the root directory of FSX, since this seemed to cure a similar problem with FSX in Windows 7.  I have done this but it has not cured this problem.

 

Ray

 

 

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. See our image posting rules here.

 

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.

 

 

Someone did suggest inserting 'UlAutomationCore.dll' in the root directory of FSX, since this seemed to cure a similar problem with FSX in Windows 7. I have done this but it has not cured this problem.

 

You need to check out the AVSIM CTD Guide (see pinned topic at top of this forum).  Here's what the guide says about the uiautomationcore.dll -

 

"UIAutomationcore.dll - This module placed in your main FSX directory will sometimes fix FSX from freezing up after hitting the FSX menu and also right clicking the menu repeatedly (20 or more hits).  The Vista version of this module will stop FSX from freezing up when you hit the FSX menu or do a lot of right clicking inside of FSX several times during a flight session.  Some AVSIM members have tried to duplicate this crash by repeatedly hitting the FSX menu and have been unsuccessful.  The UIAutomationcore.dll is part of the Microsoft.net package, released for various versions of Windows.  We advise members as follows:

• This “fix” only fixes menu and right clicking crashes and will not prevent any other type of FSX crash.
• Use only if you have Windows 7, 64 bit installed.  Not for 32 bit Windows OS systems.  Based on an Internet search, it was found that many individuals have been wrongly advised to install the 64-bit version since they have the 64 bit version of Windows installed.  This is wrong as FSX is a 32-bit application and doing so will have no effect on FSX.
• Windows 8, 64 bit users can try this fix for menu freezes but at your own risk. We believe it is incompatible. See below regarding a memory leak in Windows 8.
• We do not recommend placing this module in the main P3D V2.0 folder.
• Do not automatically place this module in your main FSX folder. Wait until a problem as described above occurs.  There have been several incidents where this module has been found incompatible and has actually caused other types of CTD’s.  When the individual removes the module, CTD’s stop.
• It has been proven beyond any doubt that the module will not fix any other type of FSX crashes.  Any member can see this by looking at AppCrashView reports in the CTD Forum where the UIAutomationcore.dll in the main FSX folder loaded but the crash was caused by another module. 

If FSX freezes up while going back and forth from the FSX menu or right-clicking your mouse during a flight, try placing one of the following 32 bit UIAutomationcore.dll modules into your main FSX folder:

Version: 6.05840.16386 - This 32 bit version was the Vista and pre-FSX SP1 version which seems to work the best for the majority of members. We recommend this version be installed.

 

Version: 6.0.6001.18000 - This version is the version used with Vista and FSX SP1.  It is recommended by many computer experts throughout the flight simulator community but has caused problems for several as attested in our CTD Forum.  This version is not readily available on the Internet except at a few commercial websites (i.e., Flight1 SimForums or PMDG) that believe this version is the proper one to install.  If you find that the 16386 version did not prevent FSX menu freezes, you can conduct a search for the 18000 version.  More information about the proper version can be found at the following link - http://forum.avsim.net/topic/421820-wrong-version-of-uiautomationcoredll/.

 

Memory leak when using UIAutomationcore.dll in Windows 8 – This problem may or may not have been fixed but more information about this problem can be found here - http://support.microsoft.com/kb/2885482."

 

You need to download and run AppCrashView (see AVSIM CTD Guide).  Here is what the guide says about AppCrashView:

 

"AppCrashView - usually, when you get a CTD, a Windows Error Report (WER) is generated by Windows.  This report is not very detailed and Microsoft did not make it easy for you to find or interpret the report.  After a crash you should download and run a neat utility called AppCrashView (click on AppCrashView to go to the website to download this program).  It interprets the Microsoft WER reports and provides more details.  If you post a CTD or problem, you should copy and paste the report in your topic.  Along with this, include your system specifications." 

 

You should post your system specs and/or put them in your AVSIM Profile (see mine in the sidebar). 

 

Hope this helps.

 

Best regards,

Jim - thanks for prompt reply.

 

I've read the guide regarding "UIAutomationcore.dll" fix and it states:

 

1)   the 'fix' only fixes menu and right clicking crashes, and

 

2)   for Windows 8, 64bit users, we believe it is incompatible.

 

I don't have right click crashes and I'm a Windows 8.1 64bit user. So it seems the fix won't be much help.  Also, I don't exactly have a CTD.  FSX 'freezes' momentarily, and then immediately re-starts the chosen flight.

 

I was hopeing this feature might be experienced by someone else with my OS and, since Windows 8.1 is only out a couple of months, it might be a new unique feature.   I will though use 'AppCrashView' but what do you think?

 

Ray

 

 

I don't exactly have a CTD. FSX 'freezes' momentarily, and then immediately re-starts the chosen flight.

 

Well, in your OP you stated a fatal error occurred and fsx must close.  Those usually show up at least in the Event Viewer (which is described in the AVSIM CTD Guide).  AppCrashView should find the crash too if there's a fatal error. 

 

I only mentioned the uiautomationcore.dll as you stated someone had suggested placing it in your fsx folder in your OP.  There shouldn't be any difference between FSX freezing in Windows 8.1 and Windows 7.  FSX is a 32-bit application working inside a 64-bit environment.  Hopefully you can provide more information or, like you say, someone who has Windows 8 will see this and provide a solution.

 

Best regards,

Jim - indeed I did and I should be more careful: I said "FSX will close".  Now I'm not too sure if this is so, because as I said, "FSX freezes and then re-starts the flight".  So FSX is not closing.  The next time I get the "freeze" I will read the message more precisely.

 

I had a look in the 'Event Viewer' but couldn't see the event.  I will check the 'AppCrashView' .

 

Ray

I've just had the "Freeze" again and do not get a CTD.  Rather, as before, an immediate re-launch of the flight chosen originally.   I have looked in the Event Viewer but I only see 2 events and both are "Event 410, Kernel-PnP" from some time ago with under general I see "Device SCSI\----".   Also, should I be able to select "custom View" in the Event Viewer?   I only see things like "Create (or Import) Custom View".

Thanks

Ray

 

 

Also, should I be able to select "custom View" in the Event Viewer? I only see things like "Create (or Import) Custom View".

 

As shown in the AVSIM CTD Guide, you want to look at Custom Views>Administrative Events.  This lists all events that occurred so you don't have to go looking through a bunch of logs.  As the AVSIM CTD Guide suggests, you should run a Driver Scanner program which is freeware to run but, if it finds outdated drivers, it will offer to download and install them for you for a small annual registration fee.  Since it shows what drivers are outdated and the name of the update, you can simply Google the driver and search for it, download it, and install it yourself.  It's amazing how many device drivers, system bus and USB drivers are out of date (Microsoft Update does not update these drivers).  The Event 410 indicates to me you have an outdated driver.

 

Best regards,

I have Windows set to download driver software automatically for all devices.  Is this sufficient to ensure drivers are always up to date?

 

Also, as I say, how do I select Custom View in the Event Viewer?   I cannot see this on the right hand side of the event viewer.

 

Ray

 

 

I have Windows set to download driver software automatically for all devices. Is this sufficient to ensure drivers are always up to date?

 

Hi Ray,

 

The only one I have seen them update or notify you about an update is the video card.  I might have seen the sound card and maybe the keyboard (if it is a Microsoft one) but I have never seen anything for IDE ATA/ATAPI controllers, the Intel Chipset Family SATA AHCI controller (good if you have an SSD), Intel Management Engine Interface, DVD drives, disk drives, network adapters, your CPU, USB controllers, High precision event timer, direct memory access controller, the PCI Bus, the Microsoft Virtual Drive Enumerator driver, PCI Express standard Downstream Switch Port, printers, keyboard, mice, throttle controllers, any external HDD's, and other device drivers.  These drivers are constantly being updated as bugs are found and fixed.

 

 

 

Also, as I say, how do I select Custom View in the Event Viewer? I cannot see this on the right hand side of the event viewer.

 

On page 2 of the AVSIM CTD Guide is a picture with a red arrow showing Administrative Events.  That is for Windows 7 though and maybe it is different for Windows 8.1.  Here's a How to link - http://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/.  They say it is for Windows 8.  The Internet says Administrative Events is included with Windows 8.  Also, from the people who invented AppCrashView, here's a program to review events w/o opening the Event Viewer -http://www.nirsoft.net/utils/my_event_viewer.html.  If you have a 64 bit system, get that version.

 

Best regards,

Hi Jim

 

I've pinned down the fatal error in the event viewer.  It was in "THIS PC->Local Disk(D:)->FSX->Modules" and it was a file called FSUIPC4.  I have updated this and it seems to have cured my problem.  Many thanks for staying with me on this one.

 

Ray

Thanks for posting the solution to your problem.  This is a reason why I recommend disabling the modules in your dll.xml whenever you have a crash, restart FSX and see if the problem is fixed.  If so, then it is one of the modules.

 

Best regards,

Hi Jim

 

Opooos - I spoke to quick.   I have been doing a "stress test" on my FSX setup and am getting other crashes.  One of the high speed crashes gave this message:

 

Microsoft Flight Simulator has stopped working.

A problem caused the program to stop working correctly.

Windows will close the program and notify you if a solution is available.

 

I looked in the Event Viewer and found an Application Error for fsx.exe at the precise time: 

 

Faulting Module Name:   ntdll.dll

 

Where is this module: a search doesn't find it.   You also recommended disabling the modules in my "dll.xml".  Where do I find these modules?  Could you explain this more fully?  Is ntdll.dll the culprit this time?

 

Thanks again.

 

Ray

I've done another search and found dll.xml.  Double clicking this does not reveal any modules to me, but a lot of text.    Further, I've searched for ntdll.dll and found this to be a file in Windows!  Another site says they can fix dll in Windows.  Finally, the site PMDG says that several addons (most notably, several of Wilco/FeelThere) can corrupt the FSXdll.xml file.  Is all this of any help to me?

Ray

I've done another search and found dll.xml.  Double clicking this does not reveal any modules to me, but a lot of text.    Further, I've searched for ntdll.dll and found this to be a file in Windows!  Another site says they can fix dll in Windows.  Finally, the site PMDG says that several addons (most notably, several of Wilco/FeelThere) can corrupt the FSXdll.xml file.  Is all this of any help to me?

Ray

You disable a module by changing the word False to True as follows:

 

<Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>  This is the line to change.  Change False to True for each module.  Save and restart FSX.  

    <Path>as_srv\as_btstrp.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Disabled>False</Disabled>

    <Path>Modules\FSUIPC4_Loader.dll</Path>

  </Launch.Addon>

 

Do not disable the top module:

 

<?xml version="1.0" encoding="windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

 

If you still get the ntdll.dll error, then that is not the problem.

 

You still have not posted an AppCrashView report.

 

Do you have MyTrafficX 5.4c installed?  It has been known to cause an ntdll.dll crash.  Uninstall MyTrafficX or go back to Version 5.4b or go to the MyTrafficX support forum for more details about this issue.  The AVSIM CTD Guide has more information about the ntdll.dll CTD.

 

Best regards,