I believe you are onto something, in that Windows 10, Chrome, has something to do with it.
I have four computers - 3 laptops and a desktop. Three of them have Windows 10, on Windows 7. All four have the same audio apps, and are setup for the same external hardware (USB2 and USB3).
The desktop uses a ZOOM UAC-8. It's my main audio DAW. One older laptop has only 4G of memory, runs Win7, another had 8G, came with Win8.1 and upgraded to Win10, and has been a major disappointment since day one. It's been relegated to internet use only...put out to pasture. I still use the Win7 machine for GuitarPort only - it too slow for current Chrome - too little RAM.
Chrome is my browser of choice on all four. One thing Chrome does is suck up memory, specifically when Facebook is up. One session of Facebook will use as much a 2G of memory for that one process after a time...as if it's leaking. Even though there are 5 tabs open as my default web pages only Facebook does this, so I blame it for many Chrome issues. That said, Chrome itself seems to be one issue why Facebook uses so much. Other browsers use a lot when logged into facebook in them, but not as much as when in Chrome and they don't seem to go up. Facebook is alway loading data so we can scroll down to it. Regardless, Chrome uses 2-4G of RAM for the whole session, typically, all pages. Even 4G usage isn't that bad in the big scheme of things if the machine has enough physical RAM in the first place. It does seems typical usage for Chrome with my tabs.
My machines are 16G (newer main laptop - came with Windows 10), 12G DAW desktop (is upgrade to Win10 from Win7). 8G (newer crappy laptop - came with Win8.1, upgraded to Win10), 4G (older laptop, came with Vista, upgraded to Win7, upgraded to Win10, wiped clean, restored to Vista and upgraded to Win7...added regkeys to prevent the automatic unwanted upgrade to Win10 which is how it happened in the first place....UGH). (I have these regkeys for DL if anyone wants them.)
I've had all these machines for over a year, and three of them over 3 years each. While Chrome uses a lot of RAM, only the newer main laptop is having blue screen issues. The one difference? It's the only one the UX2 is installed on. The blue screen started after installing the UX2.
I suspect two things, neither of which we can do anything about easily. 1) It's memory fragmentation. Even though there's plenty of physical RAM, if it's fragmented and someone needs big chunks, as the UX2 might need via the ASIO drivers then all bets are off. Someone is running out of contiguous memory and not handling it well. And 2) There is memory corruption in the ASIO driver. Past experience (my day job for almost 20 years) has shown many times this to be an issue with drivers that try to be super low latency while not being high CPU users. Some of the first ASIO drivers to come out years ago were great but very unstable. (Rule of thumb was to cold reboot before a session, then cold reboot when done.) Yes, it's possible and likely both of these issues are the "cause" in that they set up the scenario someone isn't handling well.
There are other gotchas that are relevant. Insertion and removal of the USB Audio Device, the UX2, forcing Windows tries to flip around what it's current audio device is. I'm keeping a eye on "exactly" what the situation is then a blue screen happens. Have I removed the UX2? (usually) Is the audio app still open? (no). None of the audio apps will automatically switch to the default audio device, by design. Other apps, and Windows itself will, and sometimes it's flaky, as when using bluetooth. The blue screens are unrelated to bluetooth. Don't use bluetooth device very often.
I've found that rebooting, working with the UX2, and rebooting, is making this situation better.
Sorry for the book. Hope it helps us all get thinking. (especially the devs....grin)