Archived

This topic is now archived and is closed to further replies.

ryanair

FSX crashes UIautomationcore.dll

Recommended Posts

Hi,


 


everytime when I land or approach with FsPassengers fsx crashes and says only an bad  problem has occured.  When I open the fail message in my system it shows that on Windows/Syswo64 the  ntdll.dll is missing, how can I fix that? I also tried many UIautomationcore.dll ´s from vista 32 and for win7, nothing really works!  


 


Can anyone please send as attached the FSX default UIautomationcore.dll ? I didn´t backup it, because I overwrote it :(


I think with the default fsx dll it will work!


 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

There are several copies of the ntdll.dll on your computer.  The one that should be in your SysWow64 folder has a version of 6.1.7601.17725.  Look for the same version and copy it over to the SysWow64 folder.  Do not understand how you could be missing the ntdll.dll in that folder though.

 

The Uiautomationcore.dll is only suppose to be placed in your main fsx folder.  You should never try to replace the Windows 7 version.  If used, only the Vista version should be placed in your FSX folder.

 

Probably the fastest and easiest way to fix missing or corrupt Windows 7 files is to run the system file checker command - SFC \scannow - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm.

 

Uiautomationcore.dll -  The uiautomationcore.dll only fixes one problem and that's a crash if you repeatedly hit the FSX menu bar.  I personally cannot replicate this crash and have tried several times to crash my FSX by repeatedly clicking on the fsx menu bar.  No joy... I really think the menu bar crash is caused by high settings where fsx is running short of memory by the constant hitting on the menu bar.  I do not have the uiautomationcore.dll in my main fsx folder and never have (except for testing). The uiautomationcore.dll belongs with the Microsoft.net framework packages and, developers of FSX and FSX addons require dotnet versions 1.1 thru 4.5 installed to make their products work properly. I believe the Vista version of dotnet is 1.1 as it is installed with FSX/Acceleration.  Installing the Uiautomationcore.dll in your main fsx folder could create more problems so, if it doesn't work, take it out.  I have seen several reports here already (including me) where CTD's have stopped after removing the Vista version from the Main FSX folder.

 

Hope this helps.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks for your response!

 

I checked in my Syswo64 folder, there is allready the  ntdll.dll in the correct version 6.1.7601.17725.  But why my system tells me that he didn´t found it?

I had deleted one time also the Uiautomationcore.dll from FSX folder but the problem did still occured. I try this time to delete all Uiautomationcore.dll´s from System32 + Syswo64 + fsx , and see what happens.

 

PS: If I install windows vista, does the crashes still occur?

Share this post


Link to post
Share on other sites

Thanks for your response!

 

I checked in my Syswo64 folder, there is allready the  ntdll.dll in the correct version 6.1.7601.17725.  But why my system tells me that he didn´t found it?

I had deleted one time also the Uiautomationcore.dll from FSX folder but the problem did still occured. I try this time to delete all Uiautomationcore.dll´s from System32 + Syswo64 + fsx , and see what happens.

 

PS: If I install windows vista, does the crashes still occur?

 

You should not delete Uiautomationcore.dll from System32 + Syswo64, or mess with any Uiautomationcore.dll other then that from FSX main folder.

This is the right version: https://www.dropbox.com/s/adxsx0mxb6wztil/UIAutomationCore.rar

Just put Uiautomationcore.dll in your main FSX folder and that's all. Don't try to add to registry or to copy to other locations. 

 

BTW, Windows 7 is the best for FSX, and it's highly recommended. This Vista Uiautomationcore.dll fixes FSX menu crashes in Windows 7

 

It's posible now that you will experience some other strange crashes and system instability, becouse you have deleted some system files from System32 + Syswo64. Try to repair or re-install windows 7 if that happens.

 

hope this helps

Share this post


Link to post
Share on other sites

 

 


ntdll.dll in the correct version 6.1.7601.17725. But why my system tells me that he didn´t found it?

 

That probably stated it was the faulting module and the file was not missing.  Getting an ntdll.dll indicates settings are set too high for you to run fsx properly.  A bad overclock or bios settings will do it too.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

@ firehaw44

 

My Fsx settings are high, but my system aint overclocked, maybe you are right? Do you have the original fsx Uiautomationcore.dll ? FSX was made for Windows Vista not for Win7 , so maybe when I run windows vista those crashes dont occur? 

 

heres the appcrash view:

 

Version=1
EventType=APPCRASH
EventTime=130201172691873517
ReportType=2
Consent=1
UploadTime=130201172695733738
ReportIdentifier=154b0054-fd3a-11e2-aa3c-bc5ff460c978
IntegratorReportIdentifier=154b0053-fd3a-11e2-aa3c-bc5ff460c978
WOW64=1
Response.BucketId=562950098
Response.BucketTable=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=fsx.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=10.0.61637.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=46fadb14
Sig[3].Name=Fehlermodulname
Sig[3].Value=g2d.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=46fadb58
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=0001de63
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=Ein schwerwiegender Fehler ist aufgetreten.
UI[4]=Windows kann online nach einer Lösung für das Problem suchen und versuchen, das Programm neu zu starten.
UI[5]=Online nach einer Lösung suchen und das Programm neu starten
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\AppPatch\AcXtrnal.DLL
LoadedModule[60]=C:\Windows\system32\SHUNIMPL.DLL
LoadedModule[61]=C:\Windows\system32\SortServer2003Compat.dll
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80DEU.DLL
LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[65]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[68]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[71]=C:\Windows\system32\DINPUT8.dll
LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[78]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[79]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[80]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[81]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[82]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\d3d9.dll
LoadedModule[84]=C:\Windows\system32\d3dx9_26.dll
LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[93]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[94]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[95]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[96]=C:\Windows\system32\DSOUND.dll
LoadedModule[97]=C:\Windows\system32\POWRPROF.dll
LoadedModule[98]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[99]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[100]=C:\Windows\system32\MSIMG32.dll
LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[102]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[103]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[104]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[105]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[106]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[107]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[108]=C:\Windows\system32\rsaenh.dll
LoadedModule[109]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[110]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[111]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[112]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[113]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[114]=C:\Windows\system32\wbemcomn.dll
LoadedModule[115]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[116]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[117]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[118]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[120]=C:\Windows\system32\dxgi.dll
LoadedModule[121]=C:\Windows\system32\d3d11.dll
LoadedModule[122]=C:\Windows\system32\d3d9.dll
LoadedModule[123]=C:\Windows\system32\d3d8thk.dll
LoadedModule[124]=C:\Windows\system32\nvd3dum.dll
LoadedModule[125]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[126]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[127]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[128]=C:\Windows\system32\d3d10_1.dll
LoadedModule[129]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[130]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[131]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[132]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[133]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[134]=C:\Windows\system32\winbrand.dll
LoadedModule[135]=C:\Windows\system32\nvapi.dll
LoadedModule[136]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[137]=C:\Windows\system32\WINSTA.dll
LoadedModule[138]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[139]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[140]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[141]=C:\Windows\SysWOW64\wer.dll
LoadedModule[142]=C:\Windows\System32\Wpc.dll
LoadedModule[143]=C:\Windows\System32\wevtapi.dll
LoadedModule[144]=C:\Windows\System32\msxml6.dll
LoadedModule[145]=C:\Windows\system32\SAMLIB.dll
LoadedModule[146]=C:\Windows\system32\netutils.dll
LoadedModule[147]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll
LoadedModule[148]=C:\Windows\system32\OLEACC.dll
LoadedModule[149]=C:\Windows\System32\MMDevApi.dll
LoadedModule[150]=C:\Windows\System32\PROPSYS.dll
LoadedModule[151]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[152]=C:\Windows\system32\RICHED20.DLL
LoadedModule[153]=C:\Windows\system32\HID.DLL
LoadedModule[154]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[155]=C:\Windows\system32\wdmaud.drv
LoadedModule[156]=C:\Windows\system32\ksuser.dll
LoadedModule[157]=C:\Windows\system32\AVRT.dll
LoadedModule[158]=C:\Windows\system32\msacm32.drv
LoadedModule[159]=C:\Windows\system32\midimap.dll
LoadedModule[160]=C:\Windows\system32\dinput.DLL
LoadedModule[161]=C:\Program Files (x86)\Avira\AntiVir Desktop\avsda.dll
LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[163]=C:\Windows\system32\WINNSI.DLL
LoadedModule[164]=C:\Windows\System32\wship6.dll
LoadedModule[165]=C:\Windows\System32\wshtcpip.dll
LoadedModule[166]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\iFly737NG.dll
LoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[168]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FsPassengers\bin\fspassengersx.dll
LoadedModule[169]=C:\Windows\system32\msadp32.acm
LoadedModule[170]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[171]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[172]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[173]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[174]=C:\Windows\system32\ntmarta.dll
LoadedModule[175]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[176]=C:\Windows\system32\Secur32.dll
LoadedModule[177]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[178]=C:\Windows\system32\msimtf.dll
LoadedModule[179]=C:\Windows\system32\msls31.dll
LoadedModule[180]=C:\Windows\system32\d2d1.dll
LoadedModule[181]=C:\Windows\system32\DWrite.dll
LoadedModule[182]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[183]=C:\Windows\system32\MLANG.dll
LoadedModule[184]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX.DLL
LoadedModule[185]=C:\Windows\system32\NETAPI32.dll
LoadedModule[186]=C:\Windows\system32\srvcli.dll
LoadedModule[187]=C:\Windows\system32\wkscli.dll
LoadedModule[188]=C:\Windows\system32\WSOCK32.dll
LoadedModule[189]=C:\Windows\system32\MSVCP100.dll
LoadedModule[190]=C:\Windows\system32\MSVCR100.dll
LoadedModule[191]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[192]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX_3.DLL
LoadedModule[193]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges\PMDG_737NGX_2.dll
LoadedModule[194]=C:\Windows\system32\snmpapi.dll
LoadedModule[195]=C:\Windows\system32\NLAapi.dll
LoadedModule[196]=C:\Windows\system32\napinsp.dll
LoadedModule[197]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[198]=C:\Windows\system32\DNSAPI.dll
LoadedModule[199]=C:\Windows\System32\winrnr.dll
LoadedModule[200]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[201]=C:\Windows\system32\rasadhlp.dll
LoadedModule[202]=C:\Windows\system32\asycfilt.dll
LoadedModule[203]=C:\Windows\system32\RICHED32.DLL
LoadedModule[204]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FsPassengers\bin\FsPassengersMini.DLL
Sec[0].Key=LCID
Sec[0].Value=1031
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Share this post


Link to post
Share on other sites

The faulting module this time was the g2d.dll module.

 

G2D.dll - The dll handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running FSX and the plain text words in the FSX Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items.

 

Again I would recommend you remove the Uiautomationcore.dll from your main fsx folder as it really isn't stopping any of your crashes.  You can move it to a temp directory and, if you ever need it again (or start having menu crashes), you can move it back to see if it fixes the problem.

 

You should make sure you have Microsoft Visual C++ 2008 installed.  I cannot believe it did not load as I believe the iFly737 used it during its installation.  I cannot be certain so, if it is installed (looking in your Add/Remove Programs), then forget about this suggestion.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I allready have C++2008 installed on new version, but you are right the plain text above is always opened, when I want to end flight with FsPassengers fsx crashes. I allready deledet the Uiautomationcore.dll but that doesn´t helped! I think its hopeless, why not install win vista that is made for fsx? Do you think that it will fix those problems? Or maybe WinXp?

Share this post


Link to post
Share on other sites

Vista came out shortly after the release of FSX but Vista did not last very long as it was buggy so Microsoft "upgraded" Vista with Windows 7.  I think is much more stable.  FSX barely ran on XP and the new Vista and high settings were almost out of the question.  Now we have more powerful systems (some of us) and we can crank up FSX a bit more but I don't think anyone can do so for any length of time without an occasional crash or other anomaly (such as a temporary freeze).  That's why I keep my settings down as low as I can get them and still have great graphics.

 

You indicate you deleted the Uiautomationcore.dll but it loaded in the last crash report as module 147.

 

You can uninstall FS Passengers and see if that fixes your crashes.  There have been several who have had crashes caused by FS Passengers and it is my understanding the developer no longer supports the product.

 

I would uninstall and reinstall FSX too and install it into a non-default directory such as C:\FSX.  This has helped many and it might help you too.  I have mine installed in the default as you do and have had no problems with FSX but I have turned a lot of the computer security garbage off of my system and that has helped.  There are a lot of people who post here that have had many crashes with FSX installed in the non-default directory so it obviously has not helped many.  But this is the recommendation of the computer "experts" so you have to listen to them once in a while.  Here's the best uninstall/reinstall guide that I have seen - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.  The only thing I would add to this guide is to run a registry cleaner like CCleaner before reinstalling.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Yes the deleting of Uiautomationcore.dll didnt helped, I also screwed the settings abit back not too high, but that also didn´t helped. Will try without FSpassengers and see what it helps. 
Do you have the old fsx uiautomationcore.dll? I never had problems with the standard dll. since I placed the vista version. ( Unfortunately I replaced it without backup) 

 

PS: My fsx is on C: folder but why is it not recommened? I only have FSX on this pc nothing else.

Share this post


Link to post
Share on other sites

 

 


My fsx is on C: folder but why is it not recommened? I only have FSX on this pc nothing else.

 

The reason is stated in the link I provided above about uninstalling/reinstalling FSX (in the reinstall section).  I do not recommend it but perhaps it will work for you as it is recommended by many who are much more knowledgeable about computer systems than me.

 

 

 


Do you have the old fsx uiautomationcore.dll? I never had problems with the standard dll. since I placed the vista version. ( Unfortunately I replaced it without backup)

 

Only a certain version of the Uiautomationcore.dll works in the FSX main folder.  The one from Windows 7 in your system folders should never be deleted or removed.

 

There is no "magic bullet" that will fix your problem.  You will have to conduct an investigation and try to find out why FSX crashed with the g2d.dll.  The only solution I know of for sure that will fix your crash is to reinstall Windows 7 and then reinstall FSX and your addons.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hi,

 

I found the problem now! I just recognize that FSpassengers is the problem ! Everytime when I land on airport and taxing to gate and then shut down the engines end press on Fspassengers " end flight" it crashes! Without fspassengers it doesn´t crashes. But now I dont know which of those Uiautomationcore.dll works, because the .16386 version makes no crashes possible on flight, but crashes by clicking on menu, and the .18000 version crashes on flight but not when clicking on menu.

 

So both of the dll´s aren´t a solution. PS: How about to but both dll´s to fsx directory ? maybe it will work?  

Share this post


Link to post
Share on other sites

There's no indications you are getting menu crashes.  In any case, only the Vista version can go into the main FSX folder (do not know what the Vista Version is but maybe someone else will come on and let you know.  You can also look in the AVSIM Software and Hardware Guide on how to set up your system for FSX under the Content Tab at the top of this forum).  Now, you have to click the menu about 20 times before the menu crashes start happening.  If you click it once and a crash occurs, then that is another problem.

 

Glad you got your problem fixed.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hey, I recenty found the error of d3d9.dll !!!

 

Its not Fspassengers! Its ENB SERIES! ENB Series mod has the d3d9.dll and makes cdt when clicking on end flight with fspassengers or clicking on menue bar.

I will try to press shift + F12 to disable enb mod when clicking on menue bar above, if that wont help I will completely delet the d3d9.dll from enb in fsx directory,

 

Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14
Name des fehlerhaften Moduls: d3d9.dll, Version: 1.0.0.1, Zeitstempel: 0x48751493
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00006d1c
ID des fehlerhaften Prozesses: 0xe50
Startzeit der fehlerhaften Anwendung: 0x01ce937b0ab0c77f
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\d3d9.dll
Berichtskennung: ab32681e-ff6f-11e2-8974-bc5ff460c978

Share this post


Link to post
Share on other sites

It works when I completely delete the 3 enb files from fsx folder, no Crashes anymore  B)

But without ENB FSX is poor on graphic  :(

Anyone know how to fix that???

Share this post


Link to post
Share on other sites

Okay.  I missed that loaded module 83 in your crash report (and I looked twice for it!).  Glad you found the problem.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hi Jim,

 

yes that was the problem. But now the mission is to fix the CTD with ENB MOD, I don´t know why the d3d9.dll crashes from enb?

Maybe I need to install directx 9 because enb is only compatible with 9er version, but I have the dx 11 on my win 7 64. Do I need to delete it and install dx 9 instead?

Share this post


Link to post
Share on other sites

 

 


Maybe I need to install directx 9 because enb is only compatible with 9er version, but I have the dx 11 on my win 7 64. Do I need to delete it and install dx 9 instead?

 

FSX is only capable of going to DX10 Preview.  You could have DX15 on your system and the highest level of DirectX you could get would be DX10 Preview.  Most people stay with DX9.  The ENB Mod is notorious for causing CTD's and anomalies (bad textures/graphics).  Most people have removed the D3D9.dll and the enb.ini from the main fsx folder.  A program similar to the ENB mod is SweetFX.  Everyone was enjoying that mod as it replaced the ENB mod but people started getting CTD's and unexplained bad graphics/textures.  Only a very few have gotten ENB or SweetFX to work properly.  Me?  I use a $10 program called Shade.  I heard it is not as good but I don't care.  It works and it does not cause crashes.  The ENB and SweetFX mods hack into one of the DirectX's files.  I think you are only asking for trouble when hacking into a system file so I would avoid it.  DX11 is installed on your system but is backwards compatible to I think DX8.  So, if you run any program that only uses DX9 or DX10, like FSX, you have all the system files there to do that.  Unfortunately FSX will not be able to use anything higher than DX10.  We would need a new engine for FSX and that's not going to happen.  There are a lot of games being released that are DX11 capable.  So, if you want to take full advantage of your video card, you would have to play one of those games.

 

Here is more information about DirectX http://en.wikipedia.org/wiki/DirectX .

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

 Thanks Jim,

 

allways appreciate your responses.

Well I think Im at the end of my power. I really tried everything, I putted the Dx9 dll into fsx folder also, and started flight with no CTD even by clicking 10 times on menue bar, I was so happy, but second flight crashed again.

I will try SweetFx, but Shade doesnt make bloom effects as enb unfortunately.

I dont want to give up, but I think theres nobody who can run ENB with fsx without crashing.

Share this post


Link to post
Share on other sites

Has anyone actually figured out WHY  uiautomationcore.dll is an issue.

 

If one's system does not have uiautomatiuoncore.dll installed  (ie  early XP),  then FSX runs fine without it.    So why is it called an needed  when it is present.

 

How does FSX even know anything about UIautomationcore.dll,  as I don't believe it even existed, when FSX was released. ?

 

So, we all just blindly put the Vista copy into the FSX folder,  but does anyone actually know the technical reason why it is needed  at all for FSX, and way the W7 version causes the crashes, while the Vista Version does not. ?

Share this post


Link to post
Share on other sites

It doesnt crashes uiautomationcore.dll is not the problem! Its enb mod but nobody knows it ;) Try simply delete your 3 enb files from your fsx folder and see theres no CTD anymore!

Share this post


Link to post
Share on other sites

I am not able to run sweet fx, I did set all settings and also locate the fsx directory, but in game I dont see any differences??

Share this post


Link to post
Share on other sites

Allright I finally fixed the ENB Crash-problem, 100 % !!! :P

 

I just tried the newest ENB File from J.V. (ORBX-CEO) " Purple Haze V 2 " and before ending flight with fspassengers I disable enb with Shift+12 and see there no crashes anymore :lol: !!!!!!!

I really gaved up before, there was no hope, but than I finally fixed it! @ all :try it, it should be fine now! I tried it 2 times now and it wont crash anyomore ;)

 

So the famous ENB Crashes are definately history from today on!

 

Thanks to me  B)

Share this post


Link to post
Share on other sites

Could someone please clarify the path for "Main FSX folder"? I am having a disagreement with a fellow simmer on this. Thanks.

Share this post


Link to post
Share on other sites

Main FSX folder is the folder where you did install fsx , search on windows for fsx and you´ll see the path! If you mean the FSX.config, its on App folder which is a hidden folder that has to be opened.

Share this post


Link to post
Share on other sites