Sorry for the double post!!!I recently installed Radar Contact 4.3 and disabled fsx atc functions per the r/c instructions.All was well for a few days but now I'm experiencing random atc.dll errors that shut down fsx.I rechecked my settings and contacted r/c and was told that my settings were correct.It's happening approx 2 out of every 5 flights.AlexSystem Specs:Mainboard-EVGA x58 3x SLIGraphics-GeForce GTX 285 OCFUCPU-Intel i7 950 3.07ghz (oc-4.0ghz)MEM-OCZ DDR3(6GB)OS-Windows 7 Pro x64FS-FSX SP2Activesky AdvanceGround Environment XUltimate Terrain X EuropeMytraffic X LiteRadar Contact 4.3

HelloThis used to be a problem in FS2004 and was fixed by an option in FSuipcI do not know if the fix will still apply to the FSX atc.dll

Thanks, I'll check it out.Alex

HelloThis used to be a problem in FS2004 and was fixed by an option in FSuipcI do not know if the fix will still apply to the FSX atc.dll

No. The problem in FS9's ATC.DLL doesn't exist in the FSX version. In fact I believe the guy in the FS team actually fixed it in the source in FS9, after I supplied proof and actual code locations showing where it went wrong, but I don't think the team were allowed to release anything else for FS9 by then.I've not heard of or every experienced any ATC.DLL crashes in FSX. I can only think there's some corruption someplace in the FSX installation. Maybe a re-install is called for.RegardsPete

Alex--I had a bout of trouble with this problem too. I'm not ready to declare victory just yet, but it seems that two changes I made to my system might be responsible.First, I have the same eVGA X58 mobo as you and I flashed my mobo with the eVGA SZ2Z BIOS about a month ago. I noticed when I did some troubleshooting with E-LEET that the CPU core voltage was running about .03v lower than it had been under version SZ2F with the same settings. I re-ran a Prime95 burn-in test with the new BIOS, and sure enough, after 90 min it faulted. I bumped up the core voltage a notch to get the reported Vcore back to where it was before the BIOS change, and the 12-hr Prime95 test is clean again.Second, I was using the nVidia 196.21 drivers on my eVGA 2GB GTX285 (fiddling with the Bufferpools settings given all the recent buzz on that topic) and I noticed that the GPU temps were running a full 10 deg C lower with that driver than they were with my old trusty 182.50 driver. There's some discussion out there that suggests that the 19x series nVidia drivers have the board's regulator undervolting the GPU, and that may be responsible for a persistent rash of black-screen crashes and other anomalies. I went back to the 182.50 drivers.The combo of the two actions has given me three crash-free flights over the same route that was crashing with an ATC.DLL error an hour or so into the flight every single time before. BTW, I had the same CTD (with ATC.dll reported as the faulting module in FSX) with and without Radar Contact running, too. Bottom line...I can't find anything definitive to lead me to conclude that this is a software issue.I'm keeping my fingers crossed...this problem has been giving me a major case of the beak for weeks now.My system specs:eVGA E-758-A1 X58 3x SLI motherboardi7-975 CPU o/c to 4.40 GHz on water cooling6 GB (3 x 2GB) Mushkin 1600 MHz CAS 6 RAMeVGA GTX285 2GB (P3-1185-AR) at stock speedsIntel X-25M 160GB SSD (FS drive)WD Velociraptor 300GB 10K RPM HDD (system drive)PC Power & Cooling 910W Silencer single-rail pwr supplyRegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO