The faulting module was listed as ATC.dll
Quote:
Problem signature:
Problem Event Name: APPCRASH
Application Name: FS9.EXE
Application Version: 9.1.0.40901
Application Timestamp: 4135a208
Fault Module Name: ATC.DLL
Fault Module Version: 9.1.0.40901
Fault Module Timestamp: 4135a88e
Exception Code: c0000005
Exception Offset: 0002a63b
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
- it seems that this can be caused by identical adjacent Comm frequencies - I don't know if that was the problem in this case of course, but the CTD certainly happened at the moment PF3/ATC was in the middle of changing radio frequencies en route. (I need to check that later somehow to see if frequencies are the same, if I can). Would that be a problem to PF3? (It was FS9 ATC that crashed, not PF3 of course). Looking at some of the suggestions to avoid this occurring in the AVSIM CTD forum, I see one is that you add the line RemoveATC=Yes to the FSUIPC.ini file.
Any comments on this, or on ATC.dll CTDs in general? Would the line in any way affect the operation of PF3? I managed to continue the flight by reloading the AutoSave file and a suitable Lvl-D panel state file, but I wasn't able to get PF3 back to where I was at the time of the CTD - I thought it gave an option of resuming where a flight left off if it didn't finish, but I didn't get that for some reason... I tried tuning to local approach frequencies and tower frequencies, but PF3 gave the same response to all my attempts, that I wasn't tuned to any frequency and wanted me to tune to my departing airport's clearance frequency. Did I do something wrong?