Fabio Rubato
It's fairly stable for me, although still getting blue screens when working with wave files...the more I work it, the higher probability it's going to happen. If I close and then load another project, it's usually not long before a problem occurs. I've since uninstalled and then re-installed in safe mode and am currently testing. 
 
Other than that, it's good. My Alchemy plug-in however asks me to locate its data every time I run a scan, which I do once on start-up. I'm not sure whether I need to do a scan every time though.

Re: still getting blue screens when working with wave files..
Fabio are you mixing VST2 & VST3 Waves plug-ins in the same project?
The Waves VST2 & VST3 Shells are incompatible and can not be running within the same project.
It's been mentioned in other threads that its a known Waves issue that affects usage in ANY DAW.

TheSteven
Have you tried Asio4All for your using with your internal sound card?
 http://www.asio4all.com/
 
Might help with both the MME and switching from MME to Asio.
 
...Steven

Thanks TheSteven,  
 
Kudos to you! This workaround seems to be working for me as I no longer need to re-configure the driver modes between MME and ASIO, I also seem to be able to use the internal sound card with very little (if any) latency, pops, crackles and garbage!  
 
I now plug in Samson graphite 49 K/B control surface, since everything seems to be stable for a change and configure it using mackie control in the control surfaces. The sliders and stuff work really well, however I found none of the midi sounds play, playing the keyboard I can see the meter bar is active but no sound coming out of sound card. 
 
So I use the help midi troubleshoot and follow the instructions and get it to work by inserting soft synth, although I  can't choose the options "Simple Instrument track" and "First Synth Audio Output" together as pointed out in the list in step two, I can only choose one or the other, (I suspect this is an error in the documentation or it could be a logic problem with the interface):
 
ie: http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=Troubleshooting.07.html

Stable as hell here,
but I had no issue´s with X2a either.
So take my statement as of a fanboy.
 
Pragi

Hi Markynzo,
I've just seen that you have both Sonar and Pro Tools. On the stability point with windows 7 wich is the best?
Thanks!

Noel Borthwick [Cakewalk]

Anderton
However, I agree with the comments about X3 being "snappier" and "smoother." I believe what happened is someone at Cakewalk took SONAR apart, sprayed it with WD-40, then put it back together again.
Meanwhile I haven't yet had a crash or freeze. I would have expected at least some "new update" hiccups or something. Very encouraging.

Close, but I used DoxIT Gold spray. I've found that spray works like magic :-)

I think you meant DeoxIT...I didn't know that they made a digital (soft) version??? Probably straight out of MIT to you guys at CW...

aixmusique
Hi Markynzo,
I've just seen that you have both Sonar and Pro Tools. On the stability point with windows 7 wich is the best?
Thanks!

PT ISNT supported on Win 8 (which is what I use, NOT WIN 7) But Once I got past the DAE errors of installation I have found PT to be stable.
 
Sonar IS Win 8 supported and its amazing.
 
The ONLY reason I use PT is because the film industry dictates so in terms of how to cross channel projects from lets say a Video Editor to a Sound Guy, but then export it in a way that "the industry" has deemed fit.
 
If I had my way, we'd get rid of PT ENTIRELY and use Sonar.....Its a WAY better creative tool.
 
 But, to answer your question, PT is a RIGHT SO AND SO to install and Sonar isnt, but if you want to use them side by side then it can be done.
 
I hope that X3c addresses a few of these Video/PT issues and I'm sure it will.
 
I professionally work in film and use Sonar 95% and PT a very reluctant 5%.
 
 

markyzno

aixmusique
Hi Markynzo,
I've just seen that you have both Sonar and Pro Tools. On the stability point with windows 7 wich is the best?
Thanks!

The ONLY reason I use PT is because the film industry dictates so in terms of how to cross channel projects from lets say a Video Editor to a Sound Guy, but then export it in a way that "the industry" has deemed fit.
 
If I had my way, we'd get rid of PT ENTIRELY and use Sonar.....Its a WAY better creative tool.
 
 

Same here, I've given PT an honest shot as a creative DAW many times, but quite frankly, it sucks. It only gets fired up for project delivery to the editors.

Fabio Rubato
It's fairly stable for me, although still getting blue screens when working with wave files...the more I work it, the higher probability it's going to happen. If I close and then load another project, it's usually not long before a problem occurs. I've since uninstalled and then re-installed in safe mode and am currently testing. 
 
Other than that, it's good. My Alchemy plug-in however asks me to locate its data every time I run a scan, which I do once on start-up. I'm not sure whether I need to do a scan every time though.

It's been repeated time and time again that an application, such as Sonar, cannot cause a blue screen directly.
 
A bad device driver or bad hardware can, but an app can't.  Simple as that.  I don't know why the message isn't sinking in.
 
Every time Sonar gets blamed for a BSOD, I roll my eyes.

Silicon Audio

Fabio Rubato
It's fairly stable for me, although still getting blue screens when working with wave files...the more I work it, the higher probability it's going to happen. If I close and then load another project, it's usually not long before a problem occurs. I've since uninstalled and then re-installed in safe mode and am currently testing. 
 
Other than that, it's good. My Alchemy plug-in however asks me to locate its data every time I run a scan, which I do once on start-up. I'm not sure whether I need to do a scan every time though.

It's been repeated time and time again that an application, such as Sonar, cannot cause a blue screen directly.
 
A bad device driver or bad hardware can, but an app can't.  Simple as that.  I don't know why the message isn't sinking in.
 
Every time Sonar gets blamed for a BSOD, I roll my eyes.

I know LOL! It's the same people that chronically claim Sonar is full of bugs....when it's actually a system issue. Even way back to Sonar 3, I can't recall a BSOD caused directly by Sonar.

Mixing Waves VST2 & VST3 issues:
 

Cakewalk Knowledgebase

Mixing Waves VST2 and VST3 Plugins Not Supported

The information in this article applies to:

• SONAR X3 Producer
• SONAR X3 Studio
• SONAR X3

Running both VST2 and VST3 versions of Waves plug-ins in the same SONAR session is currently not supported by Waves. Mixing and matching VST2 and VST3 plugins will likely result in the plugins crashing or the UI not drawing.
A mix of VST2 and VST3 Waves plugins can happen under the following scenarios:

• You have "Replace VST2 Plugins when opening projects" (under Edit > Preferences > File - VST Settings) turned off, open a project containing VST2 versions of Waves plugins and later add a VST3 Waves plugin
• You have "Hide Related VST2 Plugins" disabled (under Edit > Preferences > File - VST Settings) and open both VST2 and VST3 plugins

Note that this limitation applies to all projects that are open in SONAR not just mixing and matching in the same project. Additionally if you are experiencing Waves plugin parameters being lost, make sure you have the SONAR X3b update installed.
 
from http://www.cakewalk.com/Support/kb/reader.aspx/2007013327
This page last updated: 10/9/2013