Ryzen 5 1600
Gigabyte G-AB350-GAMING (Audio: Realtek chipset)
XFX R9 270X
ADATA 128GB M.2 NVMe SSD
Corsair 100R case, speakers run through my keyboard that is hooked to the rear jacks (passthrough).
Logitech H390 headset hooked to USB 3.0 port in the front of the case.
OK, I've got a weird issue that I'm not sure how to troubleshoot. To start, I've had a problem for the last year or so where my M.2 drive took anywhere from 2-10 minutes to boot Windows, but it'd only happen after the first time I updated the graphics drivers. I recently found the solution to this which involved hopping into the registry and disabling the ULPS (Ultra Low Power Setting) for Radeon. After that, my boot time dropped to between 10 and 20 seconds, and all was right with the world.
Until my kids broke the mic on my headset. I was using a cheap BEEXCELLENT headset that had separate headphone and mic connections, along with USB for power only. Of course I didn't know this until I was grouping up on Destiny2 and no one could hear me. The next day I ran to the local NEX and grabbed a Logitech H390 headset that operates completely through USB.
Now, the headset sounds great and I have no issues with it, but since I installed it the audio from my speakers cuts out randomly, and Windows takes 2-4 minutes to boot again. My computer switches audio from the speakers to the headset when it's plugged in, but while using the headset I still hear the speakers reset occasionally (faint click off, faint click on, but audio isn't affected on the headset). So basically I know the event that caused the problem, but I have no idea what could have changed. I tried uninstalling all the audio drivers and refreshing to see if that would kick it back in line, but it didn't help. I used to have the Gigabyte audio manager installed that would manage when the ports shut down, but I removed it because it was a pain with popping up all the time.
Any thoughts on this would be appreciated, I can't find anything on Google that matches the issue I'm having so it's really hard to even begin troubleshooting it. ULPS is still disabled, so there was no change there for the boot time part of the problem.