December 2, 201411 yr Author OK. Did all those steps from the manual. Looks like it is a different reason now. Same errors past 3 crashes. It only happens when I push button for FS2crew to command to Start Engine. I cannot figure out if there is a conflict. No double keys assignments Thx again. Log Name: Application Source: Application Error Date: 12/2/2014 9:26:24 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Owner-PC Description: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x7553cb49 Faulting process id: 0x1260 Faulting application start time: 0x01d00e4183c4e56b Faulting application path: F:\FSX\fsx.exe Faulting module path: unknown Report Id: 92c4c11c-7a37-11e4-9e6f-e03f498675dd Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-12-02T15:26:24.000000000Z" /> <EventRecordID>13555</EventRecordID> <Channel>Application</Channel> <Computer>Owner-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>7553cb49</Data> <Data>1260</Data> <Data>01d00e4183c4e56b</Data> <Data>F:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>92c4c11c-7a37-11e4-9e6f-e03f498675dd</Data> </EventData> </Event> --------------------- Version=1 EventType=BEX EventTime=130620075842465505 ReportType=2 Consent=1 UploadTime=130620075844415616 ReportIdentifier=92c4c11d-7a37-11e4-9e6f-e03f498675dd IntegratorReportIdentifier=92c4c11c-7a37-11e4-9e6f-e03f498675dd WOW64=1 Response.BucketId=3431695840 Response.BucketTable=5 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=StackHash_e16f Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Offset Sig[6].Value=7553cb49 Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Data Sig[8].Value=00000008 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=e16f DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=e16f26ed920b77e80b57d6228a772083 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=c050 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=c050ce9318e2fdcce8b19a1e937d6310 UI[2]=F:\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]=F:\FSX\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.3079_none_cbf38852470c569f\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\XmlLite.dll LoadedModule[37]=C:\Windows\syswow64\WININET.dll LoadedModule[38]=C:\Windows\syswow64\iertutil.dll LoadedModule[39]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[40]=C:\Windows\syswow64\MSASN1.dll LoadedModule[41]=C:\Windows\system32\MPR.dll LoadedModule[42]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[43]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[44]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[46]=C:\Windows\system32\mscms.dll LoadedModule[47]=C:\Windows\system32\DDRAW.dll LoadedModule[48]=C:\Windows\system32\DCIMAN32.dll LoadedModule[49]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[50]=C:\Windows\syswow64\IMM32.dll LoadedModule[51]=C:\Windows\syswow64\MSCTF.dll LoadedModule[52]=C:\Windows\syswow64\WS2_32.dll LoadedModule[53]=C:\Windows\syswow64\NSI.dll LoadedModule[54]=C:\Windows\system32\msi.dll LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.3079_none_03cbcb30205b7fe3\MFC80ENU.DLL LoadedModule[56]=F:\FSX\language.dll LoadedModule[57]=F:\FSX\API.DLL LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[59]=F:\FSX\ablscpt.dll LoadedModule[60]=F:\FSX\flight.dll LoadedModule[61]=F:\FSX\ai_player.dll LoadedModule[62]=F:\FSX\acontain.dll LoadedModule[63]=F:\FSX\controls.dll LoadedModule[64]=C:\Windows\system32\DINPUT8.dll LoadedModule[65]=F:\FSX\fsui.dll LoadedModule[66]=F:\FSX\atc.dll LoadedModule[67]=F:\FSX\facilities.dll LoadedModule[68]=F:\FSX\demo.dll LoadedModule[69]=F:\FSX\main.dll LoadedModule[70]=F:\FSX\fe.dll LoadedModule[71]=F:\FSX\util.dll LoadedModule[72]=F:\FSX\simprop.dll LoadedModule[73]=F:\FSX\g2d.dll LoadedModule[74]=C:\Windows\system32\d3dx9_34.dll LoadedModule[75]=F:\FSX\d3dx10_34.dll LoadedModule[76]=C:\Windows\system32\MSVCR100.dll LoadedModule[77]=F:\FSX\reald3dx10_34.DLL LoadedModule[78]=F:\FSX\dx10fixerlib.DLL LoadedModule[79]=F:\FSX\d3d9.dll LoadedModule[80]=C:\Windows\system32\d3dx9_43.dll LoadedModule[81]=F:\FSX\g3d.dll LoadedModule[82]=F:\FSX\panels.dll LoadedModule[83]=F:\FSX\multiplayer.dll LoadedModule[84]=F:\FSX\ui.dll LoadedModule[85]=F:\FSX\sound.dll LoadedModule[86]=F:\FSX\sim1.dll LoadedModule[87]=F:\FSX\simscheduler.dll LoadedModule[88]=F:\FSX\visualfx.dll LoadedModule[89]=F:\FSX\window.dll LoadedModule[90]=F:\FSX\terrain.dll LoadedModule[91]=F:\FSX\weather.dll LoadedModule[92]=C:\Windows\system32\DSOUND.dll LoadedModule[93]=C:\Windows\system32\POWRPROF.dll LoadedModule[94]=F:\FSX\symmap.dll LoadedModule[95]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll LoadedModule[96]=C:\Windows\system32\MSIMG32.dll LoadedModule[97]=F:\FSX\xuipc.dll LoadedModule[98]=F:\FSX\livingwater.dll LoadedModule[99]=F:\FSX\fs-traffic.dll LoadedModule[100]=F:\FSX\gps.dll LoadedModule[101]=C:\Windows\system32\MSWSOCK.dll LoadedModule[102]=C:\Windows\system32\SHFOLDER.dll LoadedModule[103]=C:\Windows\system32\d3d9.dll LoadedModule[104]=C:\Windows\system32\d3d8thk.dll LoadedModule[105]=C:\Program Files\NVIDIA Corporation\Display\NvSmartMax.dll LoadedModule[106]=C:\Windows\system32\WTSAPI32.dll LoadedModule[107]=C:\Windows\system32\ntmarta.dll LoadedModule[108]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[109]=C:\Windows\system32\CRYPTSP.dll LoadedModule[110]=C:\Windows\system32\rsaenh.dll LoadedModule[111]=C:\Windows\syswow64\WINTRUST.DLL LoadedModule[112]=C:\Windows\syswow64\imagehlp.dll LoadedModule[113]=C:\Windows\system32\ncrypt.dll LoadedModule[114]=C:\Windows\system32\bcrypt.dll LoadedModule[115]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[116]=C:\Windows\system32\GPAPI.dll LoadedModule[117]=C:\Windows\system32\cryptnet.dll LoadedModule[118]=C:\Windows\system32\SensApi.dll LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[120]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[121]=C:\Windows\System32\msxml3.dll LoadedModule[122]=C:\Windows\system32\credssp.dll LoadedModule[123]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[124]=C:\Windows\system32\WINNSI.DLL LoadedModule[125]=C:\Windows\system32\dhcpcsvc6.DLL LoadedModule[126]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[127]=C:\Windows\system32\DNSAPI.dll LoadedModule[128]=C:\Windows\system32\rasadhlp.dll LoadedModule[129]=C:\Windows\SysWOW64\schannel.dll LoadedModule[130]=C:\Windows\system32\secur32.dll LoadedModule[131]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[132]=C:\Windows\system32\wbemcomn.dll LoadedModule[133]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[134]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[135]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[136]=C:\Windows\system32\NTDSAPI.dll LoadedModule[137]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[138]=F:\FSX\dxgi.dll LoadedModule[139]=C:\Windows\system32\d3d10.dll LoadedModule[140]=C:\Windows\system32\d3d10core.dll LoadedModule[141]=C:\Windows\system32\d3dx10_43.dll LoadedModule[142]=C:\Windows\system32\d3dx11_43.dll LoadedModule[143]=C:\Windows\system32\D3DCOMPILER_43.dll LoadedModule[144]=C:\Windows\system32\dxgi.dll LoadedModule[145]=C:\Windows\system32\d3d11.dll LoadedModule[146]=C:\Windows\system32\nvd3dum.dll LoadedModule[147]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[148]=C:\Windows\system32\nvwgf2um.dll LoadedModule[149]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[150]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[151]=C:\Windows\system32\d3d10_1.dll LoadedModule[152]=C:\Windows\system32\d3d10_1core.dll LoadedModule[153]=C:\Windows\system32\WINSTA.dll LoadedModule[154]=C:\Windows\SysWOW64\gameux.dll LoadedModule[155]=C:\Windows\SysWOW64\wer.dll LoadedModule[156]=C:\Windows\System32\Wpc.dll LoadedModule[157]=C:\Windows\System32\wevtapi.dll LoadedModule[158]=C:\Windows\System32\msxml6.dll LoadedModule[159]=C:\Windows\system32\SAMLIB.dll LoadedModule[160]=C:\Windows\system32\netutils.dll LoadedModule[161]=F:\FSX\uiautomationcore.dll LoadedModule[162]=C:\Windows\system32\OLEACC.dll LoadedModule[163]=C:\Windows\System32\MMDevApi.dll LoadedModule[164]=C:\Windows\System32\PROPSYS.dll LoadedModule[165]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[166]=C:\Windows\system32\RICHED20.DLL LoadedModule[167]=C:\Windows\system32\HID.DLL LoadedModule[168]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[169]=C:\Windows\system32\wdmaud.drv LoadedModule[170]=C:\Windows\system32\ksuser.dll LoadedModule[171]=C:\Windows\system32\AVRT.dll LoadedModule[172]=C:\Windows\system32\msacm32.drv LoadedModule[173]=C:\Windows\system32\midimap.dll LoadedModule[174]=C:\Windows\system32\dinput.DLL LoadedModule[175]=C:\Windows\System32\wship6.dll LoadedModule[176]=C:\Windows\System32\wshtcpip.dll LoadedModule[177]=F:\FSX\bglmanx.dll LoadedModule[178]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[179]=C:\Windows\system32\inetmib1.dll LoadedModule[180]=C:\Windows\system32\snmpapi.dll LoadedModule[181]=F:\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll LoadedModule[182]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[183]=F:\FSX\PMDG\DLLs\PMDG_Interface.dll LoadedModule[184]=F:\FSX\RAASPRO\RAASPRO.dll LoadedModule[185]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[186]=C:\Windows\system32\MSDART.DLL LoadedModule[187]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[188]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL LoadedModule[189]=C:\Windows\system32\comsvcs.dll LoadedModule[190]=C:\Windows\system32\ATL.DLL LoadedModule[191]=C:\Windows\SysWOW64\msjetoledb40.dll LoadedModule[192]=C:\Windows\SysWOW64\msjet40.dll LoadedModule[193]=C:\Windows\SysWOW64\mswstr10.dll LoadedModule[194]=C:\Windows\SysWOW64\msjter40.dll LoadedModule[195]=C:\Windows\SysWOW64\MSJINT40.DLL LoadedModule[196]=C:\Windows\SysWOW64\mstext40.dll LoadedModule[197]=C:\Windows\system32\mlang.dll LoadedModule[198]=C:\Windows\system32\RAASAUDIO32.DLL LoadedModule[199]=C:\Windows\system32\X3DAudio1_6.dll LoadedModule[200]=C:\Windows\SysWow64\xactengine3_4.dll LoadedModule[201]=C:\Windows\SysWow64\XAudio2_4.dll LoadedModule[202]=F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[203]=F:\FSX\VistaMare\ViMaCoreX.dll LoadedModule[204]=F:\FSX\VistaMare\bin\VMCX_AP.dll LoadedModule[205]=F:\FSX\VistaMare\bin\ViMaNET_AP.dll LoadedModule[206]=F:\FSX\Modules\VAInterface.dll LoadedModule[207]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[208]=F:\FSX\Modules\FSUIPC4.dll LoadedModule[209]=F:\FSX\as_srv\as_btstrp.dll LoadedModule[210]=C:\Windows\system32\mscoree.dll LoadedModule[211]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[212]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll LoadedModule[213]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\38bf604432e1a30c954b2ee40d6a2d1c\mscorlib.ni.dll LoadedModule[214]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll LoadedModule[215]=F:\FSX\as_srv\as_connect.dll LoadedModule[216]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll LoadedModule[217]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\908ba9e296e92b4e14bdc2437edac603\System.ni.dll LoadedModule[218]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\836e10dfd0811b303553216f5cb092ef\System.Drawing.ni.dll LoadedModule[219]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[220]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[221]=C:\Windows\SysWOW64\msls31.dll LoadedModule[222]=C:\Windows\system32\msimtf.dll LoadedModule[223]=F:\FSX\GAUGES\PMDG_777X.DLL LoadedModule[224]=C:\Windows\system32\NETAPI32.dll LoadedModule[225]=C:\Windows\system32\srvcli.dll LoadedModule[226]=C:\Windows\system32\wkscli.dll LoadedModule[227]=C:\Windows\system32\WSOCK32.dll LoadedModule[228]=C:\Windows\SysWow64\XAudio2_7.dll LoadedModule[229]=F:\FSX\GAUGES\PMDG_777X_3.DLL LoadedModule[230]=F:\FSX\FS2Crew2010\Versions\PMDG777\Gauges\FS2Crew777.GAU LoadedModule[231]=F:\FSX\libcurl.dll LoadedModule[232]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[233]=C:\Windows\system32\FS2AUDIO.dll LoadedModule[234]=C:\Windows\system32\RASAPI32.dll LoadedModule[235]=C:\Windows\system32\rasman.dll LoadedModule[236]=C:\Windows\system32\rtutils.dll LoadedModule[237]=C:\Windows\system32\NLAapi.dll LoadedModule[238]=C:\Windows\system32\napinsp.dll LoadedModule[239]=C:\Windows\system32\pnrpnsp.dll LoadedModule[240]=C:\Windows\System32\winrnr.dll LoadedModule[241]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[242]=C:\Windows\System32\fwpuclnt.dll LoadedModule[243]=C:\Windows\System32\netprofm.dll LoadedModule[244]=C:\Windows\System32\npmproxy.dll LoadedModule[245]=F:\FSX\Gauges\PMDG_777X_2.dll LoadedModule[246]=C:\Windows\system32\icmp.Dll LoadedModule[247]=F:\FSX\VistaMare\bin\ViMaIScnX_AP.dll LoadedModule[248]=C:\Windows\system32\msadp32.acm LoadedModule[249]=C:\Windows\SysWOW64\msjtes40.dll LoadedModule[250]=C:\Windows\system32\VBAJET32.DLL LoadedModule[251]=C:\Windows\system32\expsrv.dll LoadedModule[252]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=BEX AppName=Microsoft Flight Simulator® AppPath=F:\FSX\fsx.exe I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 2, 201411 yr Author I did some testing and I have a feeling that EGLL Extended is causing issues. All other airports are fine so far. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 2, 201411 yr This time you got the BEX/StackHash (explained in the AVSIM CTD Guide in the probable causes section). The most likely cause is the MyTrafficX 5.4c program with the 2012 or 2013 AI schedule loaded. 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
December 2, 201411 yr Author That is strange. I do not have MyTrafficX 5.4c installed. May be it is something included into EGLL scenery package...but I was unable to find anything like that. It just crashed in EDDF as well at engine start.. crap.. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 3, 201411 yr Author Jim. Do you think I may need to reinstall whole Windows and FSX just to fix that engine star issue? That will be a torture for me . I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 3, 201411 yr It only happens when I push button for FS2crew to command to Start Engine. I cannot figure out if there is a conflict. Jim. Do you think I may need to reinstall whole Windows and FSX just to fix that engine star issue? That will be a torture for me . If you are getting the StackHash just for FSCrew, I would not even think of reinstalling Windows. Technically you have found what is causing your StackHash - FS Crew. I would uninstall FSCrew and then reinstall making sure you have Admin privileges. I would also make sure your fsx folders are shared or that you have taken ownership (see AVSIM CTD Guide, Version 2 which was just released). If you have more than one monitor, make sure you open and close windows in Windowed Mode when you startup/shutdown fsx. Did the latest crash at EDDF show a StackHash too like your earlier crash reports? I have looked at your latest crash report and everything is properly installed, Microsoft Visual 2005, 2008, and 2010 have proper versions showing. Microsoft.net appears to be installed properly with the proper versions for dotnet 2.0 and 4.0. Make sure EDDF and EGLL have been installed properly with Admin Rights. Make sure those folders are shared or takeownership. In the new AVSIM CTD Guide, we provided more guidance for actions you should take after you get a crash. I would go through those too and look at the modules in the dll.xml. Like the guide says, just move the dll.xml over to a temporary folder and see if this fixes your problems. You won't have FSCrew or RAASPRO but if it fixes the crashes, it is one of those modules that is not installed properly and you can investigate that by enabling them one by one until the crashes start up again. A StackHash is usually followed by a NTDLL.dll crash and sometimes they will alternate. If this happens, you have too high settings or there is a tweak in your FSX.cfg that your system does not like (the BufferPool tweak causes instability in most modern computer systems if not properly employed). Best regards, 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
December 5, 201411 yr Author Jim. I reinstalled Acceleration per CTD guide, ran Micisift Repair Tool. Rebuilt fsx.cfg, no tweaks in it, just a few per AVSIM guide. Keeps crashing right at Engine start command again. FS2crew was reinstalled. No luck. Can you clarify something regarding modules in the dll.xml? What does it mean to "move the dll.xml over to a temporary folder and see if this fixes your problems." Do I have to delete some of those dll.xml files from FSX folder? If so then which one? I did not quite understand. Another thing: "You won't have FSCrew or RAASPRO but if it fixes the crashes, it is one of those modules that is not installed properly and you can investigate that by enabling them one by one until the crashes start up again." Does it mean FS2crew will not be working? If so then how will I be able to fix the problem? Everything is working and FScrew is working fine but up to the point where I command Engine start. Thank you Last CTD: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3 Exception code: 0xc000000d Fault offset: 0x00008aa0 Faulting process id: 0x1698 Faulting application start time: 0x01d010e24431748a Faulting application path: F:\FSX\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll Report Id: 66c90e29-7cd7-11e4-8e97-e03f498675dd I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
December 6, 201411 yr Can you clarify something regarding modules in the dll.xml? What does it mean to "move the dll.xml over to a temporary folder and see if this fixes your problems." Do I have to delete some of those dll.xml files from FSX folder? If so then which one? I did not quite understand. When you open up Windows Explorer to view your files (and the dll.xml), you should see a C:\Temp. If not, you can add the file to the C:\directory. You can move the dll.xml file over to your Downloads directory too. Just put your cursor over the dll.xml and left click the Mouse. Drag it over to a temporary folder. It is now gone from the hidden folder where your fsx.cfg is located. Now, restart FSX. None of your modules, like FSUIPC, RAASPRO, PMDG, etc., etc., will not load when you restart FSX. Did this fix the problem. If so, then it is most likely one of the modules in the dll.xml. Move the dll.xml back over to the folder where your fsx.cfg is located. Open the file up using notepad. Now, as indicated in the AVSIM CTD Guide, disable each module except for the top one. You do this by changing that disable line from False to True. Save the file and try running FSX again and see if you can replicate the crash. For the last CTD, there is a solution for this crash in the AVSIM CTD Guide under probable solutions. Just look up MSVCR80.dll and follow the directions there. Does it mean FS2crew will not be working? If so then how will I be able to fix the problem? Everything is working and FScrew is working fine but up to the point where I command Engine start. What you are doing when you disable a module or move the dll.xml to a temporary folder is disabling the module. It is better to do this than to uninstall FSCrew or RAASPRO. This is the simple solution to find out if your product was installed properly or not. Of course, you can go ahead and uninstall all of your addons and add them one at a time too but that takes up too much time. My solution is to shorten your investigation to try to find the culprit for your crashes. Of course, you need to fix that MSRVC80.dll as that is the proper version install but sometimes they somehow get corrupted. This module belongs to the Microsoft Visual C++ 2005 Redistributable. If it is not installed properly (or not installed), FSX will not start up, plain and simple. It is needed to run FSX and many FSX addons. 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
December 8, 201411 yr Author OK. I had to reinstall C++ libraries twice and looks like it helped. I have made three flights so far with now issues from different airports. Will keep testing to make sure the problem has really gone. Thank you I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
March 8, 201511 yr Author Jim. Hello again. :( I am having CTD again. I think this time Aivlasoft EFB is causing issue. Getting this error: MICROSOFT .Net FRAMEWORK Exception from HRESULT 0xC000014B I cannot figure out what exactly is casing error within Aivlasfot EFB. Changes I have made before CTD began: Installed updated version PMDG 737NG sp1D and change path in folders inside Aivlasoft EFB to update lates AIRAC cycle. Before it was not updating due to wrong folder path to install AIRAC updates. So AIRAC updates went fine but now I have CTD. Thx for looking. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.FlightSimulator.SimConnect.SimConnect.TransmitClientEvent(UInt32 ObjectID, Enum EventID, UInt32 dwData, Enum GroupID, SIMCONNECT_EVENT_FLAG Flags) at bh.a(Boolean A_0) at bh.b(Object A_0, EventArgs A_1) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) ---------------------------------------- AivlaSoft.Efb.DataProvider Assembly Version: 1.5.1.15704 Win32 Version: 1.5.1.0 ---------------------------------------- log4net Assembly Version: 1.2.10.0 Win32 Version: 1.2.10.0 ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- DevExpress.Utils.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 ---------------------------------------- Rhino.Commons Assembly Version: 2.0.0.0 Win32 Version: 2.0.0.1414 ---------------------------------------- Castle.Windsor Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 ---------------------------------------- Castle.Core Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 ---------------------------------------- Castle.MicroKernel Assembly Version: 1.0.3.0 Win32 Version: 1.0.3.5114 ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400) ---------------------------------------- Rhino.Commons.Clr Assembly Version: 2.0.0.0 Win32 Version: 2.0.0.1414 ---------------------------------------- System.Web Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- Castle.DynamicProxy2 Assembly Version: 2.0.3.0 Win32 Version: 2.0.3.5114 ---------------------------------------- AivlaSoft.Efb.Common Assembly Version: 1.5.1.15699 Win32 Version: 1.5.1.0 ---------------------------------------- System.Core Assembly Version: 3.5.0.0 Win32 Version: 3.5.30729.5420 built by: Win7SP1 ---------------------------------------- DevExpress.Data.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 ---------------------------------------- DevExpress.XtraEditors.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 ---------------------------------------- System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- DevExpress.XtraGrid.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 ---------------------------------------- DevExpress.XtraBars.v9.1 Assembly Version: 9.1.4.0 Win32 Version: 9.1.4.0 ---------------------------------------- Desaware.MachineLicense35 Assembly Version: 1.6.0.0 Win32 Version: 1.6.3.0 ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- Desaware.Dls.Interfaces20 Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 ---------------------------------------- System.Security Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400) ---------------------------------------- Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61259.0 Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421) ---------------------------------------- msvcm80 Assembly Version: 8.0.50727.6195 Win32 Version: 8.00.50727.6195 ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. ---------------------- Log Name: Application Source: Application Error Date: 3/7/2015 12:39:27 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Owner-PC Description: Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: API.DLL, version: 10.0.62608.0, time stamp: 0x54abe5da Exception code: 0xc0000005 Fault offset: 0x000b8aff Faulting process id: 0x43c Faulting application start time: 0x01d0589f4af6c26f Faulting application path: G:\FSX\steamapps\common\FSX\fsx.exe Faulting module path: G:\FSX\steamapps\common\FSX\API.DLL Report Id: b2cbdc93-c494-11e4-a932-e03f498675dd Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-03-07T06:39:27.000000000Z" /> <EventRecordID>22895</EventRecordID> <Channel>Application</Channel> <Computer>Owner-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.62608.0</Data> <Data>54abe5b4</Data> <Data>API.DLL</Data> <Data>10.0.62608.0</Data> <Data>54abe5da</Data> <Data>c0000005</Data> <Data>000b8aff</Data> <Data>43c</Data> <Data>01d0589f4af6c26f</Data> <Data>G:\FSX\steamapps\common\FSX\fsx.exe</Data> <Data>G:\FSX\steamapps\common\FSX\API.DLL</Data> <Data>b2cbdc93-c494-11e4-a932-e03f498675dd</Data> </EventData> </Event> I read in CTD manual that API.DLL is VAS issue. However I have 1959600 remaining, does not look like it is a VAS issue. Texture max load is 1024. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
March 8, 201511 yr I am having CTD again. I think this time Aivlasoft EFB is causing issue. Getting this error:MICROSOFT .Net FRAMEWORK Exception from HRESULT 0xC000014B According to the AVSIM CTD Guide: HRESULT: 0xc000014B error – Mostly occurs in networked computers. This is a Microsoft.net error. The 0xc000014B is a "broken pipe" exception. A pipe is a communication channel between two applications (such as FSX/P3D and an add-on program like ASN or OPUS, or network). SimConnect offers add-ons the possibility to use pipes to communication with FSX. A "broken pipe" is a situation where one of the pipes no longer exists, while the other tries to communicate using the pipe. A typical scenario would be fsx crashing and then ASN or OPUS tried to use the pipe (communications channel) and the “pipe” was broken. The 014B exception would then occur. Check your network setup or an application that uses SimConnect and troubleshoot. Microsoft.net 2.0 was loaded and indicates the correct version of Simconnect was loaded. I believe you are correct about the Electronic Flight Bag as it is probably not "seeing" FSX-SE properly because the FSX-SE file structure is totally different from FSX. I read in CTD manual that API.DLL is VAS issue. However I have 1959600 remaining, does not look like it is a VAS issue. Texture max load is 1024. The api.dll for fsx-se was modified and is not the same version as used in FSX. Many computer techs have tried to hack the API.dll to solve OOM's and were unsuccessful. Unfortunately I cannot help you with this problem. It is most likely connected with the EFB crash. When you install a product not made specifically for FSX-SE, then you are playing with dynamite. When you disable EFB, does all of your crashes stop? In regards to our probable causes for CTD's, we did extensive research around the flight sim community and the Internet to look for probable causes and solutions when someone reported the faulting module was "api.dll". What is shown in the CTD Guide are all of the probable solutions found as reported by other flight sim users. We did not take in consideration any crashes related to FSX-SE as we had not seen any before the CTD Guide was prepared and finalized. For your information, API, abbreviation of application program interface, is a set of routines, protocols, and tools for building software applications. The API specifies how software components should interact and are used when programming graphical user interface (GUI) components. So I think one of your applications is not interacting properly with FSX-SE. I would suspect the EFB. It could also be another application addon but since you got the Microsoft.net 2.0 error (used by FSX, not FSX-SE), an older application is causing your issues. 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
March 12, 201511 yr Author Jim. Sorry I am here again. I ended up updating BIOS to the latest version. My PC clocks were messed up. ASUS and other simmers recommended to update BIOS. Update went ok but now I am getting CTD with this error: Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4 Faulting module name: SimConnect.dll, version: 10.0.61637.0, time stamp: 0x46fad5b6 Exception code: 0xc0000005 Fault offset: 0x00004a5b Faulting process id: 0x1464 Faulting application start time: 0x01d05ce755a8a0ab Faulting application path: G:\FSX\steamapps\common\FSX\fsx.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll Report Id: 2a61201b-c8e3-11e4-94ac-e03f498675dd I found the topic: http://forum.avsim.net/topic/455249-ctd-caused-by-simconnect/ where you mentioned something about ASN simconnect on page 79, but it is related to networked computer. I do not have networked PC, ASN is installed in main one. SO it was working till I updated BIOS and now it is causing issues as before while using FS2crew and it crashes at engine start. Thx for help again. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
March 12, 201511 yr ended up updating BIOS to the latest version. My PC clocks were messed up. ASUS and other simmers recommended to update BIOS. Update went ok but now I am getting CTD with this error: Updating the BIOS should not have caused a problem with simconnect. I'm not totally sure how you install FSX-SE but the faulting module, simconnect.dll, belongs to FSX/Acceleration and not to FSX-SE. So, some addon you installed in FSX-SE installed the simconnect.dll for FSX/Acceleration and the paths are completely different. So, whatever add-on program uses simconnect I would uninstall and make sure you use the installer they have for installing their application into FSX-SE. 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
June 3, 201511 yr Author Based on your crash report, the faulting module was d3d11.dll. According to the AVSIM CTD Guide: D3D11.dll – Remove Windows Update KB2670838. CTD occurs with SweetFX installed. The Windows Update recommendation is an old one from over a year ago so it may not be applicable anymore but it is definitely the fix if you still have this Windows Update installed. Best regards, Good morning Jim. I am getting occasional CTD and the report was: Faulting module path: C:\Windows\SysWOW64\ntdll.dll Based on CTD Guide: Remove the D3D9.dll modules (there are several) from your main FSX folder. SweetFX installs the following files that should be moved to a temporary directory if problems occur: D3d9.dll, D3d9.fx, Dxgi.dll, Shader.fx, and the injector.ini. 1. What does it mean- following files that should be moved to a temporary directory if problems occur: D3d9.dll, D3d9.fx, Dxgi.dll, Shader.fx, and the injector.ini. I didn't quite understand the procedure how to do it. Will you be able help or give me some reference so I can take a look? 2. Remove the D3D9.dll modules (there are several)... I have only one D3D9.dll, or I need to remove all those from SweetFX - D3d9.dll, D3d9.fx, Dxgi.dll,? Thanks for looking. I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”
June 3, 201511 yr 2. Remove the D3D9.dll modules (there are several)... I have only one D3D9.dll, or I need to remove all those from SweetFX - D3d9.dll, D3d9.fx, Dxgi.dll,? Any .dll or .ini file in your fsx folder will load when you start it up and that could cause fsx to crash. They are not needed by FSX to operate. You should move or delete them all. I recommend moving first to a temporary folder to see if this is causing your ntdll.dll. crash. If the ntdll.dll crash continues then you know SweetFX was not the issue and you can move the files back to the FSX folder if you desire. What does it mean- following files that should be moved to a temporary directory if problems occur: D3d9.dll, D3d9.fx, Dxgi.dll, Shader.fx, and the injector.ini. I didn't quite understand the procedure how to do it. Will you be able help or give me some reference so I can take a look? Here's a reference - http://windows.microsoft.com/en-us/windows/working-with-files-folders#1TC=windows-7 . Look for how to move or copy files. I have set up my computer with a temporary folder in my download directory (i.e., C:\Downloads\Temp). I then go to the main fsx directory, find the files I do not want in the main FSX directory and move them over to the Temp directory. This way, if moving the files to the Temporary directory did not stop my crashes, I can move the files back into FSX directory and continue to look for the problem with FSX. 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
Create an account or sign in to comment