Studious
My X2 on Win 7 x64 has also been crashing more frequently lately.  BitBridge is always a problem, and was the source of many crashes, so I've been trying to get rid of ALL 32-bit plug-ins in projects so BitBridge won't load.
 
Other crashes are still happening, and I have a support ticket open.  Maybe a recent Windows update caused some problems across Win 7 and 8...who knows.  But I hope to get to the bottom of it.  Good luck to you too!

Try JBRIDGE

Jbridge?  Not too sure about adding another component to an already buggy installation.  But does JBridge allow you to start/stop playback while a VST is in focus?  That is one big pain with BitBridge: you have to click off of it to start/stop playback.  That, and the memory it consumes and how it tends to crash my projects.

Studious
Jbridge?  Not too sure about adding another component to an already buggy installation.  But does JBridge allow you to start/stop playback while a VST is in focus?  That is one big pain with BitBridge: you have to click off of it to start/stop playback.  That, and the memory it consumes and how it tends to crash my projects.

JBridge is an alternative to BitBridge (BBRidge I find to be quite tiresome).....
 
It handles some 32 bit plugs that BBridge cant handle.
 
Certainly sorted a few of my 32 bit woes.

why is he not giving us any specs ?
os ?
soundcard?
computer specs?
 
this can sometimes narrow down an issue instantly.
 
sure been using the same hardware, same os..
but what ? what is that ?
 

I have been having problems as well. Been getting the old triangle with the ! in the middle. Started off once here and there, and now all the time. Today I was mixing down a tom track and tried to pull up ez drummer by double clicking on the icon and that's all it took. Its happens when im EQing individual tracks and have everything muted except a kick lets say. Im running all 64bit VSTs using sonar EQs and FXs. It really suck too, I had my mix all most complete and a really good mix of 14 tracks and forgot to save as I went and BOOM! Startover. Should I have went with like Presonus or Cubas?
 
My system is a msi m-power, I7 quad core 2770, 16 gig patriot RAM 2000 set, drive C Samsung SSD, drive E western digital 7200, 720W power supply, Focusrite Scarlett 2i2 interface windows 7 64bit pack 1.
 
 

bloeff
Thanks guys for all your help. I ended up rebuilding the main project from scratch and moved a lot of plugins from it to the mixdown projects and everything is working fine now. I guess it was too much processing for X2. I don't think my hardware was the issue, because the CPU never went above 30% and memory never went above 2GB (I have 32GB) and my soundcard has never been an issue in the past. It's a bit inconvenient, because I really like to apply track effects in the main project. It's too bad X2 doesn't have a dynamic feature that recognizes bottlenecks and automatically makes adjustments. Though I have an M.S. in Computer Science, I certainly don't want to spend the rest of my life bogged down in latency, buffer sizes, ad infinitum. My programming days are behind me. I just want to enjoy software at the user level!
 
Thanks again,
Bruce

Sorry Bruce, but this cannot be correct.
 
To give you an example, I have a project which consists of 75 audio tracks, multiple (100+) plugins, V-Vocal every where (live, not bounced) and this project runs like a dream on my old Win XP32 system with 4Gb of RAM, under Sonar 8.5.3 & X1d Expanded
 
To get the best performance from your machine, you NEED to invest time experimenting with buffer sizes, latency, drivers etc.
 
Your machine deserves it

To quote myself :  "When you do have a crash, if the crash details are not displayed, be sure to get the details from Windows Event log (Application section).  It helps find what is bugging out, at least for a particular crash event."
 
When Sonar crashes, you have to check the crash event details!  It might not help if it's a generic apphang or similar event.  BUT...there is a chance the crash event will reference a specific dll, service, etc.  Then you've pretty much found the problem immediately.  It could be a symptom of something larger, but at least you have something to go on, rather than trying everything under the sun.  If you then need more help, forward that to Cakewalk support and they should provide adequate support, because you provided adequate detail.

I'm just curious... after updating your OS to Win 8 (or after you patched it) did you check for updated drivers for your interface and other hardware? You said you didn't change the drivers at all. That can definitely cause problems when you upgrade/update your OS.