As an update and following a members advice, I uninstalled my IObit virus program and then installed MS Essentials. That stopped the blue screens when using CC, so now I can update without having to go to safe mode. I'm slowly using Plt more and it's proving to be more reliable now, although not as dependable as X3. For example, yesterday, I created a Melodyne region on a small bit of a wave, but then deleted it as I found it wasn't what I needed. Not too long after that, Plt just froze. So for me, it's still not rock solid.

It is incorrect reasoning to say that because X2 or 3 works fine that the problem rests with Platinum.

Platinum may well have dependencies that X2 or 3 don't and maybe exposing deficiencies in your system that X2 or don't.

Remember that Windows is a moving target as its regularly updated by MS. I'm sure that Cakewlak always work with the latest on their dev machines. They would have to, otherwise they couldn't certify that Cakewlak software works on particular OSes. I've had the weirdest interactions between programs that have had an effect on Sonar and once deleted Sonar has run fine.

mudgel
It is incorrect reasoning to say that because X2 or 3 works fine that the problem rests with Platinum.

Platinum may well have dependencies that X2 or 3 don't and maybe exposing deficiencies in your system that X2 or don't.

Remember that Windows is a moving target as its regularly updated by MS. I'm sure that Cakewlak always work with the latest on their dev machines. They would have to, otherwise they couldn't certify that Cakewlak software works on particular OSes. I've had the weirdest interactions between programs that have had an effect on Sonar and once deleted Sonar has run fine.

Hmm, I take your point that crashing in Plt and not in X3 might not necessarily rest solely at Plt's doorstep. However, the reality is - at least for some users - that we need to rely on a DAW to reliably work. If X3 is not crashing, and Plt is, and it's from the same company, then I think it's a fair comparison to suggest that there may be an issue with Plt. Saying it's solely Plt fault, does nothing to pinpoint the possible causes and indeed may stop the user looking beyond it to software perhaps interacting with Plt and its dependencies that aren't triggering the same thing in X3...but who has the time to dick around problem solving when there's work to be done and X3 will do it. 
 
I too am grateful to be able to turn to X3 and have it finish - or start - a job that Plt is stuffing up. It also does me good to be able to leave it alone for a while and come back to it in a couple of weeks to see if an update, or indeed a Win update has improved its reliability. I am also grateful for the patience - and support - that most members have when one of their colleagues is struggling with an issue that perhaps they or many others are not.
 
 

Fabio Rubato
I am also grateful for the patience - and support - that most members have when one of their colleagues is struggling with an issue that perhaps they or many others are not.

 
Well, I think all of us have been there at some point. I'm pretty sure that when Windows was invented, no one at Microsoft said "Hey!! Let's create the ultimate operating system for real-time audio streaming of projects that really tax a CPU and need lots of RAM!" 
 
But it's also frustrating trying to help, because those of us who have experienced these problems often find out it's some weird/stupid thing and we just happened to stumble upon the solution ("Really? If my motherboard has a Fujitsu floppy drive that is set to B drive in the motherboard BIOS, SONAR explodes if Microsoft Word is running Fast Find at the same time?").
 
I just ran SONAR Platinum for 5 hours straight without a hiccup. It's been by far the most stable release of SONAR for me, and more stable than many other programs. I only got it to freeze once, which was when I deleted the IR file from the REmatrix folder and when I re-opened SONAR, REmatrix couldn't find its folder and crashed, which froze SONAR and required a restart. But that's it after 2+ months of pretty solid exercising SONAR. 
 
So it's almost like "survivor guilt" to be having these great experiences while others have problem after problem. You know it's not the software itself, because it can run stably. It's the software interacting with something but...trying to find what that interaction is can try your patience and your sanity.

Just consider why it is working for other people and not you.....
As everybody is using the same Platinum code then wouldn't it be crashing for everybody single Platinum user ??? (That's a far better test than comparing it to X2 which is bogus!!!).

If I was doing mission critical work I would never use a new version of anything, unless it was at least as stable as the version I was currently using. That's just common sense and best practice for your business.

When I was still working full time I would install a new version in a special partition just to quarantine that program from any of my work related programs. Once it was proven to be stable then I would install in parallel to my existing version and make sure my current version was still in full working order. I would get familiar with the new version and then and only then would I start using it keeping my previous version available for fallback.

I'm having the same issues, it got ridiculous Friday night, my singer would do one line and I would immediately save. It was freezing every 10 minutes. Meters would be stuck, no message about sending the crash to Cakewalk would come up. My system would let me alt ctl dlt to get to task manager where I would have to end task on Sonar. But once back to my desktop, I couldn't open Sonar, I would have to do a complete system restart, then repeat the process. Kinda stifles the creative process a bit, and it's so annoying that I'm paying monthly for it and it doesn't work. I'm at work right now, so I don't have all my info, I'm running around 18 tracks, 5 buses and a master bus. I use a Roland Octa-Capture for my interface. One thing I noticed is the Octa-Capture was running at 48000Khz instead of 44100Khz due to the fact that I use an Axe-FxII to do all the guitars and bass, and it runs at 48000Khz. So I was wondering if that could be an issue, I never even knew the Roland could run at that to be honest, unless its picking up on what my settings are in Sonar. At one point, my phantom power kicked off by itself. It was an extremely buggy night. I've never had issues with Sonar Plt until that night trying to track vocals. It has never froze or anything, but now when I go back and mix this project, the line that scrolls acrossed the screen as its playing is jerky, like its a lack of memory or something. But that can't be, I've got a beast of a computer, its a gaming system, 8 core, 2.3 GHZ, 16 mg memory, I can't remember what video card is in it, but it never has issues with anything. I do use Waves plug ins, and I think I may be mixing in a 32 bit in there with the VST3's. I will pull that VST2 32 bit and see if it helps, and check for updates on my drivers. I will also try what meh suggested once I'm home and free to mess about. Sorry about the long drawn out post, I get long winded sometimes. 
 
Wgmj

In SPLAT, the crashes I have seen tend to be related to

• switching between open projects where I have several projects open at once and I'm flipping back and forth copying and pasting audio.
• Drawing of wave forms.

In both of these cases, I'm not doing anything that needs urgent saving (that can't be re-done in a few seconds) so I don't really care.
 
Cakewalk recently did some work to change the way the wave forms are drawn and I am assuming there is some bug in there somewhere that causes crashes on my PC. SPLAT has never crashed for me while actually recording in years.
 
I could probably cause a dropout while recording if I really wanted to, but I have not had a recording interrupted in more than 5 years or so due to a dropout.

 the line that scrolls acrossed the screen as its playing is jerky, like its a lack of memory or something. But that can't be, I've got a beast of a computer

 
Sounds like you've pressed the Pause key.

I went in tonight, changed some buffer settings, even though my computer doesn't need the help, now I'm crashing almost everytime I use Melondyne, even on my Prochannel Eq, when I close it, it hangs up like its having trouble closing. This is nuts. I took off the Channel Tools, didn't change anything. Looked at all my settings, they look fine. I did what meh said to do, that didn't change anything. Tomorrow I am going to have to go to a different project and see if I'm getting the same problem. Maybe its just this project.