Good News!!!!
I just re-istalled the X2a patch again, before I was going to do a complete re-install, and it completely fixed the problem here. I can't seem to make it crash, or hang at all right now.
Funny thing though...This time when I re-did the X2a patch one of those Microsoft V++ install windows popped up and said it was intalling.  That DEFINATELY did not happen the first time I ran the patch.  Any ideas on that one?

Hi guys! Glad to hear it, revsnd! The 2012 VC++ installed with the update over here. I'm not sure what might have caused that - although I vaguely remember something similar happening in the past with an update for another product - where the included MS installer didn't run during install. Good news here, too - so far! I reinstalled SONAR X2 and X2a after uninstalling/reinstalling the latest VC++ 2005, 2008, 2010, and 2012 packages - and after cleaning the registry with CCleaner (per Shambler's advice). All seems to be working much better now. There still seem to be some BitBridge issues, but that might have had to do with the plugins I was using. I worked with X2a for hours yesterday without any major issues. Thanks again for the help, guys! Hopefully we all have it figured out now. I'll post again if there's any changes or issues. Cheers!

 
It might be worth trying step 7 first as this is the least destructive and may cure some of the issues.

1) Uninstall Sonar
2) Uninstall all of the VC++ redistributables
3) Update windows several times, install all the critical and recommended updates until it says you are up to date.
4) Download and install the 2012 VC++ redistributable from microsoft site (unless the update already installed it)
5) Reinstall SonarX2
6) Apply the X2a patch
7) Download and run CCcleaner.exe from pirisoft ,specifically the registry clean, run it several times until it says there are no errors.

After that lot my system now appears to be stable although I still have a support case open just in case something comes to light in the next couple of days.

So Shambler/Scott J, from the above; this is what you have basically done to fix the issues with both X2 install and then 'a' upgrade?

I ask because I am having virtually the same issues althought my problems started after I first installed the 'a" upgrade.
 
And now after having re-installed X2  (no upgrade yet) I don't have the RMix plugin. And I'm looking for just what is the issue.


Del
 

Hi Del,
 
Sorry for a late reply.
 
The problems appeared after I first installed the Xa update, too.
 
That list is what I did.
 
Funny thing is, I thought the problem was fixed; but now I'm getting repeatable errors, again, tonight. R6025 - pure vitual calls. It's repeating this error/crashing in Kore2 - the same as it started to do right after the Xa update - that included the MS2012 VC++ package. I'm going to check SONAR X2a and see if it's having issues now, too. There hasn't been any updates to this computer in a few weeks and has been fairly stable.

Hi Scott; After cleaning up Win 7, that is to say making sure that all MS VC++ (2005, 2008, 2010 and 2012) were re-installed and working, I reloaded the "a" update and to date all is well.

Awesome, Del! I'm really glad to hear it!
 
I might have came across another possible solution - that I should have tried before - cleaning up the temporary files; 28gigs. Ouch.
 
While reading this article about solving R6025 errors, the author mentioned this step. http://www.ehow.com/how_5009906_fix-runtime-error-r.html
 
"Click on the Windows "Start" button, type "cleanmgr" into the Search field and press "Enter." Click on "Files from all users" if it asks and select "Continue." Choose the drive where the program was installed, check the boxes next to "Temporary Internet Files," "Temporary Files," "Recycle Bin," "Downloaded Program Files" and "Setup Log Files." Click "OK" and select "Delete Files.""  
KORE2 isn't reporting the R6025 error, yet. I still have to test X2a.
 
BTW: I'm using a Windows 7 64bit/i7920/24g
 
 

Thanks for the info Scott, I ran x2 for a few hours yesterday and had no issues but it's nice to have something else to try if it comes back.