I know your position relative to the relationship between ASv6 and CTD's and other problems, but I'm one of those folks having a problem that seems to exist only when using ASv6. I've been tearing my hair out (not really) trying to track it down. I can't say that not using ASv6 completely eliminates the problem, but my experience so far is that this is true. But, having used ActiveSky since the WxRE days, I can't envision being without it.My system: Athlon 4200+ dual core, Nvidia Nforce 4 chipset, ATI Radeon X800XL video card, 1 GB OCZ RAM, Creative Soundblaster Audigy sound card, etc.I have several other add-ons -- Ultimate Terrain, FSG mesh, FlyTampa KSEA, and lots of freeware scenery, PMDG's 737NG, Level D's 767, and Flight1's ATR72. I fly pretty much exclusively online on VATSIM, and have the options in ASv6 set up for that use. FS2004 weather is set to clear, FSUIPS weather options are off, and so is Squawkbox weather.Here is an example of the the problem that I have recently been encountering. Last night, I tried flying from KSEA (where it was raining) to KGEG. I start ASv6, let it update (KSEA is the default location), then load the flight plan. After it updates, I start FS2004 (PMDG 737). After I log onto VATSIM, and the weather updates, the computer locks up solid. This happened three times in a row. After the 3rd reboot, I did everything the same, but without ASv6 (but with Squawkbox weather turned on) and did not have a lockup.Today, I set up a flight from KPDX to KSEA. I ran filemon in the background. Sure enough, it locked up again. The last set of files listed in filemon were a long series of "current_wx_snapshot.asd." I rebooted, then re-tried the flight without ASv6, instead using FS2004 online weather. It worked fine. After completing the flight, I re-set it up again with ASv6. This time the computer locked up while still loading ASv6 (before FS2004 was started). It locked up at the point where it says, "Updating All Graphics (FS Closed)."I went away for a while, came back a couple of hours later and actually was able to successfully complete the flight using ASv6.I know you guys have spent plenty of time chasing down too many people's problems that are not being caused by ASv6 (and I realize that ASv6 is probably not the root cause of my problems), but is there any advice you can give me for tracking this down? I think I can avoid the problems by not using ASv6, but I really prefer using it.Oh, and I have the 1-C update. I also have render-to-texture on in FS2004 (I had to manually delete the rendertotexture=0 line in fs9.cfg as suggested in the PMDG forum post on CTD'S), anti-aliasing is on, and I re-named the Active Radar dll. I've also scanned my AFCAD files, and used Flight Sim Manager to check for scenery problems.Don S.

Hi,I'll point Damian to this.Hope this helps,Jimhttp://www.hifisim.comhttp://sales.hifisim.com/pub-download/asv6...development.jpg http://sales.hifisim.com/pub-download/asv6-banner-proud.jpg http://sales.hifisim.com/pub-download/asv6-banner-beta.jpg

Thanks Jim. I don't want to distract you guys if I've got a Windows problem or something. I had the same lockup happen tonight in ASv6 before starting FS2004 with filemon showing the current_wx_snapshot.asd file. Not to start another wild goose chase, but in all these cases, I have been running ServInfo at the time. After the lockup tonight, I tried it again, but forgot to start ServInfo. Serendipity or not, everything is working fine right now, and I am happily flying my PMDG 737-700 from KDFW to KDEN.Don S.