Strange dropouts with USB-audio on Catalina

[Benedict Lightning]

Hello
In the past few months, I've started to have some trouble with my audio. As the topic's name says, I am using a USB2-powered audio interface, which happens to be the RME Babyface Pro FS. And, frankly, I really should ask about something like this on their forum, but since there are plenty of topics with similar problems and no solutions on the RME forum, I've decided to stop here first. We're talking OSx86 projects here, so...
Now the specs I have, briefly: i7-10700k, gigabyte z490 vision g board, crucial ballistix 32gb ram, RME Babyface Pro FS connected via USB2-cable, OSX 10.15.7 Catalina and OC 0.9.0. 

Before writing this topic I've tried a lot of things to fix this by myself. Things such as:
 

• disabling C-States and Serial Port in BIOS,
• mapping the USB ports via USBMap,
• removing all connected USB devices and switching off my BT keyboard,
• upgrading OC from 0.6.5 to 0.9.0, fixing IRQ via SSDTime,
• messing with DAW's config to optimize it's work,
• updating and reinstalling RME drivers.

Nothing helps. I get random dropouts which can happen once in a 10 minutes or several times within a minute. 
Good thing is that I can point out what happens with coreaudiod when dropout occurs. When that happens, I can see this: coreaudiod log 2.rtf

So it seems like coreaudiod tries to enumerate audio devices. This happens with and without RME audio driver installed and can occur even when nothing plays. Dropouts however only occurs when using USB2 audio-interface. When I play something through it or using it with DAW. I also want to notice that dropouts occurs more often when DAW is opened. When it's completely closed, but Im still using my USB2 interface to listen to music, dropouts happens less frequent. 
I also get an error 0xE00002EE sometimes. 

It's really annoying, and I don't know what to do with that.
It seems like a program-related or OS-related error. I even suspect OC config errors, but I haven't updated anything there drastically since 2021, so that would be surprising.
Please, help me point out the problem and fix it.

P.S. While I assume that it might be a DAW problem, I want to eliminate all other possible reasons that may cause such behavior.

Edited April 6, 2023 by Benedict Lightning

[Slice]

Look

#define kIOReturnIsoTooOld       iokit_common_err(0x2ee) // isochronous I/O request for distant past!

May be a problem in the hardware?

[Benedict Lightning]

On 4/7/2023 at 8:40 PM, Slice said:

Look

#define kIOReturnIsoTooOld       iokit_common_err(0x2ee) // isochronous I/O request for distant past!

May be a problem in the hardware?

Hello, thanks for the answer.

I don't get it. Where should I look it up? Is that what I should check in the console output when a dropout occurs? And what hardware do you mean? CPU? Motherboard? 
Anyway, I made some progress here; it seems like it might be a software problem after all. I've tried to use another DAW, and it seems like there are no such problems there, so maybe REAPER is messing up my audio somehow. Im not 100% sure yet, but that's what Im trying to investigate right now.

UPDATE: Checked if problem will occur in Ardour 6 DAW while doing same things - nope, there's no problem in other software like that. Just REAPER. Still, Im not sure that it's a problem of that particular DAW. I've already tried to downgrade REAPER from actual 6.78 to 6.25, the one that I was using before - the problem still occurs with REAPER but not with Ardour. 
I assume that it's something else causing the trouble since Im still thinking that REAPER 6.25 had no such problems before.

Edited April 9, 2023 by Benedict Lightning