Crash when toggling ADF/VOR switches in A320

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

I was flying from EHRD to EGLC with the standard A320 neo. When flying from waypoint JACKO to the ILS runway 09 approach. I was fiddling with the ADF/VOR switches when the sound stuttered and the application crashed.

Provide Screenshot(s)/video(s) of the issue encountered:

Sorry, I don’t have any screenshots. It crashed.

Detailed steps to reproduce the issue encountered:

Create a flight plan EHRD to EGLC. Use Runway 6 with SOM2AY departure. Then use the XAMA1C arrival and ILS runway 09 approach. I’m using low altitude airways.

When close to waypoint TANET (not part of the flight plan, mind you) toggle ADF/VOR switches.

PC specs and/or peripheral set up if relevant:

XBox controller on Windows 11/ 32GB Memory/AMD Rizen 3700X.

Build Version # when you first started experiencing this issue:

Latest world update 8.


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I managed to grab some stuff from my event viewer in Windows.

Fault bucket 2210428589068451507, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 1220749227636682545

Problem signature:
P1: FlightSimulator.exe
P2: 1.24.5.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.24.5.0
P6: 00000000
P7: c0000005
P8: 0000000001a07003
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.867d58d9-c06b-4c73-8a0e-10d7dbe3e450.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d9b049bb-f54c-48c9-96b9-d0d4383e3443.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FlightSimulator._db3437c4a4ae721379ebd1f27e33487b52613f0_954089eb_cab_0779a9fd-1313-420c-9070-f0a2d5f77825\WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20220325_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.65ecbed6-cdbb-4898-acbb-68f4b3d982f9.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FlightSimulator._db3437c4a4ae721379ebd1f27e33487b52613f0_954089eb_cab_0779a9fd-1313-420c-9070-f0a2d5f77825\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.07ad93c5-1a2f-4f60-9819-3b5d7604717d.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.432c78c0-4bb1-4adf-b223-4bc3f2cd604b.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.65e6c214-55af-4bc5-be6f-8c00d7fce7f5.tmp.txt
\\?\C:\Users\wme\AppData\Local\Temp\WER.5135c750-9b08-4f2a-b4bc-18eefc743e42.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7df8d913-391c-4aed-bf9d-a15809d02b8b.tmp.xml
\\?\C:\Windows\SystemTemp\WER.663e29cb-bf4d-47b7-ac1e-714266d85999.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._db3437c4a4ae721379ebd1f27e33487b52613f0_954089eb_cab_0779a9fd-1313-420c-9070-f0a2d5f77825

Analysis symbol: 
Rechecking for solution: 0
Report Id: 78123c7d-96d2-453c-af0d-fd05f87d7f67
Report Status: 268435464
Hashed bucket: ff8bc3089b4e36a96ead051724cafeb3
Cab Guid: 4f80d75f-366b-45ea-90f0-f8f4691def31

Found the solution. Disable AI traffic completely. It looked like it was related to me doing something but it turns out that it was the AI traffic that caused the issue.