[CLOSED] AIG Traffic Crashing MSFS

[flyup_]

Hi, new to the forum, but I installed AIG recently and noticed that it has been crashing MSFS. (Presumably.) I tried to do another flight with no traffic and it ran fine. I have the error code for the crash as well, but I'm not sure if it'll help too much.

Faulting application name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000012fda76
Faulting process id: 0x2b88
Faulting application start time: 0x01d7fc4bc0158ca3
Faulting application path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: a66bae7d-92c6-43b5-bb73-c8d6cec01ba9
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: AIGTech - Traffic Controller.exe, version: 0.5.0.19, time stamp: 0xd64b9ed6
Faulting module name: clr.dll, version: 4.8.4420.0, time stamp: 0x6109cbc8
Exception code: 0xc0000005
Fault offset: 0x0000000000058dd5
Faulting process id: 0x2f68
Faulting application start time: 0x01d7fbc7c30b3a67
Faulting application path: D:\AIG Traffic Controller\AIGTech - Traffic Controller.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 84a79f8b-4010-4c5a-bb5a-90c50e2d7acf
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 internal error in the .NET Runtime at IP 00007FFEE3718DD5 (00007FFEE36C0000) with exit code 80131506.


Faulting application name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001447457
Faulting process id: 0x32b4
Faulting application start time: 0x01d7fb95ad02b3db
Faulting application path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 29e02f4f-f4ca-418a-80ae-a20c80c57c4e
Faulting package full name:
Faulting package-relative application ID:

Today, it ran fine with no traffic running, however.

[airBAJAN]

Funny, I, too, having the same issues -expect that I brought MSFS2020 from Microsoft Store - seeing that your is from Steam store. Here is my logs along with the AIG Traffic Controller Log. Kaiiii3, any take on this issues? Thanks.
========
Log #1
Faulting application name: AIGTech - Traffic Controller.exe, version: 0.5.0.19, time stamp: 0xd64b9ed6
Faulting module name: clr.dll, version: 4.8.4420.0, time stamp: 0x6109cbc8
Exception code: 0xc0000005
Fault offset: 0x0000000000058dd5
Faulting process id: 0xc98
Faulting application start time: 0x01d8002c383d0665
Faulting application path: E:\AIG TC\AIGTech - Traffic Controller.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: eafebe60-3319-4d56-a80d-4ddeebf2330f
Faulting package full name:
Faulting package-relative application ID:
======
Log#2
Application: AIGTech - Traffic Controller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFFB8C28DD5 (00007FFFB8BD0000) with exit code 80131506.

[Kaiii3]

crashes in MSFS are hard to track down unless you can pinpoint the exavt situation.

The crash of TC is currently under investigation

[lmhariano]

In my situation, is rather easy to reproduce the issues:
- Load MSFS.
- Select a flight with the FBW A320.
- Open AIGTC for MSFS.

As soon as traffic is loaded, I can keep MSFS running for 5-10-30 minutes, until it crashes. Somehow with the PMDG DC-6 (the other airliner I fly in this sim) it does not happen. For reference, I have MSFS with FPS internally locked to 20 (with a 120 Hz monitor, this means 40 FPS actually). Haven't tried yet with other VSync/FPS lock combinations.

This is what I've got in the Event Viewer:

Code Select Expand

Faulting application name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.21.13.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001bb9832
Faulting process ID: 0x4f28
Faulting application start time: 0x01d802a5c85fbeab
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report ID: f79f056c-1c41-43c4-ba87-aabf965b58d1
Faulting package full name:
Faulting package-relative application ID:

Code Select Expand

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe
P2: 1.21.13.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.21.13.0
P6: 00000000
P7: 80000003
P8: 0000000001bb9832
P9:
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FlightSimulator._46d77197987982506684b3a0b68a586ef6f4c_0950a464_b1523f3e-d335-44a4-b09a-f4b6b7b979aa

Analysis symbol:
Rechecking for solution: 0
Report Id: f79f056c-1c41-43c4-ba87-aabf965b58d1
Report Status: 4
Hashed bucket:
Cab Guid: 0

Code Select Expand

Fault bucket 2039577704183524621, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe
P2: 1.21.13.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.21.13.0
P6: 00000000
P7: 80000003
P8: 0000000001bb9832
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER87F4.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._46d77197987982506684b3a0b68a586ef6f4c_0950a464_b1523f3e-d335-44a4-b09a-f4b6b7b979aa

Analysis symbol:
Rechecking for solution: 0
Report Id: f79f056c-1c41-43c4-ba87-aabf965b58d1
Report Status: 268435456
Hashed bucket: 82d43d9a2a383559dc4e091da5aa6d0d
Cab Guid: 0

I retried now, I got no Event Viewer entries, but I got this error message:

Code Select Expand

FlightSimulator.exe - Application Error
The exception Breakpoint
A breakpoint has been reached.
(0x80000003) occurred in the application at location 0x00007FF6964D2322.

Click on OK to terminate the program 

[Kaiii3]

so basically the crash is caused by AI and FBW? Since you can run PMDg and AI without issues the CTD of MSFS is FBW related

[lmhariano]

I'm not 100% sure: there must be an interaction between FBW and AIGTC that is triggering the crash. FBW without AI gives no issue at all. PMDG with or without AI gives no issue either.

Too bad FBW don't keep a proper support forum, those Discord thingies are so messy. I would have posted there if not for this Discord stuff..

[AndyM001]

I use the FBW Exp version, and have recently flown a few 2 hour flights and AIGTC has not crashed at all for me. Before the recent AIGTC update, AIGTC was crashing all the time, I would usually have to restart it 3 or 4 times in a 2 hour flight.

[Kaiii3]

same on my end today but woith the Dev Version of FBW, the crashes of TC are very hard to track down at the moment...

[lmhariano]

I use the FBW Exp version, and have recently flown a few 2 hour flights and AIGTC has not crashed at all for me.

same on my end today but woith the Dev Version of FBW

Mmmm, I'll try then using the Dev version. I'm running the (so-called) Stable version.

[AndyM001]

I use the FBW Exp version, and have recently flown a few 2 hour flights and AIGTC has not crashed at all for me.

same on my end today but woith the Dev Version of FBW

Mmmm, I'll try then using the Dev version. I'm running the (so-called) Stable version.

I'm also running it in Windows 8 compatibility mode, I changed it to that a while ago, initially it didn't make a difference to the crashes, but since the last update I haven't had any, just haven't changed it back. Not sure it that makes a difference.

[fox_4]

Hi,

I also encountered a CDT issue flying both the FBW A32NX (experimental version) and using AIGTC on both attempts I made since the sim update.

I unfortunately don't have any additional info.

I'll try to check in with FBW as well, maybe the new Sentry logs of theirs caught something useful