Francescom 4 Posted January 5, 2016 Author Share Posted January 5, 2016 Dear Dave, yes I confirm that yesterday the Sim did not crash, but I think is a case to be investigate deeply. As you compare the FlightPlan, is very similar to the FlightPlan of my first post, so I think that a Crash could happen again in the same route. Just to add additional info: Windows Update is always OFF when I use Flight Simulator (To avoid automatic Download, additional work on CPU and Network) NOD 32 Antivitus is Temporary disabled when I use Flight Simulator both for Online and Offline session (to avoid Update and Additional Work on CPU) Just for info do you need also of a MiniDump report? I'll continue to try in these days. Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 5, 2016 Author Share Posted January 5, 2016 Dear Dave, here we go! I had a Crash usind DIR TO. Here below the configuration: Airbus A319-112 Winglet. ZFW: 55.3 Block Fuel 5500 KG. CG 23% . COST INDEX: 50 Flight Plan LIRP UM729 GEN UM858 UNITA UL50 ELB UM729 NORNI FL 220 I climbed out initially to SPEZI POINT. Inbound SPEZI I Pushed DIR TO " LUKIM" point (on UM729 Airway). I got FL 220 inbound Lukim and I pushed again DIR TO GEN VOR (still on UM729). Approximately 30 NM to GEN VOR I Pushed Again DIR TO inbound PIBUM (on UM 858 Airway). Finally I pushed DIR TO inbound UNITA (UL50 Airway) and the Sim after 3 Second crashed. I Attached the following files: - FSX minidump (created from Sysinternal Process Explorer) - Application Error Log (in Italian sorry) - Airbus Folder. I am at your disposal if you need some other info or other tests. Regards Error log.txt fsx-Crash Minidump.zip Airbus.zip Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 6, 2016 Share Posted January 6, 2016 AppCrashView Frances, Thank you for the information. Would you please do me a favor and download AppCrashView (English version if that's possible for you to work with), open AppCrashView and go to the Crash/Hang, and copy that info and past into this thread? That would be a big help to me. Thanks! Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 6, 2016 Author Share Posted January 6, 2016 Dear Daves, here below the report: Version=1 EventType=APPCRASH EventTime=130965006269638855 ReportType=2 Consent=1 UploadTime=130965006270186143 ReportIdentifier=f25866c1-b3ed-11e5-82d8-bcee7b8b6caa IntegratorReportIdentifier=f25866c0-b3ed-11e5-82d8-bcee7b8b6caa WOW64=1 NsAppName=fsx.exe Response.BucketId=87f42755d24f26807ba705a309b31e38 Response.BucketTable=1 Response.LegacyBucketId=74083966432 Response.type=4 Sig[0].Name=Nome applicazione Sig[0].Value=fsx.exe Sig[1].Name=Versione applicazione Sig[1].Value=10.0.61637.0 Sig[2].Name=Timestamp applicazione Sig[2].Value=46fadb14 Sig[3].Name=Nome modulo con errori Sig[3].Value=FMGS.DLL Sig[4].Name=Versione modulo con errori Sig[4].Value=1.2.7.82 Sig[5].Name=Timestamp modulo con errori Sig[5].Value=552db3f3 Sig[6].Name=Codice eccezione Sig[6].Value=c0000005 Sig[7].Name=Offset eccezione Sig[7].Value=00036b03 DynamicSig[1].Name=Versione SO DynamicSig[1].Value=6.3.9600.2.0.0.768.101 DynamicSig[2].Name=ID impostazioni locali DynamicSig[2].Value=1040 DynamicSig[22].Name=Informazioni aggiuntive 1 DynamicSig[22].Value=5861 DynamicSig[23].Name=Ulteriori informazioni 2 DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2 DynamicSig[24].Name=Ulteriori informazioni 3 DynamicSig[24].Value=a10f DynamicSig[25].Name=Ulteriori informazioni 4 DynamicSig[25].Value=a10ff7d2bb2516fdc753f9c34fc3b069 UI[2]=C:\FlightSimulator\fsx.exe UI[3]=Microsoft Flight Simulator® ha smesso di funzionare UI[4]=Windows: è possibile ricercare online una soluzione al problema. UI[5]=Cerca una soluzione online e chiudi il programma UI[6]=Cerca una soluzione online in seguito e chiudi il programma UI[7]=Chiudi il programma LoadedModule[0]=C:\FlightSimulator\fsx.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\apphelp.dll LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll LoadedModule[11]=C:\Windows\SYSTEM32\OLEAUT32.dll LoadedModule[12]=C:\Windows\SYSTEM32\MPR.dll LoadedModule[13]=C:\Windows\SYSTEM32\SETUPAPI.dll LoadedModule[14]=C:\Windows\SYSTEM32\sfc.dll LoadedModule[15]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[16]=C:\Windows\SYSTEM32\RPCRT4.dll LoadedModule[17]=C:\Windows\SYSTEM32\combase.dll LoadedModule[18]=C:\Windows\SYSTEM32\CFGMGR32.dll LoadedModule[19]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[20]=C:\Windows\SYSTEM32\sfc_os.DLL LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll LoadedModule[22]=C:\Windows\SYSTEM32\sechost.dll LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[24]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[25]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17810_none_7c5b6194aa0716f1\COMCTL32.dll LoadedModule[26]=C:\Windows\SYSTEM32\mscms.dll LoadedModule[27]=C:\Windows\SYSTEM32\ADVAPI32.dll LoadedModule[28]=C:\Windows\SYSTEM32\ole32.dll LoadedModule[29]=C:\Windows\SYSTEM32\WINMM.dll LoadedModule[30]=C:\Windows\SYSTEM32\DDRAW.dll LoadedModule[31]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[32]=C:\Windows\SYSTEM32\COMDLG32.dll LoadedModule[33]=C:\Windows\SYSTEM32\IMM32.dll LoadedModule[34]=C:\Windows\SYSTEM32\WS2_32.dll LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll LoadedModule[36]=C:\Windows\SYSTEM32\msi.dll LoadedModule[37]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[38]=C:\Windows\SYSTEM32\DCIMAN32.dll LoadedModule[39]=C:\Windows\SYSTEM32\profapi.dll LoadedModule[40]=C:\Windows\SYSTEM32\SHCORE.DLL LoadedModule[41]=C:\Windows\SYSTEM32\MSCTF.dll LoadedModule[42]=C:\Windows\SYSTEM32\NSI.dll LoadedModule[43]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2\MFC80.DLL LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.42_none_0e9c2a8d74fd3ce6\MFC80ITA.DLL LoadedModule[47]=C:\FlightSimulator\language.dll LoadedModule[48]=C:\FlightSimulator\API.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll LoadedModule[50]=C:\FlightSimulator\ablscpt.dll LoadedModule[51]=C:\FlightSimulator\acontain.dll LoadedModule[52]=C:\FlightSimulator\ai_player.dll LoadedModule[53]=C:\FlightSimulator\atc.dll LoadedModule[54]=C:\FlightSimulator\controls.dll LoadedModule[55]=C:\FlightSimulator\demo.dll LoadedModule[56]=C:\FlightSimulator\facilities.dll LoadedModule[57]=C:\FlightSimulator\fe.dll LoadedModule[58]=C:\FlightSimulator\flight.dll LoadedModule[59]=C:\FlightSimulator\fsui.dll LoadedModule[60]=C:\FlightSimulator\g2d.dll LoadedModule[61]=C:\FlightSimulator\g3d.dll LoadedModule[62]=C:\FlightSimulator\gps.dll LoadedModule[63]=C:\FlightSimulator\livingwater.dll LoadedModule[64]=C:\FlightSimulator\main.dll LoadedModule[65]=C:\FlightSimulator\multiplayer.dll LoadedModule[66]=C:\FlightSimulator\panels.dll LoadedModule[67]=C:\FlightSimulator\sim1.dll LoadedModule[68]=C:\FlightSimulator\simprop.dll LoadedModule[69]=C:\FlightSimulator\simscheduler.dll LoadedModule[70]=C:\FlightSimulator\sound.dll LoadedModule[71]=C:\FlightSimulator\symmap.dll LoadedModule[72]=C:\FlightSimulator\terrain.dll LoadedModule[73]=C:\FlightSimulator\fs-traffic.dll LoadedModule[74]=C:\FlightSimulator\ui.dll LoadedModule[75]=C:\FlightSimulator\util.dll LoadedModule[76]=C:\FlightSimulator\visualfx.dll LoadedModule[77]=C:\FlightSimulator\weather.dll LoadedModule[78]=C:\FlightSimulator\window.dll LoadedModule[79]=C:\FlightSimulator\xuipc.dll LoadedModule[80]=C:\Windows\SYSTEM32\MSWSOCK.dll LoadedModule[81]=C:\Windows\SYSTEM32\SHFOLDER.dll LoadedModule[82]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[83]=C:\Windows\SYSTEM32\POWRPROF.dll LoadedModule[84]=C:\Windows\SYSTEM32\DINPUT8.dll LoadedModule[85]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll LoadedModule[86]=C:\Windows\SYSTEM32\d3dx9_34.dll LoadedModule[87]=C:\Windows\SYSTEM32\d3dx10_34.dll LoadedModule[88]=C:\Windows\SYSTEM32\d3d9.dll LoadedModule[89]=C:\Windows\SYSTEM32\DSOUND.dll LoadedModule[90]=C:\Windows\SYSTEM32\WININET.dll LoadedModule[91]=C:\Windows\SYSTEM32\MSACM32.dll LoadedModule[92]=C:\Windows\SYSTEM32\MSIMG32.dll LoadedModule[93]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[94]=C:\Windows\SYSTEM32\kernel.appcore.dll LoadedModule[95]=C:\Windows\system32\uxtheme.dll LoadedModule[96]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[97]=C:\Windows\system32\rsaenh.dll LoadedModule[98]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[99]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[100]=C:\Windows\SYSTEM32\clbcatq.dll LoadedModule[101]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[102]=C:\Windows\SYSTEM32\dxgi.dll LoadedModule[103]=C:\Windows\SYSTEM32\d3d11.dll LoadedModule[104]=C:\Windows\SYSTEM32\aticfx32.dll LoadedModule[105]=C:\Windows\SYSTEM32\atiu9pag.dll LoadedModule[106]=C:\Windows\SYSTEM32\atiumdag.dll LoadedModule[107]=C:\Windows\SYSTEM32\atiumdva.dll LoadedModule[108]=C:\Windows\SYSTEM32\D3DCompiler_34.dll LoadedModule[109]=C:\Windows\SYSTEM32\WindowsCodecs.dll LoadedModule[110]=C:\Windows\SYSTEM32\d3d10_1.dll LoadedModule[111]=C:\Windows\SYSTEM32\d3d10_1core.dll LoadedModule[112]=C:\Windows\SYSTEM32\dxdiagn.dll LoadedModule[113]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[114]=C:\Windows\SYSTEM32\wbemcomn.dll LoadedModule[115]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[116]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[117]=C:\Windows\system32\winbrand.dll LoadedModule[118]=C:\Windows\SYSTEM32\WINTRUST.dll LoadedModule[119]=C:\Windows\SYSTEM32\CRYPT32.dll LoadedModule[120]=C:\Windows\SYSTEM32\MSASN1.dll LoadedModule[121]=C:\Windows\SYSTEM32\WTSAPI32.DLL LoadedModule[122]=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule[123]=C:\Windows\SYSTEM32\gameux.dll LoadedModule[124]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17810_none_a9edf09f013934e0\COMCTL32.dll LoadedModule[125]=C:\Windows\SYSTEM32\XmlLite.dll LoadedModule[126]=C:\Windows\SYSTEM32\msxml6.dll LoadedModule[127]=C:\Windows\System32\Wpc.dll LoadedModule[128]=C:\Windows\System32\NETAPI32.dll LoadedModule[129]=C:\Windows\SYSTEM32\Normaliz.dll LoadedModule[130]=C:\Windows\System32\wevtapi.dll LoadedModule[131]=C:\Windows\System32\netutils.dll LoadedModule[132]=C:\Windows\System32\srvcli.dll LoadedModule[133]=C:\Windows\System32\wkscli.dll LoadedModule[134]=C:\Windows\System32\SAMCLI.DLL LoadedModule[135]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[136]=C:\Windows\System32\Bcp47Langs.dll LoadedModule[137]=C:\Windows\System32\Windows.Web.dll LoadedModule[138]=C:\FlightSimulator\uiautomationcore.dll LoadedModule[139]=C:\Windows\SYSTEM32\OLEACC.dll LoadedModule[140]=C:\Windows\System32\MMDevApi.dll LoadedModule[141]=C:\Windows\SYSTEM32\AUDIOSES.DLL LoadedModule[142]=C:\Windows\SYSTEM32\RICHED20.DLL LoadedModule[143]=C:\Windows\SYSTEM32\USP10.dll LoadedModule[144]=C:\Windows\SYSTEM32\msls31.dll LoadedModule[145]=C:\Windows\SYSTEM32\HID.DLL LoadedModule[146]=C:\Windows\SYSTEM32\XInput9_1_0.dll LoadedModule[147]=C:\Windows\SYSTEM32\wdmaud.drv LoadedModule[148]=C:\Windows\SYSTEM32\ksuser.dll LoadedModule[149]=C:\Windows\SYSTEM32\AVRT.dll LoadedModule[150]=C:\Windows\SYSTEM32\msacm32.drv LoadedModule[151]=C:\Windows\SYSTEM32\midimap.dll LoadedModule[152]=C:\Windows\SYSTEM32\dinput.DLL LoadedModule[153]=C:\Windows\SYSTEM32\XInput1_4.dll LoadedModule[154]=C:\FlightSimulator\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[156]=C:\FlightSimulator\IvAp v2\ivap_fsx_bootstrap.dll LoadedModule[157]=C:\Windows\SYSTEM32\mfc100.dll LoadedModule[158]=C:\Windows\SYSTEM32\MSVCR100.dll LoadedModule[159]=C:\Windows\SYSTEM32\MSVCP100.dll LoadedModule[160]=C:\Windows\SYSTEM32\PSAPI.DLL LoadedModule[161]=C:\Windows\SYSTEM32\MFC100ITA.DLL LoadedModule[162]=C:\Windows\system32\propsys.dll LoadedModule[163]=C:\FlightSimulator\Modules\FSUIPC4.dll LoadedModule[164]=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[165]=C:\Windows\SYSTEM32\WINNSI.DLL LoadedModule[166]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[167]=C:\Windows\SYSTEM32\Secur32.dll LoadedModule[168]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[169]=C:\Windows\system32\msimtf.dll LoadedModule[170]=C:\Windows\SYSTEM32\d2d1.dll LoadedModule[171]=C:\Windows\SYSTEM32\DWrite.dll LoadedModule[172]=C:\Windows\SYSTEM32\d3d10warp.dll LoadedModule[173]=C:\Windows\SYSTEM32\MLANG.dll LoadedModule[174]=C:\Windows\SYSTEM32\uiautomationcore.dll LoadedModule[175]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\FMGS.DLL LoadedModule[176]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\Airbus_ECAMD2D.DLL LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCP90.dll LoadedModule[178]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll LoadedModule[179]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\ASC.DLL LoadedModule[180]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\ND\AB_ND_GDI.DLL LoadedModule[181]=C:\Windows\SYSTEM32\ntmarta.dll LoadedModule[182]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\AsInput.DLL LoadedModule[183]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\DLLs\FBW.DLL LoadedModule[184]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\AirbusXE2.DLL LoadedModule[185]=C:\FlightSimulator\SimObjects\Airplanes\Aerosoft Airbus A318_A319 Base\Panel_Fallback\AirbusXE.DLL LoadedModule[186]=C:\Windows\SYSTEM32\atiuxpag.dll LoadedModule[187]=C:\Windows\SYSTEM32\atidxx32.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Ha smesso di funzionare ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\FlightSimulator\fsx.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=31736CD664C91611E8FACF7B443412D4 Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 6, 2016 Share Posted January 6, 2016 Thank you so much for the information. It's interesting, because I'm not seeing a module flagged as being the "Fault". The information you provided, along with similar reports, will help us begin to narrow this down. Right now I am struggling to find a common denominator as only a hand full of people are having this problem. I have 8 people making 4 flights per week and continually using Direct To to each way point without the ability to reproduce. Three of those have FSX Steam and the rest are using FSX Disk. We are not able to support any Aerosoft product testing on P3D. Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 6, 2016 Author Share Posted January 6, 2016 Dear Dave, what does it means that you don't find a module with fault? In the Windows crash log is indicated that the error is caused by FMGS.dll.. Do you need further report on other flight leg? Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 6, 2016 Share Posted January 6, 2016 Usually AppCrashView will pull the Faulty module from the log, that's all. It's interesting only because it's not pulled in the report, and I'll make a mental note of this. Understand it was the FMGS module. We're going to need to get a number of these types of reports from other people to help narrow down the cause. RIght now, there is everyone reason to believe it is something installed or not installed on the system (not the Aerosoft software). I did come up with one thing which would certainly cause this problem. If someone didn't completely uninstall the Airbus Version 1.30 AND manually remove the Simobjects folder, there is every reason to believe the result would be the error you're seeing. You could certainly test this theory in uninstalling, manually removing the Airbus SimObjects folders, rebooting, and reinstalling the Airbus. It only takes a few minutes to do. Thanks again for all your help! Link to comment Share on other sites More sharing options...
bachino88 0 Posted January 7, 2016 Share Posted January 7, 2016 On 4/1/2016 at 9:50 PM, DaveCT2003 said: Stefano, I'm not sure this will help narrow down the problem, but certainly all information helps! Below is my complete list, and no matter what I do I'm not able to reproduce this problem. I have my team trying to reproduce it and gather data on it. If this occurs again, your help in collecting some important data would be much appreciated. Before you're next flight, please be sure that you have the three check boxes under "Logging" selected in the Airbus Configurator, and provide the information and files in my post above. I have the following installed: FSX:SE Majestic Dash 8 Q400 Professional Aerosoft Airbus A318/A319/A320/A321 PMDG 737NGX PMDG 777 NavData: Navigraph Cycle 1513 (updated each month) Thanks! Please login to display this image. Thank you Dave, and just for information (while waiting another occurence on next flights), after DIR TO fails, in my case, I have a Windows pop up with 2 choice: close FSX or debug. At this point, I'm still able to fly the 32x, even with autopilot ON (HDG, TRK etc.), but the MCDU is totally freezed. After pressing debug, FSX crashes to desktop. I hope this may help you. Edit: ah and yes, by the way, I totally uninstall and remove folders from fsx and then back to clean install for every new installer available in this months. Regards Stefano Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 7, 2016 Author Share Posted January 7, 2016 Quote Edit: ah and yes, by the way, I totally uninstall and remove folders from fsx and then back to clean install for every new installer available in this months. Regards Stefano Me too. At each new Release I uninstalled completely the Airbus, including cleaning of the Airbus folder, and then I Re-Installed the software from New by Rebooting. Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 7, 2016 Share Posted January 7, 2016 Stefano and Frances, and anyone else who is having this problem.... 1. Would you please tell if you have any of the former Aerosoft Airbus aircraft installed? Please also let me know if you had them and uninstalled them. 2. If it's not too much trouble, would you please do the following steps below? This should only take about 10 or 15 minutes, and what will help us to both establish common ground for the people having this problem AND it will eliminate many potential causes of this problem. a. Uninstall the Airbus A318/A319/A320/A321 (all variants). b. Manually delete all associated folders in the SimObjects folder. c. Reboot. d. Ensure User Account Control is set to it's lowest settings. e. Disable your Anti-Virus software. f. Reinstall the Airbus (all variants), running the installer(s) as Administrator. g. Reinstall your AIRAC h. Reboot. i. Set the aircraft back up using the Airbus Configurator. Then start FSX, and test to see if you are still having the CTD when using the Direct To function. Let me know if the problem still remains. Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 9, 2016 Author Share Posted January 9, 2016 Hi Dave, unfortunately I will come back to home next week. I'll proceed with test suggested as soon as possible. Link to comment Share on other sites More sharing options...
Chok 49 Posted January 9, 2016 Share Posted January 9, 2016 On 1/7/2016 at 4:25 PM, DaveCT2003 said: Stefano and Frances, and anyone else who is having this problem.... 1. Would you please tell if you have any of the former Aerosoft Airbus aircraft installed? Please also let me know if you had them and uninstalled them. 2. If it's not too much trouble, would you please do the following steps below? This should only take about 10 or 15 minutes, and what will help us to both establish common ground for the people having this problem AND it will eliminate many potential causes of this problem. a. Uninstall the Airbus A318/A319/A320/A321 (all variants). b. Manually delete all associated folders in the SimObjects folder. c. Reboot. d. Ensure User Account Control is set to it's lowest settings. e. Disable your Anti-Virus software. f. Reinstall the Airbus (all variants), running the installer(s) as Administrator. g. Reinstall your AIRAC h. Reboot. i. Set the aircraft back up using the Airbus Configurator. Then start FSX, and test to see if you are still having the CTD when using the Direct To function. Let me know if the problem still remains. Hello I have been getting this error on and off for the past 6 months (maybe more I cannot remember exactly), over the period I have been using different Sims and windows versions. It happens in the A319, 320, and 321 in different locations. (I never fly the A318 but probably that one as well) I started getting it back on FSX on windows 7 home premium. I am now in P3D V3.0 on windows 10 and I still get the error from time to time. Last time it appeared was 8 days ago on arrival into Munich in the A319 IAE. During this time, I have always been using Navigraph as my Airac source and at the time it crashed last, I was running 1513. I can recall getting it the CTD on these occasions. On departure out of ENBR after getting a direct to (FSX) On departure out of EKAH after getting a direct to (P3D V2.5 A320). A couple of times in cruise from EKCH To LOWW after getting “Direct to” different points on the route (the majority of the times the direct was HDO Vor) (Both FSX and P3D V2.5/V3 in the A319 and A320 CFM and IAE) And the most recent one on approach into Munich after getting direct from MAREM to DM421. (flight plan: SIMEG M736 SALLO UM44 KOGIM ADLIR MAREM T106 BAGMI) A319 IAE on V1.31. I haven’t been able to locate the error log for the Munich crash (it only saves 7 days ? correct me if I am wrong and tell me how to find older ones) but I will as soon as I get the error again post a log file. Last time I did a full reinstall of windows and sim I went over everything to make sure I followed the recommendations you give in accordance to how you install the Airbus. These were: To reinstall my windows followed by drivers, not install Anti virus(I know you recommend just turning it off but I wanted to be sure), turning off firewall, turning off UAC, running the Airbus installer as admin(as with every other addon I installed), making sure I have all the correct Microsoft C++ versions. Having the latest version on the airbus (and all other addons used), installing the sim outside of programs 86. My current system is: MSI Z97 Gaming 7 Nvidia 970 GTX (MSI version) 4790K. G.Skill Ripjaws 2133 MHz 4x4GB Samsung 840 EVO (to run windows and P3D) 1TB of a regular to run the rest. My sim is: (the addons mentioned have been applied to the sim during all the CTD) some new ones have been added to P3D which I did not have in FSX but since the crashes happened before those I figured they are not worth mentioning. ORBX Vector, Global. ASN. Ezdok, Aerosoft Airbus both Soft clouds Flytampa EKCH, Flytampa, Vienna, Aerosoft Oslo. For me it appears that there is not a pattern to how the crash happens and I have tried a couple of times to replicate the CTD right after getting it as in spawning in and doing exactly the same thing I did on the flight of the crash again. However, as of now I have been unable to make it crash on the second attempt. I have seen it crash when going “direct to” through the left buttons on the MCDU where you choose a point and press insert and by manually writing it and using the right side option on the direct to page. If you need more information, please let me know I am eager to find a solution. Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 9, 2016 Share Posted January 9, 2016 Many thanks FrederiK! The information you provided would seen to rule out this being a permissions related issue, but we suspected this already as CTDs via the MCDU are frequently math related. This doesn't mean that this one is. Whether it is accurate or, not, some people have implied this problem occurs any time the Dir To function is used. I have 8 guys on the team who have tried to replicate this prblems and don't have any problems with the Dir To function. Several of the guys (including me) have sat and pressed DIr To repeatedly on a 2.5 hour flight without any problems, both manually entering waypoints and selecting them from the flight plan. I suppose what I need to do next is make sure that everyone is using the Dir To function the same way, though I can't imagine that they aren't doing so already. Looking forward to the other guys having this problems providing additional information. Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted January 10, 2016 Share Posted January 10, 2016 Gentlemen, Tens of hours have been poured into this issue without reproducible results with latest internal builds. The developers team can't fix anything without reproducible steps (Doctors don't go into surgery without knowing where to cut). The only advice that can be given as of now is to try uninstalling the C++ redistributables once more and reinstalling it. Nevertheless, since this issue has not appreared in the internal builds, it is possible this issue won't reappear in the next service pack, because code has changed since the last fmgs build in release versions. Link to comment Share on other sites More sharing options...
keithgiannni 25 Posted January 10, 2016 Share Posted January 10, 2016 I will join this thread and start recording data as requested. Thanks to Dave for advising me that my problems are linked. Reports to follow as I try to replicate CTDs. Keith Link to comment Share on other sites More sharing options...
keithgiannni 25 Posted January 10, 2016 Share Posted January 10, 2016 Ok first report (attached) from me. IVAO flight EGLL LFPO route MID L151 SITET UN859 LGL A34 BOBSA. FP downloaded via Simbrief. Cleared direct to Sitet via ATC. Approximately four minutes later CTD. (Thanks to FSUIPC auto save!!). Flight resumed. Directed to fly direct to Bobsa then direct Vasol. Flight concluded without any other incidents. For info, reinstalled AS Airbus 318 to 321 as instructed. Also uninstalled and reinstalled C++ files having also reinstalled them from MS Support today. Hope this data helps. Files include Process Explorer and those requested by Tom. FSX W10. Keith FSX DUMP FILES.zip Link to comment Share on other sites More sharing options...
keithgiannni 25 Posted January 10, 2016 Share Posted January 10, 2016 And here's another!! First, flew part offline then online VTBS to VTSP. A319 Easy livery. Numerous Directs, no incidents. Then re flew (off line this time) the flight from EGLL LFPO (BA 319 again). Direct Sitet OK, Dir Bobsa OK, CTD not long after Dir to Odio. Report attached. So 1 in 3 flights good so far. More testing tomorrow, sadly, I suspect more reports. Hope they help to solve the issue. Incidentally, I have Orbyx Global, Europe LC, ASN with Rex. Will fly again in Thailand to see if I can get another free of CTD flight. Best, Keith DUMP1.zip Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 11, 2016 Author Share Posted January 11, 2016 Quote Gentlemen, Tens of hours have been poured into this issue without reproducible results with latest internal builds. The developers team can't fix anything without reproducible steps (Doctors don't go into surgery without knowing where to cut). The only advice that can be given as of now is to try uninstalling the C++ redistributables once more and reinstalling it. Nevertheless, since this issue has not appreared in the internal builds, it is possible this issue won't reappear in the next service pack, because code has changed since the last fmgs build in release versions. Hi Joshua, in order to be sure to Re-install the right software, could you please provide the Revision to be installed on my PC? 32 and 64 Bit? Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted January 11, 2016 Deputy Sheriffs Share Posted January 11, 2016 11 minutes ago, Francescom said: in order to be sure to Re-install the right software, could you please provide the Revision to be installed on my PC? 32 and 64 Bit? Both packages, as far as they are available. Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 11, 2016 Author Share Posted January 11, 2016 1 minute ago, Tom A320 said: Both packages, as far as they are available. yes but what? 2010, 2012, 2013 I don't know how many versions of the C++ are available... Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted January 11, 2016 Deputy Sheriffs Share Posted January 11, 2016 #26 On 7/24/2015 at 3:51 PM, Tom A320 said: As far as I understood the dev the dump didn't lead directly to the bug... Just to rule this out as source of the problem: please make sure, that you have the Microsoft C++ Redistributables 2005 , 2008, 2010, 2012 and 2013 installed. Link to comment Share on other sites More sharing options...
DaveCT2003 2553 Posted January 11, 2016 Share Posted January 11, 2016 34 minutes ago, Francescom said: yes but what? 2010, 2012, 2013 I don't know how many versions of the C++ are available... Francesom, Tom is absolutely correct, but I can also provide you with exactly what I have installed. Please login to display this image. Hope this helps! Link to comment Share on other sites More sharing options...
Francescom 4 Posted January 11, 2016 Author Share Posted January 11, 2016 43 minutes ago, DaveCT2003 said: Francesom, Tom is absolutely correct, but I can also provide you with exactly what I have installed. Please login to display this image. Hope this helps! Ok I'll try to Uninstall and Re-Install all the packages.. Link to comment Share on other sites More sharing options...
Squawk2810 1 Posted January 11, 2016 Share Posted January 11, 2016 Hi, i had the same issue today, departed from LSZH. P3D V3.1 crashed after a Direct To with a FMGS.dll report. Spoiler Quelle Prepar3D exe Zusammenfassung Nicht mehr funktionsfähig Datum 11.01.2016 16:56 Status Der Bericht wurde gesendet. Beschreibung Pfad der fehlerhaften Anwendung: E:\Prepar3D v3\Prepar3D.exe Problemsignatur Problemereignisame: APPCRASH Anwendungsname: Prepar3D.exe Anwendungsversion: 3.1.2.15831 Anwendungszeitstempel: 5672b60a Fehlermodulname: FMGS.dll Fehlermodulversion: 1.2.7.82 Fehlermodulzeitstempel: 552db3f3 Ausnahmecode: c0000005 Ausnahmeoffset: 00036b03 Betriebsystemversion: 10.0.10586.2.0.0.256.48 Gebietsschema-ID: 1031 Zusatzinformation 1: bdcb Zusatzinformation 2: bdcb33e65a9843796b7ec31cc25bda3b Zusatzinformation 3: 7ae5 Zusatzinformation 4: 7ae5ff970d16e403baf57c3408d06e56 Weitere Informationen über das Problem Bucket-ID: 1c43cbd33fbd995773f84a8b7fa1eb82 (107837036332) Greetings Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted January 11, 2016 Deputy Sheriffs Share Posted January 11, 2016 3 minutes ago, MegaSunrise69 said: i had the same issue today, departed from LSZH. P3D V3.1 crashed after a Direct To with a FMGS.dll report. I would like to ask you to also install/update the Microsoft C++ Redistributables 2005 , 2008, 2010, 2012 and 2013 as in the posts directly above yours described. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.