OK. I had SONAR Professional running perfectly on my Win 10 Home PC.  Then I decided to upgrade for lifetime updates and move to Platinum.  BIG MISTAKE!!
 
For some reason I am not able to fathom, I cannot get Platinum to run.  I asked Support, and they suggested the following linl:

 
Somehow, this did not help - as in my case SONAR Platinum did actually fire up - but then as soon as you either attempt to open one of the templates presented on the opening screen, OR attempted to open an existing project, SONAR would freeze, and then after some period of time the Windows Blue Screen would come up - and the reported error is 'DPC_WATCHDOG_VIOLATION' is displayed.
 
So then I did a complete NEW fresh install of Win 10 Home.  I completed this successfully, installed some of the other apps that I normally use (Lightroom, OFFICE 365), and then proceeded to complete the Command Center and other installs - all NEW, FRESH.
 
After completion, I rebooted my PC and then attempted to fire up Platinum, and much to my disappointment, ended with exactly the same error I had before!!  I am at my wits end!
 
If anyone can help, as SUPPORT does not seem to be very helpful, I truly would appreciate that.
 
DELL XPS; INTEL Core i7; 9 GB RAM; x64 processor; CPU 920 @ 2.67 GHz
Windows 10 Home
 
Thanks!

did you try this ?

It is a Windows 10 issue - try the video fix posted above, or do a Google search on DPC_WATCHDOG_VIOLATION and you will see many posts that you can evaluate and apply.
 
I hope you are able to get this resolved, 
 
Bob Bone
 

Hello Chuck and Bob
Well, I reinstalled Win 10 Home completely, and yes I did check that I was using the latest drivers available for all the installed devices. I did search Google for this DPC error and have attempted some of them.  To no avail - still faced with this issue with Sonar Platinum.  All my other s/ware (incl Adobe Lightroom, MS Office 365) run perfectly!
 
Strange that before all this happened and I decided to "upgrade", my installation of SONAR Professional worked perfectly!  So what went wrong?  Can't simply understand why this does not work after doing a clean Win 10 Home reinstall on my DELL machine!
 
Thanks for your support, but I am still struggling to get this to work!

Try deleting your aud.ini which can be found here:
 
C:\Users\[username]\AppData\Roaming\Cakewalk\SONAR Platinum
 
If that doesn't work, do a FULL reinstall, as per:
 
https://www.cakewalk.com/Support/Knowledge-Base/2007013392/SONAR-2015-Clean-Install-Instructions
 

Thanks Bristol_Jonesey
I have been down that route before. No luck.
There is a suggestion to update drivers, Win 10 tells me I have all the latest drivers.  Thing is my boot SSD is running off of an ASMEDIA SATA controller card. While the system boots up without any difficulty, and all my other s/ware runs fine, I cannot figure out why just SONAR Platinum appears to crap out!
 
Mind you, all this is after I went through a complete reinstall of the O/S Win 10 Home on my PC!
Still struggling!
Does anyone know if Win 10 creates log files from a DPC violation that can be sent out for analysis?
 
Thanks all.  Appreciated!

what kind of soundcard do you have ?
 
and is it hooked up while trying to open Sonar ?

Hi Chuck - well, the sound card on the board is the Creative SB X-Fi.  This is what I use normally when just using the PC. When I use SONAR, I have a Firewire interface from M-Audio - the Profire 610.  This is hooked up to my studio speakers.  Yes, these are all hooked up - but typically I only use the M-Audio for sound when using Sonar.

Chuck, just listening to your Elements of Love - very nice!
 

The DPC_WATCHDOG_VIOLATION indicates that a driver is not responding. If there is a minidump, you should be able to pinpoint which hardware device is raising the exception. If there is no minidump, there will likely be an entry in the Windows Event Log that'll point you in the right direction.
 
I'd try a few experiments, e.g. disabling each of the audio interfaces in turn, to see if the problem goes away after turning one of them off. Or switching to a different driver, e.g. try WDM if you're currently using ASIO or vice versa.