konradh
Craig, I'm sorry, I did not only because it seemed very time-consuming given the number of tracks.
 
Now, however, I am curious and will check that out.  I did not overwrite the problem version so I can still analyze it.  Infact, I'm going to do that right now.

You don't have to do all the tracks. Just do a few and see what happens. If they all stop at the same point, then once you get past a half-dozen tracks or so don't go any further. But if it plays all the way through when some tracks are archived, that might be worth pursuing.

Just to close this out—unless it happens again!—I tried the archive test.  With only one vocal trck playing (no Melodyne or effects), the project played OK,
 
It tooks some time, though, because the track view did not want to scroll vertically and when it did, it jumped around.  When I un-archived another harmony track, Sonar frzoe up again which required a total PC reboot.  I am afraid this may not be worth the time investment until I get my immediate work out of the way and can afford to do some testing.
 
If, God forbid, this happens on the new version of the project, then I will have to revisit everything.  I am praying that the full-disk-pic cache thing was the issue.  Reading related threads on this forum makes me think that is a strong possibility.
 
Thanks again for your patience helping me.

You can streamline the process - play half the tracks. If they make it to the end, then play the other half. If there's a crash, sub-divide that group into half again and see which half causes the crash.
 
The reason why I think this is important is because if you can isolate your issues to a particular plug-in or track setting, you can avoid it in the future.

It is my understanding that the picture cache can be deleted, as Sonar will rebuild it.  This seems to have fixed some issues for some folks - mostly with redraws, but if it doesn't hurt to do it, it might be worth doing.  PLEASE SOMEONE confirm that Sonar will indeed recreate the picture cache after it gets deleted.
 
Also, If this is a large project that has accumulated a large number of unused audio clips, it might be worth first making a backup of the entire project folder (with its Audio sub-folder), just to make sure you don't lose anything.  Then, open the project and do a Save As to a new folder, with the Copy All Audio option checked.  This will save the project file to the new location, and will also only copy audio clips that are actually referenced by the project in its current state.  This effectively cleans out all the leftover unused clips.
 
The above two sets of things may or may not fix the current problems, but I think if there is something wrong with the picture cache - which from one of your comments may be the case, then there may be a chance rebuilding the picture cache might help.
 
And while there may not be anything inherently amiss with a bunch of old non-referenced audio clips, maybe something in there IS getting confused for some reason.  Cleaning out the old unused clips might help - IF that is part of the situation.  I do not see it as hurting anything.
 
Maybe some other folks have some thoughts on the above?
 
Bob Bone
 

Konrad,
 
If you find a way to send me the project, I can at least validate that the project plays fine for me in X3.
 
I may even have an old version of X1 on my laptop and I can test there too.
 
Let me know if you want me to try it. (Gobbler would work).
 
G
 

konradh
OK, time to start recreating my work in an older version of the project.
 
1. The PicCache was on D, not on C as I was told.
2. The size was set in the configuration file as 500 MB.  The file on the disk was bigger than that. (How?)  I changed the size to 1500.
3. I unfroze all the frozen VIs.
4.  I deleted Dim Pro, in case that was the issue.
 
The project will play about one third of the way through before it stops and Sonar locks up.

Regarding 2, sonar creating a wov file bigger than the allocated storage, sounds like a bug,and a recipe for a crash... Is it a truncated wov that causes the halt when it huts the truncation maybe?

Did you clear the picture cache after increasing the size?