I don't know what's happened to the SONAR installation on my laptop, but something is definitely wrong.
 
I was at the time running the Early Release for January - but see later.
 
Last night I opened up a project I've been using just for testing purposes.
Most functions would result in a "Sonar is not Responding" message and I had to force closure.
Tasks I attempted to prompt this included Save, Bounce to Clip, dragging audio to an audio track form the browser.
 
I closed the project and started with a completely blank project with exactly the same outcome.
 
I rolled back to December and was again getting exactly the same
Next step was to rollback to October - same story.
 
I've since deleted my Aud.ini file, rebooted SONAR but no change.
 
This isn't exactly mission critical because I never use this laptop for recording, just for testing, troubleshooting and as a means to provide information to people requiring help on the forum.
 
So, any ideas? This one has me stumped.
 
 
 
 
 

Hi Colin. I have a laptop I use for simple tasks, but is almost useless unless I use the WASAPI Exclusive driver..
But I guess you have been through that route  Sorry to be of no more help.
All the best.

So did this laptop run Sonar in the past? 
Laptops can be problematic as even their BIOS is different from desktops.
It would seem there are certain laptops that no matter how you optimize them they just don't like audio apps.
And I used to tell people they need an Audio interface, but that is now changed and myself having good luck on a W7 laptop using WASAPI exclusive with out issue.  

I have to ask. . . you tried rebooting, right?

What state are the audio drivers in?
Using built in audio or an add on?
 
Also worth noting that if the system hasn't been used a lot it can take about a day for Windows to churn through all the Windows Updates to become generally usable again.  It uses a lot of system overhead downloading all of them, bg work, etc.
 
Respendence has released a new tool that might offer some system level insights.
http://www.resplendence.com/whysoslow
 
 
 
 
 

Hi guys, thanks for your replies.
 
To answer:
 

• yes, system rebooted several times
• using onboard realtek chip
• system used to run fine
• using WASAPI driver since December
• laptop running Win 10 - I don't think it's updated itself recently

Are you sure Win 10 hasn't recently updated itself?  I had lots of problems with Windows 10. . . one day something works and the next day it doesn't on my laptop.  I reverted back to Windows 8.1 and things went back to working.

rlared
Are you sure Win 10 hasn't recently updated itself?

That was my immediate thought as well.  Have a look in Windows update history just to make sure an update was not installed between the time it was working and now. Remember, in mid December 2016 there was an update for Windows 10 and there was a smaller one on January 10 (Patch Tuesday)

Also, maybe try a restore to an earlier restore point to a time when you remember it was working fine.

Other than that, I am thinking a hardware issue (Although you're not BSODing). Mind you, it would not hurt to update all your hardware drivers.

Yeah it looks like there was a fairly hefty update about 36 hours ago.
 
I'll just sit on it and wait a while, see what happens

I have a laptop that I use just as a remote recording devise with Sonar and using the realtek audio just has never worked or been an option on my system.  I have 2 audio outboard USB units that are not rock solid , but get by.  The M-audio ozone-has a midi keyboard and the other thing is a Berhinger FCA1616.  I can get them to work. but not the realtek. Just FYI.