![]() I fly, for example, at the busiest airport in Latin America (SBGR - Guarulhos Internacional Airport), this is the only addon I have, if the problem was in it, even the supplier had launched a new update which, in fact, was in February and on the blog of vendor has no complaints about crashes in the addon region. Yes, but let’s get to the facts, first of all that this theory has been tested so much that it is at the beginning of the topic, so for some it may not have worked, in this case, me.Īnother fact is that if the problem were addons the whole planet would be in trouble, even the streamers. The fault address in not in any loaded module, please check your build’s rebase *** WARNING: Unable to verify checksum for XPlatCppWindows.dll *** WARNING: Unable to verify checksum for CoherentUIGT.dll *** WARNING: Unable to verify checksum for WTF.dll *** WARNING: Unable to verify checksum for WwiseLibPC圆4P.dll (2728.43e8): Access violation - code c0000005 (first/second chance not available)įor analysis of this file, run !analyze -v ![]() The stored exception information can be accessed via. This dump file has an exception of interest stored in it. Windows 10 Version 19042 MP (8 procs) Free 圆4 User Mini Dump File: Only registers, stack and portions of memory are available Microsoft (R) Windows Debugger Version 6.1007 AMD64Ĭopyright (c) Microsoft Corporation. Report ID: 1f8d8923-f5de-460e-bba7-3b420dd20fbbįaulting package full name: Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbweįaulting package-relative application ID: App I was also in the JF Arrow, with the GTN 750.įaulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0圆0783c14įaulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0圆0783c14įaulting application start time: 0x01d7362b6f769192įaulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbwe\FlightSimulator.exeįaulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbwe\FlightSimulator.exe Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbweĪnwendungs-ID, die relativ zum fehlerhaften Paket ist: AppĬrash on final, runway 22L at KBOS, about 2 miles out. Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbwe\FlightSimulator.exeīerichtskennung: 8bc15333-6d30-4968-9ed3-fa240ef07531 Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_圆4_8wekyb3d8bbwe\FlightSimulator.exe Startzeit der fehlerhaften Anwendung: 0x01d73612377439fe Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0圆0783c14 ![]() Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0圆0783c14 Will do this leg again tomorrow to see if there is a reproducable issue there. Flew the Justflight PA28, crash was enroute over the Lake District, UK. First CTD after a long time (at least where are no scenery addons involved).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |