Noel Borthwick [Cakewalk]
If you open a VST3 version of waves after a VST2 waves plugin in the same SONAR session it will crash. This is a known Waves limitation.

When I thought about this ^ I realised for quite some time now that I had been using the Pro Channel for most of my mixing in Sonar X2 and the projects I had pulled into X2 thus far did not contain Waves plugins. Also whilst I do use Ozone 5 for mastering, I normally do that in Wavelab. So Ozone is not normally saved as part of the project, as I generally only add it to get an idea of what I'll be dealing with when I bounce for mastering.
 
It took a bit of digging but I found an X2 test song from a while back that contained the VST 2 versions of Waves SSL, NLS and Izotope Ozone 5. It took all of about 5 seconds of being open, to crash like a brick through a windshield!!! Turns out, Ozone has it's own fault reporter as well, in case anyone is interested? I filled out the Cake crash dump fault report accordingly...
 
Well my bubble is burst! Thanks heaps, Noel! Hrmmpfff!!! So VST 2 versions are a "no go" of these plugs, when the VST 3 versions are installed in X3!!!
 

 
Incidentally, I've noticed that only the VST 3 versions of waves plugs show up in my browser? I did nothing to make that selection, so I assume this is intended?

LePou's ('Poulin') amp sim plugins destabilise it (they are 64 bit / VST2).
 
The symptoms are that it stops responding.  Those are the only problematic plugins I've found thus far.

Good for you.. x3 lasted all of 5 mins over here. a recurrence of CWBRN-18923
 
new crashlog submitted.

Ol

Royal Yaksman
It took a bit of digging but I found an X2 test song from a while back that contained the VST 2 versions of Waves SSL, NLS and Izotope Ozone 5. It took all of about 5 seconds of being open, to crash like a brick through a windshield!!! Turns out, Ozone has it's own fault reporter as well, in case anyone is interested? I filled out the Cake crash dump fault report accordingly...
 
Well my bubble is burst! Thanks heaps, Noel! Hrmmpfff!!! So VST 2 versions are a "no go" of these plugs, when the VST 3 versions are installed in X3!!! 
Incidentally, I've noticed that only the VST 3 versions of waves plugs show up in my browser? I did nothing to make that selection, so I assume this is intended?

You can mix and match VST2 and 3 plugins from most vendors. Only Waves have a problem that we know of when a VST3 and VST2 from waves are loaded simultaneously.
It should be no problem to use a VST2 from another vendor alongside the VST3 from Waves.
By default with waves the corresponding VST3 plugin is loaded using automatic migration to avoid this issue.
 
What is the exact circumstance of your crash?

I've had my computer lock up on me twice while X3 was running in the last couple days. Strangely, in both cases, it happened after being inactive for 10-15 minutes. I sat back down and found that the cursor was frozen and my faderport was unresponsive as well. Weird. When I'm actually working on it, it's been flawless. I still love X3!

Noel Borthwick [Cakewalk]
You can mix and match VST2 and 3 plugins from most vendors. Only Waves have a problem that we know of when a VST3 and VST2 from waves are loaded simultaneously.
It should be no problem to use a VST2 from another vendor alongside the VST3 from Waves.
By default with waves the corresponding VST3 plugin is loaded using automatic migration to avoid this issue.
 
What is the exact circumstance of your crash?

I opened a song that was created in X2. Once the general frame work of X3 had rendered, the first thing I saw was the outline of the Waves SSL Eq first appear normally, then it went all grey. What I think is the border (outline) of Ozone 5 then appeared but with nothing inside the border, then the border disappeared. Around this time 'Not Responding' appeared in the header bar. About 5 seconds in all elapsed before first Izotope's Ozone crash log appeared, followed by Sonar's. Unless I missed something, I only had the option to fill in the initial details of the crash. Checking the report online there are empty details as to computer specs, interface etc. I take it I missed something? Is there anyway to go in and update these to give you guys a more complete report to work with? The reporter had 'Not Responding' in its a header twice, while I was filling it out and sending it. The reporter number is: CWBRN-20124.
 
I have been able to open a few songs from X2 prior to this with no problems at all. But they didn't contain any Waves or Izotope plugs.
 
*The OI at the top has me wondering if you took my tone wrong? My thanks and Hrrmpff, was intended jokingly btw*

BTW.. that bubble bursting picture was pretty cool.  

Royal Yaksman
*The OI at the top has me wondering if you took my tone wrong? My thanks and Hrrmpff, was intended jokingly btw*

Lol no thats a typo in my post thats all :-P

X3b SOLVED THE PROBLEM!!!
Very good job!
Thank you Cakewalk!!!