Hi all,Have been having a problem flying a route from EKBI to EGBB lately, every time I am asked to contact London (not sure what freq) I get an FS ctd and it reprts atc.dll as the culprit. Radar Contact continues to run after fs crashes.I have looked through the forum and have tried the fixes, I have FSUIPC version 3.74 but still no luck.I also note that this should have been fixed with FSUIPC.Some ideas?ThankyouGarry

Hi GaryThis is a very difficult bug to fix. Pete Dowson had some success with FSUIPC but couldn't trap all instances of it.Rather than repeat all the help have a read through this exchange. It may help. Fortunately the problem is relatively rare. The down side is that a permanent fix is unlikely.http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchCheers,

Thanks Ray,I discovered that the frequency that caused the crash was London Control 118.77, in my F4.csv file I changed a frequency in Billund, that has the same frequency.I saved this and tried again, same results as before crashed when asked tochange frequencies to 118.77.Have I missed a step in changing the frequency?ThanksGarry

Hi Garry,Did you use Notepad to edit the F4.csv? Using Excel will cause problems. Assuming you did all I can suggest is you change London Control to a different frequency - say 118.75 - and see if that resolves it.Not satisfactory I know but these crashes tend to be few and far between. I can honestly say with my hand on my heart I haven't had one since that test on the LIRF-EGLL flight and I always fly with RC4.One thing you might check is that you have the ATC option enabled in Sounds but turn the level down to zero. That might help.Cheers,

Hi Ray,Can you do me a big big favor? I just got RCV4.3 this week. I installed and did a few KEWR-TNCM hops with no issues other than self induced. ;) I am really enjoying the program so far and the enhancements are really noticeable.There is always a BUT...I know you are a LVL-D 767 buff just like me. Can you try to do KEWR-EGLL and see if you get a crash? This is probably my MOST flown flight in FS with this configuration for years and I have never black screened before. I have tried ~ 6 times now and get different crashes at various times. I spent the entire day yesterday trying all of the recommended fixes. JD, I don't want to log it until I can isolate that RC is the issue. If Ray can replicate that will pretty much confirm it. The only reason I am not sure is the first day I got the crash was yesterday coincidentally the first day of summer. I got it again today and I am trying right now without RC to see what happens.(At least you know I searched the entire forum before posting ;) )I am using FSUIPC V3.70 registeredLatest version of RC4Default ATC is enabled with sound turned down and RemoveATC is enabled in FSUIPCEGLL and KEWR both appear to have ATIS of 118.00 but I changed EGLL manually in the controller setup screen. I am doing BA 184 the AM flight using LVL-D,/FS2Crew/British Voice Sets. I am sure you use that setup :)I am using MT as well so there is a BAW 777 leaving at the same time as me but I think that is 186...Thanks so much in advance,Cheers Ray!!!-Paul

Hi Paul,I don't have the LDS767. I'm a Project Magenta user so I use the PMDG737 AIR file and model but with no PMDG panel.Having said that the crash you're getting isn't probably connected to the panel. If it's ATC.DLL then it is related to clashing frequencies but as you mention black screens it sounds like some other kind of crash. Maybe graphic driver related?? The only known crash connected to RC4 is ATC.DLL but because it's a FS9 bug nothing can be done about it.Just changing the EGLL ATC in the Controller setup screen may not be enough. The data file containing the frequencies could still contain the original frequency.Remember that this is a known FS9 bug and whilst Pete Dowson managed to trap and eliminate some of them in FSUIPC he wasn't able to catch them all.KEWR-EGLL is a very long flight. I could fly it using Concorde which will help on the time issue but if it does crash it probably isn't something that can be fixed.Please attach a FS9 PLN so I can match your path as closely as possible. By now you may have completed your latest flight. Did it also crash?Glad you're enjoying RC4 :-)

Hey Ray,That is why I was so hesitant to point the finger at RC in the first place. It is just Murphy's law that something will go wrong right after the RC install...I did attempt another flight and did indeed receive the black screen even without RC.So I went into safe mode and did the driver uninstall/Driver Cleaner/Crap Cleaner/Registry cleaner routine and reinstalled the same driver rev. They have been stable for quite some time so best to go back to a known variable. I then attempted a quick circuit with the LVL-D and all was well. Now I will add FS2Crew back into the mix and move one step at a time.I also because I am OCD, deleted my PF, defragged, recreated my PF and now I am going to try again minus RC4. Provided that is succesful I will then re-install RC and try again. Ah the frustrations of this hobby we love so much...Thanks Ray,-PaulPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0

Hi Paul,The black screen crash is almost certainly not related to the ATC.DLL problem. That shows itself with the standard MS crashed program advisory message with the option to send to MS.Having reinstalled your drivers I would be reluctant to make any further changes for 2-3 days. Only then after you have completed several flights without problem will you be certain that you have a stable system.I know it's tempting to add the others in quickly but it's best to be snail-like in these circumstances. If it takes a week to complete at the end you will have far more confidence that the problem is cured.Unless of course you do get the dreaded atc.dll :-erks

Hey Ray, 3 of the crashes did reference the ATC.DLL only on KEWR-EGLL which is when everything started. I had already done a few KEWR-TNCM hops without any issues at all.I agree, I will be diligent,Thanks so much,-PaulPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0

Hi Paul,Oh, I thought you said you got the black screen? Maybe it's down to how we describe things ;-)The ATC.DLL crash is a lot more complicated than just a matching ATIS. If only it was that simple.Keep us informed on how you get on. In the meantime I'll try to find time for the KEWR-EGLL hop although I have changed the London ATIS from the default of 118.00 so I may not get the problem.Cheers,

Thanks Ray, To be clear it was a black screen followed by the typical FS error and then you can click on details and it lists ATC.dll as the culprit. I have never seen it before. I am now ~45 minutes into KEWR-EGLL right now after re-installing drivers and not using RC4. It will be interesting to see how the rest of the flight makes out.Thanks for trying but if you already changed the frequencies I doubt you will get it. What is the file that needs to be edited?Thanks again Ray, greatly appreciated,-PaulPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0

Hi again Paul,If you fly in full-screen mode it probably explains the black window before a error message is displayed. I fly in windowed mode for my sins.If you're not using an ATC program (RC or the default one in FS) I doubt you'll get the problem because you won't be changing frequencies. Well not comms frquencies which are responsible for the crashes.If you want to replace the ATIS frequency at EGLL with the real one you need to edit f4.csv (from memory) in the Data folder. Don't use Excel if you have it as it will corrupt the data. Right-click the file and choose Open With... and select NotePad.Search for EGLL and then look for 118.00. The real ATIS frequency at EGLL is 128.07 (Arrival) and 121.85 (Departure). Unfortunately only one can be stored in RC so I'll leave it to you which one you want to use.After doing this try your KEWR-EGLL flight again and see what happens or what doesn't happen) ;-)Cheers,

Thanks Ray,Interestingly enough I decide to load up the PSS 777 and try that as I had only tried with the LVL-D. I had another crash without RC and starting going through the usual. I pulled my memory, re-set it tested it and kept trying with continuous crashes. I finally decided to switch the season back to spring and guess what I am farther now than I got with any of my other "fixes." If this flight works I will try moving it forward by a week? Maybe it is something to do with transitional textures? Really weird but I just passed TA with the PSS 77 enroute to EGLL in Spring.Thanks again for the suggestions and I will let you know,-PaulPrimary RigLiquid CooledIntel C2D E6600 @3.2 gigsAsus P5N32SLI-Plus2 gigs Corsair XMS PC6400 4 4 4 12 @810Dual OC'd XFX 8800GTX @ 2 gigs24 inch Widescreen LCD 16XAA/16XAFDual 19 inch LCD'sRaid-0+1PCPower and Cooling 1k Quad SLIhttp://home.comcast.net/~psolk/3monitorsa.htmlBackup RigAMD 4000 San Diego @ 2.72 Gigs Kingston Corsair XMS CL2XFX 7900 GTX Raid-0