I have a brand new project that I just started recording to and it is already corrupt.
 
At first the cursor stopped moving, but the audio would continue. I kept retrying the project and it started working again after multiple reboots etc.  Now when I try to delete a single clip, I select it press Delete and - POOF!- every track in my project is deleted as well!
 
I have made sure that clip grouping is disabled if it were to somehow be turned on (I don't use it).
 
Any ideas?

Yup definitely a corrupt project - I recreated it in a new project and the clip deletes correctly.  Quickest corrupt project I have ever had in Sonar, usually they corrupt when they are nearing completion.

I have never had a corrupt project (knock on something wood-ish), in 20 years. There must be something that causes the corruption. If you are creating new projects from a template, it might be time to update the template.
 
Regards,
Dan

I saw an interesting thing on data corruption caused by fast-moving particles from outer space. If one of these particles hits your CPU or memory in just the right way, it can change the value of one bit i.e. change a 1 to a 0 or vice versa, which will change the value of the data. Maybe that's your problem :)
 
I have had only a couple of projects get corrupted over the years. It sucks but any file/data corruption is possible and can be caused by all sorts of strange things including crap from outer space.

35mm
file/data corruption is possible and can be caused by all sorts of strange things including crap from outer space.

I guess anything is possible, but this is extremely unlikely.  Most memory and disk products produced over the past 25 years have stored their data with parity and/or error correcting codes.  It is certainly possible that electro-magnetic waves can kill the whole system, but flipping a single bit and carrying on as if nothing happened is most unlikely.
 
If the SONAR file is being corrupted, it is most likely some software bug related to the user using a workflow that most others do not use.  I have had a few SONAR projects go bad over the years, but nothing recently.

In addition to those wacky particles from outer space, there is also a more down to earth possibility!
 
Do you have bad RAM? Here's how to find out
http://www.pcworld.com/article/3040544/hardware/do-you-have-bad-ram-heres-how-to-find-out.html
 
"Corrupt files can be another sign of bad RAM, especially when the corruption is found in files that you’ve used recently."
 
5 Signs and Symptoms That Your RAM Is About to Fail
http://www.makeuseof.com/tag/5-signs-symptoms-ram-fail/
 
"4. Corrupted Data Files
You might suddenly find that files which you access and use frequently are corrupted and cannot be opened."

I dunno, I prefer mischievous space particles as the reason for everything not working right.

...wicked
I dunno, I prefer mischievous space particles as the reason for everything not working right.

Especially my faulty bass tracks.

ABACAB Brings up a good point = Bad RAM.
Typically when I think of corrupt projects, I think of a bad HD or bad RAM.
I rebuild a system every 2 years or so my HD and RAM are never more than a few years old. With that being said, ive gotten bad RAM right out of the box / defected.
My system ran okay, but it would produce crashes and conflicts. Finally traced it down to bad RAM that was brand new and once replaced, my issues vanished.
 
I would try using another PC to do some tests. look for corruption on this 2cnd PC.
You are allowed to have Sonar on 2 PC's, so no biggie there.

There are also memory tests you can run under DOS. I had a Mac with mysterious corruption problems that traced to bad RAM. I found it only by using a program that required using the Mac's CLI.