A reset can be done by renaming RB.CONFIG and Realband.INI.
On launch RB will rebuild them.
Looking at my files, seems the last time I had to do that (or did during beta testing) was in 2013, but I'm pretty sure that is one trick.
You can rename them back if needed and be back where you started in worse case scenario.

However, I don't think this is the cause.
I think yu're on the right track and it's either an ASIO conflict with another app, or an issue with the combination of selected options between RB and Windows.

FWIW, for day to day use I use the 1010 MME drivers, changing to ASIO when I need to.
I'll post my everyday RB/1010 driver settings in a minute.
I send RB out 3/4 of the Delta and have that wired to my distribution/headphone amp and monitors.

I don't use the multichannel out for RB .. not sure why, just something I must have learned in the past and never changed it.
Your error report, as you explain it, says; undefined external error code 1
In my experience, if the error comes from inside RB it would give more data and clues (in an obvious popup).
This sounds to me like RB was relying on something (driver?) that, when RB tried to use them, they returned an error message that RB can't interpret beyond 'a basic error code happened'.
As for not hearing anything using MME, that's likely a combination of RB settings and Windows settings.

/I've emailed support before too and had it take a while. Sometimes I've had surprisingly much better luck with Chat.



Attached Files (Click to download or enlarge) (Only available when you are logged in)
RB_1010_MME.jpg (133.63 KB, 213 downloads)
RB 1010 MME driver settings
1010-Windows_34out.jpg (48.7 KB, 211 downloads)
Windows using 3/4 outs
I do not work here, but the benefits are still awesome
Make your sound your own!