You use an outdated driver. Version 0.9723 from our website fixes those Pause BSODs.

I am running the exact same version of Windows 10 Pro (2004 19041.508) without any issues. This is also on recently built PC and I should mention that I was getting some random BSODs for a while on this machine but they turned out to be caused by Razer DeathAdder v2 Gaming Mouse. After I switched to different mouse I have had no issues whatsoever.
Also, I have ADI-2 PRO FS (not sure if it makes a difference that it's PRO vs DAC version of ADI-2).

I'm also using JRiver for music (just upgraded to version 27 with no issues, and I also had no issues with version 26). I assume you are using RME ASIO driver and have specified that in JRiver audio output options? Anyhow, if you are only getting BSOD's when you have thumb drive plugged in perhaps the issue is not with ADI-2 DAC (may want to check thumb drive drivers?). Of course if you are getting BSOD's randomly even when nothing else is connected that must be frustrating and concerning.

Does the use of the other DAC solve ALL BSOD problems on your system?
The other way round, the BSOD does only appear when the ADI-2 is connected?

After doing a fresh Windows installation, very often people forget to install the hardware/chipset drivers supplied from the hardware manufacturer.

The windows supplied drivers are often outdated, or less performant.

Installing the latest mainboard BIOS, before driver install, can improve things too.

Can you try disabling the input SPDIF device that also gets installed with the RME? In my case, this helped somewhat.

For what it is worth, my RME DAC is also boxed up and unused just because of driver errors that cannot be resolved!!!

Hi MC,

I too have been having a series of OS core dumps since last month - some blue some black screen. I haven't reported them until now because I cannot reproduce them reliably and they did not implicate the madiface ASIO driver as before.
The latter changed this morning, the driver is noted in the slice of the dump below. Coredumps with much detail are hard to come by now, this is the first in 7  that have mentioned a non-kernel module. Too, I have not had any of these crashes occur while I am using Roon, It occurs after I am done listening to music, power everything off. 

I cannot avoid the crashes now regardless of what I do - I started using Jriver last week to avoid Roon, but now I see others are having issues with it. Maybe others can let you know if the stop codes are the same and other details. I did a clean install of the OS again  last week.

When/if I can reproduce it I will let you know.   

========================

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a,
Arg2: 0000000000049f46
Arg3: 0000000000000006
Arg4: 0000000000000002

Debugging Details:

  [....]
    Key  : WER.OS.Branch
    Value: vb_release
    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z
    Key  : WER.OS.Version
    Value 10.0.19041.1

SYMBOL_NAME:  madiface_usb_64+5c9a
MODULE_NAME: madiface_usb_64
IMAGE_NAME:  madiface_usb_64.sys
STACK_COMMAND:  .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET:  5c9a
FAILURE_BUCKET_ID:  0x4E_9a_madiface_usb_64!unknown_function

Yes, I am. You have the October update preview, which does not release until next week. Are you part of windows insider?

I could be a few days off, I know its coming this week or next because I am looking forward to seeing if it helps correct this issue. It started with the advent of v2004, so hopefully they do. [Edit - Msft is late but it should be out in a few dasys ~CNET]

The October 2020 (aka 2nd half 2020) release is live today. I logged into my Roon Core (Server) and it was ready to dl it. So now I have

• Edition    Windows 10 Pro
  Version    20H2
  Installed on    10/2/2020
  OS build    19042.572
  Experience    Windows Feature Experience Pack 120.2212.31.0

Note the release build number, 19042.572, is different from the preview build number you listed, 19041.572. So you should be able to upgrade soon - It was not available on any of my other computers, but is available for dl from the  primary MS windows media dl site at: https://www.microsoft.com/en-us/softwar … /windows10

I do agree with @bejoro that one should not generally upgrade to any release other than prod releases from MS, when they are offered, and only through the official update site.   

For example, when trying previews to fix the ADI-2 DAC/Roon BSOD issue, the previews were even more unstable. When I  exited the preview program on that machine, I gave MS feedback about the issues encountered and what I was trying to accomplish, hence that may be part of the reason (if MS pays attention) why I was able to get the upgrade on only one of my computers today.

Anyway - a protracted answer to provide details about something that may help others or make their situation worse depending on their outcomes.

One more thought, it seems that the machines in both threads reporting this issue and that identified their systems are using Intel based ASUS ROG MBs of different sorts. Collecting the config info may help resolve the issue.

Thanks for the post, I checked the issues and I do not have any of the devices present in my system.  All is going well since the upgrade. I need to start testing to stress my system.

Update: The day after the Windows 20H2 install I had another crash, no BSOD and only a partial dump listing kernel issues. My ADI-2 was still on but had not been used for about an hour, apparently stressful to Windows/Roon.