Hello all

 

I have just migrated to FSX from FS9 after many years. I have to say the transition has been painful. I'd read lots about FSX being slow and hungry for power and it's not a lie!

 

However  controlling the aircraft with my homemade control column is exceptionally good. I'm using Prosim and their Jetstream 737-800 aircraft and it's an excellent combination.

 

I'm going to persevere but first I am experiencing this CTD which occurs usually when I click on one of the options on the menu at the top of the screen.

 

I receive the "fatal error' message which I have learned very quickly is common but also there appears to be many resolutions to this problem. I'm wondering if anyone can share a secret

or two on how I might cure this problem or indeed where to find and use some kind of logging?

 

Thank you in advance for your advice

 

Regards

 

Alan W

 

 

 

 

try and copy the UIautomation from windows to the FSX root folder.

Thanks but I wouldn't know where to start with that one.

 

What exactly is it?  Sorry not that PC literate

 

Regards

 

Alan

It is in "your windows \windows\system32\UIAutomationCore.dll"  so it could c:\windows\system32\UIAutomationCore.dll depending on the partition you have windows installed in.

 

 copy "UIAutomationCore.dll"  and paste it under your FSX folder , again "your fsx path \Program Files (x86)\Microsoft flight simulator X"  copy it here and check fsx if it crashes. Does it show a window on Crash ?

I think I can manage that but will have to wait til tomorrow.

 

What will it prove?

 

Thanks

 

Alan

 

 

 

I think I can manage that but will have to wait til tomorrow.

 

What will it prove?

 

NP

 

the crash you get when clicking on the menu.

try and copy the UIautomation from windows to the FSX root folder.

 

I think I can manage that but will have to wait til tomorrow.

 

What will it prove?

 

Thanks

 

Alan

I'm sorry but the recommendation from ironmaiden is totally incorrect.  In fact I have never heard of this one before.  There are some other bad and wrong suggestions throughout the Internet on employing the uiautomationcore.dll.  Mostly individuals are recommending you download the 64 bit version and put it in your main fsx folder.  But, copying and placing the one in your Windows folder and placing it in the main FSX folder doesn't harm a thing as FSX will simply read both of them. The correct information is located in the AVSIM CTD Guide (see pinned topic in this forum).  Here's a quote to make it easier to find:

 

"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 should also download and run AppCrashView (see AVSIM CTD Guide for link) then copy and paste the crash report here so experts can take a look at it and possibly find a solution.  The uiautomationcore.dll will not fix the problem you are having with touching the FSX menu as you have to right click at least 20 times and you already stated you just click it once and your sim crashes.  This is an indication of memory starvation and high settings in the fsx.cfg and/or display driver settings.  The AVSIM FSX Configuration Guide (see link in my signature) has great suggestions on how to configure FSX and your NVidia video card.  There are several tweaks that cause memory starvation and you may have one or two in your fsx.cfg.  The main culprit is the BufferPool tweak.  If you used the Venetubo tweaks, then this is most likely the cause of your problem(s).  You should delete or rename your fsx.cfg and let it rebuild.  Go fly.  Hope this helps!

 

Best regards,

Hi Jim

 

Thank you very much for your detailed explanation. Unfortunately I'm not much the wiser due to my lack of knowledge and confidence interfering with the norm certainly where MSFS is concerned.

 

Nevertheless I'll read your post a few times more-it might sink in.

 

I've installed FSX Deluxe straight out of the box, I've added one UK2000scenery airport, FSUIPC and Prosim Jetstream aircraft for FSX.

 

With regard to my PC, I specifically ordered one that would cope with FS9 and it does very well

but FSX seems hopeless. All FSX settings are set at default.

 

I've attached my PC specs. Would you mind having a look and telling me what you think?

 

Intel core i7-(four core,10MB cache) 3.6 GHZ  

Memory 16384 (4x4  GB) 1600Hz DDR3 Quad channel

Hard drive 2TB RAID 0 (2 x 1TB, SATA 6Gb/s,7200RPM,32MB Cache)

Graphics 2GB GDDR5 Nvidea GTX680

 

Much appreciated

 

Regards

 

Alan

 

 

I'd read lots about FSX being slow and hungry for power and it's not a lie!

 

LOL!  When you install FSX Deluxe and then SP1 and then SP2 (or just installed FSX/Acceleration), you fps should be nearly 200-300. When you install FSX you need to run it first before installing SP1.  After installing SP1, you must run it again before installing SP2.  Should you just have FSX and Acceleration, then you need to install FSX, run it once, then install Acceleration.  Many people install FSX out of the x86 folder and place it in a separate location like C:\FSX.  FSX and all updates must be installed with elevated permissions (Run as Administrator).  User Access Controls (UAC) must be disabled.  Any anti-virus program must be disabled during the installations.  I like the following guide for installing/uninstalling FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.  FSX has superior technology compared to FS9 (duh!).  When it was first released in late 2006, computers were not very fast and even an overclock to 3.8 with an 8800GTX video card had issues running it with 30 fps.  Since Sandy Bridge (two years ago), FSX has gotten much better.  If you cannot get around 300 fps with fsx w/o any addons, then something is seriously wrong with the configuration of your computer system (not FSX).  Everything runs great with FSX until you start adding addons then things start going down the tubes.  High FSX settings to get that "eye-candy" will also destroy FSX even on the most powerful systems.  That's why you need to follow the FSX Configuration Guide as I suggested in my previous post. 

 

 

 

With regard to my PC, I specifically ordered one that would cope with FS9 and it does very well
but FSX seems hopeless. All FSX settings are set at default.
I've attached my PC specs. Would you mind having a look and telling me what you think?

Intel core i7-(four core,10MB cache) 3.6 GHZ
Memory 16384 (4x4 GB) 1600Hz DDR3 Quad channel
Hard drive 2TB RAID 0 (2 x 1TB, SATA 6Gb/s,7200RPM,32MB Cache)
Graphics 2GB GDDR5 Nvidea GTX680

 

Since you do have a Sandy Bridge or high level system (i7 shows that), then you should be running fsx near 300 fps without any addons.  If not, you employed tweaks and tweaks will destroy any Sandy Bridge or better system.  Do you know the name of your CPU (i.e., 2600, 2700, 4770)?  It looks like you might have a high-powered system like mine (a Haswell 4770K).  Look at the basic information about your computer by clicking on the Start button, right clicking the Computer menu item and selecting Properties.  It will show you some basic data as well as an opportunity to run the Windows Experience Index.  A 'K' at the end of the name of the CPU name indicates you can overclock your computer (i.e., 4770K).  The rest of your system looks very good.  You have 16GB of memory.  Was it overclocked when you bought it?  You need to update your profile in the sidebar with your new system.

 

I heard UK2000 scenery is not frame rate friendly.  Disable it in the Scenery Library and see how much better your fps are.  If that's the only addon scenery then you do have serious problems and I cannot help you there other than to tell you to live with the ugly fps with UK2000 scenery installed.  Of course you should also seek advice in the FSX or Hardware forums.  Be careful!  Everyone thinks he's an expert (including me).  B)

 

Hope this helps.

 

Best regards,

Hello Jim

 

Well I followed the PMDG link and uninstalled/re-installed FSX and don't quote me on this as I haven't done extensive testing but there was a definite improvement.

 

So thanks for all your help it's very much appreciated. I shall stick with it because there are things in FSX I couldn't do with FS9 which have made such a significant difference.

 

Kind regards

 

Alan

Hello Jim

 

Well I followed the PMDG link and uninstalled/re-installed FSX and don't quote me on this as I haven't done extensive testing but there was a definite improvement.

 

So thanks for all your help it's very much appreciated. I shall stick with it because there are things in FSX I couldn't do with FS9 which have made such a significant difference.

 

Kind regards

 

Alan

Yes, you probably had settings in your fsx set a little too high and/or a couple bad tweaks.  You have to be careful.  Glad to hear FSX is working better for you.

 

Best regards,

Hello Jim

 

Still esperiencing CTD when switching views and using the menus so following your guide I found this. Are you able to suggest what the issue might be?

Thank you.

 

Regards

 

Alan

 

Log Name:      Application
Source:        Application Error
Date:          25/01/2014 21:14:44
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FS9MainMachine
Description:
Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: uiautomationcore.dll, version: 7.0.0.0, time stamp: 0x4a5bdb1d
Exception code: 0xc0000005
Fault offset: 0x0000e52a
Faulting process id: 0x1b8c
Faulting application start time: 0x01cf1a10ab4a12a2
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\Windows\system32\uiautomationcore.dll
Report Id: b60feca8-8605-11e3-8ee8-d4bed9fc96d2
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-25T21:14:44.000000000Z" />
    <EventRecordID>23210</EventRecordID>
    <Channel>Application</Channel>
    <Computer>FS9MainMachine</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>uiautomationcore.dll</Data>
    <Data>7.0.0.0</Data>
    <Data>4a5bdb1d</Data>
    <Data>c0000005</Data>
    <Data>0000e52a</Data>
    <Data>1b8c</Data>
    <Data>01cf1a10ab4a12a2</Data>
    <Data>C:\FSX\fsx.exe</Data>
    <Data>C:\Windows\system32\uiautomationcore.dll</Data>
    <Data>b60feca8-8605-11e3-8ee8-d4bed9fc96d2</Data>
  </EventData>
</Event>

Hey maybe I made a mistake about the UIautomation , guess Jim was right , and Jim sorry, but I had this issue once and it had fixed it.

 

Have you copied the UIautomation in to the FSX folder ? if you did remove it and try again.

 

 

Are you able to suggest what the issue might be?

 

The following link helped one person.  It has the link to one of the recommended uiautomationcore.dll that can be placed in your main fsx directory.

 

http://jonsview.com/solution-to-microsoft-flight-simulator-x-side-by-side-error

 

Best regards,

Hello

 

I'm happy to paste this file into the folder but what exactly is meant by main FSX directory?

 

Thank you.

 

Kind regards

 

Alan