I've been running 48k since the day I abandoned my ADAT XT's and switched to computer audio! Ha ha! I used to run 24 + tracks flawlessly on my old i5 with 8ghz RAM and SATA HDD's with tons of active plugins. 
This is what seems so odd to me. Something happened to cause me to suddenly get this problem at some point. I decided it must be because my computer was getting too old so, I bought a new, higher spec'd computer and, the problem is still there. And remember, this problem only seems to be affecting Cakewalk and previously Sonar Platinum. Now, as much as I want to say it's gotta be a problem with Cakewalk, that should mean that everyone should be seeing it as well. This is what has me so confused.
And, yes, I would love to have SSD's but, I don't and can't afford to go that route right now and, I know from past experience that SATA HDD's are more than capable of doing what I need when everything is working correctly.
FWIW, I just looked back on my forum posts and, this problem started for me in March of 2017

With regards to the sample rates, do you open Saffire's MixControl when working? I do recall issues where that GUI had to be opened (can minimize it) in order for SONAR to properly handshake with the unit. I have just gotten into the habit of popping MixControl open and verifying that "locked" appears at the bottom before opening a DAW these days.
 
Your sig also has the Octapre listed, do you experience the same issue there?

rodreb
Pragi - Yes, I do have an Nvidia video card. What do you mean "a not actual driver"?

Rod,
what I mean is an elder driver , a Nvidia driver which 
was developed 1 year or longer ago.
Often Nvidia drivers were the cause for issues with audio soft- and hardware.
I recommend installing the driver which was running flawless on your old system if it is
possible and you remember
or, if there is,
to try the onboard video card.
 
Sorry for my inconvenient way to express that. 
 
 

stickman393
Also, pay attention to anything scook says.

I love this! Great advice. Honestly.

Last night I reformatted my audio drive then, transferred all my projects back onto it (again). Didn't help at all. Then I moved one project over to may C drive and loaded it into Cakewalk from there, to bypass the audio drive altogether. Didn't help at all.
I tried bypassing all effects and I tried loading a project in "safe mode" with no effects loaded. Didn't help at all. I watched Dave Molton's video on tweaking Windows 10 for DAW use and tried any of his tweaks that I hadn't already tried. Didn't help at all.
I saved all the tracks of a project as WAV files and loaded them into Studio One and, everything works perfectly. I even added a HUGE amount of plugins to each track in Studio One and still, not a hiccup.
I love Cakewalk and am not that fond of Studio One but, man, I'm just about at a dead end here. I am totally stumped.

rodreb
I really don't know if that "Device Not Migrated" message on my audio drive can actually cause problems or not. Anyway, I wish I could figure out how to fix it, just to eliminate one more question. I'm considering physically disconnecting it and reconnecting it or, completely reformatting it and reloading all the data.

rodreb
Last night I reformatted my audio drive then, transferred all my projects back onto it (again). Didn't help at all. Then I moved one project over to may C drive and loaded it into Cakewalk from there, to bypass the audio drive altogether. Didn't help at all.
I tried bypassing all effects and I tried loading a project in "safe mode" with no effects loaded. Didn't help at all. I watched Dave Molton's video on tweaking Windows 10 for DAW use and tried any of his tweaks that I hadn't already tried. Didn't help at all.
I saved all the tracks of a project as WAV files and loaded them into Studio One and, everything works perfectly. I even added a HUGE amount of plugins to each track in Studio One and still, not a hiccup.
I love Cakewalk and am not that fond of Studio One but, man, I'm just about at a dead end here. I am totally stumped.

I think the "Device Not Migrated" is probably worth looking into further. The reason being:
 
1. The fact that the audio stops (as if CbB can't read from the disk fast enough); and
2. Enabling read caching improves things
 
The fact that Studio One works is probably down to differences in the way it streams data from the disk.
 
Have you installed the latest IDE/SATA drivers for your motherboard?  Quite often Microsoft's latest drivers will kind of work, but they're very generic and in no way tuned to your hardware. So if there's drivers available from your motherboard manufacturer, I'd take a look at installing them.
 
 

I think the solution for you is clear. It's just a case of familiarity, the familiarity you have with SONAR/Cakewalk because you have used it for so long, and because of that familiarity you can do things quicker and easier, you've done the learning already, you know the workarounds to get around all the quirks and bugs within SONAR/Cakewalk. Give yourself the time get as comfortable with another product as you are with SONAR/Cakewalk, at least comfortable enough to do what you need without having to think about it, obviously you can't give it the same amount of time it has taken you to get as familiar and fluent with SONAR/Cakewalk as you have become, but enough time to get where you need to be, it really doesn't take that long if you apply yourself and let go of your bias's, and allow yourself to get past the frustrations of learning something new, forget your perceived loyalty to a product/company etc.
 
I put down a lot of the issues you see talked about to what I like to call "Cake Flake", you see it in many threads, for eg the recent "Can't writ, disk may be full" thread, this has been going on for years and years, it doesn't affect everyone, but enough to be a well known issue here, then you have things like project/file corruption, has been ongoing for many years, again doesn't affect everyone, you could go on and on, there are many many examples of "Cake Flake" and you don't see the issues with other products, draw your own conclusions. If it wasn't for being a Cakewalk?SONAR user since Pro Audio 9 up until about 3 years ago, I would never have known what an audio engine drop out was, has never happened to me with ANY other product, only Cakewalk/SONAR. You'll see many threads that repeat the same thing as you have said, that everything works fine with other DAW's but not Cakewalk/SONAR, again, draw your own conclusions.
 
I believe if you give another DAW an honest chance, forgetting your bias's, you love of Cakewalk etc etc, your perceived loyalty to a product/company, life will become much easier, it did for me 3 years ago, I knew the workarounds and everything to avoid many of the issues, but when I gave myself the chance to experience other products, and allowed myself to get past the problem of being familiar with Cakewalk/SONAR, the frustrations of learning something new, I saw for myself what it was that I had been putting up with for years, and it just isn't necessary. Maybe for you it could end up that it is worth it to stay with Cakewalk, and that's fine, at least you'll know if you give something else a good honest chance.
 
Every program has quirks and bugs, but in my experience, Cakewalk?SONAR has more than it's fair share, best of luck with your problems, hope you get it sorted out which ever way.
 
When considering given solutions, remember, it works fine with other products, it does not with Cakewalk/SONAR

msmcleod - I agree and, I will look again for different drivers.
Matron Landslide - I know exactly what you're saying and, if I can't get this sorted out pretty soon, I will be forced to go that route. I know there's nothing I do in Cakewalk that can't be done elsewhere. I am a very "visual" person and, I really like the way Cakewalk looks and the colors in Studio One are so strange and kind of gaudy to me. Also, I am the kind of guy that does the bulk of my mixing in the track view. Studio One seems geared toward mixing in the console view. Still, if I need to, I will learn.

rodreb
I've been running 48k since the day I abandoned my ADAT XT's and switched to computer audio! Ha ha! I used to run 24 + tracks flawlessly on my old i5 with 8ghz RAM and SATA HDD's with tons of active plugins. 
This is what seems so odd to me. Something happened to cause me to suddenly get this problem at some point.

Yes, it did, so you need to track down what it was, and it could be anything, and don't rule anything out.
 
I was a tech support dude for a long time. Settings do get "magically" altered without us, the users, ever going into the UI and changing them.
 
Did you try the suggestions I gave you, all of them?
 
There could be some other program on your computer that you don't know about that is popping in and switching your audio interface back to 44.1. That was my reason for having you check your Windows sound settings. Make sure that the Windows properties for your interface are set to 48K and that the box for "Allow applications to take exclusive control of this device" is checked. Also that all Windows sounds are turned off, etc. Check Device Manager.
 
Yes, I know ASIO is supposed to override all of that stuff. I also know that I can be running a session and if I forget to turn off my messaging program it will merrily pop up and go "ding." So much for taking full control.
 
And don't assume that since you already set all of that stuff up the right way 2 years ago and nobody else has had access to the computer and you don't download anything and it's not connected to the Internet or whatever that it's still set that way. I've gone into the Sound properties and found them set to 48K when I do all my stuff in 44.1K. Whatever, I set it back the right way and get recording.
 
If I start to have troubles, then I go through and check it all again.
 
Sometimes all it takes is playing one rough mix that a client has sent me in a different bitrate and oddball format and it opens in the wrong program and things get weird. iTunes is notorious for being "helpful" about changing my settings if they are not what it thinks are "correct."
 
I've even gone into the control panel for my Firepods and found their settings all ganked up when I never touched them. Who knows? Maybe some latency checking program I ran went in and messed with it. Who cares, set them back the right way and roll on.
 
Have you tried, as a troubleshooting experiment, switching over to your computer's onboard sound chip to see if your problem still happens when you use that?

Euthymia
Have you tried, as a troubleshooting experiment, switching over to your computer's onboard sound chip to see if your problem still happens when you use that?

Good call - this would at least rule this out.