A few observations from my studio:

The operating system is windows... not always a rock solid OS. Things do go wrong from time to time .... just because. 

I don't generally "run out" and buy the latest upgrades and don't always load the updates as they come out. 

My current DAW is running XP pro/32 and X1 essentials (no updates) and is not internet connected. It runs pretty much like the day I first turned it on after I built it myself. 

If I load X1, and while working in my project, I notice that the generally smooth operation of X! starts to become erratic in any way..... audio glitches or a cursor that starts to get a bit "jumpy"... I will click on SAVE and then close the system completely down, including the interface and start again from a complete power off condition.

I have melodyne editor (ME) and it is probably, without a doubt the most CPU hungry plug in the stable. 

As a result, I use some precautions when I work with it. I don't very often run multiple instances of it, as having it in two or more tracks at any given time. One track at a time.  The second thing I have learned about ME.... it will crash and glitch the DAW from time to time when things don't flow correctly inside the box, and that will often result in a crash and subsequent loss of work. So I tend to work in manual correction mode, and I work on one line of the song at a time. I click SAVE when I finish that line, before moving to the next. 

Most of the time, my system is rock solid and ME runs perfectly fine and smooth and causes no problems. However, when I do see that the system is not running like a top, whatever the reason, I'm always willing to click SAVE and reboot to a fresh start.   

Clicking on the SAVE should be a habit anyway if you do not have the autosave feature turned on, which I do not. 

Good advice from Herb.
IF Sonar had a "Save" icon, I WOULD click on "Save".
Fortunately Sonar's key "bindings" allows a single click on the ` (tilda) to prevent
Ctrl+S from causing my carpel tunnel being life threatening. ;)
Had another "white out" yesterday, this time it did launch the "problem reporter"
or whatever its called. (saved in appdata, is that right; no internet on the Cat)
Had some "issues" with the PC EQ, moving knobs DID NOT change the freq, Q, gain
"reported" new levels until I turned the EQ off/on.
Should have done exactly what Herb suggested; power down and re-boot.
I guess I'll move this project to X2 and "see"...

T

If you want a save icon, Duckbar has one.

Thanks Scook,
I think my "save" rants are just my passive/aggressive evil twin coming to the surface.
Between the ` and the save button on the FW, I'm covered.
Just forgot the other day, the "old Fart" other twin, Senior moment, nothing to see here...
If I had "Duckbar" installed, Cake and I would have someone/something to blame for the
occasional "white out"; no?

T

Maybe, however since the whiteouts are occurring now without Duckbar, it would indicate the problem probably lies elsewhere. Who knows, it might fix the problem. Although, I have installed Duckbar on my machine, I do not use it. Installing Duckbar makes no changes to SONAR. Running Duckbar will launch SONAR unchanged with the Duckbar toolbar on top of SONAR. The program also has a backup facility to make it easy to get back to the original SONAR install should you elect to use the Duckbar modification tools.