I experienced my first CTD the other day. The details of the error message said that the program that faulted was atc.dll . Is this the atc for the AI traffic in FSX? I was not actively talking to FSX's ATC at the time. I was flying enroute, but there were numerous AI aircraft around me (depicted by their contrails). Since the crash, I have reduced the amount of AI traffic. This may solve the problem. I just want to know what atc.dll does and why it may of crashed. I have a pretty high performance computer -980x with a good card and a decent amount of memory. I have never experienced any problems before and I run Air hauler, ASE, and AI smooth at the same time.

This used to be a fairly common issue in FS9, not much in FSX see this: http://forum.simflight.com/topic/58511-atcdll-crash/Also this: http://dll.paretologic.com/detail.php/atc

Hmm...that is interesting. It seems the old problem was a factor of what freq you have set up and if you go out of range of a facility. I think I may try flying on 122.8 or 121.5 when I am not using any atc or any online atc in FSX. Thank you for the nudge in the right direction.

Hello,I got a CTD caused by atc.dll just yesterday. I was wondering if there's any update on a possible solution for this.Thanks

Has anybody found a way around the CTD, I just got it for the first time over the UK and I wasn't even using ATC!

I just want to know what atc.dll does and why it may of crashed.

According to this link which describes the ATC dll in length for FS2K4 (doubt it has changed for FSX), it has to do with graphics and nothing to do with AI Traffic or FS ATC - http://dll.paretologic.com/detail.php/atc. Best regards,Jim

I get this ATC.DLL whenever I fly in Europe and not in the FTX AU. I don't know how to combat it, I've disabled the ATC sound and I've tuned my radio's to 121.5 (dead FSX freq) and Im not even using any kind of ATC at all! Really really frustrates me.

I get this ATC.DLL whenever I fly in Europe and not in the FTX AU. I don't know how to combat it, I've disabled the ATC sound and I've tuned my radio's to 121.5 (dead FSX freq) and Im not even using any kind of ATC at all! Really really frustrates me.

Did you see the link I posted? The ATC.dll has nothing to do with ATC. Zilch. Nada.... Since nothing happens while flying in FTX AU, then I suspect a scenery problem with the default setup. Best regards,Jim

Yes, I did see your links and I read them, thanks you for showing them too me. However, I don't get this CTD when I fly in North America or Australia, but only in Europe. I dont understand how there could be something wrong with my set-up or install when Im using some of the CPU intensive scenery/planes in the world and I don't get any CTD's. I really dont want to reinstall EVEYTHING as that would take me days. Can I pull this .dll off of the FSX Disc?

Yes, I did see your links and I read them, thanks you for showing them too me. However, I don't get this CTD when I fly in North America or Australia, but only in Europe. I dont understand how there could be something wrong with my set-up or install when Im using some of the CPU intensive scenery/planes in the world and I don't get any CTD's. I really dont want to reinstall EVEYTHING as that would take me days. Can I pull this .dll off of the FSX Disc?

You cannot delete the ATC.dll. It was updated with SP2/Acceleration. I don't think you need to reinstall FSX. I've seen this crash in CPU intensive situations like with commercial scenery, commercial aircraft, in heavy weather (or real weather loaded), at dusk or night. I don't see anything about your computer but, if it's overclocked, I would be looking there at those settings in the bios and also check your computer memory settings/timings. Overheating will also bring down your system as FSX is CPU intensive and the more strain you put on it the more likely a crash. So, if you have all or most of your sliders to the right in the FSX.cfg, your chances of a crash increase considerably. There is no magic bullet to fix the ATC.dll error but I can almost guarantee it has something to do with your system memory. Best regards,Jim