September 15, 20187 yr Hi there! My Flight Simulator (Steam Edtition) crashes every time during a flight. Im not able to complete my flights. The only Addons I use are: Rikooo A330 and A340 Package (No Graphic Addons or something else). I hope that someone can help me. Thanks in Advance! Here is the AppCrashView log file: Version=1 EventType=APPCRASH EventTime=131809058526288754 ReportType=2 Consent=1 UploadTime=131809058529399995 ReportStatus=268435456 ReportIdentifier=c8728ef7-6c9b-4dc7-9236-6e492d05461a IntegratorReportIdentifier=cca26c96-3b82-4fd5-8f7f-1c94c31af82d Wow64Host=34404 Wow64Guest=332 NsAppName=fsx.exe OriginalFilename=fsx.exe AppSessionGuid=0000283c-0007-000d-1d09-55459f47d401 TargetAppId=W:000637a153a159d5c2b9b8242acf4aaf242300000904!0000eb723381c97f481af15094e7ac42101d371bd1ba!fsx.exe TargetAppVer=2015//07//10:10:12:42!2ac31c!fsx.exe BootId=4294967295 ServiceSplit=7 TargetAsId=3405 IsFatal=1 Response.BucketId=9d71c310b8e30060edbfdcc0e6083ef3 Response.BucketTable=1 Response.LegacyBucketId=2143674668702777075 Response.type=4 Sig[0].Name=Anwendungsname Sig[0].Value=fsx.exe Sig[1].Name=Anwendungsversion Sig[1].Value=10.0.62615.0 Sig[2].Name=Anwendungszeitstempel Sig[2].Value=559f9a9a Sig[3].Name=Fehlermodulname Sig[3].Value=MSCTF.dll Sig[4].Name=Fehlermodulversion Sig[4].Value=10.0.17134.191 Sig[5].Name=Fehlermodulzeitstempel Sig[5].Value=fcde487c Sig[6].Name=Ausnahmecode Sig[6].Value=c0000005 Sig[7].Name=Ausnahmeoffset Sig[7].Value=000d62c8 DynamicSig[1].Name=Betriebsystemversion DynamicSig[1].Value=10.0.17134.2.0.0.768.101 DynamicSig[2].Name=Gebietsschema-ID DynamicSig[2].Value=1031 DynamicSig[22].Name=Zusatzinformation 1 DynamicSig[22].Value=0470 DynamicSig[23].Name=Zusatzinformation 2 DynamicSig[23].Value=0470a16fe6bc665dcd61ff5725c4b85d DynamicSig[24].Name=Zusatzinformation 3 DynamicSig[24].Value=f10e DynamicSig[25].Name=Zusatzinformation 4 DynamicSig[25].Value=f10ee3daae135405a05bfbd054037302 UI[2]=D:\Programme (D=)\steamapps\common\FSX\fsx.exe LoadedModule[0]=D:\Programme (D=)\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\SYSTEM32\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\profapi.dll LoadedModule[27]=C:\WINDOWS\System32\powrprof.dll LoadedModule[28]=C:\WINDOWS\System32\FLTLIB.DLL LoadedModule[29]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[30]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[32]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[33]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL LoadedModule[35]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\sfc.dll LoadedModule[37]=C:\WINDOWS\SYSTEM32\sfc_os.DLL LoadedModule[38]=C:\WINDOWS\SYSTEM32\AcSpecfc.DLL LoadedModule[39]=C:\WINDOWS\System32\ole32.dll LoadedModule[40]=C:\WINDOWS\System32\COMDLG32.dll LoadedModule[41]=C:\WINDOWS\System32\IMM32.dll LoadedModule[42]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[43]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.17134.228_none_40fd37ce451407b3\COMCTL32.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[45]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[46]=C:\WINDOWS\SYSTEM32\DDRAW.dll LoadedModule[47]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[48]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[49]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[50]=C:\WINDOWS\SYSTEM32\ColorAdapterClient.dll LoadedModule[51]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[52]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[53]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll LoadedModule[54]=C:\WINDOWS\SYSTEM32\SortWindows61.dll LoadedModule[55]=C:\WINDOWS\system32\uxtheme.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.9445_none_d08c58b4442ba54f\MSVCR80.dll LoadedModule[58]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9445_none_d08c58b4442ba54f\MSVCP80.dll LoadedModule[59]=D:\Programme (D=)\steamapps\common\FSX\steam_api.dll LoadedModule[60]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80DEU.DLL LoadedModule[61]=D:\Programme (D=)\gameoverlayrenderer.dll LoadedModule[62]=C:\WINDOWS\System32\PSAPI.DLL LoadedModule[63]=D:\Programme (D=)\steamapps\common\FSX\language.dll LoadedModule[64]=D:\Programme (D=)\steamclient.dll LoadedModule[65]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[66]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[67]=C:\WINDOWS\System32\imagehlp.dll LoadedModule[68]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[69]=D:\Programme (D=)\tier0_s.dll LoadedModule[70]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[71]=D:\Programme (D=)\vstdlib_s.dll LoadedModule[72]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[73]=D:\Programme (D=)\steam.dll LoadedModule[74]=D:\Programme (D=)\Steam2.dll LoadedModule[75]=D:\Programme (D=)\DbgHelp.dll LoadedModule[76]=D:\Programme (D=)\CSERHelper.dll LoadedModule[77]=D:\Programme (D=)\steamapps\common\FSX\API.DLL LoadedModule[78]=D:\Programme (D=)\steamapps\common\FSX\ablscpt.dll LoadedModule[79]=D:\Programme (D=)\steamapps\common\FSX\acontain.dll LoadedModule[80]=D:\Programme (D=)\steamapps\common\FSX\ai_player.dll LoadedModule[81]=D:\Programme (D=)\steamapps\common\FSX\atc.dll LoadedModule[82]=D:\Programme (D=)\steamapps\common\FSX\demo.dll LoadedModule[83]=D:\Programme (D=)\steamapps\common\FSX\controls.dll LoadedModule[84]=D:\Programme (D=)\steamapps\common\FSX\facilities.dll LoadedModule[85]=D:\Programme (D=)\steamapps\common\FSX\fe.dll LoadedModule[86]=D:\Programme (D=)\steamapps\common\FSX\flight.dll LoadedModule[87]=D:\Programme (D=)\steamapps\common\FSX\g2d.dll LoadedModule[88]=D:\Programme (D=)\steamapps\common\FSX\gps.dll LoadedModule[89]=D:\Programme (D=)\steamapps\common\FSX\g3d.dll LoadedModule[90]=D:\Programme (D=)\steamapps\common\FSX\fsui.dll LoadedModule[91]=D:\Programme (D=)\steamapps\common\FSX\livingwater.dll LoadedModule[92]=D:\Programme (D=)\steamapps\common\FSX\multiplayer.dll LoadedModule[93]=D:\Programme (D=)\steamapps\common\FSX\main.dll LoadedModule[94]=D:\Programme (D=)\steamapps\common\FSX\panels.dll LoadedModule[95]=D:\Programme (D=)\steamapps\common\FSX\sim1.dll LoadedModule[96]=D:\Programme (D=)\steamapps\common\FSX\simprop.dll LoadedModule[97]=D:\Programme (D=)\steamapps\common\FSX\simscheduler.dll LoadedModule[98]=D:\Programme (D=)\steamapps\common\FSX\sound.dll LoadedModule[99]=D:\Programme (D=)\steamapps\common\FSX\fs-traffic.dll LoadedModule[100]=D:\Programme (D=)\steamapps\common\FSX\symmap.dll LoadedModule[101]=D:\Programme (D=)\steamapps\common\FSX\terrain.dll LoadedModule[102]=D:\Programme (D=)\steamapps\common\FSX\util.dll LoadedModule[103]=D:\Programme (D=)\steamapps\common\FSX\ui.dll LoadedModule[104]=D:\Programme (D=)\steamapps\common\FSX\visualfx.dll LoadedModule[105]=D:\Programme (D=)\steamapps\common\FSX\weather.dll LoadedModule[106]=D:\Programme (D=)\steamapps\common\FSX\window.dll LoadedModule[107]=D:\Programme (D=)\steamapps\common\FSX\xuipc.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[109]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[110]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.17134.228_none_73ddc3559f715468\gdiplus.dll LoadedModule[111]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[112]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll LoadedModule[113]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll LoadedModule[114]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[115]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[116]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[117]=D:\Programme (D=)\steamapps\common\FSX\sdkencryptedappticket.dll LoadedModule[118]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[119]=C:\WINDOWS\SYSTEM32\inputhost.dll LoadedModule[120]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll LoadedModule[123]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[124]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[125]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[126]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[127]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[128]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[129]=C:\Windows\System32\urlmon.dll LoadedModule[130]=C:\Windows\System32\iertutil.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[132]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvldumd.dll LoadedModule[133]=C:\WINDOWS\System32\WINTRUST.DLL LoadedModule[134]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvd3dum.dll LoadedModule[135]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f5be1f8d25335236\nvwgf2um.dll LoadedModule[136]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[137]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll LoadedModule[138]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[139]=C:\WINDOWS\SYSTEM32\d3d10_1.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll LoadedModule[141]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[142]=C:\WINDOWS\SYSTEM32\gpapi.dll LoadedModule[143]=C:\WINDOWS\SYSTEM32\cryptnet.dll LoadedModule[144]=C:\Windows\System32\dxdiagn.dll LoadedModule[145]=C:\Windows\System32\d3d12.dll LoadedModule[146]=C:\Windows\System32\msvcp110_win.dll LoadedModule[147]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[148]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[149]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[150]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[151]=C:\WINDOWS\system32\winbrand.dll LoadedModule[152]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[153]=C:\WINDOWS\SYSTEM32\DEVRTL.dll LoadedModule[154]=C:\WINDOWS\SYSTEM32\SPINF.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\drvstore.dll LoadedModule[156]=C:\WINDOWS\System32\NSI.dll LoadedModule[157]=C:\Windows\System32\D3DSCache.dll LoadedModule[158]=C:\WINDOWS\SYSTEM32\twinapi.appcore.dll LoadedModule[159]=C:\Windows\System32\RMCLIENT.dll LoadedModule[160]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[161]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[162]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll LoadedModule[163]=C:\Windows\System32\gameux.dll LoadedModule[164]=C:\WINDOWS\SYSTEM32\uiautomationcore.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[166]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[167]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[168]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[169]=C:\Windows\System32\Windows.UI.dll LoadedModule[170]=C:\WINDOWS\SYSTEM32\RICHED20.DLL LoadedModule[171]=C:\WINDOWS\SYSTEM32\USP10.dll LoadedModule[172]=C:\WINDOWS\SYSTEM32\msls31.dll LoadedModule[173]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[174]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[175]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[176]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[177]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[178]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[179]=C:\WINDOWS\SYSTEM32\dinput.DLL LoadedModule[180]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[181]=C:\Windows\System32\ieframe.dll LoadedModule[182]=C:\Windows\System32\NETAPI32.dll LoadedModule[183]=C:\Windows\System32\WKSCLI.DLL LoadedModule[184]=C:\Windows\System32\NETUTILS.DLL LoadedModule[185]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.228_none_42f2d07044deda9a\comctl32.dll LoadedModule[186]=C:\WINDOWS\SYSTEM32\msIso.dll LoadedModule[187]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[188]=C:\WINDOWS\system32\dcomp.dll LoadedModule[189]=C:\Windows\System32\mshtml.dll LoadedModule[190]=C:\Windows\System32\srpapi.dll LoadedModule[191]=C:\WINDOWS\SYSTEM32\WLDP.DLL LoadedModule[192]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\winhttp.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[195]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[196]=C:\Windows\System32\rasadhlp.dll LoadedModule[197]=C:\WINDOWS\system32\msimtf.dll LoadedModule[198]=C:\Windows\System32\d2d1.dll LoadedModule[199]=C:\Windows\System32\DWrite.dll LoadedModule[200]=C:\WINDOWS\SYSTEM32\d3d10warp.dll LoadedModule[201]=C:\WINDOWS\SYSTEM32\MLANG.dll LoadedModule[202]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[203]=C:\WINDOWS\System32\schannel.dll LoadedModule[204]=C:\WINDOWS\SYSTEM32\mskeyprotect.dll LoadedModule[205]=C:\WINDOWS\SYSTEM32\ncrypt.dll LoadedModule[206]=C:\WINDOWS\SYSTEM32\NTASN1.dll LoadedModule[207]=C:\WINDOWS\System32\DPAPI.DLL LoadedModule[208]=C:\WINDOWS\system32\ncryptsslp.dll LoadedModule[209]=C:\Windows\System32\jscript9.dll LoadedModule[210]=D:\Programme (D=)\crashhandler.dll LoadedModule[211]=C:\WINDOWS\SYSTEM32\msadp32.acm LoadedModule[212]=D:\Programme (D=)\steamapps\common\FSX\gauges\CALLOUT_SOUND.dll LoadedModule[213]=C:\WINDOWS\SYSTEM32\d3dx9_31.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=17134 OsInfo[3].Key=ubr OsInfo[3].Value=228 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1031 OsInfo[7].Key=geoid OsInfo[7].Value=94 OsInfo[8].Key=sku OsInfo[8].Value=101 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=768 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=140270 OsInfo[15].Key=osinsty OsInfo[15].Value=3 OsInfo[16].Key=iever OsInfo[16].Value=11.228.17134.0-11.0.80 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=8150 OsInfo[19].Key=svolsz OsInfo[19].Value=222 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=180410 OsInfo[22].Key=bldtm OsInfo[22].Value=1804 OsInfo[23].Key=bldbrch OsInfo[23].Value=rs4_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.17134.228.amd64fre.rs4_release.180410-1804 OsInfo[30].Key=buildflightid OsInfo[30].Value=7B3F085B-AF94-4576-9A9C-9A5E41CD1FC9.1 OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[33].Key=expid OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 FriendlyEventName=Nicht mehr funktionsfähig ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=D:\Programme (D=)\steamapps\common\FSX\fsx.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=381DF571ED60C2BD257C942B863BDC44 MetadataHash=-16676852
September 15, 20187 yr 2 hours ago, DeniDan said: Sig[3].Name=Fehlermodulname Sig[3].Value=MSCTF.dll Sig[4].Name=Fehlermodulversion Sig[4].Value=10.0.17134.191 The crash was caused by a Microsoft system file - MSCTF.dll. Some additional information regarding this module can be found at https://www.file.net/process/msctf.dll.html. If the module cannot be found is the error message then you should scan your system to look for missing/corrupted Windows files. If found, Windows will replace them. See page 14, AVSIM CTD Guide or go to the following link - https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system. I really do not know how to fix this problem and would recommend you search for mscft.dll using Google or Bing and see what others around the world did to fix this issue. 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
September 16, 20187 yr Commercial Member The error log says: LoadedModule[124]=C:\WINDOWS\System32\MSCTF.dll So it's not a missing file. What the message means is that MSCTF.dll or any dlls loaded into FSX that are 'hung' will CTD the sim. I don't expect youhave a problem in MSCTF.dll but it could be affected by malware in some way. Instead I expect some other reason the CTD happens, maybe file or folder can't be accessed, we have to do a process of elimination first. In the steam menu refresh the installation and try again, there's an option in the submenu that checks all the files. Next try the same thing, but disable the addons and refresh the files. Next you could try to eliminate any dlls you have attached, To eliminate dlls - go to: "C:\Users\<you>\AppData\Roaming\Microsoft\FSX-SE" (may not have "-SE" on the end). find the file dll.xml and rename it. Don't delete it, just add '.org' or something on the end to remove later. With dll.xml renamed try the sim again, and try with a stock plane. You may also check the folder: "C:\ProgramData\Microsoft\FSX-SE" Do the same with files in that folder. After tests remember to name back any files you changed. With no idea what's going on in your system, I would need to know at what stage you get the error and with what plane if any in particular, and when did the error start to happen, is it crashing since installing or did it start later. After that we would look at your installation in more detail. Edited September 16, 20187 yr by SteveW Steve Waite: Engineer at codelegend.com
September 16, 20187 yr Author First time many thanks to you both for the quick help! I'll check the links you sent me and tell you later if it worked. To SteveW: Unfortunately, the game crashed without addons and was deleted several times (over 5 times), including Appdata files. Everything really. I have also checked for errors (via Steam). Unfortunately, it still crashes. As I said, I will now check the things you have sent me and tell you later! Great thanks!
September 16, 20187 yr Author Hello! I have tested my Windwos system by mistake over the cmd. It has been confirmed that corrupted files have been replaced. Then I started FSX again. This time it crashed again! 😞 In the directory: "C: \ Users \ <you> \ AppData \ Roaming \ Microsoft \ FSX-SE" I have no dll.xml Only in the Steam directory there are five pieces. To the crash: My game crashes after the charging icon appears for 2 seconds. Then I'm on the desktop. Since the installation is like that. Best regards.
September 16, 20187 yr 4 hours ago, DeniDan said: This time it crashed again! 😞 In the directory: "C: \ Users \ <you> \ AppData \ Roaming \ Microsoft \ FSX-SE" This is the folder where the FSX.cfg, dll.xml (if appropriate), exe.xml (if appropriate) reside. When you get a crash, FSX will create a dxdiag file which checks all of your directx components. Open up this file and review it and see if it shows any errors with your display or sound. Did you delete or rename the fsx.cfg? This fixes crashes for many as it could have been corrupted or you added a tweak that is not compatible. The file will be rebuilt. There are files in the appdata/roaming/microsoft/fsx folder that cannot be deleted as they will not be rebuilt unless you do a repair of FSX-SE. You should also rename the logbook.bin to logbook.off in the Documents/Microsoft/Flight Simulation X folder. It sometimes gets corrupted. It will be rebuilt. If it fixes the problem, you can keep the new one or repair the old one as it contains a record of every flight you have done. If you have multiple monitors, FSX will crash at startup if you shutdown FSX in full screen mode. It will throw a certain error though so I doubt this happened but mentioning it just in case. 4 hours ago, DeniDan said: My game crashes after the charging icon appears for 2 seconds. If you are using a laptop, you need to have sufficient power to run your laptop. You need to make sure it is plugged in or fully charged. It is good that a scan of your system found corrupted Windows files and replaced them. It may not have caused your issues with FSX but at least it repaired some system files that may be needed for other software you have installed. 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
September 16, 20187 yr Commercial Member Seems to be a regular install of SE and an unusual error. Try without antivrus/internet running. Disengage any controllers and disable them. Make sure all drivers are up to date. Maybe try changing installed language/date/time/numbers to US. Steve Waite: Engineer at codelegend.com
September 16, 20187 yr @SteveW - I was getting strange CTD's referencing Windows files and many BSOD's too last month. They were random meaning I could fly P3DV4 a couple of flights without an error and the next flight would have a BSOD or CTD somewhere along the flight route. I built my current system and I went (for the 2nd time) to check the CPU and look for bent MB pins. I could see none with the naked eye. I pulled out a magnifying glass and still could not see any bent pins but next to a couple of pins I saw a bit of thermal paste. I used a needle and gingerly removed the gunk around the pins. Put the system back together and no more CTD's or BSOD's. The system is running better than it ever has! 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
September 16, 20187 yr Commercial Member @Jim, I'm really pleased to hear it's worked out - amazing you found that. With CTDs mostly just errors in setup or code but the BSOD made you think the hardware was having problems. Good job! Steve Waite: Engineer at codelegend.com
September 16, 20187 yr 1 hour ago, SteveW said: With CTDs mostly just errors in setup or code but the BSOD made you think the hardware was having problems. I'm sitting here with egg on my face as I told you above my BSOD's went away after removing some thermal paste that had dropped on the CPU pins. When I did that, I also removed two memory modules and decided to just fill two memory slots. This afternoon, I decided to replace those two memory modules so all four slots would be filled. After doing that, I set up a flight from KLAX to KSFO in the PMDG 777. Soon after takeoff, I got hit with a BSOD just like in the past. So it was most likely one or both of the memory modules that caused my BSOD's/CTD's with faulting modules leading to Window system files. So this could be the OP's issue too. Perhaps he has bad memory modules. I took the two memory modules back out and started another flight from KLAX to KSFO in the 777 and it completed without any problems. When I get some time, I'll have to figure out which module was bad. It is also possible my ASUS Maximus X Hero MB does not accept all four modules. 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
September 16, 20187 yr Commercial Member Aha! Two changes at once caught you out that time. Even so led you to find out what it was. Since it's got two modules in place working fine you can swap one for one of the other pair and see if it holds up do it with the other from the 'faulty pair'. I'd clearly label them before mixing them up. Had a similar issue with an older system and glad it had four modules since it's only got two now but works fine. Steve Waite: Engineer at codelegend.com
September 17, 20187 yr Author Hello, I have now deleted the fsx.cfg and changed the logbook.bin to a off data. I play Fsx on my computer with one monitor. Unfortunately that still does not fix my problem. With my antivirus I have already approved everything for the fsx.exe. I also played without internet.
September 17, 20187 yr You are using FSX-SE without any add-ons other than the Rikooo A330 and A340 Package (both of which I have verified are compatible with FSX-SE). You have rebuilt your fsx.cfg. You have no dll.xml or exe.xml. FSX out of the box is impossible to crash. It is when you add a scenery or aircraft to the fsx application when you start running into problems and you start pushing up your settings to the max. Some add-ons take up a lot of resources and, in FSX-SE, FSX will crash when it runs low on Virtual Address Space (VAS). If your computer is not very powerful (you did not include any system specs), there can also be a lot of resources placed on the video card, memory modules, and CPU. I do not have the freeware packages you have installed but they must be placing more resources on your computer than normal. What happens if you put your fsx setting to the default (just go into your settings and look for "reset to default")? All you are doing is testing to see if it is your settings that might be causing these crashes. You should do this for the display driver settings too. Yes, FSX will not look very good! I would save your current fsx.cfg first, then if you still get crashes, you can go back to your original settings. If this does not find the cause, then you will have to uninstall the two aircraft packages and make sure they are not the cause of your crashes. I'm wondering what the following modules are used for - LoadedModule[210]=D:\Programme (D=)\crashhandler.dll LoadedModule[212]=D:\Programme (D=)\steamapps\common\FSX\gauges\CALLOUT_SOUND.dll 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
September 19, 20187 yr Author It says: What is Crashhandler.dll.old? -> Crashhandler.dll.old is a type of OLD file associated with Steam Crash Handler Library developed by Valve Corporation for the Windows Operating System. The latest known version of Crashhandler.dll.old is 01.71.93.25, which was produced for Windows. This OLD file carries a popularity rating of 1 stars and a security rating of "UNKNOWN". I forgot to say that I bought and installed the "HD Airport" package on Steam. However, I do not think that the bug is in this addon. To my PC: -Windows 10 -16 Gb Ram - Nvidia Geforce GTX 960 (drivers are up to date) -intel core i7 6700k -4x4.00GHz -64Bit My graphics settings are set to ULTRA because I think my PC is capable of withstanding this. With other games (Xplane 11) I do not have this problem. I will try your advice. Thank you! Best regards
Archived
This topic is now archived and is closed to further replies.