February 7, 20188 yr Hello to all, I have being enjoying some two weeks now the P3D V4.1 after some years with FSX. My addons are Orbx, Active Sky, UTLive, GSX, Fs2Crew, MJS Q400, Reshade and PTA. I have also some scenery from FlyTampa LGAV (Athens) & LGKR (Corfu). All items where installed by their "original installers" and bought especially to be compatible with the 64bit version. I made some flights and all systems were working fine. I've decided to expand my payware addons with PMDGs 737+Fs2Crew and some scenery for Poland EPWA and Polish Airports Vol 3 from aerosoft online store. Once I've installed everything and tried to start the app, when the initial screen appears it freezes while everything is "appearing", location, time and weather windows, apart from the window plane selection (only black screen there). After a few seconds the app crashes and that's all. I've spend already 5 hours trying to go step by step with AVSIM CTD guide but I was unable to achieve something. Afterwards I repaired the app by the P3D installer, I uninstalled all the new addons but still no luck. So my last resort before re-installing the sim all together from the beginning is to ask for help here. So please if somebody can help me it will be highly appreciated and as per guide suggests below my logs from Appcrachview and Event viewer. Thanks in advance AppCrashView Version=1 EventType=APPCRASH EventTime=131624927963713588 ReportType=2 Consent=1 UploadTime=131624927972828037 ReportStatus=97 ReportIdentifier=01e6cb4e-7039-4327-8061-1a075ff870e7 IntegratorReportIdentifier=29ead934-2307-4a83-b63a-199355b874a7 Wow64Host=34404 NsAppName=Prepar3D.exe AppSessionGuid=000024ac-0009-000b-7301-c49e2ca0d301 TargetAppId=W:0000b5ecc21cc8f33f56f7e9f620fed39c6700000904!0000fe4ba4844cdbd482c25c2fa58f1644d0a18615dd!Prepar3D.exe TargetAppVer=2017//10//05:18:48:53!2d051c!Prepar3D.exe BootId=4294967295 TargetAsId=9662 UserImpactVector=269488912 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.1.7.22841 Sig[2].Name=Application Timestamp Sig[2].Value=59d67e95 Sig[3].Name=Fault Module Name Sig[3].Value=facilities.dll Sig[4].Name=Fault Module Version Sig[4].Value=4.1.7.22841 Sig[5].Name=Fault Module Timestamp Sig[5].Value=59d67e03 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=0000000000011446 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.16299.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0811 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=081112851b54da3e6953e812018b3948 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=281a DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=281a95b744e2d8e165943e743d40f1eb UI[2]=C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe UI[3]=Prepar3D exe 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]=C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.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\USER32.dll LoadedModule[6]=C:\WINDOWS\System32\win32u.dll LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[11]=C:\WINDOWS\System32\ole32.dll LoadedModule[12]=C:\WINDOWS\System32\combase.dll LoadedModule[13]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[15]=C:\WINDOWS\System32\sechost.dll LoadedModule[16]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll LoadedModule[17]=C:\Program Files\Lockheed Martin\Prepar3D v4\api.dll LoadedModule[18]=C:\WINDOWS\System32\IMM32.dll LoadedModule[19]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\Cabinet.dll LoadedModule[21]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[22]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[23]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[24]=C:\WINDOWS\System32\ADVAPI32.dll LoadedModule[25]=C:\WINDOWS\System32\msvcrt.dll LoadedModule[26]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.16299.192_none_887f70824ab5b0de\COMCTL32.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[28]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[29]=C:\WINDOWS\System32\cfgmgr32.dll LoadedModule[30]=C:\WINDOWS\System32\shcore.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[32]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[33]=C:\WINDOWS\System32\windows.storage.dll LoadedModule[34]=C:\WINDOWS\System32\shlwapi.dll LoadedModule[35]=C:\WINDOWS\System32\kernel.appcore.dll LoadedModule[36]=C:\WINDOWS\System32\powrprof.dll LoadedModule[37]=C:\WINDOWS\System32\profapi.dll LoadedModule[38]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[39]=C:\Program Files\Lockheed Martin\Prepar3D v4\acontain.dll LoadedModule[40]=C:\Program Files\Lockheed Martin\Prepar3D v4\atc.dll LoadedModule[41]=C:\Program Files\Lockheed Martin\Prepar3D v4\ai_player.dll LoadedModule[42]=C:\Program Files\Lockheed Martin\Prepar3D v4\demo.dll LoadedModule[43]=C:\Program Files\Lockheed Martin\Prepar3D v4\controls.dll LoadedModule[44]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[45]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[46]=C:\Program Files\Lockheed Martin\Prepar3D v4\DIS.dll LoadedModule[47]=C:\Program Files\Lockheed Martin\Prepar3D v4\facilities.dll LoadedModule[48]=C:\Program Files\Lockheed Martin\Prepar3D v4\fe.dll LoadedModule[49]=C:\Program Files\Lockheed Martin\Prepar3D v4\flight.dll LoadedModule[50]=C:\Program Files\Lockheed Martin\Prepar3D v4\fs-traffic.dll LoadedModule[51]=C:\Program Files\Lockheed Martin\Prepar3D v4\gps.dll LoadedModule[52]=C:\Program Files\Lockheed Martin\Prepar3D v4\g3d.dll LoadedModule[53]=C:\Program Files\Lockheed Martin\Prepar3D v4\livingwater.dll LoadedModule[54]=C:\Program Files\Lockheed Martin\Prepar3D v4\g2d.dll LoadedModule[55]=C:\WINDOWS\System32\WLDAP32.dll LoadedModule[56]=C:\Program Files\Lockheed Martin\Prepar3D v4\menus.dll LoadedModule[57]=C:\Program Files\Lockheed Martin\Prepar3D v4\main.dll LoadedModule[58]=C:\WINDOWS\System32\COMDLG32.dll LoadedModule[59]=C:\Program Files\Lockheed Martin\Prepar3D v4\multiplayer.dll LoadedModule[60]=C:\Program Files\Lockheed Martin\Prepar3D v4\pdk.dll LoadedModule[61]=C:\Program Files\Lockheed Martin\Prepar3D v4\panels.dll LoadedModule[62]=C:\Program Files\Lockheed Martin\Prepar3D v4\simscheduler.dll LoadedModule[63]=C:\Program Files\Lockheed Martin\Prepar3D v4\sim1.dll LoadedModule[64]=C:\Program Files\Lockheed Martin\Prepar3D v4\simprop.dll LoadedModule[65]=C:\Program Files\Lockheed Martin\Prepar3D v4\sound.dll LoadedModule[66]=C:\Program Files\Lockheed Martin\Prepar3D v4\symmap.dll LoadedModule[67]=C:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll LoadedModule[68]=C:\Program Files\Lockheed Martin\Prepar3D v4\util.dll LoadedModule[69]=C:\Program Files\Lockheed Martin\Prepar3D v4\visualfx.dll LoadedModule[70]=C:\WINDOWS\SYSTEM32\MSVCP140.dll LoadedModule[71]=C:\WINDOWS\SYSTEM32\CONCRT140.dll LoadedModule[72]=C:\Program Files\Lockheed Martin\Prepar3D v4\weather.dll LoadedModule[73]=C:\Program Files\Lockheed Martin\Prepar3D v4\window.dll LoadedModule[74]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[75]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[76]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[77]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\MFPlat.DLL LoadedModule[79]=C:\Program Files\Lockheed Martin\Prepar3D v4\mplEasyBlendSDKDX1164.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[81]=C:\Program Files\Lockheed Martin\Prepar3D v4\D3DCOMPILER_47.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll LoadedModule[85]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll LoadedModule[86]=C:\Program Files\Lockheed Martin\Prepar3D v4\librti1516e.dll LoadedModule[87]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[88]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[89]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[90]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll LoadedModule[91]=C:\Program Files\Lockheed Martin\Prepar3D v4\dxgi.dll LoadedModule[92]=C:\Program Files\Lockheed Martin\Prepar3D v4\audiere.dll LoadedModule[93]=C:\Program Files\Lockheed Martin\Prepar3D v4\libfedtime1516e.dll LoadedModule[94]=C:\Program Files\Lockheed Martin\Prepar3D v4\OpenRTI.dll LoadedModule[95]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL LoadedModule[96]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[97]=C:\Program Files\Lockheed Martin\Prepar3D v4\language.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\inputhost.dll LoadedModule[99]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll LoadedModule[100]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[102]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[103]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[104]=C:\WINDOWS\SYSTEM32\MSXML6.DLL LoadedModule[105]=C:\Program Files\Lockheed Martin\Prepar3D v4\uiInterface.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[107]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll LoadedModule[108]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll LoadedModule[109]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[110]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\8a9c7ab28dfd1baa08e20283667c4c7e\mscorlib.ni.dll LoadedModule[111]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll LoadedModule[112]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\308a31a8a7d6c1bbc98a29187d026452\System.ni.dll LoadedModule[113]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\591cd3b387a9fb88ead436368131effc\System.Core.ni.dll LoadedModule[114]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\7476d617a17fd34a1755556696d7661b\WindowsBase.ni.dll LoadedModule[115]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[116]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[117]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[118]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[119]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationCore\c4357a944d83cdbc89351bbc2c22eb3c\PresentationCore.ni.dll LoadedModule[120]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\723c295308c9981562fd8f9215240ca8\PresentationFramework.ni.dll LoadedModule[121]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\0dcd91724ed84a5401541432ae92c1b2\System.Xaml.ni.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\dwrite.dll LoadedModule[123]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll LoadedModule[125]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[126]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\75e3f7cd8c8086d5c5b54fb6cf3ee8f2\System.Configuration.ni.dll LoadedModule[127]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\0c032f2c2d3d88c7b46155cb13d8e30d\System.Xml.ni.dll LoadedModule[128]=C:\WINDOWS\system32\dwmapi.dll LoadedModule[129]=C:\WINDOWS\SYSTEM32\iphlpapi.dll LoadedModule[130]=C:\WINDOWS\System32\NSI.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[132]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[133]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[134]=C:\WINDOWS\SYSTEM32\secur32.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[136]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[137]=C:\Windows\System32\rasadhlp.dll LoadedModule[138]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[139]=C:\WINDOWS\system32\dxgi.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[141]=C:\WINDOWS\System32\WINTRUST.dll LoadedModule[142]=C:\WINDOWS\system32\nvapi64.dll LoadedModule[143]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4wui.inf_amd64_393cbe542dcfcdfd\nvldumdx.dll LoadedModule[144]=C:\WINDOWS\System32\imagehlp.dll LoadedModule[145]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4wui.inf_amd64_393cbe542dcfcdfd\nvwgf2umx.dll LoadedModule[146]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[147]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[148]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[149]=C:\WINDOWS\SYSTEM32\CLDAPI.dll LoadedModule[150]=C:\WINDOWS\SYSTEM32\FLTLIB.DLL LoadedModule[151]=C:\WINDOWS\SYSTEM32\AEPIC.dll LoadedModule[152]=C:\Windows\System32\Windows.StateRepositoryPS.dll LoadedModule[153]=C:\WINDOWS\system32\ntshrui.dll LoadedModule[154]=C:\WINDOWS\system32\srvcli.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\cscapi.dll LoadedModule[156]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.192_none_15c8cdae9364c23b\comctl32.dll LoadedModule[157]=C:\WINDOWS\system32\netutils.dll LoadedModule[158]=C:\WINDOWS\System32\coml2.dll LoadedModule[159]=C:\WINDOWS\system32\mssprxy.dll LoadedModule[160]=C:\WINDOWS\SYSTEM32\LINKINFO.dll LoadedModule[161]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[162]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[163]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[164]=C:\Windows\System32\Windows.UI.dll LoadedModule[165]=C:\Windows\System32\TextInputFramework.dll LoadedModule[166]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[167]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[168]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[169]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[170]=C:\Program Files\Lockheed Martin\Prepar3D v4\radar.dll LoadedModule[171]=C:\Program Files\Lockheed Martin\Prepar3D v4\ControllableCamera.dll LoadedModule[172]=C:\Program Files\Lockheed Martin\Prepar3D v4\Gauges\TargetInfo.dll LoadedModule[173]=C:\Program Files\Lockheed Martin\Prepar3D v4\Gauges\Fury_1500.dll LoadedModule[174]=C:\Program Files\Lockheed Martin\Prepar3D v4\Gauges\F-16.dll LoadedModule[175]=C:\Program Files\Lockheed Martin\Prepar3D v4\SimDirector.dll LoadedModule[176]=C:\Program Files\Lockheed Martin\Prepar3D v4\simpropext.dll LoadedModule[177]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[178]=C:\Users\Petros\AppData\Local\Orbx\FTXCentral\v3.2.3.0\Orbx_ObjectFlow_x64.dll LoadedModule[179]=C:\WINDOWS\SYSTEM32\MSVCP120.dll LoadedModule[180]=C:\WINDOWS\SYSTEM32\MSVCR120.dll LoadedModule[181]=C:\Program Files (x86)\Addon Manager\bglmanx64.dll LoadedModule[182]=C:\WINDOWS\System32\psapi.dll LoadedModule[183]=C:\WINDOWS\SYSTEM32\SHFolder.dll LoadedModule[184]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\b227187873642faa120414623621f712\System.Drawing.ni.dll LoadedModule[185]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\795a1cb0756d4bb88b4120baf31f88d3\PresentationFramework.Aero2.ni.dll LoadedModule[186]=C:\WINDOWS\SYSTEM32\urlmon.dll LoadedModule[187]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[188]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[189]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4wui.inf_amd64_393cbe542dcfcdfd\nvd3dumx.dll LoadedModule[190]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationUI\efa2cf70c504be0847cbc9c6c68d2125\PresentationUI.ni.dll LoadedModule[191]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\fbf4ea9b0c6c5588433406a97121f488\System.Windows.Forms.ni.dll LoadedModule[192]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[194]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[195]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[196]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Web\3b16716f76f5fa02cae5325c3224c5ca\System.Web.ni.dll LoadedModule[197]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll LoadedModule[198]=C:\WINDOWS\SYSTEM32\dcomp.dll LoadedModule[199]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\UIAutomationTypes\796da9ee62379ff7c98353cf5e0cca6b\UIAutomationTypes.ni.dll LoadedModule[200]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll LoadedModule[201]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[202]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[203]=C:\WINDOWS\system32\RMCLIENT.dll LoadedModule[204]=C:\WINDOWS\system32\msctfui.dll LoadedModule[205]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Runteb92aa12#\bf472a51537745494d433901b8564196\System.Runtime.Serialization.ni.dll LoadedModule[206]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\SMDiagnostics\c37b6d0a3db6d5d1082e5f44cc1c82ae\SMDiagnostics.ni.dll LoadedModule[207]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Servd1dec626#\e796eab7b3bebad3ff00c187eeec2770\System.ServiceModel.Internals.ni.dll LoadedModule[208]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.16299.192_none_46b3c093edf73c09\gdiplus.dll LoadedModule[209]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\UIAutomationProvider\1ee07ebc6ea6f46af47a65e3f2c7028a\UIAutomationProvider.ni.dll LoadedModule[210]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[211]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[212]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Accessibility\5bf6cf17dd7b6597c5e6f0fbae3edb8e\Accessibility.ni.dll OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=16299 OsInfo[3].Key=ubr OsInfo[3].Value=192 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=2057 OsInfo[7].Key=geoid OsInfo[7].Value=191 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=125286 OsInfo[15].Key=osinsty OsInfo[15].Value=1 OsInfo[16].Key=iever OsInfo[16].Value=11.192.16299.0-11.0.50 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16331 OsInfo[19].Key=svolsz OsInfo[19].Value=1831 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=170928 OsInfo[22].Key=bldtm OsInfo[22].Value=1534 OsInfo[23].Key=bldbrch OsInfo[23].Value=rs3_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.16299.192.amd64fre.rs3_release.170928-1534 OsInfo[30].Key=buildflightid OsInfo[30].Value={9BAFE49B-5C79-488B-8185-E6FF7EC1C2F4}.204 OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=containerid OsInfo[34].Key=containertype OsInfo[35].Key=edu OsInfo[35].Value=0 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Prepar3D exe AppPath=C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=9FB1B8D4FB0CC3149DD52CA673504AF7 MetadataHash=-111423573 EventViewer Log Name: Application Source: Application Error Date: 07/02/2018 16:59:56 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: PETROS Description: Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95 Faulting module name: facilities.dll, version: 4.1.7.22841, time stamp: 0x59d67e03 Exception code: 0xc0000005 Fault offset: 0x0000000000011446 Faulting process ID: 0x24ac Faulting application start time: 0x01d3a02c9ec40173 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\facilities.dll Report ID: 29ead934-2307-4a83-b63a-199355b874a7 Faulting package full name: Faulting package-relative application ID: 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="2018-02-07T15:59:56.222551100Z" /> <EventRecordID>7797</EventRecordID> <Channel>Application</Channel> <Computer>PETROS</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.1.7.22841</Data> <Data>59d67e95</Data> <Data>facilities.dll</Data> <Data>4.1.7.22841</Data> <Data>59d67e03</Data> <Data>c0000005</Data> <Data>0000000000011446</Data> <Data>24ac</Data> <Data>01d3a02c9ec40173</Data> <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\Program Files\Lockheed Martin\Prepar3D v4\facilities.dll</Data> <Data>29ead934-2307-4a83-b63a-199355b874a7</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
February 7, 20188 yr Perhaps the following fix will work for you: 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
February 7, 20188 yr Author Dear Jim, Thanks for your quick response and for trying to help, its highly appreciated. Excuse my ignorance but as far as I know there is no such option in P3D to activate or deactivate scenery like in FSX, right? And if it is, as I said, while the sim loads the startup screen ( control panel), after a few seconds the app crashes, so I have no chance to go to any settings section or so. Would you recommend a clean setup from scratch?
February 7, 20188 yr Author Also I forgot to write that I'm still having FSX:SE installed and using the migration tool, but no scenery was taken yet from FSX to P3D.
February 7, 20188 yr 45 minutes ago, Petspi77 said: Excuse my ignorance but as far as I know there is no such option in P3D to activate or deactivate scenery like in FSX, right? You can disable. If you have Scenery Config Editor, it can be done through that (if you do not have your scenery in Add-on.xmls). If you have Lorby_Si Addon Organizer, you double click on each addon until it turns red. The Lorby_Si Addon Organizer also sees all of the scenery in the scenery.cfg and you can double-click those too and they will be turned off. When you start up P3D, in the Menu you can open up the Scenery Library via the World menu (will have to restart). 51 minutes ago, Petspi77 said: And if it is, as I said, while the sim loads the startup screen ( control panel), after a few seconds the app crashes, so I have no chance to go to any settings section or so. UTLive is one of the modules that loads at startup plus every module in both of your dll.xml's. I would disable UTLive from starting up first by changing Disabled>False<Disabled line to True in the exe.xml. If it is not there, here is the entry: <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>utLive fs client</Name> <Path>C:\PROGRAM FILES\FLIGHT ONE SOFTWARE\ULTIMATE TRAFFIC LIVE\utl_client.exe</Path> <NewConsole>True</NewConsole> As stated in my AVSIM CTD Guide, anything in the dll.xml or exe.xml will be loaded at startup and, if you do not get to the setup screen, it is probably one of these modules. You can quickly determine if it is a module in one of the two dll.xml's or exe.xml's for P3D (one in the same folder as the P3D.cfg and one in the same folder as the scenery.cfg) by renaming the two dll.xml's to dll.xml.off and the two exe.xml's. If you start up to the setup screen, you know where the problem lies (most likely the latest module installed). I always suspect either the fsuipc module or the CMeteo module used by Carenardo. They still continue to install the 32-bit version into P3Dv4.1 when the entry in the dll.xml should be the 64 bit version or CMeteoXmlx64.dll. The faulting module is the facilities.dll and I have never heard of the dll.xml, exe.xml, a bad module ever causing this crash so me thinks you need to figure out what duplicate AFCAD's you have installed. ScruffyDuck has a good program to determine that - http://www.scruffyduck.org/simple-airport-scanner/4584282795. My suggested solution in the link I provided earlier might work but the OP did not indicate it worked so it could be anything. 56 minutes ago, Petspi77 said: Also I forgot to write that I'm still having FSX:SE installed and using the migration tool, but no scenery was taken yet from FSX to P3D. I suspect you are talking about the Orbx Migration Tool? Or the fly by night migration tool many have been using to get products they bought for previous versions of FS in to P3DV4? That tool will create issues. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
February 7, 20188 yr Author Dear Jim, I have renamed the files but the problem still existed, that being said the way you are describing the way to solve the problem it seems that I might have made some wrong moves during this process. I will follow again the procedure and I will post my update. Also thanks for the tool link I'll definitely use it. The migration tool which I'm using is the migration tool Estonia and you are right it can be a hassle. Kind Regards
February 7, 20188 yr Renaming the dll.xml to dll.xml.off saves the file. The default will be rebuilt and placed in the same folder as the scenery.cfg. Are you still getting the facilities.dll as the faulting module? 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
February 7, 20188 yr Author Yes I'm still getting the same fault, but I guess I made a mistake on the directory. In my installation there were two directories with the dll, exe and scenery files. One under the C:\Users\......\AppData\Roaming\Lockheed Martin\Prepar3D v4 and C:\ProgramData\Lockheed Martin\Prepar3D v4 Don't know how and it seems I was messing up with the wrong files at different times. I need to clean this up and start with your solution
February 7, 20188 yr 1 hour ago, Petspi77 said: One under the C:\Users\......\AppData\Roaming\Lockheed Martin\Prepar3D v4 and C:\ProgramData\Lockheed Martin\Prepar3D v4 This is the way I told you only I do not like writing out the directories like you did so just say one is in the same folder as your P3D.cfg and one in the same folder as your scenery.cfg. So, if you renamed the dll.xml to dll.xml.off in both of those folder, restarted, and you still are getting the crash? Never heard of that before. 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
February 9, 20188 yr Author Dear Jim, Yes you are right, now that I renamed the dll's the problem is gone. Also I decided to uninstall my FSX:SE and Estonia migration tool. I hope that now P3D will be stable when installing addons. I want to thank you once again for the support.
February 10, 20188 yr 5 hours ago, Petspi77 said: Dear Jim, Yes you are right, now that I renamed the dll's the problem is gone. Also I decided to uninstall my FSX:SE and Estonia migration tool. I hope that now P3D will be stable when installing addons. I want to thank you once again for the support. Glad you found the Source of your problem. I know the EMT is a popular tool but it does create issues as some products are not installed properly. It only takes one messed up installation to ruin all the fun and enjoyment. 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
Archived
This topic is now archived and is closed to further replies.