I can see why VB-Audio VoiceMeeter is under suspicion but looking at the CPU Usage (Sampled) Utilization by CPU graph with Module and Function columns added to the left of the gold bar suggests to me a very strong correlation between the Ripsawx64.sys driver and the very high CPU utilization while processing USBXHCI.sys DPCs on CPU 0. Whatever it's doing is causing those DPCs to often run for a very long time which will cause audio glitches.
I assume the Ripsaw device basically just sends encoded digital video via the USB 3.0 port to the PC. I'm not sure what the transfer rate would be but compared to me copying 3GB of files to a secondary HDD from an external HDD via USB 3.0 the longest DPC duration I'm seeing is .6 milliseconds while on your system, sending what is likely a much smaller amount of data, it's taking as much as 285 milliseconds. I realize they probably aren't 100 percent comparable but that seems way off from what I'd expect.
You wrote that the configuration worked before without problems. Has anything about the system changed significantly since then? For example, have you updated to a newer version of Windows 10 or installed new streaming software/equipment that you weren't using previously - such as VoiceMeeter?
