I installed it on the advice of one of the cake staff, even though my issues weren't listed' and it fixed it perfectly.  Solid as a rock now.  No more crashes.

Absolutely; seconded (to my amazement)!!! Phew

Glad it's worked.  Is it all okay now, then?

Actually, no... I'll have to withdraw my previous statement. While I don't get anymore crashes at all, when I start doing more intricate automation, and press play, the audio on that track starts stuttering/'seizuring' massively: ProChannel and its parameters blinking on and off, fader levels too etc... It especially doesn't like automating enable/disable parameters. It's not a case of processing power either because it's just the track I'm working the automation on that goes out of wack, not the whole project. And I'm not messing up the automation, either (as in, it's not an unintended effect of the automation I drew in)... *groan* It's like the QuickFix won't let it crash even though it really wants to

Automation issues are independent from the crashes which would be addressed with the quickfix. Can you explain in more detail exactly what parameters you are automating with the steps? Also please log a problem report with as much detail as possible and an attached project file that demonstrates it. List the CWBRN number here.

Sorry for the delay-- it's been more cooperative lately. Maybe it 'got used' to what I was trying to do, in a manner of speaking if that makes sense at all. I have had more of the same problems, but not quite as drastic. It is definitely a bug though, since fader levels start flickering and the sound on the track with the heaviest amount of automation starts snap-crackle-n-popping. It's usually solved by either making the automation smoother/simpler, stop-starting playback/audio engine or rebooting SONAR. To answer your question more precisely, I've been automating all sorts of parameters and modules on the ProChannel and a few SONAR-native FX plug-ins. Cut-off frequencies, enable/disable parameters, automated mute button, reverb, delay, tube saturation input amount, Saturation knob wheel enable/disable and saturation amount, volume, pan etc... As I say, it's been more cooperative of late, so unless it starts getting out of hand again it's easy enough to work around, so I won't log a problem report just yet. PS: ALL fader levels of the tracks currently outputting audio flicker on and off, not just the one/s with automation. However, audio playback isn't necessarily affected, apart from the track I'm working on at the time of the bug presenting itself.

There's many things about automation that don't make sense to me, and even more so in X2. I've experienced the same sort of issue with automation as Mike, which is due to the fact that X1/X2 doesn't seem to forewarn the signal path that "we are about to quickly turn up the Gain or Volume on this track", so the API to the drivers is late to respond and thus you get get artifacts (some pretty frikkin NASTY!). Now, something I want to address when it come sto automation is the ill-deployment of "lanes", which i find to be pretty klunky and more or less "thrown together". Some more thought put behind this would be beneficial. When the track's subtracts are collapsed, you only see the 'first' sub-track in the track, not the entire list of sub-tracks (i.e. T1, T2, T3, and so on). However, your automation shows up in the collapsed track. in this case it's near impossible to accurately perform automation changes or edits when only seeing the 'first' sub-track and not the one you have solo'd. For example, if I have a lead vocal track that has 3 sub-tracks, or lanes (or whatever people call them depending on the DAW), the first two of which are muted, and I collapse the track so that the sub-tracks are no longer showing, any automation I set to sub-track T3 will be transposed on top of the only sub-track displayed, which is T1. This can quickly become confusing. More, I experience issues where certain automated segments of the envelope just stop responding to mouse-clicks. The only fix I have found is the infamous Restart Sonar, or re-open the session. @Noel: yep, still found some crashes with plug-ins after the patch. I'm eagerly awaiting X2a before coming back to Sonar. Also, I sincerely apologize for this huge paragraph that appears un-formatted. It's the board doing that, not me.

I was experiencing all of those kind of crashes and hangs when clicking around on the console and the Pro Channels, even after the quick fix (although certainly less). I pretty much stopped it entirely by using a new Windows user account set up especially for DAW use, with all of the start-up programs that I have in my default account disabled. Do you have any programs that load on startup, things like cloud sync (Live Mesh etc) or programs that are set to automatically update (I had all sorts of Quickbooks junk that was running). 

I still suffer all kinds of weirdness and frustrations with X2, but random hangs are not one of them. I'm 95% sure that setting up a new, pared-down user account had a lot to do with it. 

Same here, brconflict, re take/automation lane disorganisation & confusion... Sharke, my DAW is custom built and I only use it for music purposes. I also have nothing in my system tray aside from my soundcard driver/control panel (same as yours btw), and I deselect all irrelevent processes from start-up with CCleaner, as well as regularly defragging and fixing the registry. I also have 'authorization-less' admin priviliges on everything. I really don't think that's the problem, for me at least.

Hi guys,

If you have sent in a crash report its likely that we have addressed it in X2A. We were careful to investigate all the common clusters of crash reports. All the ones coming in recently have all been addressed. So let us know if you still see this after the update.

Also there have been many updates to the prochannel and automation that should improve general stability and responsiveness, including improvements with rendering automation when delay compensation is present in a project.