Jump to content
Sign in to follow this  
Followers 0
Sandy_Bridge

FSX CTD, Windows 10, not tweaked

By Sandy_Bridge, in Crash To Desktop (CTD) Forum

Recommended Posts

Sandy_Bridge    11

Sandy_Bridge
Posted

Hello.

 

So I built a new PC for FSX, but I have been getting quite frequent crashes to the desktop. The AppCrashView report is linked at https://dl.dropboxusercontent.com/u/30271625/Report.wer These happen quite randomly, this one was at a gate in EGKK in the PMDG737NGX. The only addons running were UK2000 EGKK scenery, the NGX, and AES 2.39a. My OS is Windows 10 x64 and the only tweaks to FSX are HGHMEMFIX, WideViewAspect, and NVIDIA Inspector tweaks.

 

I would like to resolve this without installing Windows 7.

 

Thanks in advance.

Mihkel Kiil

Share this post

Link to post
Share on other sites

Sandy_Bridge    11

Sandy_Bridge
Posted

Now it seems that UIAutomationCore.dll is the problem.

Version=1
EventType=APPCRASH
EventTime=130875773561323837
ReportType=2
Consent=1
UploadTime=130875773561954605
ReportIdentifier=d6792e70-62c5-11e5-9be4-0862664c35fd
IntegratorReportIdentifier=d35a7f3e-a39e-43b5-945c-9f1713681c83
WOW64=1
NsAppName=fsx.exe
Response.BucketId=17a27be16108f093f7dfc2d62461c922
Response.BucketTable=1
Response.LegacyBucketId=107535217019
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=uiautomationcore.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.2.10240.16431
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=55c9b4ec
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00064475
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a3dc
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a3dc5dbdb64b01201fd6b823fc873afe
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=d5fe
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=d5fe8903ab168eec701a67f28413fdfb
UI[2]=D:\FSX\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\apphelp.dll
LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\Windows\SYSTEM32\windows.storage.dll
LoadedModule[11]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[12]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[13]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[14]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[17]=C:\Windows\SYSTEM32\advapi32.dll
LoadedModule[18]=C:\Windows\SYSTEM32\shlwapi.dll
LoadedModule[19]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[20]=C:\Windows\SYSTEM32\shcore.dll
LoadedModule[21]=C:\Windows\SYSTEM32\powrprof.dll
LoadedModule[22]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[23]=C:\Windows\SYSTEM32\OLEAUT32.dll
LoadedModule[24]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[25]=C:\Windows\SYSTEM32\CFGMGR32.dll
LoadedModule[26]=C:\Windows\SYSTEM32\MPR.dll
LoadedModule[27]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[28]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[29]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[30]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[31]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[32]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\COMDLG32.dll
LoadedModule[34]=C:\Windows\SYSTEM32\IMM32.dll
LoadedModule[35]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[36]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[37]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[38]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10240.16384_none_49c02355cf03478c\COMCTL32.dll
LoadedModule[39]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[40]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[41]=C:\Windows\SYSTEM32\DDRAW.dll
LoadedModule[42]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[43]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[44]=C:\Windows\SYSTEM32\msi.dll
LoadedModule[45]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[46]=C:\Windows\SYSTEM32\DCIMAN32.dll
LoadedModule[47]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[48]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[49]=C:\Windows\SYSTEM32\UxTheme.dll
LoadedModule[50]=C:\Windows\SYSTEM32\samcli.dll
LoadedModule[51]=C:\Windows\SYSTEM32\MSACM32.dll
LoadedModule[52]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[53]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[54]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[55]=C:\Windows\SYSTEM32\SortWindows61.dll
LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[57]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCR80.dll
LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[59]=D:\FSX\language.dll
LoadedModule[60]=D:\FSX\API.DLL
LoadedModule[61]=D:\FSX\ablscpt.dll
LoadedModule[62]=D:\FSX\acontain.dll
LoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9185_none_d0905a48442809b8\MSVCP80.dll
LoadedModule[64]=D:\FSX\ai_player.dll
LoadedModule[65]=D:\FSX\atc.dll
LoadedModule[66]=D:\FSX\controls.dll
LoadedModule[67]=D:\FSX\demo.dll
LoadedModule[68]=D:\FSX\facilities.dll
LoadedModule[69]=D:\FSX\fe.dll
LoadedModule[70]=D:\FSX\flight.dll
LoadedModule[71]=D:\FSX\fsui.dll
LoadedModule[72]=D:\FSX\g2d.dll
LoadedModule[73]=D:\FSX\g3d.dll
LoadedModule[74]=D:\FSX\gps.dll
LoadedModule[75]=D:\FSX\livingwater.dll
LoadedModule[76]=D:\FSX\main.dll
LoadedModule[77]=D:\FSX\multiplayer.dll
LoadedModule[78]=D:\FSX\panels.dll
LoadedModule[79]=D:\FSX\sim1.dll
LoadedModule[80]=D:\FSX\simprop.dll
LoadedModule[81]=D:\FSX\simscheduler.dll
LoadedModule[82]=D:\FSX\sound.dll
LoadedModule[83]=D:\FSX\symmap.dll
LoadedModule[84]=D:\FSX\terrain.dll
LoadedModule[85]=D:\FSX\fs-traffic.dll
LoadedModule[86]=D:\FSX\ui.dll
LoadedModule[87]=D:\FSX\util.dll
LoadedModule[88]=D:\FSX\visualfx.dll
LoadedModule[89]=D:\FSX\weather.dll
LoadedModule[90]=D:\FSX\window.dll
LoadedModule[91]=D:\FSX\xuipc.dll
LoadedModule[92]=C:\Windows\SYSTEM32\MSWSOCK.dll
LoadedModule[93]=C:\Windows\SYSTEM32\SHFOLDER.dll
LoadedModule[94]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10240.16384_none_d15682eeaf714889\gdiplus.dll
LoadedModule[95]=C:\Windows\SYSTEM32\DINPUT8.dll
LoadedModule[96]=C:\Windows\SYSTEM32\d3dx9_34.dll
LoadedModule[97]=C:\Windows\SYSTEM32\d3dx10_34.dll
LoadedModule[98]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[99]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[100]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[101]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[102]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[103]=C:\Windows\system32\rsaenh.dll
LoadedModule[104]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[105]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[106]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[107]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[108]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[109]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[110]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[111]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[113]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[114]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[115]=C:\Windows\SYSTEM32\nvd3dum.dll
LoadedModule[116]=C:\Windows\system32\nvspcap.dll
LoadedModule[117]=C:\Windows\SYSTEM32\PSAPI.DLL
LoadedModule[118]=C:\Windows\SYSTEM32\WINHTTP.dll
LoadedModule[119]=C:\Windows\system32\nvapi.dll
LoadedModule[120]=C:\Windows\SYSTEM32\D3DCompiler_34.dll
LoadedModule[121]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[122]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[123]=C:\Windows\SYSTEM32\d3d10_1.dll
LoadedModule[124]=C:\Windows\SYSTEM32\d3d10_1core.dll
LoadedModule[125]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[126]=C:\Windows\SYSTEM32\dxdiagn.dll
LoadedModule[127]=C:\Windows\SYSTEM32\d3d12.dll
LoadedModule[128]=C:\Windows\SYSTEM32\msvcp110_win.dll
LoadedModule[129]=C:\Windows\system32\winbrand.dll
LoadedModule[130]=C:\Windows\SYSTEM32\WTSAPI32.DLL
LoadedModule[131]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[132]=C:\Windows\SYSTEM32\gameux.dll
LoadedModule[133]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10240.16384_none_3bccb1ff6bcd1849\COMCTL32.dll
LoadedModule[135]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[136]=C:\Windows\System32\Wpc.dll
LoadedModule[137]=C:\Windows\System32\msvcp_win.dll
LoadedModule[138]=C:\Windows\SYSTEM32\ucrtbase.dll
LoadedModule[139]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[140]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[141]=C:\Windows\SYSTEM32\uiautomationcore.dll
LoadedModule[142]=C:\Windows\System32\MMDevApi.dll
LoadedModule[143]=C:\Windows\System32\PROPSYS.dll
LoadedModule[144]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[145]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[146]=C:\Windows\SYSTEM32\RICHED20.DLL
LoadedModule[147]=C:\Windows\SYSTEM32\USP10.dll
LoadedModule[148]=C:\Windows\SYSTEM32\msls31.dll
LoadedModule[149]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[150]=C:\Windows\SYSTEM32\XInput9_1_0.dll
LoadedModule[151]=C:\Windows\SYSTEM32\wdmaud.drv
LoadedModule[152]=C:\Windows\SYSTEM32\ksuser.dll
LoadedModule[153]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[154]=C:\Windows\SYSTEM32\msacm32.drv
LoadedModule[155]=C:\Windows\SYSTEM32\dinput.DLL
LoadedModule[156]=C:\Windows\SYSTEM32\XInput1_4.dll
LoadedModule[157]=D:\FSX\VistaMare\ViMaCoreX.dll
LoadedModule[158]=D:\FSX\VistaMare\bin\VMCX_AP.dll
LoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[160]=D:\FSX\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[161]=D:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[162]=C:\Windows\SYSTEM32\MSVCR100.dll
LoadedModule[163]=D:\FSX\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[164]=D:\FSX\RAASPRO\RAASPRO.dll
LoadedModule[165]=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[166]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[167]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[168]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[169]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[170]=C:\Windows\System32\rasadhlp.dll
LoadedModule[171]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[172]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[173]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[174]=C:\Windows\SYSTEM32\MSDART.DLL
LoadedModule[175]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[176]=C:\Windows\SYSTEM32\DPAPI.dll
LoadedModule[177]=C:\Windows\SYSTEM32\comsvcs.dll
LoadedModule[178]=C:\Windows\SYSTEM32\msjetoledb40.dll
LoadedModule[179]=C:\Windows\SYSTEM32\msjter40.dll
LoadedModule[180]=C:\Windows\SYSTEM32\msjet40.dll
LoadedModule[181]=C:\Windows\SYSTEM32\MSJINT40.DLL
LoadedModule[182]=C:\Windows\SYSTEM32\mswstr10.dll
LoadedModule[183]=C:\Windows\SYSTEM32\mstext40.dll
LoadedModule[184]=C:\Windows\SYSTEM32\mlang.dll
LoadedModule[185]=C:\Windows\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[186]=C:\Windows\SYSTEM32\X3DAudio1_6.dll
LoadedModule[187]=C:\Windows\SYSTEM32\xactengine3_4.dll
LoadedModule[188]=C:\Windows\SYSTEM32\XAudio2_4.dll
LoadedModule[189]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[190]=C:\Windows\system32\dataexchange.dll
LoadedModule[191]=C:\Windows\system32\d2d1.dll
LoadedModule[192]=C:\Windows\system32\dcomp.dll
LoadedModule[193]=C:\Windows\system32\twinapi.appcore.dll
LoadedModule[194]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[195]=C:\Windows\SYSTEM32\ieapfltr.dll
LoadedModule[196]=C:\Windows\system32\msimtf.dll
LoadedModule[197]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[198]=C:\Windows\SYSTEM32\d3d10warp.dll
LoadedModule[199]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[200]=D:\FSX\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[201]=D:\FSX\GAUGES\PMDG_737NGX.DLL
LoadedModule[202]=C:\Windows\SYSTEM32\NETAPI32.dll
LoadedModule[203]=C:\Windows\SYSTEM32\WSOCK32.dll
LoadedModule[204]=C:\Windows\SYSTEM32\MSVCP100.dll
LoadedModule[205]=C:\Windows\SYSTEM32\wkscli.dll
LoadedModule[206]=C:\Windows\SYSTEM32\netutils.dll
LoadedModule[207]=C:\Windows\SYSTEM32\srvcli.dll
LoadedModule[208]=C:\Windows\SYSTEM32\XAudio2_7.dll
LoadedModule[209]=D:\FSX\Gauges\PMDG_737NGX_2.dll
LoadedModule[210]=C:\Windows\SYSTEM32\OLEACC.dll
LoadedModule[211]=C:\Windows\SYSTEM32\snmpapi.dll
LoadedModule[212]=C:\Windows\system32\napinsp.dll
LoadedModule[213]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[214]=C:\Windows\system32\NLAapi.dll
LoadedModule[215]=C:\Windows\System32\winrnr.dll
LoadedModule[216]=C:\Windows\SYSTEM32\icmp.Dll
LoadedModule[217]=C:\Windows\SYSTEM32\d3dx9_31.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=D:\FSX\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=31736CD664C91611E8FACF7B443412D4

Mihkel Kiil

Share this post

Link to post
Share on other sites

Jim Young    2,356

Jim Young
Posted

Strange installation you have there of Windows.  Your title indicates Windows 10.  The AppCrashView report shows Windows 8 (see the almost last entry of the report)(that could be there because the developers of AppCrashView haven't changed their program to see Windows 10 installed) (Windows 8 and 10 are similar).  The faulting module was the uiautomationcore.dll with a version that belongs only to Windows 10 or, at least, when I do a search on the Internet for it it is showing that it belongs to Windows 10.  So think this is your problem.  I did not see where you might have placed the dll in your main FSX directory so it's a problem with your system.  FSX is an old program.  It requires Microsoft.net 2.0 at least.  You can also try placing one of the uiautomationcore.dll versions shown in the AVSIM CTD Guide.  There is a link to each version that you can download and try.  If you place it in your FSX directory, it will load and take over the one in your Windows System folder.

 

Your Microsoft Visuals are all installed properly and I see no other problems.

 

Best regards,

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post

Link to post
Share on other sites

Sandy_Bridge    11

Sandy_Bridge
Posted

Strange installation you have there of Windows.  Your title indicates Windows 10.  The AppCrashView report shows Windows 8 (see the almost last entry of the report)(that could be there because the developers of AppCrashView haven't changed their program to see Windows 10 installed) (Windows 8 and 10 are similar).  The faulting module was the uiautomationcore.dll with a version that belongs only to Windows 10 or, at least, when I do a search on the Internet for it it is showing that it belongs to Windows 10.  So think this is your problem.  I did not see where you might have placed the dll in your main FSX directory so it's a problem with your system.  FSX is an old program.  It requires Microsoft.net 2.0 at least.  You can also try placing one of the uiautomationcore.dll versions shown in the AVSIM CTD Guide.  There is a link to each version that you can download and try.  If you place it in your FSX directory, it will load and take over the one in your Windows System folder.

 

Your Microsoft Visuals are all installed properly and I see no other problems.

 

Best regards,

I will try to remember to do that when I install FSX on Windows 10 again. For now, I'm setting up a dual-boot with Windows 7.

Mihkel Kiil

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

LoadedModule[141]=C:\Windows\SYSTEM32\uiautomationcore.dll

is not strictly compatible with FSX, use v6.0.5840.16386 placed in the FSX program files folder. The dll will be loaded from the local path of fsx.exe, if not found will load the system version. The stackhash implies the exact location of the fault is unknown.

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

RaptyrOne    1,398

RaptyrOne
Posted

I have been getting a similar issue after a clean instal of Windows 10. Without using any replacement uiautomatiocore.dll, my FSX has crashed on occasion, but only ever during the first few minutes of running FSX, usually while sitting in the flight deck doing preflight. Nothing to do with going into the menu too often. Maybe one out of every 6-10 startups of FSX will result in a crash. The uiautomationcore.dll is always reported as the issue. I foind that if it does not crash in these first few minutes, I can fly for the entire day/night in the NGX with all sim settings pretty much maxed out with no problems. This includes repeatedly entering into the menu, something well known to cause a wobble with uiautomationcore.dll. For this reason it has not bothered me too much but it is irritating when you are in the middle of programming the FMC and you have to start all over again.

 

I have now dropped the 18000 version into the FSX root and will see if this resolves the issue.

 

Apart from using one of the two file versions mentioned here (v18000 and v16386) , another suggestion, should these not work, has been to copy the version sitting in the Windows 10 Windows/System32 folder into FSX root. For some, this apparently works (for some). Although FSX should call the version in the Wndows/System32 folder, it may also call the one in the WOW64 folder, if running 64-bit OS. While the two in Win 10 have the exact same version number, they are not the same, as can be seen from the file sizes which are significantly different.

GregH

Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor

Share this post

Link to post
Share on other sites

SteveW    1,792

SteveW
Posted

Good post Greg. The menu problem often requires some other interaction due to the menu item selected. The starting issue you had would be a combination of things depending on differing periods associated with loading up the sim components as it starts.

Steve Waite: Engineer at codelegend.com

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0
Go To Topic Listing

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...