I agree with all the above. For me CbB freezes when I am editing on track lanes and usually doing something with a fade in/out. It suddenly seems confused and then falls over. I don't do big projects just little ones with proper purchased plugins. Don't know if this is where the problem lies though. I just keep saving and saving.....and saving.....and

And you have gone into comp mgmt and searched the app and system logs?

Maybe time to test your memory?

System diagnostics?

Maybe a bad sector on the drive?

I don't know if using the wrong driver would cause a crash, but you really need to take the time to sort that out. 
 
ASIO audio drivers are SUPER important to using a DAW. 
 
Follow the link someone posted a few posts back. 

I have everything updated as I mentioned in post #21

A few were having issues with not having plugin load balancing checked. Not sure it it's related or not. I would make sure that is checked though to be sure.
 
I think you can roll back versions if the most recent build is giving you problems. This would be my last resort though.I get occasional lockups when I try to write multiple track automation all at the same time with grouped tracks. I don't think grouping is intended for large numbers of tracks.
Oh yes, and if you have these kinds of issues engage the auto save features. 

Are the issues with splits, trims, fades, etc. happening mostly with mono files?
 
Craig

Are the issues with splits, trims, fades, etc. happening mostly with mono files?
Yes with me. I only record in mono. All my takes lanes are mono. All my stereo stuff/tracks come from soft synths via midi then rendered. I never use loops.

Anderton
Are the issues with splits, trims, fades, etc. happening mostly with mono files?
 
Craig

For me, not specific to that although I also deal mostly with mono tracks.  99% of the time I'm given a stereo track instrumental to record vocals over.  And although everything after that is pretty much all mono or aux/busses, I have gotten crashes before even recording a track (meaning, just with the stereo file).
 
Anyway, I give up and moving to another DAW.  I really appreciate everyone's help to get me through, but this has already cost me too much everything and I need to move on to something that will be stable for me asap.
 
cheers,
Dave

I'm also getting lots of crashes triggering 'Fault Reporter' dumps - which I always complete and send off.  I very rarely got these in Sonar Platinum. The project is new and was started in CWbBL a couple of weeks ago and only has a half a dozen tracks at present.
 
For me, it's happening when I do various simple MIDI track things, e.g: Process/changing the length of a clip to 50% = crash; tweaking volumes and velocities from within CW on a Kontakt Session Horns brass track = crash.  There's no pattern to events that I can see/repeat.  The scary thing is, I've now taken to continuing the project in Sonar Platinum - no crashes whatsoever.  I realise this can't serve as a long term solution.
My confidence in CWbBL has been badly shaken in the last few days.
 

What if a recent Microsoft update has affected something the only the newer Cakewalk has a dependency on?  That could explain why the older Sonar is not having the same issues.  It's possible that CbB has been updated to use newer MS programming libraries.  This is just speculation, but I was thinking about what the possible reasons could be.
 
Did you apply the July MS patches (released 7/10) to your system, and was CbB stable before that date?