January 2, 201412 yr Hello, I've installed few sceneries (airports, FTXG, FTX Vector etc) last few weeks and since i often have CTD. Here is the crash report. Thanks a lot and Best wishes for 2014. Version=1EventType=AppHangB1EventTime=130331031542486280ReportType=3Consent=1UploadTime=130331031566027627ReportIdentifier=33e60e59-7355-11e3-87b5-5404a6359278IntegratorReportIdentifier=33e60e5a-7355-11e3-87b5-5404a6359278WOW64=1Response.BucketId=651592957Response.BucketTable=5Response.type=4Sig[0].Name=Nom de l’applicationSig[0].Value=fsx.exeSig[1].Name=Version de l’applicationSig[1].Value=10.0.61637.0Sig[2].Name=Horodatage de l’applicationSig[2].Value=46fadb14Sig[3].Name=Signature de blocageSig[3].Value=f7fcSig[4].Name=Type de blocageSig[4].Value=256DynamicSig[1].Name=Version du systèmeDynamicSig[1].Value=6.1.7601.2.1.0.256.48DynamicSig[2].Name=Identificateur de paramètres régionauxDynamicSig[2].Value=3084DynamicSig[22].Name=Signature de blocage supplém. 1DynamicSig[22].Value=f7fc88831a14516a1a53b7dc654b9c89DynamicSig[23].Name=Signature de blocage supplém. 2DynamicSig[23].Value=0a03DynamicSig[24].Name=Signature de blocage supplém. 3DynamicSig[24].Value=0a0361110b548a85e6238b8d704beae7DynamicSig[25].Name=Signature de blocage supplém. 4DynamicSig[25].Value=f7fcDynamicSig[26].Name=Signature de blocage supplém. 5DynamicSig[26].Value=f7fc88831a14516a1a53b7dc654b9c89DynamicSig[27].Name=Signature de blocage supplém. 6DynamicSig[27].Value=0a03DynamicSig[28].Name=Signature de blocage supplém. 7DynamicSig[28].Value=0a0361110b548a85e6238b8d704beae7UI[3]=Microsoft Flight Simulator® ne répond pasUI[4]=Si vous fermez le programme, vous risquez de perdre des informations.UI[5]=Fermer le programmeUI[6]=Fermer le programmeUI[7]=Fermer le programmeLoadedModule[0]=C:\FSX\fsx.exeLoadedModule[1]=C:\Windows\SysWOW64\ntdll.dllLoadedModule[2]=C:\Windows\syswow64\kernel32.dllLoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dllLoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLLLoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dllLoadedModule[6]=C:\Windows\syswow64\msvcrt.dllLoadedModule[7]=C:\Windows\syswow64\GDI32.dllLoadedModule[8]=C:\Windows\syswow64\USER32.dllLoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dllLoadedModule[10]=C:\Windows\SysWOW64\sechost.dllLoadedModule[11]=C:\Windows\syswow64\RPCRT4.dllLoadedModule[12]=C:\Windows\syswow64\SspiCli.dllLoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dllLoadedModule[14]=C:\Windows\syswow64\LPK.dllLoadedModule[15]=C:\Windows\syswow64\USP10.dllLoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dllLoadedModule[17]=C:\Windows\syswow64\ole32.dllLoadedModule[18]=C:\Windows\system32\apphelp.dllLoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLLLoadedModule[20]=C:\Windows\system32\UxTheme.dllLoadedModule[21]=C:\Windows\system32\WINMM.dllLoadedModule[22]=C:\Windows\system32\samcli.dllLoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dllLoadedModule[24]=C:\Windows\system32\MSACM32.dllLoadedModule[25]=C:\Windows\system32\VERSION.dllLoadedModule[26]=C:\Windows\syswow64\SHELL32.dllLoadedModule[27]=C:\Windows\system32\sfc.dllLoadedModule[28]=C:\Windows\system32\sfc_os.DLLLoadedModule[29]=C:\Windows\system32\USERENV.dllLoadedModule[30]=C:\Windows\system32\profapi.dllLoadedModule[31]=C:\Windows\system32\dwmapi.dllLoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dllLoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dllLoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dllLoadedModule[35]=C:\Windows\syswow64\urlmon.dllLoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dllLoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dllLoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dllLoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dllLoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dllLoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dllLoadedModule[42]=C:\Windows\syswow64\normaliz.DLLLoadedModule[43]=C:\Windows\syswow64\iertutil.dllLoadedModule[44]=C:\Windows\syswow64\WININET.dllLoadedModule[45]=C:\Windows\system32\MPR.dllLoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLLLoadedModule[47]=C:\Windows\system32\WINSPOOL.DRVLoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLLLoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dllLoadedModule[50]=C:\Windows\system32\mscms.dllLoadedModule[51]=C:\Windows\system32\DDRAW.dllLoadedModule[52]=C:\Windows\system32\DCIMAN32.dllLoadedModule[53]=C:\Windows\syswow64\COMDLG32.dllLoadedModule[54]=C:\Windows\syswow64\IMM32.dllLoadedModule[55]=C:\Windows\syswow64\MSCTF.dllLoadedModule[56]=C:\Windows\syswow64\WS2_32.dllLoadedModule[57]=C:\Windows\syswow64\NSI.dllLoadedModule[58]=C:\Windows\system32\msi.dllLoadedModule[59]=c:\windows\syswow64\nvinit.dllLoadedModule[60]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\detoured.dllLoadedModule[61]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvd3d9wrap.dllLoadedModule[62]=C:\Program Files (x86)\NVIDIA Corporation\CoProcManager\nvdxgiwrap.dllLoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80FRA.DLLLoadedModule[64]=C:\FSX\language.dllLoadedModule[65]=C:\FSX\API.DLLLoadedModule[66]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dllLoadedModule[67]=C:\FSX\ablscpt.dllLoadedModule[68]=C:\FSX\flight.dllLoadedModule[69]=C:\FSX\ai_player.dllLoadedModule[70]=C:\FSX\acontain.dllLoadedModule[71]=C:\FSX\controls.dllLoadedModule[72]=C:\Windows\system32\DINPUT8.dllLoadedModule[73]=C:\FSX\fsui.dllLoadedModule[74]=C:\FSX\atc.dllLoadedModule[75]=C:\FSX\facilities.dllLoadedModule[76]=C:\FSX\demo.dllLoadedModule[77]=C:\FSX\main.dllLoadedModule[78]=C:\FSX\fe.dllLoadedModule[79]=C:\FSX\util.dllLoadedModule[80]=C:\FSX\simprop.dllLoadedModule[81]=C:\FSX\g2d.dllLoadedModule[82]=C:\Windows\system32\d3dx9_34.dllLoadedModule[83]=C:\Windows\system32\d3dx10_34.dllLoadedModule[84]=C:\Windows\system32\d3d9.dllLoadedModule[85]=C:\Windows\system32\d3d8thk.dllLoadedModule[86]=C:\FSX\g3d.dllLoadedModule[87]=C:\FSX\panels.dllLoadedModule[88]=C:\FSX\multiplayer.dllLoadedModule[89]=C:\FSX\ui.dllLoadedModule[90]=C:\FSX\sound.dllLoadedModule[91]=C:\FSX\sim1.dllLoadedModule[92]=C:\FSX\simscheduler.dllLoadedModule[93]=C:\FSX\visualfx.dllLoadedModule[94]=C:\FSX\window.dllLoadedModule[95]=C:\FSX\terrain.dllLoadedModule[96]=C:\FSX\weather.dllLoadedModule[97]=C:\Windows\system32\DSOUND.dllLoadedModule[98]=C:\Windows\system32\POWRPROF.dllLoadedModule[99]=C:\FSX\symmap.dllLoadedModule[100]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dllLoadedModule[101]=C:\Windows\system32\MSIMG32.dllLoadedModule[102]=C:\FSX\xuipc.dllLoadedModule[103]=C:\FSX\livingwater.dllLoadedModule[104]=C:\FSX\fs-traffic.dllLoadedModule[105]=C:\FSX\gps.dllLoadedModule[106]=C:\Windows\system32\MSWSOCK.dllLoadedModule[107]=C:\Windows\system32\SHFOLDER.dllLoadedModule[108]=C:\Program Files (x86)\Common Files\Spigot\Search Settings\wth175.dllLoadedModule[109]=C:\Windows\syswow64\PSAPI.DLLLoadedModule[110]=C:\Windows\system32\CRYPTSP.dllLoadedModule[111]=C:\Windows\system32\rsaenh.dllLoadedModule[112]=C:\Windows\syswow64\WINTRUST.dllLoadedModule[113]=C:\Windows\syswow64\CRYPT32.dllLoadedModule[114]=C:\Windows\syswow64\MSASN1.dllLoadedModule[115]=C:\Windows\syswow64\CLBCatQ.DLLLoadedModule[116]=C:\Windows\system32\wbem\wbemprox.dllLoadedModule[117]=C:\Windows\system32\wbemcomn.dllLoadedModule[118]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[119]=C:\Windows\system32\wbem\wbemsvc.dllLoadedModule[120]=C:\Windows\system32\wbem\fastprox.dllLoadedModule[121]=C:\Windows\system32\NTDSAPI.dllLoadedModule[122]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLLLoadedModule[123]=C:\Windows\system32\dxgi.dllLoadedModule[124]=C:\Windows\system32\d3d11.dllLoadedModule[125]=C:\Windows\system32\nvumdshim.dllLoadedModule[126]=C:\Windows\system32\nvd3dum.dllLoadedModule[127]=C:\Windows\system32\nvwgf2um.dllLoadedModule[128]=C:\Windows\system32\D3DCompiler_34.dllLoadedModule[129]=C:\Windows\system32\WindowsCodecs.dllLoadedModule[130]=C:\Windows\system32\d3d10_1.dllLoadedModule[131]=C:\Windows\system32\d3d10_1core.dllLoadedModule[132]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dllLoadedModule[133]=C:\Windows\SysWOW64\dxdiagn.dllLoadedModule[134]=C:\Windows\SysWOW64\d3d10.dllLoadedModule[135]=C:\Windows\SysWOW64\d3d10core.dllLoadedModule[136]=C:\Windows\system32\winbrand.dllLoadedModule[137]=C:\Windows\system32\nvapi.dllLoadedModule[138]=C:\Windows\system32\WTSAPI32.DLLLoadedModule[139]=C:\Windows\system32\WINSTA.dllLoadedModule[140]=C:\Windows\SysWOW64\gameux.dllLoadedModule[141]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dllLoadedModule[142]=C:\Windows\SysWOW64\XmlLite.dllLoadedModule[143]=C:\Windows\SysWOW64\wer.dllLoadedModule[144]=C:\Windows\System32\Wpc.dllLoadedModule[145]=C:\Windows\System32\wevtapi.dllLoadedModule[146]=C:\Windows\System32\msxml6.dllLoadedModule[147]=C:\Windows\system32\SAMLIB.dllLoadedModule[148]=C:\Windows\system32\netutils.dllLoadedModule[149]=C:\FSX\uiautomationcore.dllLoadedModule[150]=C:\Windows\system32\OLEACC.dllLoadedModule[151]=C:\Windows\System32\MMDevApi.dllLoadedModule[152]=C:\Windows\System32\PROPSYS.dllLoadedModule[153]=C:\Windows\system32\AUDIOSES.DLLLoadedModule[154]=C:\Windows\system32\RICHED20.DLLLoadedModule[155]=C:\Windows\system32\HID.DLLLoadedModule[156]=C:\Windows\system32\XInput9_1_0.dllLoadedModule[157]=C:\Windows\system32\wdmaud.drvLoadedModule[158]=C:\Windows\system32\ksuser.dllLoadedModule[159]=C:\Windows\system32\AVRT.dllLoadedModule[160]=C:\Windows\system32\msacm32.drvLoadedModule[161]=C:\Windows\system32\midimap.dllLoadedModule[162]=C:\Windows\system32\dinput.DLLLoadedModule[163]=C:\Windows\System32\wship6.dllLoadedModule[164]=C:\Windows\System32\wshtcpip.dllLoadedModule[165]=C:\FSX\ORBX\FTX_NA\FTX_AA_PAEN\scenery\ObjectFlow_PAEN.dllLoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dllLoadedModule[167]=C:\FSX\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dllLoadedModule[168]=C:\FSX\ORBX\FTX_NA\FTX_AA_PAJN\Scenery\ObjectFlow_PAJN.dllLoadedModule[169]=C:\FSX\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ObjectFlow_SAK.dllLoadedModule[170]=C:\FSX\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dllLoadedModule[171]=C:\Flight One Software\BATX\F1TechBatX_FSX.dllLoadedModule[172]=C:\FSX\bglmanx.dllLoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dllLoadedModule[174]=C:\Windows\system32\inetmib1.dllLoadedModule[175]=C:\Windows\system32\IPHLPAPI.DLLLoadedModule[176]=C:\Windows\system32\WINNSI.DLLLoadedModule[177]=C:\Windows\system32\snmpapi.dllLoadedModule[178]=C:\FSX\ORBX\FTX_NA\FTX_AA_CYBD\Scenery\ObjectFlow_CYBD.dllLoadedModule[179]=C:\FSX\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dllLoadedModule[180]=C:\FSX\ORBX\FTX_NA\FTX_AA_KBVS\Scenery\Objectflow_KBVS.dllLoadedModule[181]=C:\FSX\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dllLoadedModule[182]=C:\FSX\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dllLoadedModule[183]=C:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dllLoadedModule[184]=C:\FSX\ORBX\FTX_AU\FTXAA_YBAS\Scenery\ObjectFlow_YBAS.dllLoadedModule[185]=C:\FSX\ORBX\FTX_NA\FTX_AA_CZST\Scenery\ObjectFlow_CZST.dllLoadedModule[186]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dllLoadedModule[187]=C:\Windows\system32\MSVCR100.dllLoadedModule[188]=C:\FSX\FeelThere\E170\EJetH.dllLoadedModule[189]=C:\FSX\VistaMare\ViMaCoreX.dllLoadedModule[190]=C:\FSX\VistaMare\bin\VMCX_AP.dllLoadedModule[191]=C:\FSX\VistaMare\bin\ViMaNET_AP.dllLoadedModule[192]=C:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dllLoadedModule[193]=C:\FSX\RAASPRO\RAASPRO.dllLoadedModule[194]=C:\Windows\system32\Secur32.dllLoadedModule[195]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dllLoadedModule[196]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dllLoadedModule[197]=C:\Windows\system32\DNSAPI.dllLoadedModule[198]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[199]=C:\Windows\System32\netprofm.dllLoadedModule[200]=C:\Windows\System32\nlaapi.dllLoadedModule[201]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLLLoadedModule[202]=C:\Program Files (x86)\Bonjour\mdnsNSP.dllLoadedModule[203]=C:\Windows\system32\dhcpcsvc6.DLLLoadedModule[204]=C:\Windows\system32\rasadhlp.dllLoadedModule[205]=C:\Windows\System32\npmproxy.dllLoadedModule[206]=C:\Windows\System32\fwpuclnt.dllLoadedModule[207]=C:\Program Files (x86)\Common Files\System\ado\msado15.dllLoadedModule[208]=C:\Windows\system32\MSDART.DLLLoadedModule[209]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dllLoadedModule[210]=C:\Windows\system32\bcrypt.dllLoadedModule[211]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLLLoadedModule[212]=C:\Windows\system32\comsvcs.dllLoadedModule[213]=C:\Windows\system32\ATL.DLLLoadedModule[214]=C:\Windows\SysWOW64\bcryptprimitives.dllLoadedModule[215]=C:\Windows\SysWOW64\msjetoledb40.dllLoadedModule[216]=C:\Windows\SysWOW64\msjet40.dllLoadedModule[217]=C:\Windows\SysWOW64\mswstr10.dllLoadedModule[218]=C:\Windows\SysWOW64\msjter40.dllLoadedModule[219]=C:\Windows\SysWOW64\MSJINT40.DLLLoadedModule[220]=C:\Windows\SysWOW64\mstext40.dllLoadedModule[221]=C:\Windows\system32\mlang.dllLoadedModule[222]=C:\Windows\system32\RAASAUDIO32.DLLLoadedModule[223]=C:\Windows\system32\X3DAudio1_6.dllLoadedModule[224]=C:\Windows\SysWow64\xactengine3_4.dllLoadedModule[225]=C:\Windows\SysWow64\XAudio2_4.dllLoadedModule[226]=C:\FSX\as_srv\as_btstrp.dllLoadedModule[227]=C:\Windows\system32\mscoree.dllLoadedModule[228]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dllLoadedModule[229]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dllLoadedModule[230]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\9a6c1b7af18b4d5a91dc7f8d6617522f\mscorlib.ni.dllLoadedModule[231]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dllLoadedModule[232]=C:\Windows\syswow64\imagehlp.dllLoadedModule[233]=C:\Windows\system32\ncrypt.dllLoadedModule[234]=C:\Windows\system32\GPAPI.dllLoadedModule[235]=C:\Windows\system32\cryptnet.dllLoadedModule[236]=C:\Windows\syswow64\WLDAP32.dllLoadedModule[237]=C:\Windows\system32\SensApi.dllLoadedModule[238]=C:\FSX\as_srv\as_connect.dllLoadedModule[239]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dllLoadedModule[240]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\5d22a30e587e2cac106b81fb351e7c08\System.ni.dllLoadedModule[241]=C:\Windows\system32\ntmarta.dllLoadedModule[242]=C:\Windows\SysWOW64\ieframe.dllLoadedModule[243]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dllLoadedModule[244]=C:\Windows\SysWOW64\mshtml.dllLoadedModule[245]=C:\Windows\system32\msimtf.dllLoadedModule[246]=C:\Windows\system32\msls31.dllLoadedModule[247]=C:\Windows\system32\d2d1.dllLoadedModule[248]=C:\Windows\system32\DWrite.dllLoadedModule[249]=C:\Windows\system32\D3D10Warp.dllLoadedModule[250]=C:\Windows\SysWOW64\uiautomationcore.dllLoadedModule[251]=C:\FSX\VistaMare\bin\ViMaIScnX_AP.dllLoadedModule[252]=C:\FSX\GAUGES\F1B200.DLLLoadedModule[253]=C:\FSX\GAUGES\Flight1_GarminG1000_KingAir.GAULoadedModule[254]=C:\Windows\system32\WSOCK32.dllLoadedModule[255]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dllLoadedModule[256]=c:\fsx\gauges\kab200svc.dllLoadedModule[257]=C:\Windows\system32\explorerframe.dllLoadedModule[258]=C:\Windows\system32\DUser.dllLoadedModule[259]=C:\Windows\system32\DUI70.dllLoadedModule[260]=C:\Windows\system32\EhStorShell.dllLoadedModule[261]=C:\Windows\system32\ntshrui.dllLoadedModule[262]=C:\Windows\system32\srvcli.dllLoadedModule[263]=C:\Windows\system32\cscapi.dllLoadedModule[264]=C:\Windows\system32\slc.dllLoadedModule[265]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dllLoadedModule[266]=C:\Windows\System32\StructuredQuery.dllLoadedModule[267]=C:\Windows\SysWOW64\actxprxy.dllLoadedModule[268]=C:\Program Files (x86)\Internet Explorer\ieproxy.dllLoadedModule[269]=C:\Windows\SysWOW64\thumbcache.dllLoadedModule[270]=C:\Windows\system32\SearchFolder.dllLoadedModule[271]=C:\Windows\system32\SHDOCVW.dllLoadedModule[272]=C:\Windows\system32\LINKINFO.dllLoadedModule[273]=C:\Windows\system32\NetworkExplorer.dllLoadedModule[274]=C:\Windows\System32\drprov.dllLoadedModule[275]=C:\Windows\System32\ntlanman.dllLoadedModule[276]=C:\Windows\System32\davclnt.dllLoadedModule[277]=C:\Windows\System32\DAVHLPR.dllLoadedModule[278]=C:\Windows\system32\wkscli.dllLoadedModule[279]=C:\Windows\system32\PortableDeviceApi.dllLoadedModule[280]=C:\Windows\system32\PortableDeviceTypes.dllLoadedModule[281]=C:\Windows\system32\EhStorAPI.dllLoadedModule[282]=C:\Windows\system32\twext.dllLoadedModule[283]=C:\Windows\system32\msadp32.acmState[0].Key=Transport.DoneStage1State[0].Value=1FriendlyEventName=A cessé de fonctionner et a été ferméConsentKey=AppHangXProcB1AppName=Microsoft Flight Simulator®AppPath=C:\FSX\fsx.exeReportDescription=Un problème a provoqué l’arrêt de l’interaction de ce programme avec Windows. Real Deraps
January 2, 201412 yr Sorry to hear you are STILL having problems again Real. You did not have a CTD but an AppHang. RaasPro has caused a hangup for me but reinstalled it with and then made sure I had ownership of the file folder. You should download and run TakeOwnership. Once installed, right click the FSX directory and select Take Ownership. Let the program run in CMD mode until the CMD mode window closes. You might also have issues with Windows Firewall in that it is blocking programs. 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
January 2, 201412 yr Author Thanks Jim. I've downloaded and run TakeOwnership. I only have time for a 1.5 hours flight. About 30nm from landing i've had a "FSX does not respond" message again but only a second or two and finally i could land without CTD. Also you say that it could be the Windows Firewall blocking programs. How i can know which program(s) is/are blocked (if so) and can i do something with the firewall? Best regards Real Deraps
January 3, 201412 yr Are you using ASN? I wouldn't mess with the firewall if you don't need too. But I added ASN as one of the programs allowed to pass through the Windows Firewall by going to the Control Panel > System and Security > Windows Firewall. On the left pane, click on Allow a program or feature through Windows Firewall . ASN was not there so I clicked on details and went to the directory where ASN was located and clicked on the directory and then added it. If you read the topic "what are the risks of allowing a program to communicate" (located on the Allow programs page), you'll see it is generally safer to add a program than opening up a port. When you add a program, the port only stays open while the program is communicating with the Internet and closes when you are finished. 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
January 3, 201412 yr Author Thanks again Jim. Yes i'm using ASN. I've just allow it though Windows firewall, We'll see if it fix the problem. Unfortunately, i don' have time to check it tonight but ASAP i will try it. Really appreciate your help. Thanks again. Best regards Real Deraps
January 3, 201412 yr So far it has worked for me. 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
January 4, 201412 yr Author Hum! Still have a "FSX does not respond" and it always happens few minutes before landing. I've done all you say but that's changed nothing. Could it be Ultimate traffic? Best regards Real Deraps
January 4, 201412 yr Hi Real, If it is happening just before landing it is most likely caused by the fact you are running out of memory (or have run out of memory). I should say you have run out of virtual address space (VAS) as you probably have tons of memory. In the AVSIM CTD Guide, look at pages 8 and 9 in regards to VAS. Page 8 talks about freezes during flight. If you have a lot of photoscenery, running out of VAS is easy as fsx loads all of your enabled photoscenery no matter whether you are flying over that area or not. This is why AVSIM recommends running the utility SceneryConfigEditor (link in CTD Guide). You can then enable only the scenery you will be using during a flight session. Hope this helps. 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
January 5, 201412 yr Author Thank you Jim. I've just downloaded and printed this guide and i'll try to see what's wrong. I'll keep you informed. Thanks again. Best regards Real Deraps
January 16, 201412 yr Author I've also installed the SceneryConfigEditor and when i run it, i can see in the areas list that the path does not exist for 268 areas (i have a total of 276 areas). How can i fix that?. Best regards. Real Deraps
January 16, 201412 yr Hi Real, For each area you will have to click on "Edit Area" and look where your scenery is actually located. The program looks at your system registry to determine the location of FSX and then reads your latest scenery.cfg (the working one in Program Data/Microsoft/FSX). That is all it is doing, reading your latest scenery.cfg and matching up where the scenery is actually located on your computer. If it finds a problem, it will tell you and offer to fix the problem. If it cannot fix it or find the scenery, you will have to manually tell it where the scenery is located on your computer. That's a lot of areas you have. I only have 183 areas. Sounds like you have major corruption. You should also look up in the menu for Actions and there are several other things you can do like reorder the Area/Layer numbers. 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
January 16, 201412 yr Author That's probably why i have so many CTD. I'll see if i'm able to manage all this stuff. I'm not really confortable with computer. But thank you again Jim. Best regards. Real Deraps
January 23, 201412 yr Author Hello, I've found few minutes to work on this CTD problem. When i start FSX i have to following msg : "Scenery.cfg file error. Local scenery directory (C:FSX\Addon.Scenery\Scenery) in scenery area 117 not found. Click to continue". In the scenery cfg file, three areas have "required=TRUE" instead of "required=FALSE". In all other areas that's "required=FALSE. Back to area 117, (which is FTX_NA_NRM06_CVX), The area is in the ORBX folders as all the other ones. Thank you very for your help. Best regards Area.115] Title=Global, Generic & Vehicle Libraries Local=C:\FSX\Scenery\Global Layer=115 Active=TRUE Required=TRUE [Area.116] Title=Propeller Objects Local=C:\FSX\Scenery\props Layer=116 Active=TRUE Required=TRUE [Area.117] Title=Addon Scenery Local=C:\FSX\Addon Scenery Layer=117 Active=TRUE Required=TRUE Real Deraps
January 23, 201412 yr Addon Scenery Required should be FALSE. The others are correct (TRUE). You should always use FTX Central to enable/disable Orbx scenery otherwise it will get corrupted. When you get a scenery.cfg error with the message that an area was not found, it means the area was uninstalled (in your case, FTX was disabled). So you need to manually remove that area by opening the scenery.cfg and deleting area 117. Then you will have to renumber the subsequent areas/layers in the scenery.cfg so that the next one down from deleted Area 117 and named Area/Layer 117. Hopefully this will fix your corruption with FTX/Orbx scenery. Do you use the Scenery Config Editor? It does just what I stated above automatically. It will show you the error in Red and you simply click delete and it is fixed. Go Fly. Never use the Scenery Config Editor to disable/enable Orbx/FTX stuff. You are asking for troubles if you do. Do it only through FTX Central. Hope this helps. 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
January 23, 201412 yr Author OMG!. Tell me if it's normal. According to the scenery config editor, i have 257 areas (C:\user\me\appdata\roaming\microsoft\FSX new scenery.cfg = 257 areas) but if i go to the FSX folder C:\FSX, the scenery.cfg has 119 areas (normal?). Also if i click on the area 117 in the scenery config editor and then i go to the text editor it becomes area 141? And finally there is no red line in the area list (scenry config editor) . All green. Also could you tell where i save the newscenery.cfg? Hope that's clear....not sure (i mean that i'm not sure if i explain it corrrectly) Thanks again Best regards Real Deraps
Create an account or sign in to comment