SOLVED!
So I figured out what my problem was.  My new motherboard has a Realtek S1220A audio chip onboard.  I had disabled the on-board audio in Device manager.  I could see references to Realtek ASIO in aud.ini, so I deleted it and restarted Sonar, again it crashed, but when I looked in the newly created aud.ini, the reference to Realtek ASIO was back, so disabling it in device manager was not stopping Sonar from seeing the drivers.  So, I uninstalled the device in device manager, choosing to remove the drivers.  I deleted the aud.ini again and this time Sonar launched without crashing.  So, to make sure it didn't come back on next boot, I went into BIOS settings and disabled the Realtek audio device there too.  I rebooted and again, Sonar launched just fine.  I was then able to select my MOTU audio I/F and all is now fine.
 
So lesson learned - disabling a dodgy onboard card in device manager is not enough - you have to get rid of all traces of it.

Toward the end where they test smaller buffer sizes with DAWbench, it seems they have audio breakup at much lower CPU utilizations on the 1700x. That is probably more a symptom of DPC latency than CPU performance problems, and probably reflects more on the motherboard or chipset.

BRuys
SOLVED!
So I figured out what my problem was.  My new motherboard has a Realtek S1220A audio chip onboard.  I had disabled the on-board audio in Device manager.  I could see references to Realtek ASIO in aud.ini, so I deleted it and restarted Sonar, again it crashed, but when I looked in the newly created aud.ini, the reference to Realtek ASIO was back, so disabling it in device manager was not stopping Sonar from seeing the drivers.  So, I uninstalled the device in device manager, choosing to remove the drivers.  I deleted the aud.ini again and this time Sonar launched without crashing.  So, to make sure it didn't come back on next boot, I went into BIOS settings and disabled the Realtek audio device there too.  I rebooted and again, Sonar launched just fine.  I was then able to select my MOTU audio I/F and all is now fine.
 
So lesson learned - disabling a dodgy onboard card in device manager is not enough - you have to get rid of all traces of it.

That's great news. Would appreciate your posting a review when you have a chance to gauge your new DAW's performance.

Brando
That's great news. Would appreciate your posting a review when you have a chance to gauge your new DAW's performance.

Sure thing.  One thing I can say off the bat is that core loading is super even in Sonar on the Ryzen, like nothing I have ever seen before.  It's 2:30 am here and I just got up because I can't sleep .  I'll do some more in-depth testing tomorrow.

dcumpian
Based on this article, and borne out by AMD's stock price, you may have made a mistake:
 
https://www.benzinga.com/news/17/03/9120314/bad-news-for-amd-ryzen-7-getting-negative-reviews
 
Dan

But then when you see benchmarks in Linux like the first three HERE, you have to concede that the raw power is there and there will likely need to be some tweaks to Windows and some applications before we see Ryzen's true power.
 
Apps and OS's have been tweaked for Intel processors for years.  Ryzen is brand new and the paint is still wet on BIOS/Driver/OS/Application support.  Things will only get better.  My early impressions of Sonar on this platform are very favorable, but I won't have a solid feel for performance for a few more days.

I just wanted to add I just got a Ryzen 1700 On a Gigabyte Gamng 3 (AMD 350 chipset), Not OC'd (yet) running Sonar Platinum through a Focusrite Scarlett 18i20. I updated my old Intel Q9650 Quad core. i did not reinstall any thing. Just put old drives on new system, chugged along for a bit while it updated the hardware in windows, but in the end every thing is working way better than i had hoped for!

I have not deap hard test. But I am running a fairly simple project of about 20 tracks for the last few hours practicing for a set. I was on the WMD but switched to ASIO and i wondered with all the talk about poor performance at low buffer settings how low could I go. In the past 10ms latency was the best i could do. I figured i would start at 4ms but then said lets just go for it. I set it to 1ms (45 samples)  and it works flawless. I went from seeing only 1 cpu bar working up a little to a thin balanced line of 16 cpus.
 
I am in love with this new found power at a reasonable price point. Plus the mother board and AMD CPU cooler lights all look cool together fading across the spectrum.
 

I believe the problem is with the realtek ASIO driver rather than the onboard audio device.
Newer SONAR builds since last year work well with onboard audio devices in WASAPI.
I've heard reports of the realtek ASIO driver crashing in SONAR but we havent been able to investigate since we don't have a PC that includes this driver. Do you know if this driver is available to download and if it works on any realtek chipset? I'm sure we could work around the crash if we get a repro.
 

BRuys
SOLVED!
So I figured out what my problem was.  My new motherboard has a Realtek S1220A audio chip onboard.  I had disabled the on-board audio in Device manager.  I could see references to Realtek ASIO in aud.ini, so I deleted it and restarted Sonar, again it crashed, but when I looked in the newly created aud.ini, the reference to Realtek ASIO was back, so disabling it in device manager was not stopping Sonar from seeing the drivers.  So, I uninstalled the device in device manager, choosing to remove the drivers.  I deleted the aud.ini again and this time Sonar launched without crashing.  So, to make sure it didn't come back on next boot, I went into BIOS settings and disabled the Realtek audio device there too.  I rebooted and again, Sonar launched just fine.  I was then able to select my MOTU audio I/F and all is now fine.
 
So lesson learned - disabling a dodgy onboard card in device manager is not enough - you have to get rid of all traces of it.

Noel Borthwick [Cakewalk]
I believe the problem is with the realtek ASIO driver rather than the onboard audio device.
Newer SONAR builds since last year work well with onboard audio devices in WASAPI.
I've heard reports of the realtek ASIO driver crashing in SONAR but we havent been able to investigate since we don't have a PC that includes this driver. Do you know if this driver is available to download and if it works on any realtek chipset? I'm sure we could work around the crash if we get a repro.

Hi Noel,
 
I notice that the driver has  been updated by my motherboard vendor since this first happened.  Not sure if it has fixed the problem, but I would be happy to check for you.  If still buggy, I will point you to the driver.
 
Also, I sent a crash dump when I logged a support issue.  I might still have the dump file - would that be useful?

In the past the dump didnt indicate why the driver crashed so having a test case would be more useful.

Noel Borthwick [Cakewalk]
In the past the dump didnt indicate why the driver crashed so having a test case would be more useful.

OK, I will re-install the onboard audio and report back.