Teal

Jim Roseberry
If you have Samplitude installed, it installs a Generic ASIO driver.
Set Sonar to use ASIO driver mode... and select the RME ASIO driver.
That's all there is to it...

NO such driver appears in Smplitude.  ASIO4All not installed.

http://www.asio2ks.de/
You don't have this installed do you?
 
Did you validate that on the Preferences > Audio > Playback and Recording tab you have selected ASIO?

gswitz
Be advised that new Windows Drivers were posted at RME on 6/13/2014.

I'm still on W7.

Despite my objections, I actually like this program.  Nice touches are the UI and multi screen sizing and customization, MMC works well with an external sequencer, the Synth rack is a nice touch now that I figured it out.  Also like the MIDI controller mapping.
 
Clip looping works exactly the same as Samplitude.  The UI docking mechanism is similar too.   In fact I would say this is the closest UI to samp from all the others I have tried.  

Teal
According to readme from driver, only a few small unrelated bugfixes.  Will install later, also requires flashing the firmware, but that won't fix this problem.

THIS. ...This is the problem right here. You seem so certain it won't fix the problem yet you obviously have no idea what is causing the problem to begin with. As Craig pointed out, you are not thinking logically. The fact that your issue seems unique to you is a sign the problem is likely you, but you would rather blame the program instead of troubleshoot.

I am a software developer, so spare me "tech police" routine.
 
The fact that SONAR is popping a dialog for a driver that is greyed out and not even selected is a BUG.  At the very least it is an undocumented feature.   There may be some way external to the software to workaround this bug.
 
This driver does not show up in any other audio programs.  Cubase, Samplitude, Ableton, Studio One have worked fine.
 
RME drivers are solid, this was a minor release with 3 tiny unrelated features addressed.  There is a .0001% chance it is the driver, but since last release of SONAR was prior to latest RME patch,  very very unlikely.
 
Another RME user in this thread reported getting this same problem, for which he came up with a workaround he cant remember, but it did not involve an RME patch.  Most likely explanation a SONAR bug.  Its possible to modify the system to avoid getting the bug, which is what you are suggesting.  That is called a workaround.
 
In software world, finding bugs is a good thing.  Acknowledging them instead of dismissing the user is the way they get fixed.

Cakewalk has a site for submitting repeatable problems or bugs. They also have a support line. Call support and get some help is my suggestion. Personally, I'm betting it's related to software you installed.

To add why don't you remove this driver? With your skill set you should be able to work out where it is and how to uninstall or forceably remove it. Or you could locate the issue by process of elimination. And update your drivers and firmware as others have said.

Teal
Another RME user in this thread reported getting this same problem, for which he came up with a workaround he cant remember, but it did not involve an RME patch.  Most likely explanation a SONAR bug.  Its possible to modify the system to avoid getting the bug, which is what you are suggesting.  That is called a workaround.

 
Unless there's some other post you're referring to I don't think you have your facts straight. He remembered what caused the problem, and it didn't involve Sonar:
 
"I have the RME unit and I have come across the problem you describe. I was able to chase it down to a MIDI device (Fishman Triple Play) in standalone mode. However I don't believe I ever came across it while utilizing the device while I was in Sonar."
 
The only other post with someone having problems with RME related to his specific computer, with the computer manufacturer blaming RME and RME blaming the computer manufacturer. Again, not a Sonar problem.
 

In software world, finding bugs is a good thing.  Acknowledging them instead of dismissing the user is the way they get fixed.

Finding bugs is good, but there's zero evidence you've actually found a bug in Sonar as opposed to one that's system-specific. Sonar exposing a bug is different compared to Sonar having a bug. You haven't provided any steps to reproduce, and no other RME user has the same problem with Sonar. Unless you can figure out how to reproduce it, or someone else encounters it, you're the only person who can find out what's wrong with your system. You haven't given any information the community (especially RME owners) can use to help you find out what's wrong.
 
What do RME and the RME forums have to say about this? By definition they're almost all RME users, and some are bound to use Sonar, so you might have a better chance of finding out if anyone else has experienced this issue in a context other than running Fishman's TriplePlay in standalone mode. But just the very fact that the same problem occurs with a program that's NOT Sonar pretty much indicates the problem lies outside of Sonar.

It's X3D I think unless they did another build since.

There have been clear pointers in this thread that should allow the OP to resolve this issue.
I suggest the OP reads through the thread again and follow advice given. Sonar does not come with this generic driver.
 
1) Update the existing drivers and firmware. Rule that out first.
2) Assuming problem still exists afterwards identify what the generic driver is, and identify which app it lives with.
3) Remove the driver by uninstalling or via manual method. Maybe you could even just disable it. Further info on what to do here within this thread...
 
It's not like issues like this have not been experienced before.

Ta.

There are similar situations and scenarios here if you scan through the results. The link closely associates itself to points (2) and (3) of my post which wasn't quoted. Many of the results are extremely relevant. Again it's not a Sonar specific issue.

The first hit is asio4all

mazing