STAVKA 4 Posted March 17, 2021 Share Posted March 17, 2021 I have, as mentioned before, the ctd or not ctd depending of load previously any default aircraft. Always on admin mode (my account is full admin) 24GB ram my OS is on C and my msfs on P from ms store, so all the profile folders of msfs were automatically symbolic linked to P drive done automatically by the ms store installer. (but i think here is not the issue, because having this or all msfs on c from what we saw in replies also have ctd). Link to comment Share on other sites More sharing options...
STAVKA 4 Posted March 17, 2021 Share Posted March 17, 2021 Maybe i’m wrong but i think this can be something about variable initialization. It remembers me even from fsx times when some complex airliners only worked well if you previously load the default cessna, if you direct load the airliner some internal vars had random values and aircraft behave wrong. Link to comment Share on other sites More sharing options...
sandpatt 5 Posted March 17, 2021 Share Posted March 17, 2021 I also have my MSFS installation on a different drive than my OS. I don't have a CRJ folder in my community folder after installation (I don't know if it should be there or not) Link to comment Share on other sites More sharing options...
Bent Schrader 4 Posted March 17, 2021 Share Posted March 17, 2021 Just to add my answer and complete the survey: I deleted all files within the folder E:\WpSystem\<SID>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\aerosoft-crj (Where E: is the SSD where I installed the sim to - installation path was E:\FlightSimulator) 1) Rerun the app as administrator. 2) Did this. 3) Community folder is located here: E:\FlightSimulator\Community 4) 32 GB Files within the folder were recreated but CTD after clicking the "Fly" button. Please login to display this image. Link to comment Share on other sites More sharing options...
FS9Guy 1 Posted March 17, 2021 Share Posted March 17, 2021 Is there any differences regarding these issues between users who have MSFS installed on the same drive as their OS, vs. those who don’t? Link to comment Share on other sites More sharing options...
Amer Yordi 0 Posted March 17, 2021 Share Posted March 17, 2021 I hope you can fix it, it’s working fine for me Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted March 17, 2021 Aerosoft Share Posted March 17, 2021 Just now, Amer Yordi said: I hope you can fix it, it’s working fine for me We are still talking to our friends at Asobo, without their help there is not a lot we can do. Link to comment Share on other sites More sharing options...
PhntmV2 8 Posted March 17, 2021 Author Share Posted March 17, 2021 vor 1 minute, Mathijs Kok sagte: We are still talking to our friends at Asobo, without their help there is not a lot we can do. Is there some kind of progress? Can we expect this to be fixed today? Link to comment Share on other sites More sharing options...
sandpatt 5 Posted March 17, 2021 Share Posted March 17, 2021 Because it is difficult for the devs to simulate the issue, please let us know if we need to test/modify/provide prntscreens/... something Link to comment Share on other sites More sharing options...
Mr Mike 11 Posted March 17, 2021 Share Posted March 17, 2021 I Aerosoft doesn't know what the issue is then the chances of it getting resolved today is highly unlikely. Even though they say not many people are having the issue it seems to me more people have it than they think. Link to comment Share on other sites More sharing options...
Bent Schrader 4 Posted March 17, 2021 Share Posted March 17, 2021 vor 1 minute, Mathijs Kok sagte: We are still talking to our friends at Asobo, without their help there is not a lot we can do. Mathijs that is not really the answer I'd expected. We've payed for the product. It seems to me, that Aerosoft see us as a minority? Shouldn't there are any logs that you need for further investigations? I feel pretty disappointed. Link to comment Share on other sites More sharing options...
Mr Mike 11 Posted March 17, 2021 Share Posted March 17, 2021 Here is the crash log from my event viewer. Spoiler Version=1 EventType=MoAppCrash EventTime=132604718450258375 ReportType=2 Consent=1 UploadTime=132604718454060474 ReportStatus=268435456 ReportIdentifier=0e12978b-8bd2-4671-9288-c3100173c786 IntegratorReportIdentifier=87f58f01-740d-499c-a692-2f3b3612db82 Wow64Host=34404 NsAppName=praid:App AppSessionGuid=000028c0-0001-000c-81e7-c738491bd701 TargetAppId=U:Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe!App TargetAppVer=1.14.5.0_x64_!2021//03//04:10:33:55!0!FlightSimulator.exe BootId=4294967295 ServiceSplit=3917995852 TargetAsId=1510 UserImpactVector=808464656 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=884505045bf69e90145f09506f317074 Response.BucketTable=5 Response.LegacyBucketId=1467902244613615732 Response.type=4 Sig[0].Name=Package Full Name Sig[0].Value=Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe Sig[1].Name=Application Name Sig[1].Value=praid:App Sig[2].Name=Application Version Sig[2].Value=0.0.0.0 Sig[3].Name=Application Timestamp Sig[3].Value=6040b793 Sig[4].Name=Fault Module Name Sig[4].Value=FlightSimulator.exe Sig[5].Name=Fault Module Version Sig[5].Value=0.0.0.0 Sig[6].Name=Fault Module Timestamp Sig[6].Value=6040b793 Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Offset Sig[8].Value=000000000188bf77 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.19041.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=f4dd DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=f4ddfa2c7c172935124c29289134ac2e DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=f6c7 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=f6c7765c9ed67b30e1db176646be6bf7 UI[2]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe LoadedModule[0]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.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\USER32.dll LoadedModule[5]=C:\windows\System32\win32u.dll LoadedModule[6]=C:\windows\System32\GDI32.dll LoadedModule[7]=C:\windows\System32\gdi32full.dll LoadedModule[8]=C:\windows\System32\msvcp_win.dll LoadedModule[9]=C:\windows\SYSTEM32\WINMM.dll LoadedModule[10]=C:\windows\SYSTEM32\dwmapi.dll LoadedModule[11]=C:\windows\System32\ucrtbase.dll LoadedModule[12]=C:\windows\System32\msvcrt.dll LoadedModule[13]=C:\windows\System32\combase.dll LoadedModule[14]=C:\windows\System32\COMDLG32.dll LoadedModule[15]=C:\windows\System32\RPCRT4.dll LoadedModule[16]=C:\windows\System32\shcore.dll LoadedModule[17]=C:\windows\System32\SHLWAPI.dll LoadedModule[18]=C:\windows\System32\SHELL32.dll LoadedModule[19]=C:\windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.844_none_ca00b6081b84eb1d\COMCTL32.dll LoadedModule[20]=C:\windows\System32\ADVAPI32.dll LoadedModule[21]=C:\windows\System32\sechost.dll LoadedModule[22]=C:\windows\System32\ole32.dll LoadedModule[23]=C:\windows\System32\OLEAUT32.dll LoadedModule[24]=C:\windows\System32\IMM32.dll LoadedModule[25]=C:\windows\System32\CRYPT32.dll LoadedModule[26]=C:\windows\System32\WS2_32.dll LoadedModule[27]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\MSVCP140.dll LoadedModule[28]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\CONCRT140.dll LoadedModule[29]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCOMP140.DLL LoadedModule[30]=C:\windows\System32\bcrypt.dll LoadedModule[31]=C:\windows\System32\WLDAP32.dll LoadedModule[32]=C:\windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.19041.789_none_faf0a7e97612e7bb\gdiplus.dll LoadedModule[33]=C:\windows\SYSTEM32\VERSION.dll LoadedModule[34]=C:\windows\SYSTEM32\DINPUT8.dll LoadedModule[35]=C:\windows\SYSTEM32\WSOCK32.dll LoadedModule[36]=C:\windows\SYSTEM32\Cabinet.dll LoadedModule[37]=C:\windows\SYSTEM32\WTSAPI32.dll LoadedModule[38]=C:\windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[39]=C:\windows\SYSTEM32\dxgi.dll LoadedModule[40]=C:\windows\SYSTEM32\d3d11.dll LoadedModule[41]=C:\windows\SYSTEM32\MFPlat.DLL LoadedModule[42]=C:\windows\System32\cfgmgr32.dll LoadedModule[43]=C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll LoadedModule[44]=C:\windows\SYSTEM32\srvcli.dll LoadedModule[45]=C:\windows\SYSTEM32\netutils.dll LoadedModule[46]=C:\windows\SYSTEM32\DNSAPI.dll LoadedModule[47]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\VCRUNTIME140_1.dll LoadedModule[48]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\Microsoft.CognitiveServices.Speech.core.dll LoadedModule[49]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\WwiseLibPCx64P.dll LoadedModule[50]=C:\windows\System32\SETUPAPI.dll LoadedModule[51]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\lib_json.dll LoadedModule[52]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\libcrypto-1_1-x64.dll LoadedModule[53]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\amd_ags_x64.dll LoadedModule[54]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\libcurl.dll LoadedModule[55]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\XPlatCppWindows.dll LoadedModule[56]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\GFSDK_Aftermath_Lib.x64.dll LoadedModule[57]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll LoadedModule[58]=C:\windows\SYSTEM32\AVIFIL32.dll LoadedModule[59]=C:\windows\SYSTEM32\WINHTTP.dll LoadedModule[60]=C:\windows\SYSTEM32\dbghelp.dll LoadedModule[61]=C:\windows\SYSTEM32\Secur32.dll LoadedModule[62]=C:\windows\SYSTEM32\ncrypt.dll LoadedModule[63]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\openxr_loader.dll LoadedModule[64]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\zlib.dll LoadedModule[65]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\nghttp2.dll LoadedModule[66]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\libssl-1_1-x64.dll LoadedModule[67]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\libssh2.dll LoadedModule[68]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\MicrosoftGeospatialTiles.dll LoadedModule[69]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\RenoirCore.WindowsDesktop.dll LoadedModule[70]=C:\windows\SYSTEM32\MSVFW32.dll LoadedModule[71]=C:\windows\SYSTEM32\MSACM32.dll LoadedModule[72]=C:\windows\SYSTEM32\DWrite.dll LoadedModule[73]=C:\windows\SYSTEM32\winmmbase.dll LoadedModule[74]=C:\windows\SYSTEM32\SSPICLI.DLL LoadedModule[75]=C:\windows\SYSTEM32\MSWSOCK.DLL LoadedModule[76]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\WTF.dll LoadedModule[77]=C:\windows\System32\PSAPI.DLL LoadedModule[78]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\CoherentGTJS.dll LoadedModule[79]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\coherenticuuc.dll LoadedModule[80]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\CoherentGTCore.dll LoadedModule[81]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\coherenticuin.dll LoadedModule[82]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\icudtcoherent53.dll LoadedModule[83]=C:\windows\SYSTEM32\kernel.appcore.dll LoadedModule[84]=C:\windows\System32\bcryptPrimitives.dll LoadedModule[85]=C:\windows\SYSTEM32\RTWorkQ.DLL LoadedModule[86]=C:\windows\SYSTEM32\NTASN1.dll LoadedModule[87]=C:\windows\System32\NSI.dll LoadedModule[88]=C:\windows\SYSTEM32\inputhost.dll LoadedModule[89]=C:\windows\SYSTEM32\wintypes.dll LoadedModule[90]=C:\windows\SYSTEM32\CoreMessaging.dll LoadedModule[91]=C:\windows\SYSTEM32\PROPSYS.dll LoadedModule[92]=C:\windows\SYSTEM32\CoreUIComponents.dll LoadedModule[93]=C:\windows\SYSTEM32\ntmarta.dll LoadedModule[94]=C:\windows\System32\clbcatq.dll LoadedModule[95]=C:\Windows\System32\Windows.ApplicationModel.dll LoadedModule[96]=C:\Windows\System32\twinapi.appcore.dll LoadedModule[97]=C:\Windows\System32\Windows.Storage.ApplicationData.dll LoadedModule[98]=C:\windows\SYSTEM32\windows.storage.dll LoadedModule[99]=C:\Windows\System32\Wldp.dll LoadedModule[100]=C:\windows\SYSTEM32\profapi.dll LoadedModule[101]=C:\Windows\System32\Windows.FileExplorer.Common.dll LoadedModule[102]=C:\Windows\System32\iertutil.dll LoadedModule[103]=C:\windows\system32\mssprxy.dll LoadedModule[104]=C:\windows\system32\uxtheme.dll LoadedModule[105]=C:\windows\System32\MSCTF.dll LoadedModule[106]=C:\windows\SYSTEM32\textinputframework.dll LoadedModule[107]=C:\windows\SYSTEM32\RICHED32.DLL LoadedModule[108]=C:\windows\SYSTEM32\RICHED20.dll LoadedModule[109]=C:\windows\SYSTEM32\USP10.dll LoadedModule[110]=C:\windows\SYSTEM32\msls31.dll LoadedModule[111]=C:\windows\SYSTEM32\TextShaping.dll LoadedModule[112]=C:\windows\SYSTEM32\WINSTA.dll LoadedModule[113]=C:\windows\SYSTEM32\msasn1.dll LoadedModule[114]=C:\windows\SYSTEM32\cryptnet.dll LoadedModule[115]=C:\windows\SYSTEM32\cryptbase.dll LoadedModule[116]=C:\windows\System32\WINTRUST.DLL LoadedModule[117]=C:\windows\System32\imagehlp.dll LoadedModule[118]=C:\windows\SYSTEM32\CRYPTSP.dll LoadedModule[119]=C:\windows\system32\rsaenh.dll LoadedModule[120]=C:\windows\system32\nvspcap64.dll LoadedModule[121]=C:\windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_c1f92232e461624f\nvldumdx.dll LoadedModule[122]=C:\windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_c1f92232e461624f\nvwgf2umx_cfg.dll LoadedModule[123]=C:\windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_c1f92232e461624f\NvCamera\NvCamera64.dll LoadedModule[124]=C:\windows\SYSTEM32\HID.DLL LoadedModule[125]=C:\windows\SYSTEM32\XINPUT9_1_0.dll LoadedModule[126]=C:\windows\SYSTEM32\WindowsCodecs.dll LoadedModule[127]=C:\windows\SYSTEM32\dxcore.dll LoadedModule[128]=C:\windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_c1f92232e461624f\NvCamera\d3dcompiler_47_64.dll LoadedModule[129]=C:\windows\SYSTEM32\nvapi64.dll LoadedModule[130]=C:\windows\SYSTEM32\dcomp.dll LoadedModule[131]=C:\windows\SYSTEM32\DEVOBJ.dll LoadedModule[132]=C:\windows\SYSTEM32\xgameruntime.dll LoadedModule[133]=C:\windows\SYSTEM32\GameConfigHelper.dll LoadedModule[134]=C:\windows\SYSTEM32\MFReadWrite.dll LoadedModule[135]=C:\Windows\System32\XblAuthManagerProxy.dll LoadedModule[136]=C:\windows\system32\GamingServicesProxy.dll LoadedModule[137]=C:\Windows\System32\msxml6.dll LoadedModule[138]=C:\Windows\System32\Windows.Networking.Connectivity.dll LoadedModule[139]=C:\Windows\System32\wpnapps.dll LoadedModule[140]=C:\Windows\System32\RMCLIENT.dll LoadedModule[141]=C:\Windows\System32\XmlLite.dll LoadedModule[142]=C:\windows\SYSTEM32\usermgrcli.dll LoadedModule[143]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll LoadedModule[144]=C:\Windows\System32\usermgrproxy.dll LoadedModule[145]=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll LoadedModule[146]=C:\Windows\System32\OneCoreCommonProxyStub.dll LoadedModule[147]=C:\Windows\System32\vaultcli.dll LoadedModule[148]=C:\Windows\System32\Windows.StateRepositoryPS.dll LoadedModule[149]=C:\Windows\System32\XblAuthTokenBrokerExt.dll LoadedModule[150]=C:\Windows\System32\threadpoolwinrt.dll LoadedModule[151]=C:\windows\System32\MMDevApi.dll LoadedModule[152]=C:\Windows\System32\CryptoWinRT.dll LoadedModule[153]=C:\windows\SYSTEM32\Xinput1_4.dll LoadedModule[154]=C:\Program Files\NVIDIA Corporation\NvContainer\MessageBus.dll LoadedModule[155]=C:\windows\SYSTEM32\dhcpcsvc.DLL LoadedModule[156]=C:\windows\system32\wbem\wbemprox.dll LoadedModule[157]=C:\windows\SYSTEM32\wbemcomn.dll LoadedModule[158]=C:\windows\system32\wbem\wbemsvc.dll LoadedModule[159]=C:\windows\system32\wbem\fastprox.dll LoadedModule[160]=C:\windows\SYSTEM32\amsi.dll LoadedModule[161]=C:\windows\SYSTEM32\USERENV.dll LoadedModule[162]=C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.2102.4-0\MpOav.dll LoadedModule[163]=C:\windows\SYSTEM32\XAudio2_9.dll LoadedModule[164]=C:\windows\SYSTEM32\AVRT.dll LoadedModule[165]=C:\windows\SYSTEM32\AUDIOSES.DLL LoadedModule[166]=C:\windows\SYSTEM32\powrprof.dll LoadedModule[167]=C:\windows\SYSTEM32\UMPDC.dll LoadedModule[168]=C:\windows\SYSTEM32\resourcepolicyclient.dll LoadedModule[169]=C:\Windows\System32\Windows.Perception.Stub.dll LoadedModule[170]=C:\Windows\System32\Windows.UI.dll LoadedModule[171]=C:\Windows\System32\WindowManagementAPI.dll LoadedModule[172]=C:\Windows\System32\MFMediaEngine.dll LoadedModule[173]=C:\Windows\System32\Windows.Media.MediaControl.dll LoadedModule[174]=C:\Windows\System32\Windows.Media.Devices.dll LoadedModule[175]=C:\windows\System32\mfcore.dll LoadedModule[176]=C:\windows\System32\ksuser.dll LoadedModule[177]=C:\windows\SYSTEM32\CompPkgSup.DLL LoadedModule[178]=C:\Windows\System32\Windows.Media.dll LoadedModule[179]=C:\Windows\System32\AppXDeploymentClient.dll LoadedModule[180]=C:\windows\System32\mfmp4srcsnk.dll LoadedModule[181]=C:\windows\System32\mfsvr.dll LoadedModule[182]=C:\windows\System32\msvproc.dll LoadedModule[183]=C:\Windows\System32\MSAudDecMFT.dll LoadedModule[184]=C:\Windows\System32\mfperfhelper.dll LoadedModule[185]=C:\Windows\System32\msmpeg2vdec.dll LoadedModule[186]=C:\Windows\System32\mfps.dll LoadedModule[187]=C:\windows\System32\npmproxy.dll LoadedModule[188]=C:\Windows\System32\dusmapi.dll LoadedModule[189]=C:\Windows\System32\Windows.Networking.HostName.dll LoadedModule[190]=C:\windows\System32\netprofm.dll LoadedModule[191]=C:\windows\SYSTEM32\sxs.dll LoadedModule[192]=C:\windows\SYSTEM32\WINNSI.DLL LoadedModule[193]=C:\windows\SYSTEM32\dhcpcsvc6.DLL LoadedModule[194]=C:\windows\SYSTEM32\webio.dll LoadedModule[195]=C:\Windows\System32\Windows.Web.dll LoadedModule[196]=C:\Windows\System32\rasadhlp.dll LoadedModule[197]=C:\windows\System32\fwpuclnt.dll LoadedModule[198]=C:\Windows\System32\Windows.ApplicationModel.Store.dll LoadedModule[199]=C:\Windows\System32\webservices.dll LoadedModule[200]=C:\windows\system32\napinsp.dll LoadedModule[201]=C:\windows\system32\pnrpnsp.dll LoadedModule[202]=C:\windows\system32\wshbth.dll LoadedModule[203]=C:\windows\system32\NLAapi.dll LoadedModule[204]=C:\windows\System32\winrnr.dll LoadedModule[205]=C:\Windows\System32\wuapi.dll LoadedModule[206]=C:\Windows\System32\wups.dll LoadedModule[207]=C:\windows\system32\schannel.DLL LoadedModule[208]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[209]=C:\Windows\System32\bcp47mrm.dll LoadedModule[210]=C:\Windows\System32\Bcp47Langs.dll LoadedModule[211]=C:\windows\SYSTEM32\DPAPI.DLL LoadedModule[212]=C:\Windows\System32\Windows.Web.Http.dll LoadedModule[213]=C:\Windows\System32\WININET.dll LoadedModule[214]=C:\windows\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[215]=C:\windows\SYSTEM32\firewallapi.dll LoadedModule[216]=C:\windows\SYSTEM32\fwbase.dll LoadedModule[217]=C:\windows\SYSTEM32\profext.dll LoadedModule[218]=C:\Windows\System32\urlmon.dll LoadedModule[219]=C:\windows\SYSTEM32\mskeyprotect.dll LoadedModule[220]=C:\windows\system32\ncryptsslp.dll LoadedModule[221]=C:\Windows\System32\certenroll.dll LoadedModule[222]=C:\Windows\System32\certca.dll LoadedModule[223]=C:\Windows\System32\DSPARSE.dll LoadedModule[224]=C:\windows\system32\mlang.dll LoadedModule[225]=C:\Windows\System32\Windows.Security.Authentication.OnlineId.dll LoadedModule[226]=C:\Users\mykey\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\bf-pgg\PGG\grammar.pggmod LoadedModule[227]=C:\windows\system32\wmphoto.dll LoadedModule[228]=C:\Users\mykey\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\aerosoft-crj\m4e01a9f8_0.dll LoadedModule[229]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\SimConnect.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=19041 OsInfo[3].Key=ubr OsInfo[3].Value=867 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 OsInfo[8].Key=sku OsInfo[8].Value=48 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 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=221005170 OsInfo[15].Key=osinsty OsInfo[15].Value=1 OsInfo[16].Key=iever OsInfo[16].Value=11.789.19041.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=32689 OsInfo[19].Key=svolsz OsInfo[19].Value=930 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=191206 OsInfo[22].Key=bldtm OsInfo[22].Value=1406 OsInfo[23].Key=bldbrch OsInfo[23].Value=vb_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.19041.867.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Professional OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[34].Key=fconid OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 FriendlyEventName=Stopped working ConsentKey=MoAppCrash AppName=FlightSimulator.exe AppPath=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=8A2BFF63AF7202D91ACE5934BA1303C4 MetadataHash=379054432 I am not sure what MoAppCrash is but that seems to be where it is pointing to. Link to comment Share on other sites More sharing options...
Mr Mike 11 Posted March 17, 2021 Share Posted March 17, 2021 Could be a C++ file from what I am researching. It was suggested to repair it. I have several in my windows apps so i repaired just the 2015 version and it did not fix the issue. Link to comment Share on other sites More sharing options...
Manny 41 Posted March 17, 2021 Share Posted March 17, 2021 I managed to load the CRJwith all systems working... it looked like it. I moved the aircraft to KDFW and loaded a saved flt pl KDFWKIAH and stook off but then when reaching 5000 feet, CTDs. Spoiler APP CRASH Info Last few lines -------------------------------- LoadedModule[200]=C:\Windows\system32\wmphoto.dll LoadedModule[201]=C:\Users\cpgmm\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\aerosoft-crj\m25e98d15_0.dll LoadedModule[202]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\SimConnect.dll LoadedModule[203]=C:\Windows\SYSTEM32\daxexec.dll LoadedModule[204]=C:\Windows\SYSTEM32\container.dll LoadedModule[205]=C:\Windows\SYSTEM32\FLTLIB.DLL State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=19041 OsInfo[3].Key=ubr OsInfo[3].Value=867 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 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=221005218 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.789.19041.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=32669 OsInfo[19].Key=svolsz OsInfo[19].Value=476 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=191206 OsInfo[22].Key=bldtm OsInfo[22].Value=1406 OsInfo[23].Key=bldbrch OsInfo[23].Value=vb_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.19041.867.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[34].Key=fconid OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 FriendlyEventName=Stopped working ConsentKey=MoAppCrash AppName=FlightSimulator.exe AppPath=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=8A2BFF63AF7202D91ACE5934BA1303C4 MetadataHash=122435902 Link to comment Share on other sites More sharing options...
Developer Hans Hartmann 3694 Posted March 17, 2021 Developer Share Posted March 17, 2021 There's not much that you or us can do right now. There is progress, but no solution yet. That's all I can say. Link to comment Share on other sites More sharing options...
Manny 41 Posted March 17, 2021 Share Posted March 17, 2021 4 minutes ago, Hans Hartmann said: There's not much that you or us can do right now. There is progress, but no solution yet. That's all I can say. Thanks Hans You guys/Asobo have realized there is an issue...right? That's half the solution. Did you or Asobo manage to recreate this problem at y'alls end? Link to comment Share on other sites More sharing options...
podzob 11 Posted March 17, 2021 Share Posted March 17, 2021 18 minutes ago, Hans Hartmann said: There's not much that you or us can do right now. There is progress, but no solution yet. That's all I can say. I just managed to launch it, in developer mode, by launching a flight with the DR400 at the end of the runway without a flight plan and then loading it. I was able to enjoy the cockpit and the exterior for 5 minutes up to 2500 feet and had a CTD. I still think that the problem is not with ASOBO, but rather with the files and contents of the CRJ folder. Considering the number of people concerned, we cannot call this an 'isolated case'. I do not understand that such a problem was not spotted earlier before release. Link to comment Share on other sites More sharing options...
The 10 Mile Final 1 Posted March 17, 2021 Share Posted March 17, 2021 1 hour ago, Bent Schrader said: Mathijs that is not really the answer I'd expected. We've payed for the product. It seems to me, that Aerosoft see us as a minority? Shouldn't there are any logs that you need for further investigations? I feel pretty disappointed. I know you're upset and a bit disappointed but you have to realize the MSFS dev team have not put together a robust development kit for 3rd party companies. They are limited in what they can see and do based on what information the MSFS dev team give Aerosoft. Luckily my copy was fine and installed first try. What I would suggest is making a copy of your community folder and then deleting all content within that folder. There could be a common addon that's causing issues. An example of this is how initially the PMP A330 was not compatible with the FBW A320. A compatibility mod had to be created so they functioned well together. Also perform a clean install of the CRJ again and ensure it is run as administrator. Lastly, run MSFS as an administrator to ensure it can use as much system resources as it needs. Link to comment Share on other sites More sharing options...
FlyByWire128 42 Posted March 17, 2021 Share Posted March 17, 2021 6 minutes ago, podzob said: I do not understand that such a problem was not spotted earlier before release. Given the number of posts here compared to the (presumed) number of purchased/downloaded/installed copies of the CRJ, I have to assume that this issue does not occur that frequently. It's entirely plausible that it was not seen during development (so Aerosoft can't be expected to have solved a problem they don't know about). There are so many combinations of hardware/software that folks are using to run MSFS that these issues sometimes aren't revealed until launch day. I'm sure @Mathijs Kok and team are doing everything in their power to find a fix to these issues; it just takes time... Link to comment Share on other sites More sharing options...
Manny 41 Posted March 17, 2021 Share Posted March 17, 2021 The testing focus must have been on the CRJ itself and fixing issues related to the realism of CRJ..rather than on the install and running of the said program. Thats why there aren't that many bugs reported by people who are flying the CRJ. Link to comment Share on other sites More sharing options...
PhntmV2 8 Posted March 17, 2021 Author Share Posted March 17, 2021 vor 16 Minuten, LaDarious Shine sagte: I know you're upset and a bit disappointed but you have to realize the MSFS dev team have not put together a robust development kit for 3rd party companies. They are limited in what they can see and do based on what information the MSFS dev team give Aerosoft. Luckily my copy was fine and installed first try. What I would suggest is making a copy of your community folder and then deleting all content within that folder. There could be a common addon that's causing issues. An example of this is how initially the PMP A330 was not compatible with the FBW A320. A compatibility mod had to be created so they functioned well together. Also perform a clean install of the CRJ again and ensure it is run as administrator. Lastly, run MSFS as an administrator to ensure it can use as much system resources as it needs. Every single point you mentioned has already been tested by many people. It didnt fix anything. Link to comment Share on other sites More sharing options...
podzob 11 Posted March 17, 2021 Share Posted March 17, 2021 18 minutes ago, FlyByWire128 said: Compte tenu du nombre de messages ici par rapport au nombre (présumé) de copies achetées / téléchargées / installées du CRJ, je dois supposer que ce problème ne se produit pas si souvent. Il est tout à fait plausible que cela n'ait pas été vu pendant le développement (on ne peut donc pas s'attendre à ce qu'Aerosoft ait résolu un problème qu'ils ne connaissent pas). Il y a tellement de combinaisons de matériel / logiciel que les gens utilisent pour exécuter MSFS que ces problèmes ne sont parfois pas révélés avant le jour du lancement. Je suis sûr@Mathijs Koket l'équipe fait tout ce qui est en son pouvoir pour trouver une solution à ces problèmes; cela prend juste du temps ... It's been 7 months since MSFS came out. I add once again that without going by chance on this forum, no response to the support ticket for 24 hours. And when I say the forum, beyond an answer 'we are waiting for the return of ASOBO' I'm sorry but I want to laugh, I feel like it's a bad joke. If Asobo has to adapt its code each time payware is released, I wonder what it will look like with addons like A2A accusim Link to comment Share on other sites More sharing options...
The 10 Mile Final 1 Posted March 17, 2021 Share Posted March 17, 2021 30 minutes ago, podzob said: It's been 7 months since MSFS came out. I add once again that without going by chance on this forum, no response to the support ticket for 24 hours. And when I say the forum, beyond an answer 'we are waiting for the return of ASOBO' I'm sorry but I want to laugh, I feel like it's a bad joke. If Asobo has to adapt its code each time payware is released, I wonder what it will look like with addons like A2A accusim You do know that Asobo hasn't fully developed an all inclusive development kit right? You know that has been stated by numerous companies in the payware space right? You all just comment and post off of emotion instead of looking at thing objectively. We all see with every world update a new set of bugs and broken items. Flaps being one recently. Until Asobo finalizes there code which, will not be until summer at the earliest with the DX12 integration, there will be problems and payware developers will need to contact Asobo until a robust all inclusive developer kit is made. Asobo, from what I've read from other developers, is keeping MSFS very close to heart when it comes to debugging log files. Link to comment Share on other sites More sharing options...
Developer Hans Hartmann 3694 Posted March 17, 2021 Developer Share Posted March 17, 2021 55 minutes ago, FlyByWire128 said: Given the number of posts here compared to the (presumed) number of purchased/downloaded/installed copies of the CRJ, I have to assume that this issue does not occur that frequently. It's entirely plausible that it was not seen during development (so Aerosoft can't be expected to have solved a problem they don't know about). You're right. Not even one of the testers reported any problems with CTDs. 34 minutes ago, podzob said: It's been 7 months since MSFS came out. Yes, and the number of WASM-based aircraft is..... one. And it was released yesterday. This is complete first and nothing like it existed before. It was to be expected that the beta test wouldn't catch all problems, although the CTD issue caught us by surprise. 1 hour ago, podzob said: I still think that the problem is not with ASOBO, but rather with the files and contents of the CRJ folder. Asobo thinks differently.... Link to comment Share on other sites More sharing options...
PropFlyer93 0 Posted March 17, 2021 Share Posted March 17, 2021 I bought it from the Sim Market yesterday didn't get to fly it till today well it wont even load into the sim looked in all my local files with no files that mention the 'M' files nor the plane it self but I can see it in sim select it and go to make a flight while loading I CTD every time. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.