Hi everyone,

 

I've had this CTD quite a few times, and am having trouble finding a solution. Most of what I've found is for FS9, and what I've found for FSX isn't always relevant (OC issues, very low system specs, other addon issues, etc)

 

System specs:

 

Windows 7

Intel i7-2600 3.4ghz (not OC'd, completely stock)

8 gb RAM

nVidia GeForce GT 545

FSX Gold- Accel installed

 

Windows Event Viewer report:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x00013ddc
Faulting process id: 0x1238
Faulting application start time: 0x01ce243e669e5049
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\FSX\atc.dll
Report Id: c209a0e8-903a-11e2-890c-d4bed99b0a12

 

2 FSX.cfg tweaks- HIGHMEMFIX=1, AFFINITYMASK=14

 

Sliders are appropriate for my system, nothing maxed besides mesh etc., Scenery Complexity Very Dense, Autogen Density Normal, no road cars, Airline traffic/GA traffic 10%, frames set to unlimited. AA/AF on. Not using nVidia Inspector.

 

This came off a fresh install a week ago, and I've had it as well several times before the clean install. Addons used during the times it has happened recently- FSUIPC (registered and up to date), AS2012, MyTraffic Pro 5.4b, NGX and Airbus X Extended. Some sceneries installed but was in cruise when the CTD's occur (to shorten the list- several from each FSDT, FlyTampa, UK2000, Aerosoft)

 

I have a creeping feeling it is caused by MyTraffic Pro, since I update it using the 'Manage FSX settings/Update ATC sound files', but of course I could be wrong.

 

It doesn't happen every flight, but it has now happened about 5 times, and has crept upon the line of wanting to find out more about it.

 

Thanks for any and all input!

I retested again and found a place where I can recreate this CTD every time.

 

Route: KSAN PEBLE4 SLI DAG KEPEC3 KLAS

 

On this route, right at the turn at SLI I encounter the same atc.dll crash.

 

Windows Event log:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x00013ddc
Faulting process id: 0x1540
Faulting application start time: 0x01ce245c27249644
Faulting application path: C:\FSX\fsx.exe
Faulting module path: C:\FSX\atc.dll
Report Id: 4eecf46b-9054-11e2-bca0-d4bed99b0a12

 

 

FSDT KLAX is just to the north of SLI, but FSDT sceneries do not activate unless you are within a certain distance from them (9nm lat/long IIRC), so I doubt any of its involvement. My flights testing this were both at night and day, so I'm thinking this may be an error that Pete Dowson once mentioned for FS9 (though I'm on FSX, we know how much was ported...) in a similar CTD thread- a related frequency around 80nm from the current position causing the crash. Maybe this will shed some light or insight?

 

Hopefully Jim or any other of the very knowledgeable members can shed some insight on this. I've definitely found it as reproducible. If you need any more info I'd be happy to test/share.

The atc.dll is a common FSX CTD.  The atc.dll module is used as one of the GUI based modules responsible for handling in-game layout and dialogue correspondence with the main game function calls, within FSX.  It is related to the graphics display during game play and sometimes has problems displaying multiple image streams, especially when it renders multiple overlays.  Gobblygook but you are probably missing a file or texture that is missing.  One way to find out the missing texture or file is to place the following lines in the [scenery] section of your FSX.cfg (thanks to FS Developers.com):

[sCENERY]// To show alerts or areas, set to = 1 // To hide alerts or areas, set to = 0 // Alert for missing texturesShowMissingTextureAlert=1// Alert for missing objectsMissingLibraryAlert=1// Render Trigger areas as visible boxesShowTriggers=1	

FSX will now display an alert dialog identifying the missing file / object, or render trigger areas. 

 

That could tell you exactly what object or texture is missing and provide a clue as to what is causing your CTD's.  You could also disable all of your addon scenery, fly the route and see if the problem occurs again.  If not, then start adding your addon scenery 2-3 sceneries at a time until the CTD reappears.

 

Hope this helps!

 

Best regards,

Jim

Thank you very much for the fast and informative reply Jim. I'll add those lines to the .cfg, fiddle around and try to find the cause with it, and report back.

 

Thanks again!

Hope it works out Kyle.  Just a warning that you will probably get a lot of hits.  Just click okay each time or take a picture and move on to the next.  Most likely you will not get a crash anymore with these lines added as the lines caught the missing texture or file before FSX had a chance to crash.  Good luck!

 

Best regards,

Jim

Hi Jim,

 

With those tweaks alone, and not removing/disabling any of my addons, just recreating the flight exactly, I managed to pull it off and make it through that turn. Like you mentioned I probably would, I encountered quite a few of these pop-ups, but they were similar to eachother and I'll explain how.

 

Any input or advice on anything I can do will be greatly appreciated!

 

1) Upon selecting the NGX in the FSX main aircraft selection page, this little guy showed up:

 

 

 

2) Once selecting the aircraft, this came up. This also came up in the sim, every time I would change from any view, to the VC view. Once I hit the VC, this popped up:

 

 

 

3) This one is most definitely a product of the scenery, which is LatinVFR's KSAN. My question on this would be should I just find that file and disable it? It popped this message anytime I panned to the western portions of the terminal buildings:

 

 

 

4) Now, for the big tamales. These are the two popups that came up, at a place 2 minutes flying time from the curve it always crashed at. I would assume they refer to a missing texture like you mentioned above, but unfortunately I'm not versed in understanding what this text means, but hopefully you can help me out:

 

 

 

 

Thank you again for your help!

Regarding the scenery library objects not found, here's an excellent post I found relating to this topichttp://forum.avsim.net/topic/352086-scenery-library-object-missing/ .  The way I understand it you'll have to go back to the developer and tell them about it and maybe they can issue a fix or maybe you can go into the scenery folder and rename the offending .bgl file that contains the object. 

 

In regards to the Latin VFR KSAN error where it failed to load a texture, you'll need to conduct a search on your system for the file and make sure it is in your KSAN texture folder.  It could be a sharing problem too where the file is not being shared with all users on the computer.  Just right click the KSAN folder and click on Properties.  There should be a Sharing tab.  Make sure the folder is being shared with all users. (This goes with the other files too that have missing objects).

 

In regards to the PMDG NGX errors, it appears the NGX was not properly installed.  I really can't say for sure.  This is definitely all out of my limited expertise.  You might post it over in the PMDG forum and see if others know what might have caused this error or submit a ticket to PMDG Support.  Of course, you can try a reinstall too.  Do a search on your system for the gauge or cabinlight.  Maybe they are somehow corrupt.

 

Best regards,

Jim

Thank you very much Jim, definitely a great start and your expertise is much appreciated!

 

I'll go from there!

Wow! Hey Jim, could you pin this one? I just made a post today concerning the atc.dll, and then I found this one. Now im really excited to try this out.

 

The ATC.dlls ive had, has not been easy to recreate. The last one ive had was on a flight from FLL to AFW using pmdg md11. It happened as I was closing in on my FSDT KDFW. I`ll get right to it and add those lines as soon as ive got a chance.

Just click on "Follow this Topic in the upper right hand corner.  That should work just as well.  Hopefully the lines added to your fsx.cfg will help you find your problem.

 

Best regards,

Jim

So after modifiying my cfg, this is what it looks like. Usually theese green boxes only appear on the fuel box at every airport where they are

found and dont go this far up. Was flying over PHNL and found these huge monsters.. What is missing? Thanks for helping out.

 

 

 

 

 

(seems its gotten abit off center, but they are still easy to see)

I'm not sure if those are your computer specs in red or you are just joking.  It is very confusing and I can't understand what you really have installed in your computer.  I'm assuming it is all tongue-in-cheek. 

 

The picture looks pretty bad to me (could be my monitor).  Is your monitor resolution set to 32 bit or 16 bit?  It is not very clear.  The resolution is very poor and you can literally see each individual pixel.  Perhaps you could upload and attach a copy of your fsx.cfg (rename it to fsx.txt or Yngve_FSX.txt) and I can take a look at it (look at more reply options on how to upload an attachment).  I also want to apologize but I do not understand what the green boxes are used for as I have never seen them before.  Is this from an addon program?

 

Best regards,

Jim

Disregard the visible pixles, I just stored the image in a poor quality. FSX looks WAAY better than that on my pc.

When I added the lines from above, to the cfg, those green things appeared. Once I remove the mentioned lines from the cfg, they disappear. Have no idea what that is.

You mean the texture missing alert lines?  Yes, that's strange if that is happening.

 

Best regards,

Jim

Will that require me to re-install FSX in order to fix it?