Just EDITed, pls re-read, thanks.

Cristi, I'm sorry to hear that, this is absolutely untypical for a RME based setup. In particular regarding the UFX+: it's a fantastic device. I own it as well and never had any problem, even under extreme application/DAW load situations for testing, as I described here: https://www.tonstudio-forum.de/blog/ind … cks-de-en/.

Now we have to find out by clever exclusion in which area the problems are, more on the computer or device side or a simple cabling problem. The user forum (also RME support) can support this process only in the best possible way, if you deliver more concrete information about your setup. Unfortunately you gave no details about the setup to get concrete starting points for troubleshooting. Windows or Apple ? Not even whether the device is connected via USB or Thunderbolt and which specific RME driver/firmware versions are in use.
Please note: its neither sufficient nor helpful to simply state to use "latest drivers and firmware". You can quickly make a mistake and then this can change as soon as new versions become available. Its also required e.g. to be able to compare with other known setups or to keep track of, what combination of hw/driver/firmware cause issues.

It would be interesting to know the following about the setup: OS, OS version (for Win10 exactly which Win10 version), whether pre-installation from the factory or new installation, CPU, memory. For laptops the name, for desktops also the mainboard and chipset.

Further OS/driver specific questions make no sense as we do not know whether you use Apple or Windows.

Proposal for some easy checks upfront:

• Did you try another USB or Thunderbolt cable ?

• Is the cable length within the specs ? Max cable length: USB3: 3m, Thunderbolt: 2m  (USB2: 5m)

• Do you see any USB transport / CRC errors in the RME driver settings window ?
  Note: You need to keep the window open, so that the CRC check continues to run.

• Do you have another computer to check whether the UFX+ runs there more stable to exclude a device problem by this ?

• IF USB: did you try all USB3 ports ? To increase the likeliness to get a port with compatible USB3 chipset behind it. USB ports from Intel/AMD chipset should work, some chipsets are known to have issues (X99 if I remember right)

• IF USB: do you use a port with a compatible chipset ? Please see the manual chapter 40.3
  https://www.rme-audio.de/download/fface_ufxplus_d.pdf
  https://www.rme-audio.de/download/fface_ufxplus_e.pdf
  

• IF USB: does it make a difference if you connect the device to a USB2 port, so that only 60 instead of 188 channels are in use (all but MADI ports) ? It might be required to check/modify the USB settings on the device from "Auto" or "USB3" to "USB2" additionally to ensure that USB2 mode is selected / in use.

One remark because of your comment, that you had no problems with the previous interface(s) on the same computer.
Are you aware of, that the UFX+ is a 188-channel interface and transmits this high number of channels permanently and therefore has higher demands on the computer hardware and valid/solid settings (BIOS, OS) compared to a smaller recording interface with a significantly less channels ? Should USB be applicable in your setup, then please see also manual ch. 40.3 in terms of compatibility requirements for USB3 chipsets on the computer side.
Could you kindly tell, which other recording interface(s) you used before without issues on this computer ?

You also need to investigate on the compute side. Suboptimal / wrong settings, bad drivers, etc. are also possible there. But again, you didn't tell, whether you have Windows or Apple, Desktop or Laptop) therefore no concrete suggestions are possible at this point. Every platform has specific things to look for and also other tools to support the troubleshooting.

EDIT1: maybe check connecting via USB2 1st as MC from RME suggests in post #7 of this thread.
You might have to set UFX+ to USB2 mode if "AUTO" doesn't work, see manual how to perform this.
EDIT2: added to set windows to optimize for background services
EDIT3: resorted order of tests and renumbered: Inspection 1st, then 1st LatencyMon run. Then Changes one by one with brief review whether audio drops still occurr and whether LatencyMon values became better. Maybe you see positive changes, but usually the sum of all changes brings best results finally.

I think, if this would be a driver problem, then you should see more problems like this here on forum, but this is not the case.
Experience shows, that there are other issues more likely, like chipset issues (X99), driver issues, BIOS / Windows related settings.

Proposal, instead posting back and forth 20 times I give you now a list of points that you could check.
Please answer the questions and/or post results.
Many thanks.

1. What other interface did you use before where you didn't have issues ?
2. Can you try the UFX+ on another PC just for testing ?
3. When or how often do these audio drops occur ?
4. is it reproducable, if yes how ?
5. Do audio drops occurr only when working with Cubase with the ASIO driver or also under Windows with the WDM drivers?
6. Is it somehow related to higher CPU / ASIO load ?
7. What sample rates / ASIO buffer sizes do you use ?
8. Do you use CPU hungry VST or VSTi (virtual instruments in your cubase project) ?
9. Are you browing the LAN or Internet when these drops occurr ?
10. Do you have WLAN enabled to access LAN / Internet or via Network Cable
11. Do you see CRC transport errors over USB3 (driver settings dialog)
12. If yes: Did you try another USB cable ? Did you try all other USB ports ?

Before doing changes to the system:

13. What does LatencyMon report on an otherwise not loaded / IDLE system if you let it run for 10 minutes ? The tool simulates a DAW load, therefore do not run any other application. Does it report something like that your system is not well suited for audio ? Please post the report on this forum.

After each of the following changes check individually, whether the situation improved. Repeat audio tests which triggered audio drops  (see also #4) and look whether LatencyMon values become better. A smaller 3 Min run should be sufficient for that.

14. How many WDM devices (for Windows compatibility) do you have enabled in the RME driver, reduce to 1 device only for the speakers.
15. Is energy saving disabled in the BIOS ? I only know Intel BIOS, on AMD BIOS the names could be different. Google for that. Most important to disable C-States, T-States, P-states. Sometimes you need to disable something called speedstep (Intel Calls this EIST, AMD might call it differently). In most cases you can keep TURBO on, as on my system this results in permanently 200MHz higher clock speed.
16. Do you use the High Performance Energy Profile ? If not please do.
17. Is CPU core parking disabled under Windows ? If not please do, you can use Bitsums Parkcontrol for that.
*18. Set Windows to optimize for background services, see also: https://www.tonstudio-forum.de/blog/ind … orderlich/

19. Final LatencyMon run like #13, did something improve ? The sum of each change might bring more than each individual change itself.

Thanks.

Ryzen 1800 is quite outdated and points to older hardware that was known to not work optimally with USB. There was a BIOS update that improves audio, but I am not sure that one is available for this system.

Else Ramses is right. This is about USB bandwidth on isochronous streaming, and there is nothing to improve on our side. Try the USB 2 test, at least.

Thank you for your solutions guys, I will try the Sonnet!

Cool ! Thanks for the feedback.

Yes this was a nice card indeed with the 4x FL1100 controllers on it, supporting USB 3.2 gen1&2.
Not cheap though, around €150 and it needed a PCIe socket offering 4 PCIe 2.0 lanes (because of the bandwidth).

The smaller and not so expensive card for around €55 - which would be fully sufficient - with only 1x FL1100 USB controller on it shared between all 4 ports is still available. And I personally regard it as very practical that it has still the Type A USB connectors. They appear more robust to me.

As the USB controller is shared by 4 ports, I would only connect the recording interface to it to isolate it from the rest of USB peripherals.

https://www.sonnettech.com/product/alle … 4port.html
https://geizhals.de/sonnet-allegro-4-po … 48037.html