Hey Folks,
 
Haven't posted in a while - things have been pretty smooth...but...
 
A couple months ago built a new machine (Win8, Core i5, 16GB RAM, SSD drives, TI chipped Firewire card, etc...) for my X3 upgrade.
 
I run a RME FF800 and a UA 2192 (connected via ADAT - UA is master clock) and never had a lick of problems with my system.
 
What's happening now though is that Sonar will randomly - during recording or playback - throw up an error which temporarily stops everything and after clicking "NO" on the error message will hang for a few seconds and then I can go back to doing whatever I was doing.  The RME drivers are up to date (new version posted just last week) and I believe I have all the Sonar patches installed as well.  RME driver in the tray never shows any problems - shows synced and the Fireface Mixer works, meaning I get levels bouncing for live inputs that were working in Sonar until it died.
 
The error message is a typical windows error message looking box with "SONAR X3 Producer" title.
 
RME Fireface 800
 
THe above Audio/MIDI device was disconnected from your system.  
Would you like SONAR to reroute these outputs to an available device?
Clicking "NO" allows SONAR to remember output settings to this device.
Note: If playback is in progress, clicking "YES" will stop the transport.
 
YES/NO
 
Anyone have the slightest clue what might be going on here?  It's driving me nuts.
 
Another issue I have is that anytime I use or enable a 64 bit engine (on export for example or in the device preferences to use the 64 bit engine) I get this weird high pitch buzzing in the background.  As soon as I uncheck the box - it goes away.
 
Thanks in advance!

mine gets disconnect messages too. I wonder if it is because SONAR is the only DAW to start and stop ASIO processing.

I get this, too, with my FF 400.  Just click no and go on.  It works for me every time.

...so bizarre.  Is this a RME thing then?  I just tried a demo install of PreSonus StudioOne 2.6 and it hung up too...no pop-up error message but kinda the same thing that it was doing in Sonar.  
 
RME's drivers have been so bullet proof - what is gong on here?  So annoying.
 
I just put a project I've been working on a 10 second loop or so and it only made it about 5 minutes before hanging up and popping the error message after a fresh reboot.  This is ridiculous.  I was working on something last night and this ruined about 4 takes I was doing because it would hang right in the middle of one and I'd have to start over.
 
I've tried clicking all kinds of different options, changing clock back to the RME, changing sample sizes, I'm out of ideas...
 
But this is unacceptable.  Maybe I'll call RME tomorrow...

Well this is scary. I have a FF800 and have been looking to upgrade to X? This makes me think twice.

Usb devices have a power saving setting that needs to be disabled. I think under advanced power options you can find a usb item. Choosing the highest power setting usually does the trick.

Do you know what I'm talking about? I can give you click by click inductions in you don't.

The FF800 isn't USB - it's FireWire.
 
That said, I'm up for trying anything.  I have no idea where you see a 'power settings' dialog box to change something to disabled...but maybe it's because I'm not running anything USB to Sonar...

The Band19
Well this is scary. I have a FF800 and have been looking to upgrade to X? This makes me think twice.

I don't think this is an "X" thing - I had weird problems when using another DAW software tonight too.  Not sure what permutation of stuff I have going on that is causing this but to say it's f'ing annoying is an understatement.

I have 2 x FF800's and they run without a hitch. also on Sonar X3d. I don't know what the problem is but its not a natural consequence of running Sonar with an FF800

> I wonder if it is because SONAR is the only DAW to start and stop ASIO processing.
 
Nope because other peoples interfaces are working perfectly fine.. Seems to be yet another RME issue... call me Sherlock but a pattern seems to be forming here. But maintaining an open mind right now (trying really really hard!)
 
> The RME drivers are up to date (new version posted just last week).

How about uninstalling the drivers, rebooting and reinstalling the drivers.
Also if you roll back to the previous driver will the problem persist?
Also try Preferences -> Project -> Record -> Allow Arm Changes During Playback/Record = Untick.
Also please make sure Windows update is up to date (run it several times).
And is your power management on "High performance"?
What is your windows firewire driver? (and chipset).
 
RME users please post your driver versions whether it's working or not so we can compare!
 
 
Thanks...