Dim Solo/Mute Issue - 2017.5

Solo a track and it plays solo, as expected.
 
Click the DIM button and you can hear the other tracks faintly as expected BUT the soloed tracks are now muted. Can't hear them at all. Dim Solo is broken!

Opened another project and it works as expected. Seems to be project specific. So easy to corrupt these cwp files I guess.

YMMV. In my 17 years of using Sonar, it's been on 6 or 7 different systems and everyone produced a few corrupted projects. I can "save-as" a project with 20-50 versions while doing a ton of edits to each one, so it's not surprising to me if one of those gets corrupted now and then. Since only one project is behaving this way and I've actually been able to trace other corruptions back to a singular project I believe it's more likely an "evolutionary" development rather than a hardware issue. Only one of my systems actually had bad ram and it was replaced under warranty.

Info on causes of file corruption from SONAR's documentation:
 
Data corruption on a DAW can occur due to various reasons, a few of which include:
 
*  Your hard drive might suffer data loss.
*  Windows delayed writes might fail leading to data corruption.
*  Many hard disks have a “write through cache” buffer for efficiency. Occasionally this write through buffer might not get flushed due to a driver error or system crash. In such cases data might not be flushed to your hard driver causing corrupt files (SONAR requests Windows to flush this buffer after a file save operation).
*  A plug-in can corrupt SONAR's memory space causing invalid data to be written to disk when the project is saved.

I routinely open up old projects in Platinum, then strip out selected tracks to create new music beds and backgrounds for videos. No problems yet...

soens
Together we keep the universe balanced.

Yes, but...I'm always looking for the "magic bullet" that makes some systems work almost flawlessly, while other people experience strings of issues. I've noticed there are some people who experience a serial line of problems and although in some cases it's pilot error, in some cases it's most definitely not. Is there some "poison plug-in?" Some background service that interferes? Pieces of Norton left over from a demo that was installed on the C: drive and never completely removed (as happened with my mother's computer - deleting every trace of Norton make it like a new machine)? There has to be something that accounts for these disparities.
 
I do try to follow good practices, and I think that has a lot to do with why I can run SONAR for hours on end without incident. But which of those "good practices" is the crucial one that makes the difference? I wish I knew so I could tell others.