January 19, 201511 yr I have been having the same problem (d3d11.dll crashes), and I came across this: http://steamcommunity.com/app/7670/discussions/0/828934913244739166 I have uninstalled windows update KB2670838 and doing a flight to check now, and so far it looks good. Before I would crash more or less at the same point every test flight, but now I have passed it a long time ago. I am also using SweetFX btw and still have it enabled. Maybe worth a shot? A bit of an advice, I've had a couple of d3d11.dll crashes and uninstalling that update screwed aircraft ground shadow. Running Steve's DX10 fixer, obviously I'm on DX10 preview and FSX. Regards SN737
August 9, 201510 yr Hi, Surprisingly I all of a sudden started to have the same problem. Yes, I'm running Steves DX10 fixer and preview. How did it happen. Recently I have updated my windows 7 AND new nvidia drivers. Problem appeared. I have removed the mentioned KB (which I had since January at least) and reverted to older nvidia driver - I was using driver from January 2015. Problem solved. However, I'm curious to know what might have caused it? KB which I deleted? But I was using it before and it was fine? Nvidia driver - latest one from 29 July could be it? Or my recent update of windows? Is there anyone who has some know how about it? Tom Link
August 9, 201510 yr I disagree with the previous so-called "fixes". Removal of the KB will remove your Windows browser, IE11 or IE12 and return your browser back to the default IE8. The KB will be reinstalled whenever you have another Windows Update (if you have the auto updates) unless you go to the Windows Update program and hide the update. I had the D3D11.dll crash in the past and removed KB2670838 (aka "The Evil Update"). The error does not just happen with FSX or DX10. It happens with many, many games. When I uninstalled it, IE11 or 12 (forget which) were uninstalled so I had no browser as Microsoft does not like anyone using an earlier browser, like IE8 or IE9. I recall reinstalling IE10 but Windows Update soon returned IE11 or 12 back to my system and, of course, KB2670838. I did some research on this KB for another member here a day or two ago and found that KB2670838 updates D3D11.dll and DXGI.dll, a component of SweetFX and the ENB Series (see http://www.avsim.com/topic/472823-got-a-very-weird-fsx-issue/. This could have caused the crashes if SweetFX were installed (I recommended SweetFX be uninstalled for one individual in this topic and that fixed the problem for him). Then someone posted and said it was KB2670838 that was causing the problem and not SweetFX. Very confusing, huh? I would like to know how KB2670838 can cause the crash and removal will get rid of it? I have KB2670838 back on my system since February 2015. I have had no d3d11.dll crashes. There are hundreds (maybe thousands) of active members here who have IE11 or 12 installed and that means KB2670838 is back on their system as it is a requirement (unless you hide the update as I mentioned above). Everyone would be coming here and reporting the CTD if that were the case and many members who have DX10 Preview and Steve's DX10 Fixer running are not reporting problems. It's SweetFX or the ENBSeries (a past or current installation) as d3d11.dll was hacked for the program. So, when the system d3d11 and dxgi files were updated by KB2670838 this probably caused some conflict with the files in the main FSX folder. There are many others out there who are saying the real problem is Windows security. UAC could have been turned on (and it should be disabled whenever you install FSX or an addon). It's purpose to to prevent hacked files from working. An anti-virus program running in the background could have done it too. You also need to run FSX or any program as the Administrator (not really required if you have FSX installed or your program outside of the default (C:\Program Files (x86) folder). I also recommend you right click on fsx.exe in the main FSX folder, select Properties, then go to the Compatibility tab. Make sure at the bottom that Run as Administrator is checked. There should be no other checkmarks on this page. You can check which version of the NVidia driver is installed on your computer by right clicking your desktop and selecting NVidia Control Panel. On the left column at the bottom, click on System Information and it will show you what version is installed. I have the latest (353.62 driver) that was released around the 31st of July. I doubt this fixed your problem but the driver probably uses the Windows System d3d11.dll and perhaps dgxi (and those were updated with KB2670838). So, if the Nvidia drivers are looking for a certain version in the Windows System folder, then maybe this causes the conflict. There are so many possibilities but removing KB2670838 is definitely not one of them. I think it is Windows Security as it only happens to a few and even those with SweetFX or the ENBSeries have no problems. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
August 10, 201510 yr I'm planning to install this KB back again and try a flight. I'm back with my old nvidia driver. If everything will run smooth, then it's nvidia driver to blame... I don't have any sweet fx or enb series installed. Never had. Only Fsx and dx10 fixer. Also worth of noticing, my problems only started once I did windows update and nvidia update. I had flights just before and no problems... Tom Link
August 10, 201510 yr So, I have done some tests today. I can say that the outcome is that I have both newest driver installed and that "faulty" KB. First I upgraded the driver. Test result = ok. Then I upgraded IE and as a result that KB was back. Test result = ok. So, if all is ok then what happened before. I was analyzing what I have done step by step, and I got it. I have updated nvidia driver thru automatic update. This time I have fully downloaded the driver, performed clean install, brought back nvidia inspector and all is working. Bottom line: looks like wrong steps during update of nvidia driver caused some issue. Tom Link
April 25, 20179 yr Hi I have a ctd ever time in Preview DirectX 10 mode, without it i can fly but the graphic is mess upp! I have some crash information bellow: Version=1 EventType=APPCRASH EventTime=131376114359756790 ReportType=2 Consent=1 UploadTime=131376114365397630 ReportStatus=268566528 ReportIdentifier=ddf162c4-a56b-4658-9983-371c36b7d759 IntegratorReportIdentifier=f581543a-7f61-4432-8eb3-8f516bdee194 Wow64Host=34404 Wow64Guest=332 NsAppName=fsx.exe AppSessionGuid=000046d8-0003-000c-12d3-9e74e0bdd201 TargetAppId=W:000637a153a159d5c2b9b8242acf4aaf242300000904!0000eb723381c97f481af15094e7ac42101d371bd1ba!fsx.exe TargetAppVer=2015//07//10:10:12:42!2ac31c!fsx.exe BootId=4294967295 ServiceSplit=3539031 TargetAsId=3504 Response.BucketId=5cbf2f689e761b0245ff1e70a0b4c9b4 Response.BucketTable=1 Response.LegacyBucketId=107492705382 Response.type=4 Sig[0].Name=Programnamn Sig[0].Value=fsx.exe Sig[1].Name=Programversion Sig[1].Value=10.0.62615.0 Sig[2].Name=Programtidsstämpel Sig[2].Value=559f9a9a Sig[3].Name=Namn på felmodul Sig[3].Value=API.DLL Sig[4].Name=Modulens version Sig[4].Value=10.0.62615.0 Sig[5].Name=Tidsstämpel för felmodul Sig[5].Value=559f9ab5 Sig[6].Name=Undantagskod Sig[6].Value=c0000005 Sig[7].Name=Undantagsförskjutning Sig[7].Value=00100043 DynamicSig[1].Name=OS-version DynamicSig[1].Value=10.0.15063.2.0.0.768.101 DynamicSig[2].Name=Språkvariant-ID DynamicSig[2].Value=1053 DynamicSig[22].Name=Ytterligare information 1 DynamicSig[22].Value=2beb DynamicSig[23].Name=Ytterligare information 2 DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46 DynamicSig[24].Name=Ytterligare information 3 DynamicSig[24].Value=4bee DynamicSig[25].Name=Ytterligare information 4 DynamicSig[25].Value=4bee0b688f92a58db71f79d49bc5b4cc UI[2]=F:\Steam\steamapps\common\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® har slutat att fungera UI[4]=Du kan söka online efter en lösning på problemet. UI[5]=Sök efter en lösning online och stäng programmet UI[6]=Sök senare efter en lösning online och stäng programmet UI[7]=Stäng programmet LoadedModule[0]=F:\Steam\steamapps\common\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\win32u.dll LoadedModule[9]=C:\WINDOWS\System32\GDI32.dll LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[11]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[12]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[13]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[14]=C:\WINDOWS\System32\cfgmgr32.dll LoadedModule[15]=C:\WINDOWS\System32\shcore.dll LoadedModule[16]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[17]=C:\WINDOWS\System32\SspiCli.dll LoadedModule[18]=C:\WINDOWS\System32\CRYPTBASE.dll LoadedModule[19]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[20]=C:\WINDOWS\System32\sechost.dll LoadedModule[21]=C:\WINDOWS\System32\combase.dll LoadedModule[22]=C:\WINDOWS\System32\windows.storage.dll LoadedModule[23]=C:\WINDOWS\System32\advapi32.dll LoadedModule[24]=C:\WINDOWS\System32\shlwapi.dll LoadedModule[25]=C:\WINDOWS\System32\kernel.appcore.dll LoadedModule[26]=C:\WINDOWS\System32\powrprof.dll LoadedModule[27]=C:\WINDOWS\System32\profapi.dll LoadedModule[28]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[29]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[32]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[33]=C:\WINDOWS\SYSTEM32\sfc.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\sfc_os.DLL LoadedModule[35]=C:\WINDOWS\AppPatch\AcSpecfc.DLL LoadedModule[36]=C:\WINDOWS\System32\ole32.dll LoadedModule[37]=C:\WINDOWS\System32\COMDLG32.dll LoadedModule[38]=C:\WINDOWS\System32\IMM32.dll LoadedModule[39]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[40]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.15063.0_none_8b4e86125c6fbfec\COMCTL32.dll LoadedModule[41]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[42]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[43]=C:\WINDOWS\SYSTEM32\DDRAW.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[45]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[46]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[47]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[48]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll LoadedModule[49]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[50]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCR80.dll LoadedModule[51]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCP80.dll LoadedModule[52]=F:\Steam\steamapps\common\FSX\steam_api.dll LoadedModule[53]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed\MFC80.DLL LoadedModule[54]=F:\Steam\steamapps\common\FSX\language.dll LoadedModule[55]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[56]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[57]=C:\WINDOWS\System32\imagehlp.dll LoadedModule[58]=C:\WINDOWS\System32\PSAPI.DLL LoadedModule[59]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL LoadedModule[60]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[62]=F:\Steam\Steam2.dll LoadedModule[63]=F:\Steam\DbgHelp.dll LoadedModule[64]=F:\Steam\CSERHelper.dll LoadedModule[65]=F:\Steam\gameoverlayrenderer.dll LoadedModule[66]=F:\Steam\steamapps\common\FSX\API.DLL LoadedModule[67]=F:\Steam\steamapps\common\FSX\acontain.dll LoadedModule[68]=F:\Steam\steamapps\common\FSX\ai_player.dll LoadedModule[69]=F:\Steam\steamapps\common\FSX\atc.dll LoadedModule[70]=F:\Steam\steamapps\common\FSX\controls.dll LoadedModule[71]=F:\Steam\steamapps\common\FSX\demo.dll LoadedModule[72]=F:\Steam\steamapps\common\FSX\facilities.dll LoadedModule[73]=F:\Steam\steamapps\common\FSX\g2d.dll LoadedModule[74]=F:\Steam\steamapps\common\FSX\gps.dll LoadedModule[75]=F:\Steam\steamapps\common\FSX\fsui.dll LoadedModule[76]=F:\Steam\steamapps\common\FSX\livingwater.dll LoadedModule[77]=F:\Steam\steamapps\common\FSX\multiplayer.dll LoadedModule[78]=F:\Steam\steamapps\common\FSX\panels.dll LoadedModule[79]=F:\Steam\steamapps\common\FSX\simprop.dll LoadedModule[80]=F:\Steam\steamapps\common\FSX\sound.dll LoadedModule[81]=F:\Steam\steamapps\common\FSX\symmap.dll LoadedModule[82]=F:\Steam\steamapps\common\FSX\simscheduler.dll LoadedModule[83]=F:\Steam\steamapps\common\FSX\fs-traffic.dll LoadedModule[84]=F:\Steam\steamapps\common\FSX\terrain.dll LoadedModule[85]=F:\Steam\steamapps\common\FSX\util.dll LoadedModule[86]=F:\Steam\steamapps\common\FSX\ui.dll LoadedModule[87]=F:\Steam\steamapps\common\FSX\visualfx.dll LoadedModule[88]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[89]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[90]=F:\Steam\steamapps\common\FSX\g3d.dll LoadedModule[91]=F:\Steam\steamapps\common\FSX\window.dll LoadedModule[92]=F:\Steam\steamapps\common\FSX\main.dll LoadedModule[93]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[94]=F:\Steam\steamapps\common\FSX\fe.dll LoadedModule[95]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[96]=F:\Steam\steamapps\common\FSX\weather.dll LoadedModule[97]=F:\Steam\steamapps\common\FSX\ablscpt.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[99]=F:\Steam\steamapps\common\FSX\sdkencryptedappticket.dll LoadedModule[100]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[102]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.15063.0_none_d802f55807fa1ec7\gdiplus.dll LoadedModule[103]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[104]=F:\Steam\steamapps\common\FSX\flight.dll LoadedModule[105]=F:\Steam\steamapps\common\FSX\sim1.dll LoadedModule[106]=F:\Steam\steamapps\common\FSX\xuipc.dll LoadedModule[107]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll LoadedModule[109]=C:\Program Files (x86)\Overwolf\0.103.223.0\OWExplorer.dll LoadedModule[110]=C:\Program Files (x86)\Common Files\Microsoft Shared\Ink\tiptsf.dll LoadedModule[111]=C:\Program Files (x86)\TeamViewer\tv_w32.dll LoadedModule[112]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[113]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[114]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[115]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[116]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[117]=C:\Windows\System32\urlmon.dll LoadedModule[118]=C:\Windows\System32\iertutil.dll LoadedModule[119]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[120]=C:\WINDOWS\SYSTEM32\d3d10.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\d3d10core.dll LoadedModule[123]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e69a53b8ddde469c\nvldumd.dll LoadedModule[124]=C:\WINDOWS\System32\WINTRUST.DLL LoadedModule[125]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e69a53b8ddde469c\nvd3dum.dll LoadedModule[126]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[127]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll LoadedModule[128]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[129]=C:\WINDOWS\system32\nvapi.dll LoadedModule[130]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[131]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_e69a53b8ddde469c\nvwgf2um.dll LoadedModule[132]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll LoadedModule[133]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[134]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\d3d10_1.dll LoadedModule[136]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll LoadedModule[137]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[138]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[139]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll LoadedModule[141]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll LoadedModule[142]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[143]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[144]=C:\WINDOWS\SYSTEM32\usermgrcli.dll LoadedModule[145]=C:\Windows\System32\gameux.dll LoadedModule[146]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.15063.0_none_583b8639f462029f\COMCTL32.dll LoadedModule[147]=F:\Steam\steamapps\common\FSX\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\AVRT.dll LoadedModule[153]=C:\Windows\System32\Windows.UI.dll LoadedModule[154]=C:\WINDOWS\SYSTEM32\RICHED20.DLL LoadedModule[155]=C:\WINDOWS\SYSTEM32\USP10.dll LoadedModule[156]=C:\WINDOWS\SYSTEM32\msls31.dll LoadedModule[157]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[158]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[159]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[160]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[161]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[162]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[163]=C:\WINDOWS\SYSTEM32\dinput.DLL LoadedModule[164]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[165]=C:\Windows\System32\deviceaccess.dll LoadedModule[166]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[167]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[168]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[169]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[170]=C:\Windows\System32\ieframe.dll LoadedModule[171]=C:\Windows\System32\NETAPI32.dll LoadedModule[172]=C:\Windows\System32\NETUTILS.DLL LoadedModule[173]=C:\Windows\System32\WKSCLI.DLL LoadedModule[174]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[175]=C:\WINDOWS\system32\dcomp.dll LoadedModule[176]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[177]=C:\WINDOWS\SYSTEM32\msIso.dll LoadedModule[178]=C:\Windows\System32\mshtml.dll LoadedModule[179]=C:\Windows\System32\srpapi.dll LoadedModule[180]=C:\WINDOWS\SYSTEM32\WLDP.DLL LoadedModule[181]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[182]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[183]=C:\WINDOWS\System32\NSI.dll LoadedModule[184]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[185]=C:\Windows\System32\rasadhlp.dll LoadedModule[186]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[187]=C:\Windows\System32\uiautomationcore.dll LoadedModule[188]=C:\WINDOWS\system32\msimtf.dll LoadedModule[189]=C:\Windows\System32\d2d1.dll LoadedModule[190]=C:\Windows\System32\DWrite.dll LoadedModule[191]=C:\WINDOWS\SYSTEM32\d3d10warp.dll LoadedModule[192]=C:\WINDOWS\SYSTEM32\MLANG.dll LoadedModule[193]=C:\Windows\System32\jscript9.dll LoadedModule[194]=C:\WINDOWS\System32\schannel.dll LoadedModule[195]=C:\WINDOWS\System32\DPAPI.DLL LoadedModule[196]=C:\WINDOWS\SYSTEM32\mskeyprotect.dll LoadedModule[197]=C:\WINDOWS\SYSTEM32\ncrypt.dll LoadedModule[198]=C:\WINDOWS\SYSTEM32\NTASN1.dll LoadedModule[199]=C:\Windows\System32\cryptnet.dll LoadedModule[200]=C:\WINDOWS\system32\ncryptsslp.dll LoadedModule[201]=C:\WINDOWS\System32\UIAnimation.dll LoadedModule[202]=C:\Windows\System32\XmlLite.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Slutade fungera ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=F:\Steam\steamapps\common\FSX\fsx.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=381DF571ED60C2BD257C942B863BDC44 MetadataHash=419017773 Any idea why the Preview DirectX 10 does not work? __________________________________________________________________ Computer: Windows 10, 64-bit, Intel i9 - 10850K, Asus Rog MAXIMUS XII HERO (WI-FI), 32GB RAM, Asus RTX3070Game control: Home Cockpit, Keyboard, Saitek Pro Flight X56 Rhino H.O.T.A.S.
April 25, 20179 yr Dovetail put the uiautomationcore.dll in your installation of FSX-SE (loaded module 147) and it was supposed to fix all crashes. The "holy grail" of all fixes for FSX! Yet people like you still suffer from crashes. Even Dovetail was duped! The API.dll is the module that allows FSX to startup. It indicates something is amiss with a module or setting and shutsdown your application. DX10 for FSX is broken and you should invest in the Steve's DX10 Fixer. I doubt the fact DX10 is enabled is the cause of your crashes. When you enable DX10 Preview, different modules from your system video card are loaded and, if the card was not installed properly, FSX will fail. I see you just got the GTX 1080 and loaded drivers for that card. I would reinstall the drivers using Administrative Privileges. Go to C:\Nvidia\Display Drivers and right click on the setup program for your latest drivers and select Run as Administrator. Page 29, AVSIM CTD Guide provides some other suggestions regarding this crash. The recommendation to follow the procedures on How to Fix Most FSX Crashes/Freezes is probably the best solution if my suggestions above did not work. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
April 25, 20179 yr Commercial Member Hi Jim, UIAutomationCore.dll is not a fix for all types of crash. This dll is responsible for the tooltip rectangle when the tooltip pops up in the 2D panels. Easy to test, you get the crash 100% of the time in DX10 and in a 2D panel with the tooltips enabled when hovering the mouse for a tooltip. The FSX code is not compatible with current versions of the dll so the compatible one is installed by steam for FSX:SE. Steve Waite: Engineer at codelegend.com
April 25, 20179 yr I am reinstalling the graphic driver now. I will reply when I have tested around :) __________________________________________________________________ Computer: Windows 10, 64-bit, Intel i9 - 10850K, Asus Rog MAXIMUS XII HERO (WI-FI), 32GB RAM, Asus RTX3070Game control: Home Cockpit, Keyboard, Saitek Pro Flight X56 Rhino H.O.T.A.S.
April 25, 20179 yr Hi I have found the faulty part :) The fault was: I have three monitors conected into the graphiccard. I find that it was not any good idea to have the monitor 2-3 mirror, the solution was having the three monitors as three monitors :) I have also reinstalled the driver but sould I buy Steve's DX10 Fixer anyway? __________________________________________________________________ Computer: Windows 10, 64-bit, Intel i9 - 10850K, Asus Rog MAXIMUS XII HERO (WI-FI), 32GB RAM, Asus RTX3070Game control: Home Cockpit, Keyboard, Saitek Pro Flight X56 Rhino H.O.T.A.S.
April 25, 20179 yr Commercial Member If you are going to stay with FSX a while then it's a good investment as it fixes most of the DX10 problems and DX10 is quite a bit better performing than DX9. A free version fixes only a few issues is available from AVSIM downloads. Steve Waite: Engineer at codelegend.com
April 25, 20179 yr See if the simulator runs in DX10 preview works first, ignoring any graphics glitches. Then, as Steve says, buy his products. Products? Yes, he has a cloud shadows add-on for the fixer! Yes, cloud shadows in FSX - wonderful stuff. Steve's active on AVSIM as you can see and tries to help. Mark Robinson Part-time Ferroequinologist Author of FLIGHT: A near-future short story (ebook available on amazon) I made the baby cry - A2A Simulations L-049 Constellation Sky Simulations MD-11 V2.2 Pilot. The best "lite" MD-11 money can buy (well, it's not freeware!)
April 26, 20179 yr We host his official support forum here at AVSIM. Glad a solution was found! The DX10 forum has info on setting up multiple monitors for DX10. 5 hours ago, SteveW said: Hi Jim, UIAutomationCore.dll is not a fix for all types of crash. This dll is responsible for the tooltip rectangle when the tooltip pops up in the 2D panels. Easy to test, you get the crash 100% of the time in DX10 and in a 2D panel with the tooltips enabled when hovering the mouse for a tooltip. The FSX code is not compatible with current versions of the dll so the compatible one is installed by steam for FSX:SE. Sorry Steve but I have a major problem with your explanation. The Internet clearly states someone found the "holy grail" for fixing CTD's for FSX and that was a version of the uiautomationcore.dll. The uiautomationcore.dll is part of the many different versions of the Microsoft.net packages. Microsoft.net packages are used to make sure a program runs properly. From my research, the two versions that many used for FSX, boxed version, were from earlier versions of Microsoft.net prior to the one originally installed with FSX in 2006 (Microsoft.net 1.1). I know there is a problem with tooltips in the boxed version but the Microsoft.net versions placed in the main folder of FSX, boxed, supposedly had only one CTD fix - if someone right clicked on the panel and clicked on the menu at least 19 times, it would stop FSX from crashing (which I still cannot replicate). I do not see how a uiautomationcore.dll coming from a completely different program than the FSX engine can fix FSX's tooltips. I think Dovetail simply installed a slightly modified placebo... It's strange Lockheed Martin P3D techs did not have to install this "placebo" in P3D (which is based on the FSX engine just like FSX-SE). Lockheed just fixed the code. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
April 26, 20179 yr Commercial Member Sorry to you Jim, my explanation can easily be verified to be correct in a few seconds hovering - no need to click them! Menu items are also rectangles. Steve Waite: Engineer at codelegend.com
April 26, 20179 yr Commercial Member ...Just tested this out and - it works - to try it do this: rename the UiAutomationCore.dll you placed in the FSX folder to UiAutomationCore.dll.OK Start a flight in DX10 choose a new time of day in the Alt menu, go to 2D panels view and start hovering the mouse to invoke the tooltip. Within a few minutes FSX may CTD. Or hover around a few mins, then try changing the time and voila! CTD - tadaa. (Win10-64, FSX+A, no 386 UiAutomationCore.dll in FSX folder) Steve Waite: Engineer at codelegend.com
Archived
This topic is now archived and is closed to further replies.