Beachdog2001 wrote on Jan 6^th, 2009 at 4:01am:

Eric,  done....this happened again 2.5 hours into a 3 hour flight.  I simply changed the runway from 35L at KDEN to Rwy 26, selected FUZZZ intersection, tried to close the discontinuity and bam, CTD, game over. I have had this problem on all flights but one so far, and that one I had the AP not disconnecting problem. Oh, and changing to FSUIPC 4.3 didn't help me with the AP disconnect problem.  Into KSEA at 200', I disconnected the AP, had no controls and the aircraft landed itself at -600 fpm :o.  I reinstalled FSUIPC 4.3 and was going to try it out again on this flight...but....CTD >:(

Yeah, I've tried everything too. The problem is with the FMC code. I suspect the customers who don't have this issue don't use the FMC fully and don't do things like switch runways or insert crossing restrictions.

This issue was reported so long ago that I can't remember if I created a ticket or not. I too assumed that since CS was aware of the issue that they would fix it. I'm starting to think they can't or won't for whatever reason.