X2 does not start up again

Thanks Riojazz. Thanks to you I discovered in my Windows Taskmanager under the process tab, that both bitbridge.exe and sonarpdr.exe were still active in the background! So even when I end my X2-session/program in a normal way (by clicking the cross in the right upper corner), the program does not really close, so it is impossible to start it up again, unless I end up the process of sonarpdr.exe in the taskmanager!

You are right Bob, I started a new blank project without any plugins, and I could close and start X2 as often as I wanted! So now I will find out what plugin causes the problem.
 
Thanks a lot guys,
didap

When I discovered this issue, I immediately put the brakes on using 32-bit plugins in 64-bit Sonar, UNTIL I went through the exercise of determining which ones worked OK and which one did not.
 
Once I had the list of ones I was comfortable with using in my 64-bit Sonar install, I moved those 32-bit plugins to a special folder within my C:\\Program Files (x86)\VST Plugins folder, as a SUB-folder called '32-Bit Cleared'.  (the name is of course arbitrary).  I then put that path into the x64-bit Sonar search path for VST plugins in the Cakewalk Plug-in Manager, and then ONLY those 32-bit plugins that I had determined would work properly in 64-bit Sonar were made available for choice in projects.  (this new path REPLACED my old path that had pointed to the entire 32-bit VST Plugins folder).
 
There are many ways to do things, but I found this to work for me, and it keeps the paths simple for both 32-bit and 64-bit Sonar installs.  By keeping those plugins in a sub-folder in the C:\\Program Files (x86)\VST Plugins folder, the 32-bit Sonar still finds them, and by ONLY having that extended path of 'C:\\Program Files (x86)\VST Plugins\32-bit Cleared' in the 64-bit Sonar, everything is peachy keen.
 
I now NEVER have crashes with my 64-bit X2a install, even when I do use 32-bit plugins, because I already know that only those that work are made available to it.
 
Hope that helps, 
 
Bob Bone
 

Thanks a lot for your answer and experiences Bob.

This can be caused by sonar not releasing sound card drivers properly. Probably the fault of the sound card drivers. Sometimes you cannot end it from task manager, but instead of restarting you can log out and log back in again. Users have reported success with that.

In my case, I can end it in Task Manager every time. No changes in drivers, or apps, but I did notice this more after re-installing iLok drivers, EastWest Quantum Spaces, and Waves IR-1.

brconflict
I've been having this issue as well. The cause in my case was that SONAR.exe was still running in the background, even though the window was closed, and one would normally think Sonar is indeed shutdown. I'm having to go into Task Manager and manually kill SONAR.exe almost every time now.

Check to see if BitBridge is running as well, and if so, check for any 32-bit plugins in the failing project, as one or more may be causing this issue.
 
Bob Bone