I'll DM you in the next few days & we switch this discussion over to whatsapp or whatever. In the mean time, you can check, if there's a setting for hot-plugging on your esata card.

I read through that microsoft thread, don't agree that, while likely, mobo or PSU are the only possibilities. Event ID 41 just means that we're recovering from unclean shutdown, like blue screens or power interruptions. I would try and examine BSODs with Bluescreenview, skipping the ones caused by bios changes. I'd try and figure out a way

Okay, so you do have a fairly deep understanding of PC troubleshooting, sound like we're at about the same level. Couldn't deduce that from your previous posts. I'll read through your microsoft post tomorrow, will let you know if I have any ideas. I can offer that we connect via phone or whatsapp or similar and I provide you with a few hours

Sorry you're having such a tough time with such an expensive machine; that is understandably infuriating. I wouldn't worry about the Thunderbolt before testing it. Those cards only working in one specific slot is normal. Thunderbolt is just PCIe + DisplayPort, and routing DP to every PCIe slot wouldn't make much sense. Changed BIOS settings

Yeah, if I were in charge, PCIe whitelisting would be considered a war crime. Also, we wouldn't be handing the people committing actual war crimes the territories they snatched on a silver platter, so I fear there is little hope all around. The following are just guesses: I'd be careful with that SSD RAID—if that Turbo Drive dies, recovery might

Robert, you're replying to an old thread. But yes, Ondrej didn't use the best tactics in replacing one sound blaster card with another. Anube31 merely added a non-working interface. Building a white and a blacklist seems reasonable, maybe we'll see a pattern. I can add the following: Not working: ASUS Xonar DGX Working: RME HDSPe AIO

Thx for the reply! I don't need a case; I'd rather have an open discussion, and if I'm wrong, I'm wrong. *Changing clip gain now takes three keystrokes (e.g., -, 5, Enter) instead of two. This looks like an (understandable) oversight by a programmer. *Having the mute function affect sequences allows for more different states. Mathematically

This might be worth a shot:>br> If the folder "C:/User/(Me)/Documents/Downloaded installations" doesn't exist on your system, create it manually. Open that folder's properties, go to the security tab & hit edit. Add the user "Everyone" and grant full control.

Two old issues I'd be thrilled for Avid to address: * Typing a new value for clip gain in the audio mixer requires hitting enter. * The audio mute command is global, used to be on a per sequence basis, which was more flexible. Both these issues are present since after 2018.12

I have no idea and I never tried your hardware. What happens, when you disable the BMD hardware? Can you route audio trough the BMD hardware for testing?