Some USB 3 ports are backward compatible, and some are not.
 
I looked at the specs for the computer and it looks like it has 2 super speed USB 3 ports and another USB 3 port, with apparently one set or the other seeming to be backward compatible.
 
Please note that backward compatible may be a sliding scale, from manufacturer to manufacturer, and while it might work for you, it also might not.
 
Certainly trying the other USB ports is worth a shot.  You may need to install the drivers for the interface again when you shift to a different port - I would actually recommend you first remove the audio interface drivers, then go through installation using one of the other ports.  if successful, you are done, and if not, then again remove the drivers and install them yet again for the 3rd port.  This approach should provide maximum potential for success.
 
I am also wondering if you can try one additional thing, if you haven't already - and I think this should be tried prior to doing audio interface driver removal/installation as explained above.
 
So - what I am asking you to try is to either turn off the laptop's Wi-Fi (there might be a physical little switch on the chassis somewhere, or perhaps a function key for it), or if not finding either a switch or function key, go into Windows Device Manager just prior to launching a Sonar session, then find and expand the Wi-Fi drivers and disable them.  (note that is disable, NOT uninstall or remove).  THEN, launch Sonar and see if you get a more stable system, as well as better audio streaming performance in Sonar.  After completing your Sonar session and closing Sonar, you can then turn on or enable the Wi-Fi again and you should get instant access to the web again.
 
The reason I mention messing with the Wi-Fi is that for MANY MANY folks, they have all kinds of sound and stability issues when running Sonar on a laptop that has Wi-Fi (which they all do).  Turning Wi-Fi off or disabling it, then running Sonar, then turning on/enabling after finishing the Sonar session seems to fix all of those issues for lots and lots of folks.
 
I look forward to you testing out that which I have put forth here, and thank you for trying the other things folks had suggested.
 
The Wi-Fi testing should be pretty quick, and may hopefully fix things up for you, or at the very least should give you better audio streaming stability.
 
Bob Bone
 

Hey robert_e_bone, I really appreciate the info. I am going to try the wifi thing and see if that works, then I'll give that driver re-installation a go if there are still any issues. Thank you very much, I'll let you know how things go. Just out of curiosity, should I disable the Bluetooth drivers as well?

I would stick with the Quad and try to find the problem, as said before, if it's not the problem you'll have wasted money on another sound card.
 
Yesterday the audio from the bass cut out, I could see it was still receiving a signal from the guitar, but the sound stopped. I feared the worse, but turned out that the internet went down and the demo version of Mark Studio had changed to a 10 min trial, instead of a 15 day trial.
 
Last night I was watching a Youtube documentary of the funk brothers, and I feared the worse. After re-starting  the browser it happened again and turned out it was a fault with the uploaded youtube video.
 
After years of problems with my M-Audio FW1814 on firewire and and a Texas chip, I gave up on it and went USB. But it becomes ingrained to doubt the soundcard. I still don''t know if it was the FW1814 at fault or if it was a red herring for something else.
 
The quad for info has worked well for me, on 2 different laptops and 3 versions of Sonar.

I agree with the others that think you should stick with the interface:

I was having the same problem with crashes 2-3 years ago with my Octa-Capture, and it was a real pain figuring out what the issue was; It eventually solved itself after installing the latest drivers for everything on my System, updating the firmware for the interface, and updating the interface driver as well.

In my experience, Sonar and the interface behave way more using WDM/KS (the lower latency is really nice too,) if you make a new .AUD and have it set up with it from the start.

I was having a pretty awful time after experimenting with the different driver modes to see which was the most stable, and had the lowest achievable latency; WDM/KS was what worked best for me, but it'd start acting up and setting off the wave profiler if I changed buffers or started a new project.

The thing works great now and I haven't had any issues from it since Roland released the updated drivers, so hopefully your problem gets resolved.

Well I tried running SONAR the past couple of days using the same USB port and with my Wifi disabled, and even though the session ran smoother than before, I still had a crash. So I decided to re-install the Quad-Capture driver using another USB port. The weirdest thing was that the new USB port I was using could only run SONAR in MME (it had some serious issues using the other drivers, crashing SONAR but not the computer), whereas the previously use USB port could run in ASIO and WDM/KS. Anyway, the computer still crashed a couple of times but I extracted the files Windows said contained information about the crash. I am not sure what to do with these but I have them on the desktop just in case. I am going to try another USB port tomorrow but honestly, it doesn't look good. I want to stick with this audio interface but it's giving me hell. Part of me wonders whether a firewire interface would give me these sorts of issues.

Hey everyone,
It seems as though I finally found the USB port that's compliant with the Quad-Capture. I hope I don't jinx myself but it looks like that's what it took. Thanks to all who helped!

WAHOO - please post back after you run with the new port for a while, and give another status.
 
GREAT news if that did fix things for you.
 
Bob Bone
 

 
Makes you realise how much we have to get involved with our machines to get and keep them working right.  And this has nothing to do with power.  I really great system can be rendered useless by a lowly usb port.
 

I am always relieved when it turns out that someone using the same Soundcard as me and is having problems finds that its not actually the our soundcard that at issue (even when mine is functioning well for me). 
 
Also good that this forum has helped another user and just saved them from selling a piece of working gear at the expense of buying another, to have found that wasn't the issue.
 
In general I think it helps to think aloud here, before you take any big steps. 

Kamikaze, I agree. I really appreciate everyone's help. I had contacted Roland so many times only to get some pretty useless answers. I contacted Cakewalk as well and they were considerable more helpful. Finally I turned to the forum and something worked out. So again, I appreciate everyone's help and input. I am also posting also to give the thread an update about the situation. I wanted to let everyone know that I have been using the Quad-Capture in a variety of situations that I know would have crashed my computer before, and I have not experienced one single crash. So yes, the solution has worked. Thanks everyone!