Sonar x3 Pro crashes

Can you please list all plugins that this particular project has loaded into it?
 
I am suspecting that one or more are 32-bit, which then causes Sonar to load a piece of 'bridging software' to allow a 32-bit program to run in 64-bit Sonar.  Sonar comes with something balled BitBridge, to perform that service, and a popular 3rd-party bridging software app is called JBridge, which some folks use when they have certain plugins that for some reason don't seem to work well with Sonar's BitBridge.
 
Anyways, the bridged plugins can sometimes cause problems in 64-bit Sonar, and many folks went through a sometimes painful/sorrowful move away from using any 3rd-party 32-bit plugins in their 64-bit Sonar installations, and MANY of these folks have subsequently reported having FAR fewer problems.
 
So, again, please list all the plugins - synths and effects - that are loaded into this project.  
 
In addition to sometimes making Sonar unstable, where it will crash, it sometimes happens that the audio interface gets 'stuck' or BitBridge doesn't release from memory for a while, and either of these conditions can cause folks to end up rebooting to be able to restart Sonar.
 
You may be able to free up things by unplugging the audio interface when you crash, then plugging it back in, as this might make you be able to restart Sonar without having to reboot.
 
Bob Bone

You could also first make a backup copy of the whole project folder for the one that seems to randomly crash Sonar, then load the project in Sonar's 'Safe Mode', skipping the load of all plugins, and then do a bunch of of things that seem to cause the project to crash Sonar, and see if those problems go away when the plugins are not present in the project.
 
If the project remains stable when the plugins are skipped from being loaded, that is a good clue that one or more of the plugins are creating some kind of scenario that causes the crashes.  At that point, it would still not yet be determined whether or not the crashes are from something Sonar is doing wrong, or if the problems are caused by the plugins and only exposed by Sonar, but at least you would know that one or more plugins are involved in some manner, and that would help in the debugging process.
 
Can you please list all the plugins loaded into one of these projects that seems to hang/crash Sonar?  I would like to do some research into them to see if any have a history of issues in Sonar.
 
The most frequently seen Sonar crashes in X3 seem to be from 3rd-party 32-bit plugins not working with the bridging software needed for them to be able to be used in a 64-bit install of Sonar.  Cakewalk includes bridging software for free in Sonar, called BitBridge, and some plugins are not stable when loaded with BitBridge.  There is an additional piece of bridging software out there, called JBridge, and that can help some of the plugins that don't work with BitBridge work in Sonar x64, but even using JBridge some 32-bit plugins still fail in 64-bit Sonar.
 
Lots of folks have made deliberate choices to minimize or even completely eliminate the use of 32-bit 3rd-party plugins in 64-bit Sonar.  Many of the larger plugins vendors offer free updates to their plugins to give you 64-bit versions, and most new commercial plugins have 64-bit versions from their inception.  Another choice would be to install a 32-bit Sonar, for situations where you REALLY want to continue to use some 32-bit plugins that just don't work in a 64-bit Sonar, and that should eliminate stability problems from bridging, as you would not be bridging anymore, being in a 32-bit Sonar.  (so, you would end up with both a 32-bit and a 64-bit version of Sonar on your computer at the same time - which works fine with no interference).
 
Are there any particular error messages that are associated with any of these crashes?
 
Is there anything recorded by Windows that can be seen in the Windows Event Viewer?
 
Bob Bone
 

OK, I have started a completely new project.  I have added NO plugins what so ever as a test.  Sonar x3 will be playing along and then just stop.  So does that mean that this isn't plugin related, and the 32bit bridge has nothing to do with it?  if so, any suggestions on what it may be that is causing this problem.
 
Your help is much appreciated.
Thanks
FADS

He posted his system (most of it) in his original post.
I am running 64 bit Windows 7 Pro, Service pack 1. Intel Core TM2 quad  Q6600 at 2.4GHz 2.39GHZ. 1 GB C Maxed out at 8gb of ram.
 
4 hard drives running 7,200 RPM
C: 1 gb
D: 1 gb
E: 2 gb
Y: 2 gb

Sorry was a bit brain dead this morning, I forgot some specs were in OP.
 
What audio interface is being used?
 
If USB, is it connected to USB 2 or USB 3 port?
 
What is driver version and if available the firmware level for the audio interface?
 
What Sample Rate is specified for both the audio interface and for Sonar?
 
Bob Bone
 

Signature is in "User control Panel" at top of this page right corner. 
 
That's good the test shows OK but did you run it with Sonar running a problem project? 
 
 
 

Also, using the Legacy Firewire driver in Windows is suggested for many Firewire devices.
 
I used to have a Focusrite Saffire Pro 40, Firewire, and when I installed Win 7 on a system I forgot to change the driver to the Legacy driver.  I was having dropouts.  I remembered about the Legacy driver and changed it and it fixed my problem.

I am in the process of testing the firewire.  I moved the firwire from the presonus firestation tube to the firewire port that came with the computer instead of an add on card that I had added later to accommodate a video device that I had needed.  I read above that the firewire could be causing the problem.  i will  post the results as soon as I have had enough time to try it out.  I am trying it now.
 
Thanks
FADS

fads
Having problems with Sonar x3 crashing. 
 

 
 cpkoch 3 hours ago  
 
Out of pure frustration I ended up re-installing Sonar X3 Producer.  I have no idea as to why; but, life with  the re-installed Sonar has returned to normal.   

It is best to put the audio folder with the project in it own folder. That will not be your issue. 
 
You have something wrong with your hardware set up. 
Software has to be really bad to cause a blue screen. 
 
Did you follow Alex's links and read up on firewire? I sort of think this is the best place to start. 
 
And with 4 hard drives, I hope you have at least a 650 watt power supply? 

I read some of the info on Firewire, but does it apply to me.  My external sound card is a presouns firestation Tube.  Alex had said **** This advise may not be applicable to non forusrite audio interfaces, generally best contact the support of the manufacturer for their recommendations as to what driver to use ****

Sorry I have been off of this for a few weeks.  Just got back and still struggling with the clicks, pops, and crashing.  It runs fine for a while, and then it happens.  CakeAlexs mentioned that if I have Mackie Control which I do that I shouldn't use the Legacy drivers. I am not sure this applies to me because I don't know if I have Focusrite.
 
In regard to Mackie control, I turned the unit off and then on, and it says V1.01.  I guess that is the version. 
 
In Device Manager I have three IEEE 1394 Bus host controllers listed as follows:
LSI 1394 OHCI Compliant Host Controller
Texas Instrument 1394 OHCI compliant Host Controller
Texas Instrument 1394 OHCI compliant Host Controller
I think the first one came with the computer, and the Texas Instrument may be a card that I had added with two ports.
 
Thanks again for any and all comments.  It is much appreciated.
 
 
 

What FireWire port are you plugged into?
 
Bob Bone
 
 

fads
Maybe I should do a fresh install of Sonar x3 as dpkock just suggested?  But,  I am really afraid to that everything will get lost.

fads
 
 
First time I've seen my name as dpkock (dippycock) eh?