It was one of the tracks. A very poorly done conversion, so I am not losing any sleep about dumping it.
Having been in IT for many years (in a previous career), I could understand the track description length crash that happened with Build 298, as tragi-comical as it turned out to be. But an incompetently developed track affecting just one car in such a peculiar and bizarre manner??? Wow...I'm glad I'm not working on the coding for this title. It really speaks to the need for a serious overhaul of the UI and component "security" system. No component should be able to break other unrelated components. Crash, yes. Not load, yes. But not stuff like this.
Thanks for your quick responses, though and attenpt to help. Appreciate it. It might not have been so easy to resolve. I knew all along something had to have changed--I just had no conception that a track could cause an issue like this, so posted first in case it was a known problem.