There are two versions of FSUIPC (4.06 for FSX and 3.71 for FSIX). I switch between FSX and FSIX and use ASv6.5 for both. However, when I use ASv6.5 in conjunction with Squawkbox 3.1 in FSIX, I will get a CTD with no error boxes. I can run Squawkbox by itself in FSIX without ASv6.5 just fine. I can also run ASv6.5 in FSIX without SB3.1 without any problems. Before I loaded Asv6.5 I never had a problem running SB3.1 and AS together in FSIX.I have latest drivers and leading edge system--memtest is fine and I have no firewall/antivirus issues (as I said no problems before). I uninstalled/reinstalled SB3.1 and FSUIPC...still get CTD in FSIX only with SB3.1 and ASv6.5 running with FSUIPC 3.71.Any thoughts?Thanks in advance RakeAMD FX-60Nvidia 7950 GX2 (1GB) video4GB ultra low latency DDR RAMRaptor 150GB (10000rpm) HDDell 24"

Hey, interesting to find someone have the exact same problem I'm having and I've also been searching for a solution. I had thought that it was just an interaction between FSUIPC and Squawkbox. I hadn't thought that AS6 might be implicated. I've discussed this with Peter Dowson and he did mention that he's posted a version 3.711 in his forum which contains a fix for something that might cause a CTD under certain circumstances. I've tried 3.711 and it seems the CTD occurances are less fequent but still do occur. If I go back to FSUIPC version 3.70 things seem ok.I'll have to try flying a while with 3.711 but without AS6 (drag) and see if that results in no CTDs.Let's stay in touch about this and see if we can find a solution.

DaveI downloaded FSUIPC 3.715, reinstalled ASv6.5 and reinstalled SB3.1 with no change. Just for kicks I also deleted FSUIPC 4.06 from FSX and same thing happened. I have no problems running either SB3.1 or ASv6.5 individually in FS9 but together get a CTD roughly 3-5 minutes after engine start. So they initialize fine together, but something goes haywire a few minutes later.Never had these issues with previous version of ASv6--only has happened with the addition of FSX (FSUIPC 4.06) and ASv6.5 (build 536).Stumped.Rake

I'm going to try 3.715 now. I have never installed FSX or FSUIPC 4.x. When I go back to FSUIPC 3.70 I don't get the CTDs, so my feeling is that whatever is going on only started with FSUIPC 3.71.

Ok same problem with 3.715 FSUIPC installed. After about 10 min of being connected to VATSIM, while climbing out of KRDU, FS9 crashed to desktop with no error message. So I thought to myself, that's about the time of the first AS6 weather update since connecting to VATSIM. So I decided to try the same flight again and this time the only change I made was to turn off VATSIM updates in AS6. Well the flight went fine all the way to KDCA. One flight is not conclusive so I'll keep flying with VATSIM updates off in AS6 and see what happens.

DaveDefinitely think you're on to something--instead of 10min updates, I went into ASv6.5 options and made it 240 minutes--flew for nearly an hour with no problems then poof--inbnd on an ILS into KCLE...CTD!!!Can you shoot me FSUIPC 3.70 so I can reinstall that? Thanks.Rake

Dave--read this:"I had something similar going on, and finally tracked it to a change that had occurred in my FSUIPC.ini that had removed the line: RemoveATC=Yes This caused the old ugly atc.dll CTD to come back and haunt me for the majority of one very frustrating weekend. No idea how the ini file was changed, but I went back to my saved copies and it looks like the change happened around the time I upgraded to 3.70 There had been a few random dumps...but a few weekends ago I found a flight profile that really tickled the atc.dll bug and it was a steady stream of midflight CTDs. Once the param was put back...voila. Regards"I am going to take a look--not sure where FSUIPC.ini (could not find it in search files/hidden files) is but there is an FSUIPC.cfg.Rake

Ok I now have two more flights under my belt with VATSIM updates turned off in AS6. No problems at all. I'm not going to say for sure yet but I think this might be the problem. This is with FSUIPC 3.715 installed and running SB3.1. We'll see.

DaveI went back to FSUIPC 3.70 and had similar CTDs with AS on-line updates selected (VATSIM updates deselected) every 10 minutes. As indicated, I've seen other posts in different forums with similar issues with FSUIPC 3.70 and later...BUT, didn't have an issue with 3.70 till running ASv6.5 with SB3.1.Jim---if you're reading this thread--have you guys experienced issues with what Dave and I are talking about? Is it an FSUIPC thing or a ASv6.5 thing?Does anyone know how to access FSUIPC.ini file?ThanksRake

Hi Rake,No, there are not other reports of this from our end.The .ini file is in the Modules folder.I am using 3.70 in FS04 and do not have CTDs.I suggest a clean reinstall of FSUIPC.Any error messages at all?Thanks All,Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Hi Jim;There are many other reports of 'no error' CTDs in other forums but they probably have no idea what's causing it.FSUIPC 3.70 works fine for me as well. This problem started and continues with every version after 3.70A clean install of FSUIPC will not fix the problem, if it's post 3.70 you will still experience the problem.There are absolutely no messages at all. The screen goes completely black for about one second and then you find yourself back at the desktop.I have now done about 5 flights with FSUIPC 3.715, AS6, and SB3.1 with the VATSIM updates turned off in AS6. In this configuration I've have not had a single CTD. I believe there is a change in FSUIPC, post 3.70 that affects the way AS6 interacts with FSUIPC when it tries to get VATSIM updates. But that's just a guess on my part. I'm not suggesting a bug in any of the software, just a change that probably needs to get looked into.And thanks for all your attention.

Hi All,Here is what I have found:1. I updated my FSUIPC to V3.71.2. I flew about 90 minutes with FS04 and AS B536 in Online Mode and did not have any CTDs.3. I turned on VATSIM weather, flew close to another 90 minute flight and did not have any CTDs.So for me FSUIPC 3.71 is good and B536 is good and FS04 is stable. The only thing I don't have is SB. So I can't duplicate this.Happy Holidays, Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Hey Jim;Thanks for your interest in this. What you've found is exactly correct. The problem is only with SB3.1 running and connected to VATSIM and AS6 set to get VATSIM updates.

Hi Dave,Waiting for Santa's elf to be done wrapping presents.Is the weather option turned Off in SB?Jimhttp://www.hifisim.com/Active Sky V6 Development Team Active Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter: http://www.jdtllc.com/AirSource Member: http://www.air-source.us/FSEconomy Member:http://www.fseconomy.com/

Yep.