I recently reset up my studio in a new apt. It's exactly how it was a few months ago and it ran fine then.  Now, the audio engine shuts down if you look at it.  LITERALLY!  I've even boosted it up 1024 buffer, which is useless.  The most I've EVER had to boost it was to 512.  I can't think of anything else I can do outside of buying a new interface, which I would really hate to do.  I bought this in '07 for $350 I think.  It's SOOO CLEAN!!, and FULL of features.  Now, the only boxes out there that have these kinds of features cost right at $1,000.  I was thinking about replacing it with the PreSonus Studio 192, since I already have the FaderPort8.  Learning their Studio 1 ver. 3 is a bit to chew off coming from Sonar.
 
Penny for your thoughts.
KC

Doesn't it use ASIO4ALL? Or are there dedicated drivers?

Ya, Alesis has never had a good rep as an audio interface, They never bothered to write proper drivers. Sorry  but if you want smooth sailing with Sonar buy a proper interface with good ASIO drivers. Otherwise might as well use your on board. 

Alesis audio interfaces suck. That's why

Well, with all due respect, and I DO mean that, it's preamps are as clean as ANY I've ever heard, and as I stated in my post, it has always worked fine...FOR 10 YRS....until now.  I'm not saying I'm completely ignoring your advice, but I would like to ask another favor if I could.  If the Alesis is such a pc of crap, what interface would you suggest for under $1000 that has 8 XLR-Bal. preamps that also toggle to phantom? 16 Ch. of ADAT, 8 Monitor Outs, and SPDIF? Now, I don't need 8 phantom mics, but it's an impressive feature. As mentioned in my original post, I was seriously considering the PreSonus Studio 192 because of it's tight integration to my FaderPort8.  The one review I read about it commented that the USB-3 really didn't improve the latency anymore than the USB-2 interfaces they have.
 
I will also add that looking at a much larger picture of Alesis in the history of this industry, it IS true that but for Alesis, we would still be paying more than $6,000/ch. instead of the $320/ch. that ADAT broke out for digital 8-track recording.  No, it wasn't perfect, and even they would tell you that, but Tascam would have waited WAAY later than when they did to break out their TDIF format.  Just sayin'.
 
Thanks,
KC

What a great opportunity for me to offer some advise.
Go figure it out yourself. You've done nothing but come to this forum and either A- Complain or B- Ask others for help with your problems. I actually cant remember once you helping some one else on this forum.
 
Im sure others will pity you but I have nothing.
 

Actually this is the first thread you've started in a long time where you even came back to respond. The last 4 threads you started people tried to help but you never responded. As Chuck said this forum is a matter of give and take and even if you have nothing to give it is only polite to respond to your questions and remain engaged in threads until problem or answers are resolved. 
 
You asked a question and we all seem to have the same answer- Alesis is not a good brand of audio interface.. Hardware is only part of what a good audio interface should be. The drivers are almost more important.  They just seem to not follow through with drivers and support. I think  even the drum modules suffer the same. 
 
Make a list of all the features you need and start shopping, or revert to what ever OS and system you had that worked. This is really your problem, not ours , we cannot shop for an interface for you, only you will know what you need. 
Here's the best place to start
https://www.sweetwater.com/shop/studio-recording/audio-interfaces/
 
( I would be looking at the Motu having what you want) 

The final drivers for the IO26 were pretty good for ASIO. Version v3.5.3.8671 I believe. If setting up your new studio involved any reinstallations, then it's a good thing to check. Otherwise, check DPC latency & other computer magic.

My first interface was an IO26.  Didn't last long and I moved on.  Never got it to work right, may have been "cockpit error" but the inputs or headset always were an issue.
 
 

chuckebaby
What a great opportunity for me to offer some advise.
Go figure it out yourself. You've done nothing but come to this forum and either A- Complain or B- Ask others for help with your problems. I actually cant remember once you helping some one else on this forum.
 
Im sure others will pity you but I have nothing.
 

Glad someone said it.