Prado
re empirical evidence.
actually you cant necesarily jump to that conclusion.
its not as simplistic with respect.
without understanding when you select and deselect a driver on the fly
how rme and biab and win interract with each other
and internal mesages sent and their execution within the pc.
particularly as to when chosen sound devices/drivers are open and closed.

mebe it is a biab problem...but not necessarily.
difficult to say without seeing biab internal source code
and the source code to the rme product.
and therein lies the rub mate.

ive seen the driver dance in lots of daw software.
you can see it on lots of recording forums.
my "xyz sound device wont work with abc daw software " etc etc.
a zillion threads on such . not just limited to biab.

sometimes the solution is to select the correct drivers , save the selection,
(which some people forget to do...seen that a few times.)
then exit the daw software so sound devices are closed properly.
and then re-open the daw software , and try to record n see if everything is
copacetic. just the other day i had to do this when testing out a new
sound device. set the drivers/save..close down daw...then come back in
to the daw and all was good.
there might also be win quirks we dont know bout ..dunno.
youve prolly also seen on some recording forums where some daw
software dont like recording sampling rates to change once in a project.
once theyve been set.
anyhoo glad you got it sorted.
i would still run the dpc test at your convenience.
its very usefull and will help youwith your pc's..

retired puter engr....powertracks on amd......NICE !
"what is the black art of audio engineering ?"
my silly songs...motagator.com/bmanning
see my tips in the tips section.