Even with the bridging routine that comes with Sonar, and sometimes also when using the commercially available JBridge, some 32-bit plugins simply give up the ghost when trying to use them in a 64-bit Sonar environment.
MOST folks that use plugins have moved to using as many 64-bit plugins as possible, many have completely moved to only using 64-bit third-party plugins. It is, unfortunately, the nature of the beast that the bridging software simply cannot always guarantee a given 32-bit plugin will work in a 64-bit environment.
I DO still use a VERY small number of 32-bit freeware plugins, running them through JBridge, and I have those plugins moved into a special folder that is the ONLY folder containing 32-bit plugins that is part of the VST search path for Sonar.
Most folks saw a HUGE reduction, or even complete elimination, of crashes, once they got rid of using 32-bit plugins in a 64-bit Sonar environment.
Lots of plugin authors, certainly most commercial companies releasing plugins, have created and released free upgrades to their 32-bit plugins, so it might serve you well to check their web sites to see if there may be 64-bit versions of any of the 32-bit plugins you want to try to continue to use. Even if you get most plugins to be 64-bit, it will help cut down on the potential for problems, and is definitely worth looking into.
Another option might be that for any 32-bit plugin you simply cannot do without, for a given project, you might run that project in a 32-bit Sonar, where everything is 32-bit, and maybe that would work for you. It won't affect the audio output, and should be way more stable, since the entire environment would be 32-bit. (as long as all your plugins have 32-bit versions).
Bob Bone
Bob Bone