Been getting these after and hour or so, consistently. Don't know if this has anything to do with RC4 or not.I've read conflicting views on what cause this--from scenrry layers to conflicts with FSX's atc.I do have utx, gex, scenery tech and fs global running.I am curious as to whether the fsuipc.ini fix will work for FSX, because it all referred to FS9.Thanks.Dan Cole

I am curious as to whether the fsuipc.ini fix will work for FSX, because it all referred to FS9.

No, there's nothing in FSUIPC4 relating to any ATC.DLL problems. I'm not aware of any specific bug in FSX's ATC like there was in FS9. I use RCV4 on every flight with FSX and have never has an ATC.DLL crash. Not that I never get FSX crashes, but never one, so far (touching wood and crossing fingers) in ATC.DLL. ;-)I suspect you might need to go through some process of elimination to find which of your add-on components is generating the conflict. My money would be one some scenery conflict or corruption, so start by switching off layers. You can do a binary-chop type search by editing the SCENERY.CFG, removing half of the (non-default) layers at a time (and renumbering), and zeroing in on the culprit. Trouble is, if it's a conflict between two of them rather than just a corruption that might not identify it.RegardsPete

Did you get an error code in the message box? If you are getting these after an hour on different flights through different areas, then check the error 713 pinned topic. Make sure RC, FSX itself, and other add-ons running are allowed to bypass checks in your security applications. In some of those security applications programs that frequently communicate with another inside any Program Files folder anyway after a measured time can be deemed to be a virus in the heuristic protection schemes.Does this only happen with RC running?

Did you get an error code in the message box? If you are getting these after an hour on different flights through different areas, then check the error 713 pinned topic. Make sure RC, FSX itself, and other add-ons running are allowed to bypass checks in your security applications. In some of those security applications programs that frequently communicate with another inside any Program Files folder anyway after a measured time can be deemed to be a virus in the heuristic protection schemes.Does this only happen with RC running?

I actually was able to fly a 5 hour flight today with no crash. I asctually applied the FSUIPC.ini FS9 fix to my FSUIPC4 ini, but based on what Pete said, this probably wasn't the reason for the one time success. Because this phenomenom does happen after an hour, with different flights and through different areas, I am curious about this 713 pinned topic. I'll have to wait until the next CTD to find out though.

make a log, instructions pinned to the top of the forumalso, make sure you have the latest versions of fsuipc installed. regardless of what version you have, go to the site (pinned to the top of the forum), and download and install the latest versionjd

Did you get an error code in the message box? If you are getting these after an hour on different flights through different areas, then check the error 713 pinned topic. Make sure RC, FSX itself, and other add-ons running are allowed to bypass checks in your security applications. In some of those security applications programs that frequently communicate with another inside any Program Files folder anyway after a measured time can be deemed to be a virus in the heuristic protection schemes.Does this only happen with RC running?

Just started a flight from KSFO to KCLE. Shortly after Modesto had a CTD with the following explanation:Problem signature:Problem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61472.0Application Timestamp: 475e17d3Fault Module Name: ai_player.dllFault Module Version: 10.0.61472.0Fault Module Timestamp: 475e180cException Code: c0000005Exception Offset: 00018fe7OS Version: 6.1.7601.2.1.0.768.3Locale ID: 1033Additional information about the problem:LCID: 1033

Fault Module Name: ai_player.dll

You appear to be getting rather random errors in a variety of different FSX modules. Whilst your earlier reports pointed to scenery layer problems this one points to corrupted traffic BGLs.With different errors occurring at different times I'd be concerned, instead, about hardware or BIOS settings. I see you are running overclocked. have you checked temperatures to make sure nothing is overheating? Also, make sure you are not accidentally overclocking the memory modules -- I see you only have 1600 MHz ones and they should not be overclocked if you want a stable system. I use 2000 MHz ones and run them at 1866 for stability.RegardsPete

You appear to be getting rather random errors in a variety of different FSX modules. Whilst your earlier reports pointed to scenery layer problems this one points to corrupted traffic BGLs.With different errors occurring at different times I'd be concerned, instead, about hardware or BIOS settings. I see you are running overclocked. have you checked temperatures to make sure nothing is overheating? Also, make sure you are not accidentally overclocking the memory modules -- I see you only have 1600 MHz ones and they should not be overclocked if you want a stable system. I use 2000 MHz ones and run them at 1866 for stability.RegardsPete

Thanks, Pete. Temps are fine--between 35 and 50 degrees. Memory is not overclocked--set to 1600.

What is your operating system? Exception Code: c0000005 means that the module is attempting to access a protected area of operating system ram.This could be instability as Pete mentioned. Try reducing your overclocking. Are you running FSX with the modification to use 3GB? (I don't know if its exe is set up for that out of the box.)On my standard old box the CPU runs at 150 degrees F (3.2GHz P4 not over-clocked) with FS9 running. Case at 95F. I have a utility that puts the data in the task bar. See if one came with your motherboard.

What is your operating system? Exception Code: c0000005 means that the module is attempting to access a protected area of operating system ram.This could be instability as Pete mentioned. Try reducing your overclocking. Are you running FSX with the modification to use 3GB? (I don't know if its exe is set up for that out of the box.)On my standard old box the CPU runs at 150 degrees F (3.2GHz P4 not over-clocked) with FS9 running. Case at 95F. I have a utility that puts the data in the task bar. See if one came with your motherboard.

I' run a utility called Real Temp all the time to check my temps. I also run Prime95 and the Intel Burn test to check stability and the system passes with flying colors. Core voltage is 1.35, which from what I've read is not too high and the temps would seem to support that.Frustrating.

Try a few flights without overclocking. This problem is too intermittent to catch.It does not appear RC is causing this problem.I do not see your Win version in your tag description.What application is generating your traffic?

I found the atc.dll errors I used to get were due to RAM timing issues as Pete of stated. Can't remember exactly how I resolved them> I think by running at 1366 but not sure.

Edited February 8, 201214 yr by Barnstormer1

Just to put closure (I hope) on this issue,I already had the most recent version of FSUIPC installed, but I re-downloaded and re-installed it anyway.For some reason, I ;have flown 5 or 6 long haul flights with no problems. Hope that was the issue.Thanks for everyone's help.Dan Cole

I'm getting this issue recently. All from ATC.DLL. I have the most recent FSUIPC4. I'm also running RC4, AS2012, GEX, UTX, UT2. Never had an issue until last last 4 flights. Ideas?Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: atc.dll, version: 10.0.61472.0, time stamp: 0x475e180eException code: 0xc0000005Fault offset: 0x00028bb1Faulting process id: 0x29b0Faulting application start time: 0x01ccf9a1fea77333Faulting application path: C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exeFaulting module path: C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xatc.dllReport Id: cc7e9bc9-65a3-11e1-a34b-a4badb02fcb3

I'm getting this issue recently. All from ATC.DLL.

Nothing in FSUIPC or RC has anything at all to do with the ATC.DLL. It sounds like either an FSX file corruption, or bad scenery files. You might do better checking in the FSX forum or the Crash To Desktop (CTD) Forum. Maybe others have experienced the same problem and can offer advice. I must admit, in the six years of FSX so far, and despite seeing a myriad of CTDs, I've never actually seen one in ATC.DLL.RegardsPete