I'm not sure if the following is related my recent upgrade to "Newburyport": Pretty much all projects now have significant pops, crackles, and I constantly get "Audio Dropout - the Audio Engine has been stopped unexpectedly". I have to reset the audio engine but upon resuming playback it promptly locks up again.
 
It also seems like the "resting" CPU utilization is far higher than before.
 
I believe this to be "new", as projects that worked fine "as is" on prior releases seem to exhibit the issue.
 
So I've resorted to bouncing the majority of my busses, which I've never had to do before.
 
Q: have anyone else seen something like this?
 
I'd like to troubleshoot a bit before submitting a bug report.
 
Thanks in advance for any thoughts.
 
Allan
 
 

AllanH
I'm not sure if the following is related my recent upgrade to "Newburyport": Pretty much all projects now have significant pops, crackles, and I constantly get "Audio Dropout - the Audio Engine has been stopped unexpectedly". I have to reset the audio engine but upon resuming playback it promptly locks up again.
 
It also seems like the "resting" CPU utilization is far higher than before.
 
I believe this to be "new", as projects that worked fine "as is" on prior releases seem to exhibit the issue.
 
So I've resorted to bouncing the majority of my busses, which I've never had to do before.
 
Q: have anyone else seen something like this?
 
I'd like to troubleshoot a bit before submitting a bug report.
 
Thanks in advance for any thoughts.
 
Allan

A few things to start troubleshooting:

Have you rolled back to Manchester to make sure "Newburyport" is the actual cause? 

When you say "I have to reset the audio engine" , is that by that exiting Sonar, renaming your AUD.ini file and restarting sonar? 

Have you confirmed you have the latest drivers for your audio interface and other hardware (including video card)?

Check your DPC latency. I'm guessing WiFi drivers got enabled or some other process/driver has increased it.

I'm having the same issue. This is a pic of my system idling at 1024. I just updated to the rig signature less than a month ago. I was under the thought that this system would run full mixes with soft synths running and a mess of plugs at 32/64 samples. Not even close. This was a update from a P8P67 3.11 mobo and 1155 socket. I have to disable all plugins to get it to run at 64 samples, which is the lowest in Twin USB's console 2. I've been trying to the point of exhaustion to figure out why it's no better than my old system whatsoever. After spending $600 and pick up the Twin USB to do it.
 
There are so many processes running, and I have no clue what most of them are. I don't use wifi, so that's 'one down' - out of 61! How do I find out what processes should be turned off for audio applications in Win 10?
 

I had a similar situation occur at one point - projects which had worked fine started having dropouts. When I got a toast notification for dropouts, I clicked on its Help button and went through each suggested option. What solved it was increasing the cache parameters under Preferences > Audio > Sync and Caching. I suspect the default might have been reset after an update.

jshep0102
I just updated to the rig signature less than a month ago.

Same advice; check your DPC Latency:
 
http://www.resplendence.com/latencymon
 
If its not high/spiking, then other processes/drivers are not the issue. If it is high, it could be motherboard drivers as well as other hardware. If the board has WiFi and/or Bluetooth, you'll want to turn those off in BIOS.
 
And, of course, make sure your CPU is running at full and fixed speed. Disable Speed Step, C-States and Turbo Boost in BIOS, and set a the High Performance power management profile in Windows. Then go to Task Manager > Performance > Resource monitor, to verify your CPU is running at 4.0GHz, and no cores are parked.

Seeing this DPC, I'm more concerned at this point about why the inability for me to playback at anywhere near 64 or even 128 samples. Here's the DPC view after 3:30 of a 4 minute project:

I had similar issues after upgrading to windows 10. My motherboard uses an Intel NIC chipset. I cant remember which it was, but after the update I either had to Install the full driver, or uninstall it and revert to the MS provided driver to stop dropouts and pops/clicks. I wish I could offer more assistance, but this is all I can recall atm.

Oddly, though I don't know pertinent, LatencyMon reports me as using Windows 8. I have the current version running I d/l'd today. Is this what you mean when you wonder if all my cores are running? I think all 4 are, but the virtual ones don't act the same by this info. But I don't understand this stuff well, so I apologize if I am off base.

if you google that worst driver there's plenty of info https://www.google.co.uk/#q=wdf01000.sys+latency