Started my Platinum subscription on Hopkinton, and I was able to install and run the program successfully, with no issues.   Life was good.   Since Ipswich, and now with Jamaica Plain, I've been experiencing constant random freezes while working.  I've read a bunch of threads here on the forum, and tried a bunch of things, but so far, I have not resolved the problem.  I would appreciate any help.
 
The problem?  Sonar freezing, and getting stuck with the spinning win 10 mouse icon, which requires a complete re-boot.  Usually occurs when I mouse click somewhere on the screen.  I've waited up to 20 minutes for Sonar to respond, but once it goes, only a complete re-boot will get it back.
 
The system?  19" I7 Laptop with 16GB memory and 2 1TB Hybrid Drives.  Roland Quad Capture Interface.  All with the latest drivers, firmware and updates.  All CCC updates installed.  Using a second 24" monitor via the laptops HDMI port.  I usually drag Sonar to the larger second monitor, and keep the console view open on the laptop screen.
 
The song?  Only has three tracks so far.  Midi Drum (Geist), Midi Bass (Sylenth) and Midi Keyboard (Mellotoon).  I've avoided adding any plugins a part of my troubleshooting.  Last night, I thought I found the problem by deleting the AUD.ini (suggestion from most threads) and a VST reset/scan, and I was able to work for about an hour (Usually the freeze happens in 10-15 minutes), but eventually Sonar froze.
 
Gonna try my last resort tonight.  Uninstalling and re-installing Sonar.   If that doesn't help, I'm out of ideas.
 

Have you tried rolling back to Hopkinton? Was the machine running Win10 with Hopkinton?
 

No, I haven't tried that yet.  Maybe I'll try that before uninstalling tonight.  Thanks.

before you rollback, you could exit Sonar, rename AUD.INI to anything else.  Restart Sonar and reset/rescan VSTs
 
It has only happened to me once in the last year, but letting Sonar rebuild AUD.INI has helped once as has reset/rescan of VST.  Once you're up to Jamaica, resetting should not need to be done again moving forward.
 
Just a couple of quick and dirty things to try before you dig in too deep.

I have this exact issue myself which I explained later on in this thread...
http://forum.cakewalk.com...problems-m3303385.aspx
 
Best roll back.
 
Couple of Q's.. In your project do you have drum maps. Do you also have multiple outputs from softsynths to audio tracks? My experience was once I deleted the drum maps it stabilized but then  the first CPU core got overloaded (more detail in the link above).

Ta.

If nothing else works and you're just about to rollback, try uninstalling and reinstalling your interface drivers. I was cursing Ipswich and Jamaica Plain until I tried this. Now all is fine. The idea is that because these releases work fine for an awful lot of folks, I surmised that it had to be a config error. That's why the above suggestions are good ones; they all deal with external objects with which Sonar has to bind, but don't forget the interface!
 
Good luck and let us know how you fare!

I forgot to say my last post points to a confirmed bug in JP.

No multiple outs from the softsynths, only stereo outs
No drum map as of yet.  Haven't got that far into the song yet.  
 
FYI.  I did the Aud.ini delete and VST rest/scan last night.   This did seem to help with the performance.   In the song mentioned above, I'm now right around 25% on core 1, and the other cores are barely registering.  Prior to the aud.ini deletion and and vst reset/scan, I was over 50% on core 1 and around 25% on the other cores.
 
Tonight, I'll try uninstalling/reinstalling the Roland drivers before rolling back to Hopkinton.
 

Ok thanks for confirming about no drum maps. That makes me (hopefully) conclude the next regression release will be fine. Thanks.

Good news.  Friday night I deleted the AUD.ini from my Sonar directory, and was able start a new project and work on it though the weekend, without one Sonar crash.  That's a good sign.   I have 4 VSTi's going, but no VST Fx yet.   Next step is to start adding fx.