[SOLVED] v 0.6.0.22 instant CTD

Bogga · November 25, 2022, 08:12:16 PM

Unfortunately the latest gives me CTD when inject traffic is pressed.

johanfrc · November 25, 2022, 09:05:01 PM

Please attach the log files. It's like asking for a certain sand corn in Sahara with that description.

Also if it's possible, please attach the Windows Event log (there usually are 2), as they might contain more info too.

Bogga · November 25, 2022, 09:12:29 PM

Quote from: johanfrc on November 25, 2022, 09:05:01 PMPlease attach the log files. It's like asking for a certain sand corn in Sahara with that description.

Also if it's possible, please attach the Windows Event log (there usually are 2), as they might contain more info too.

Totally, sorry for that. What's the path of the logs, please?

johanfrc · November 25, 2022, 09:17:02 PM

The log files are in the folder where the AIGTC exe file is located.

The Windows Event logs are in the Windows Event Manager (press the Windows logo for the start menu and then write "Windows Event" and it should show up. Then find the entry where AIGTC crashed, and copy the text.

Bogga · November 25, 2022, 09:28:13 PM

You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.

Bogga · November 25, 2022, 09:29:26 PM

Windows event logs, does not show any AIG crash but msfs. Stating this:
Faulting application name: FlightSimulator.exe, version: 1.29.28.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.28.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c63581
Faulting process id: 0x203c
Faulting application start time: 0x01d9010a3941bf5f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 8801a908-f36f-44f1-b1ce-144810cc9527
Faulting package full name: Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Farlis · November 26, 2022, 12:04:51 PM

I am going to amend myself to this topic as I have the exact same problem.
Here is what the Eventviewer gives me:
Protokollname: Application
Quelle: Application Error
Datum: 26.11.2022 12:54:16
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: Karsten-PC
Beschreibung:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.29.28.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.29.28.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001c63581
ID des fehlerhaften Prozesses: 0x405c
Startzeit der fehlerhaften Anwendung: 0x01d9018bff37ac02
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 74c7c8c6-3e2f-498e-8d5e-2d911653cf61
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-11-26T11:54:16.9082230Z" />
<EventRecordID>461</EventRecordID>
<Correlation />
<Execution ProcessID="18528" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Karsten-PC</Computer>
<Security />
</System>
<EventData>
<Data>FlightSimulator.exe</Data>
<Data>1.29.28.0</Data>
<Data>00000000</Data>
<Data>FlightSimulator.exe</Data>
<Data>1.29.28.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>0000000001c63581</Data>
<Data>405c</Data>
<Data>01d9018bff37ac02</Data>
<Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
<Data>74c7c8c6-3e2f-498e-8d5e-2d911653cf61</Data>
<Data>Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe</Data>
<Data>App</Data>
</EventData>
</Event>

jzdilts · November 26, 2022, 07:43:28 PM

Finally got traffic and now I'm having the CTD issue as well. Logs attached.

tenala · November 27, 2022, 07:20:37 AM

Messages from eventviewer:

Faulting application name: AIGTech - Traffic Controller.exe, version: 0.6.0.22, time stamp: 0xdc444cc0
Faulting module name: KERNELBASE.dll, version: 10.0.22621.755, time stamp: 0x19d26491
Exception code: 0xe0434352
Fault offset: 0x000000000009039c
Faulting process id: 0x0x5B24
Faulting application start time: 0x0x1D9022F5C979FEC
Faulting application path: C:\Users\User\MSFS Utils\MSFS Applications\AIG_TrafficController\AIGTech - Traffic Controller.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: c4c9df4e-f2a2-438a-9f1d-200feac9d683
Faulting package full name:
Faulting package-relative application ID:

Application: AIGTech - Traffic Controller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32, IntPtr)
at Microsoft.FlightSimulator.SimConnect.SimConnect.AIRemoveObject(UInt32, System.Enum)
at AIGTech.TrafficController.Classes.Manager.TrafficManager.StopAIGFPManager()
at AIGTech.TrafficController.Controller.TCController.RemoveAIGFPTraffic()
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at AIGTech.TrafficController.App.Main()

Faulting application name: FlightSimulator.exe, version: 1.29.28.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.28.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c63581
Faulting process id: 0x0x71DC
Faulting application start time: 0x0x1D9022E990762B4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 16818f06-3e80-403d-bdd9-cb0202dadd9f
Faulting package full name: Microsoft.FlightSimulator_1.29.28.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

And here are my log files

tenala · November 30, 2022, 11:26:06 AM

Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5020044) was installed on my pc today and an update for MSFS2020 yesterday. After these updates I can use AIGTC again. I really do not know if these updates are the reason or something else but I am happy to have traffic again. Should I get a CTD again, I would report it here.

Farlis · November 30, 2022, 05:28:43 PM

Quote from: tenala on November 30, 2022, 11:26:06 AMCumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5020044) was installed on my pc today and an update for MSFS2020 yesterday. After these updates I can use AIGTC again.

Same. The CTD is gone.

Bogga · December 02, 2022, 08:13:30 PM

I can't get that Windows 11 update, don't know why. So still CTD for me.

Bogga · December 03, 2022, 02:31:56 AM

Quote from: Bogga on December 02, 2022, 08:13:30 PMI can't get that Windows 11 update, don't know why. So still CTD for me.

Had to download windows assistant to update, strange. Working now fortunately. Thank you for the info tenala.