robert_e_bone
If your Windows sounds play through your audio interface, and you are using ASIO as a driver mode, then you are setting the stage for trouble, sounds like you have your audio interface set to be the default Windows audio device.  IF that is the case, and Windows sounds are enabled, then anytime Windows sounds try to play while Sonar is running, your system may hang.
 
IF the above is how you have things currently set, I would suggest:
 
1.  Turn off Windows sounds
2.  Set your Windows default audio device to your on-board sound, and set specific audio applications, such as Sonar to use your audio interface in ASIO mode.
 
I recommend you give the above a try and post back, 
 
Bob Bone
 
 

Thanks Bob...my Creative drivers are disabled when I'm using Sonar. I have no Windows 'sounds' - except startup sound. If I'm using Sonar, and want to play say a video tute and/or maybe a video from the net, then Windows will use it, so perhaps this might cause an issue? - although I usually don't do this when working on projects.  The other day, whilst using Sonar, I had my Canon printers start up - delayed - this caused Sonar to hang...but this is not the issue I'm finding here.

CakeAlexS
Not a Sonar issue (please change thread title).
+1 to what people say here so far.
 
Here are latest drivers, you also need to update the "system program":
http://www.roland.com/support/article/?q=downloads&p=UA-55
 
Thanks...

Have changed the title...what do I know? Sonar can't find the drivers, so it appears to be related to Sonar and Quad. I have the latest drivers and system program. Thanks 

Just a data point - I'm using x3d and on my laptop (not a dedicated DAW) I use a quad capture and I haven't had any issues.

Please disable on board sound in the BIOS (not device manager) I suggest, that will at least rule out a card conflict.
You may want to try renaming your AUD.INI afterwards as well.
Can you confirm that this does not happen with brand new Sonar X3D projects?
 
Cheers.

CakeAlexS
Please disable on board sound in the BIOS (not device manager) I suggest, that will at least rule out a card conflict.
You may want to try renaming your AUD.INI afterwards as well.
Can you confirm that this does not happen with brand new Sonar X3D projects?
 
Cheers.

My onboard sound card has been disabled for years now. My creative PSI is disabled via device manager. New projects usually go okay for a while, depending on what I do with them. This particular project may have something going on that causes this issue. It's not the only project that has caused this particular issue mind you...but it regularly does so and it's difficult to pin-point where the problem lies. I suspect it's related to the automation on a vocal wave file...too much going on for processing...who knows?
 
Where's that AUD.INI?

> My creative PSI is disabled via device manager
 
Please disable this in the BIOS if you can, otherwise rip it out your PC to see what happens. Just disabling it device manager may not be good enough.
 
Plenty of information on AUD.INI contained within these forums (or search you hard drive for it). When renamed this should reset your preferences.
 
This will at least rule out the root cause.
 
Cheers...

Okay, ripped out the Creative, issue still occurring. Sometimes I'll be working on a project and I'll get an audio dropout and suddenly no sound. It's all beyond me I can't figure it out. It just happens from time to time. Even if I can get sound out of the card on the system, Sonar just doesn't see it. I have to unplug the Quad, close Sonar, re-plug the card in, test it and then restart Sonar...workarounds. 
 
In a perfect world everything would work as it's supposed to. 
 
Thank to all for taking the time to offer some solutions.

I would review the other suggestions that have already been written here by other posters. In addition update your motherboard BIOS and chipset drivers via Intel auto update (assuming it's not a AMD motherboard).

Cheers

I have had Sonar unable to find drivers before in 2 kinds of situations:
 
1.  If my Sonar Driver Mode is set to something other than ASIO, it will not see Presonus Audio Interface, which has ASIO drivers, and I have to remove the check boxes for the on-board sound first, THEN I can change Driver Mode to ASIO.
 
2.  If I happen to plug in my audio interface to a different USB port, then it doesn't seem to find it, so I just always plug it into the exact same USB port anytime it gets disconnected (which itself is quite rarely done).
 
As far as drop outs go, I would suggest you look at your reported latency values in Sonar, and shoot for something around 10-11 milliseconds.  Sometimes the presence of a Wi-Fi adapter can cause all sorts of latency spikes, which cause lots of audio problems.
 
In addition, when you are experiencing audio dropouts, you can quickly determine if one or more of your loaded effects are causing the dropouts, by simply hitting the 'E' key on your computer keyboard, which will toggle all effects off/on.  If the dropouts go away after toggling the effects off, then you need to go through the process of figuring out which plugins are doing this.  (look for plugins that use look-ahead processing or chew up lots of CPU).  Boost 11 and Perfect Space can cause dropouts when these effects are loaded while in the tracking/recording process.  Those are really meant for mixing/mastering, not for recording.
 
So, give the above a shot and please post back, and I will try to help further, if needed.
 
Bob Bone
 

Creative drivers hide in your system. I had the same issue long time ago with having first a Creative Adigy II PCI card. When I bought a proper interface the Creative driver splash screen would not go away no matter what I did and audio would drop out at random. In the end I bought a new Hard drive and had to re do the OS and all was good after that. 
There seemed to be no way to get ride of the creative drivers. 
ASIO 4all seems to be the same bugaboo