I'm not sure if this is just unique to my setup but I've had an issue that seems to have started over the last few weeks. Still not exactly sure what starts it but something kills my sound card (Focusrite 8i6) dead on a regular basis when I'm running Sonar X1.
 
I /think/ it might be caused by having Chrome open in the background and maybe opening a site that's running something Flash-based. Doesn't always happen but that seems to be a common thread.

It doesn't happen every time but enough to now be very annoying. I can be playing back a mix in Sonar and then what usually happens is the sound card just crashes completely with no sound from Sonar or the browser or iTunes etc. Only way to fix it is to unplug the sound card and it all comes back fine for a while.

Sometimes just before it dies there might also be a slow buildup of feedback reaching ear-piercing levels - not pleasant!

It's all a bit vague/random but wondered if anyone else has been experiencing anything similar? I know Chrome & Flash have a history of causing audio problems and I think there might have been a Flash update in recent weeks (can't remember exactly). Don't think I've updated anything else recently but all drivers etc are up to date.

I suppose the immediate answer is don't use Chrome while I'm working but wondered if it's just me?

Sonar X1 Producer
Win 7 64 bit
Focusrite 8i6
Chrome 41.0.2272.118

Hello James P,
 
Thank you for your post. I understand that you're experiencing multiple problems- Google Chrome, Adobe Flash and your sound card crashes simultaneously. Please rest assured, we'll help you in this regards.
 
Let me tell you one thing clear, it is important to keep your audio driver up-to-date on regular basis. By downloading latest drivers, you can get rid of system bugs and internal conflicts. This shall fix sound card crashing problem.
 
Now we shall look into other problems- Chrome & Flash issues. Both are inter-linked, Flash being part of your browser. When you install Chrome, it comes with Flash pre-installed. Follow the instructions given below:
 
1. Type "chrome://conflicts" in Address Bar; press ENTER.
2. This shall open a list of all modules integrated in your browser.
3. Malfunctioning/ unsupported modules will be highlighted. Note down the names.
4. Press Windows Key + X, select Programs and Features.
5. Uninstall programs that use those modules.
 
Now the time has come to check for ActiveX/ DLL data errors that lead to Chrome and Flash crashes.
 
 
Thanks & Regards,
James Jacky

It sounds like you have both Sonar and Windows set to share your audio interface, which can be quite disastrous - particularly if using ASIO.
 
Just for grins, try setting your Windows Default Audio Device to your system's on-board sound, NOT your audio interface, and tell Sonar to use your audio interface - with a Driver Mode of ASIO.
 
See if that gets rid of that particular set of crashes, and please post back.
 
It is quite late, and I just saw your post, but will take a look at where things stand mid-day or so Saturday, if you are still needing assistance.
 
Bob Bone
 

Thanks for the replies. I took a list at chrome://conflicts and there were no conflicts listed.

Bob, your suggestion of using different interfaces for Sonar and Windows apps sounds logical but I don't know how practical it will be. My onboard sound is currently disabled (as recommended by the audio PC builder who made my machine) but even if I enable it, I'd need to have a separate set of speakers plugged into it rather than my studio monitors. Or would I route the 3.5" output from the onboard soundcard to one of the inputs on my Focusrite 8i6?

Anyway, I tried a bunch of things yesterday including completely removing Chrome then reinstalling it as well as a few system tweaks that I think I found from another thread here (http://www.acousticguitarcommunity.com/group/cakewalksonarusers/forum/topics/pc-tweaks-for-better-daw?commentId=2161554%3AComment%3A289974&xg_source=msg_com_gr_forum) and touch wood I haven't had the problem show its head again yet, although it happens randomly so I'll wait and see.

Weird thing is it's been running fine for 2 years using this same setup with no problems but just started doing this recently.