manfredd Posted June 5, 2021 Share Posted June 5, 2021 Hi Guys, On my flight from LOWW to EDDH today, Windows suddenly completely crashed. Blue screen, PC needs to be restarted because of a fatal error. Then when I looked in the event log, I found this entry: Name der fehlerhaften Anwendung: AivlaSoft.Efb.Client.exe, Version: 2.2.126.0, Zeitstempel: 0x6071554f Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000bcd380 ID des fehlerhaften Prozesses: 0x490 Startzeit der fehlerhaften Anwendung: 0x01d75a16a835ea82 Pfad der fehlerhaften Anwendung: E:\Flightsim-Tools\EFB2Client\AivlaSoft.Efb.Client.exe Pfad des fehlerhaften Moduls: unknown Berichtskennung: 4d49818f-734d-453b-8e96-d0d9a46c8789 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Was the AivlaSoft software really to blame for the Windows crash? And a second question: It happens again and again that the EFB client closes automatically. Can that have something to do with it? My version of server and client is: 2.2 (build # 126) Thank you in advance for the answer best regards, Manfred Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted June 5, 2021 Share Posted June 5, 2021 Hi Manfred, can you please create a set of support files, one from the Client and one from the Server and then upload them here? Quote Link to comment Share on other sites More sharing options...
manfredd Posted June 5, 2021 Author Share Posted June 5, 2021 I hope this are the files you need Client_202106052206.txt.zip Server_202106052207.txt.zip Quote Link to comment Share on other sites More sharing options...
manfredd Posted June 5, 2021 Author Share Posted June 5, 2021 sorry, this files are better (including logs from today) Client_202106052215.txt.zip Server_202106052215.txt.zip Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted June 8, 2021 Share Posted June 8, 2021 Hi Manfred, thank you for uploading the support files. Unfortunately there is nothing logged in these files which is related to the situation described in your opening post. From my point of view this is not abnormal because when Windows crashes (as you described) then the application itself will not be able anymore to properly write any logfile entries. Usually a blue screen is not caused by any .NET application like EFB but from hardware drivers or similar. Quote Link to comment Share on other sites More sharing options...
manfredd Posted June 8, 2021 Author Share Posted June 8, 2021 Thank you for your answer and your efforts. I thought so, but just to be on the safe side I wanted to ask. Thanks for the effort and thanks for the wonderful software! Best regards, Manfred Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.