Please do provide some info from the blue screen data, as that might help us find the right solution for you.
 
It certainly seems like a system-specific issue, as others have certainly not been reporting blue screen crashes for quite a  while.
 
Recalling past blue-screen crashes, could you possibly have a sample rate mismatch between Sonar and the settings on the audio interface?  That used to cause wacky things to happen for folks.
 
Also, could you possibly be using a USB 3 port to plug the interface into?  Many, if not most, audio interface that use USB connectivity seem to want to be plugged into a USB 2 port, and some interfaces have all kinds of stability issues if plugged into a USB 3 port.
 
Without some additional information, I don't know what else to offer....
 
Bob Bone
 

Quad Capture here, rock solid. I have the other sound disabled except the Quad, running ASIO.
 
Not running the latest driver, mine is 1.5.0, latest is 1.5.2. No issue, so I'm not upgrading the driver.

Hey everyone,
 
Wow thanks for all of the answers, so helpful. I don't know where to start. I have the latest drivers for the Quad-Capture. I have SONAR X1, X2, X3 and Platinum. I bought the Quad-Capture after I got X2 and I had some issues starting then. I've have taken a number of steps to try to remedy this situation. I don't have 'Share Drivers with Other Programs' checked. Also, my system uses the on-board soundcard when SONAR is running, and that has also helped tremendously, far less crashes when I figured that out. When I run SONAR, I don't run anything else, no internet browsing, not anything. The sample rate of SONAR also matches the sample rate used by the Quad-Capture, so I don't think that's the issue. I also used WDM/KS and that seems to be more stable than ASIO, I am not sure why.
 
I do think robert_e_bone is right. I might be plugging it into a USB 3.0 slot. That's not something I've considered as an issue up until you brought it up, so I will definitely try that as well.
 
Also, I am not familiar with how to disable other audio drivers. What does that entail? Typically, I plug in the Quad-Capture USB into one of the slots. I use WDM/KS within SONAR and I only check the Quad-Capture inputs and outputs in Preferences>Devices.
 
I think what I will do for now is try a USB 2.0 slot and see if that helps. Anyone know how to distinguish between a USB 2.0 port and a USB 3.0 port? I hope that is the issue. If it happens again, I'll read the details of the crash. But I am curious as what ampfixer means by disconnecting all other drivers. Please let me know.
 
Thanks to everyone for their input!

If the motherboard has build in sound, you can disable it in the bios setup. 
 
Or you can start Control Panel, search for sound (Change sound card settings or similar) where you see a list of device for playback and recording. In my system, the Quad Capture shows up as the default device for both playback and recording.
 
> Anyone know how to distinguish between a USB 2.0 port and a USB 3.0 port?
I'm not sure if this is a standard color, my USB 3.0 board port is blue. Do check your board manual.

I just checked my manual. I have an Alienware laptop, M18x. It doesn't look like it has a USB 2.0 port, only 3.0. I searched for USB 3.0 audio interfaces and the only one I found was around $2500, crazy. If anyone finds one for cheaper, please let me know.
 
In my system, I have found that selecting the laptop speakers as my system sound and the Quad-Capture for SONAR's use definitely makes for a more stable environment.

As Bob Bone pointed out, with ref to the Quad Capture system requirement :

http://roland.com/support/article/?q=downloads&p=UA-55&id=62264894
 
* This product cannot be used with a USB 3.0 port that is not compatible with USB 2.0 specification.
* If this product does not work correctly when connected to a USB 3.0 port, you will need to connect it to a USB 2.0 port.

tomixornot
* This product cannot be used with a USB 3.0 port that is not compatible with USB 2.0 specification.

I thought the 3.0 spec accepted 2.0 by definition.
 

I was actually thinking that, because wasn't USB 3.0 made with backwards compatibility in mind?

I have 2.0 and 3.0 available.  In theory, 3.0 is supposed to be backward compatible, but I had trouble with a couple of different 2.0 devices plugged into a 3.0 spot.
 
I'm sure some implementations are better than others, but mine is not so good in this regard.

Well I guess I would have to wait for my computer to crash to find out if that is the issue. Would that sort of info be provided a crash (i.e. USB 3.0 issues)?