Hi All,
 
I am at the tired end of what has been a long troubleshooting journey and I am hoping for fresh ideas/help.....
 

Back-Story
My desktop (Win 7 32 bit) started becoming gradually more unstable. This usually manifested as mouse and keyboard freezes and then BSD’s happening more and more often at random times. Checked for malware, viruses, etc. and all was clean. Freezes etc. continued until my decision to take the unit in for a professional check/repair. Diagnosis came back as failing motherboard. I had the motherboard replaced and that also required changes to CPU (Intel Quadcore i7-4790 3.64GHz), memory (4GB installed),new Firewire interface (could not find a motherboard with one onboard), and optical drive. New motherboard is an Asus Z97-K windows 8.1 ready x64 capable.
  
Upon getting the unit back I jumped into testing it. The initial results were that everything was working just as before the changes except for Sonar X3e Producer. Later, after more in depth testing I discovered that ALL versions of SONAR I had installed on the machine exhibited the same symptoms.  All other applications were nominal and there had been no data loss.
 
Additionally, all previously installed stand-alone synths and samplers worked perfectly. The programs were picking up my audio interface (M-Audio Firewire 2626) and making all the right noises from all the right cones.
 
The Symptoms
The issue is that all versions of SONAR stopped running....the splash screen would display, then disappear as usual, but then...nothing! There was no error window displayed. There was no diagnostics presented at all. Literally nothing else happened.SONARPDR.exe does appear in Task Manager Processes before the splash screen appears but disappears a second or two after the splash screen disappears. The byte count in Task Manager climbs to a max of about 30,000K and the entry has usually disappeared before it goes beyond this.  This max is reached after a computer restart. Subsequent attempts to start SONAR have far smaller byte counts associated. Intermittently when monitoring Task Manager I do see werfault.exe pop up on the processes screen as sonarpdr.exe disappears. It is there for less than a second. I had a look at the interface to supposedly have a look at the logs this process creates but I was not able to glean anything from what I could look at so did not investigate further......my geek-ness does have its limits.....
 
 
Troubleshooting Trail So Far
 
Cakewalk Support
Submitted a support ticket to Cakewalk which was responded to quickly within time zone restrictions (I am in New Zealand). The rep just took me through steps that are clearly available in their knowledge base on their web site. 

• Version re-installs –first just X3e but then all of the versions I had installed on the machine
• Re-installation of C++ distributables
  
• Shutting down Start Up programs via msconfig
• Manual Re-personalization of SONAR
• Sent them System Information files twice
• Finally they cut me loose with the recommendation to reinstall on ANOTHER system.

 
After each of these steps the Symptoms were the same.
 
At this point I had just X3e installed and all other versions were fully removed.
 
 
Repair Technician
I interviewed the repair tech about what he had done and/or not done during his work on the system. He is in the habit of making quite detailed notes as he does this kind or rebuild and I did a review of these with him. His notes did not have any specific mention of errors, failures, etc. And his memory of the build was “sweet as” in kiwi vernacular (translated: went well). There were only two items that came out of the interview that needed further review. The first was the fact that the onboard audio had not been disabled.  The tech explained that he had tested the onboard audio and it worked, and then tested the sound card (M-Audio Revo 7.1) and it worked too. Then he tested both simultaneously and both worked. So he left both active. The other issue was the fact that he had not updated the BIOS on the motherboard. The tech explained that he never updates the BIOS on re-builds due to ‘shop policy’. A quick check during the interview found that there were 2 updates that were available since the build was done. In my book BIOS updates are a LAST OPTION kind of thing.....so I have not updated it.
 
The tech offered –free of charge—to use a new hard drive out of their stock to replace my C: drive, to then install a fresh instance of Win 7 32bit (duplicate what I am currently running) so that I could then install SONAR X3e Producer as the only application installed to possibly eliminate a Windows cause/verify a hardware issue. This has not been done but the offer stands.
 
 
What I Have Done

1. Retested onboard audio and sound card and confirmed what the tech had stated. Further testing was repeated with onboard only, sound card only, and both active. No issues found other than in all cases SONAR does not run.
2. Restored to all previous restore points and repeated testing.
3. I ran chkdsk /R on C: drive. It ran to completion with no errors/corrections.
4. Used Win 7 Recovery/Repair CD to rebuild Win 7 32 bit.
5. I repeated Manual Re-personalization This failed again. I saw a posting where a suggestion renaming the AUD.ini file was described. This is basically a specific form of Manual Re-personalization. I repeated renaming the AUD.ini file and activated SONAR with the following methods: normal shortcut, Opening SONARPDR.exe, double clicking on a stored Project, and each of these while holding down the Shift Key (as described in the post).  On a test using a renamed AUD.ini file and activating SONAR via an existing Project with SHIFT key pressed to my GREAT surprise SONAR X3e Producer loaded, scanned for plug-ins, loaded the specified Project, and I was able to playback normally. SONAR had linked with my audio interface just as before the hardware changes. I spent a while testing basic functionality and all was well. Overjoyed at this result I closed SONAR and attempted to do it again......At this writing and after many attempts to duplicate I have not been able to reproduce the result.
6. Booted Win 7 into Safe Mode and was able to get Sonar X3e Producer running! This is completely repeatable.
7. Repeated shutting down all Start up programs and tested (the virus checker remains [ESET NOD 32]). Repeated shutting down all Start up programs including deactivating virus checker and tested. Upon failure as last time I did the same thing by also removing all non Microsoft processes. Upon failure I removed all Start up programs and all processes and retested. There are a few processes that remain activated when deactivating all processes setting is chosen. Based on internet research this is normal. This condition failed as well.
8. I reviewed all drivers within Device Manager and confirmed that all are current/up to date except a driver for Microsoft Virtual WiFi mini-port adapter #2. When trying to update the driver Windows found a newer one but I got alerts that it was not Windows Certified along with a recommendation not to install it. So I re-ran tests with this driver deactivated. All tests failed.

 
To summarize:

• New Motherboard was installed
• SONAR X3e Producer does not load...all SONAR versions do not load...ALL else is nominal
• Extensive testing has been done to troubleshoot
• Windows 7 seems sound
• Hard drive OK
• Drivers all current or deactivated
• SONAR runs in SAFE mode and this is repeatable.
• Fault still exists when systematically removing Start up programs AND processes.
• I have had SONAR run only once since the hardware changes and with a non-modified configuration (other than re-initiating AUD.ini) by renaming the AUD.ini file and then activating by loading a Project with Shift key pressed. This is not repeatable.

 
At this point I was running up against a project deadline and so I had to install SONAR X3e Producer on a backup laptop I had. The installation was done using the same set of files that I used for all the re-installs that were done in the above processes/tests. The install was flawless. I installed all the plug-ins that come with SONAR plus the few I specifically needed for my Project delivery. I got things done and delivered on time but now my mind is back to this issue.
 
I would love to hear from someone that has a suggestion for what next to try....
 
What I Might Do Next....But Would Like to Avoid

1. Try to access and review the logs possibly created by the werfault.exe process.
2. Study the AUD.ini file on the fresh install of SONAR on the spare laptop and compare with several versions that have been created through all troubleshooting described above.
3. BIOS Update
4. Take the unit back to the repair shop for free troubleshooting offer noted above. Based on subsequent testing and checks. I am  dubious that this action will add anything new to the troubleshoot, but never say never.
5. Organize myself to reinstall Windows 7 32 bit... and then tediously get all my programs and data back on the machine...but if I am committing to this level I should at least contemplate updating further.....see #6 below...
6. Organize myself to do a full rebuild of the desktop....Upgrading to Win 7 x64, add more memory, and then tediously get all my programs and data back on the machine...Taking full advantage of the new motherboard...I already have the Win 7 x64 DVD....
7. And since the desktop just started showing the Windows 10 icon, I guess I could jump into the early adopter pool and jump to this brand new ‘Technical Preview”....a chill just ran down my spine...........

 
Again, I would love to hear from someone that has a suggestion for what next to try....

Two things I would suggest. Open Event Viewer and clear all the log files.
Restart. Wait a few minutes until everything stabilizes and all the startup processes complete.
Load Sonar and mark the exact time.
When it fails, open the event viewer and look over any messages from that time.
See if that gives a clue.
 
The second thing is what I always use when faced with a messy situation: ProcMon.
 
This is a very powerful utility from SysInternals (part of Microsoft).
 
It will log every system call and registry operation by the system.
 
It will take a bit of time to get familiar with it, but basically you just start it up and then start Sonar.
Stop it when the crash occurs and then exclude unnecessary system calls by process name.
 
You will have a gazillion things to look at, but with time, this can payoff. It is mind-blowing to see all the system calls required just to open a single file.
 
Once you get familiar with ProcMon you will find it incredibly useful. I've used it many dozens of times, so I'm used to many patterns of system behavior. You can see that localization calls are made looking up language packs and locale info, crypto routines are loaded to decode stuff, etc. Eventually you just skim over a bunch of stuff and nail things down quickly.
 
Finally, by all means use a 64-bit OS. 32-bit OSes are dead. You can still run 32-bit Sonar, but why would you want to do that?
 

Wow, what an extensive and thorough post. I only hope we can live up to those same standards. BTW, welcome to the forum. Lots of good help here.
 
The first question I have for you is. are you running ASO4ALL? If so delete it from your system. We are finding time and again that it is causing major problems with Sonar.
 
Do you have an HD Audio driver for your onboard audio? Check Device Manager. If you have, disable it.
 
That's all I've got at the moment. If you can try one or both of those things we'll see what happens.
 
 

Hi Mudgel,
Not running ASO4ALL...
HD Audio driver disabled and SONAR will still not run....
Thanks for the suggestions....
 
Jim
 
 

Hi arachnaut,
 
Nothing new that I have seen using Event Viewer. In fact the only Events (2) that showed up at all were in the Security area but no error condition noted using your suggested method.
 
Working on gathering a couple of run attempts to do some sort of comparison using Process Monitor...comparing troublesome desktop vs laptop with a fresh install of Sonar X3e Producer. I have a filtered .csv from the laptop trial run just need to duplicate on the desktop and have a look to see what is the same and what may be different.
 
Thanks for your suggestions.
 
Jim

You stated you had to add a new firewire card to your PC - does it have the TI chip set?  I have seen posts before that have indicated that other chip sets have been problematic with Sonar.

Booted Win 7 into Safe Mode and was able to get Sonar X3e Producer running! This is completely repeatable.
 
That suggests that this is not primarily a Sonar problem. Do you mean that Sonar just started or that it ran normally under safe mode? The main point of safe mode is to avoid loading anything but the essential drivers or services, so I would be surprised if you had audio drivers active in that mode. In any event, Sonar loading in Windows Safe Mode but crashing in full Windows suggests that Sonar is calling a defective driver or process. In safe mode you can try to un-install/delete the most likely drivers (audio interface or other audio or midi control equipment for starters). You can then try to start Sonar and if it does not crash on startup in the full Windows load, you can start re-installing the drivers one at a time. If you can get into Sonar in Windows Safe Mode, you should also make sure that Sonar is not set to open with a project or a template, which may be calling something that is broken.
 
It is also possible that you have defective memory. Your  symptoms prior to MB replacement were consistent with that. If you have very little software running on your machine, and a fully loaded Windows fills lower memory addresses and is pushed into defective addresses when Sonar is loaded, it is possible that failure would only occur when Sonar attempts to load. Since Windows Safe Mode fills much less memory it could still work. A comprehensive memory test may take hours, and might not have been done by the tech. Memtest 86+ might be worth an overnight run.

Have you tried running Sonar and as the Administrator?

I might be wrong, but this sounds to me like either a hardware problem or a driver problem rather than a Sonar one.

Just in case it is a software problem, have you tried running Sonar without the antivirus installed? Not just with scanning turned off but the antivirus software completely removed from the PC or otherwise prevented from starting when the PC boots? If not I suggest trying that just to make sure the antivirus isn't blocking Sonar or a process Sonar calls or relies on before digging into driver issues.

You say the only hardware item changed was the motherboard. Were the correct and up to date motherboard drivers, from the manufacturer's website, installed or just the generic ones that come with Windows? If not I suggest downloading and installing them.

Another thing to try is to uninstall the video drivers then reboot so Windows uses its own VGA driver. Video driver problems can cause all sorts of issues with Windows and software.

Might also be worth re-seating the RAM and checking all the internal cables are connected properly.

Prior to your attempts at reinstalling Sonar, have you gone in and deleted the necessary registry keys?
 
I see no reference to this in your post and will stop Sonar dead in it's tracks