Installation crash - Sonar X1 Studio - solved
On Feb 3, 2011 I posted a problem with a ProChannel installation which gave me two versions of PC4KGate, an old version and new one on a different path:
http://forum.cakewalk.com/fb.ashx?m=2485197 I fixed the problem wrote a trouble ticket (Case 21915) and forgot about it.
On March 30, 2012 I got a letter from Cakewalk Support about it and they recommended I do a clean install.
I did that and found that I could not re-install Sonar X1 Studio from my originals or from new downloads.
I got this '
Blue Screen' bugcheck each time, no matter what I tried:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000135 (0xffffffffc0000005, 0xfffff8800d17ec10, 0xfffff880016d5d58, 0xfffff8a000227750). A dump was saved in: D:\MEMORY.DMP." Running the Memory Dump through
WinDbg gave this message:
"This bugcheck is caused by an unhandled exception in a registry filtering driver. This bugcheck indicates that a registry filtering driver didn't handle exception inside its notification routine." The faulting routine was
regsvr32.exe - that handles registry settings for DLLs and so on.
It took a long time for me to track the problem down and I made perhaps 30 different installation experiments, all with identical crashes, but I finally found that it was due to:
'Microsoft Software Certification Toolkit' from the
'Windows 7 Client Software Logo Program' described in
http://msdn.microsoft.com...dd371701(v=vs.85).aspx The download link is at
http://go.microsoft.com/fwlink/?LinkID=140109 Uninstalling that (
and cleaning up after the uninstall by removing its 'leftover' filter drivers) fixed the problem.
Finally, after 3 weeks of troubleshooting I now have Sonar X1 Producer Expanded X1d up and running again.
This time I don't see any path like the old one that caused the original problem:
C:\Program Files\Cakewalk\Shared Components\... and I don't know where that original path came from. Maybe it was because I had Zeta and Zeta 2 before I installed Sonar X1 Studio.
It seems ironic that a Microsoft Certification software would be the cause of a problem, and I liked using some of the tools in that package.