Machine mk3 Crashed My Whole Computer

Its really hard to know if any of this is really related to a Machine device or if generally unplugging any USB's on a computer with issues causing the crash, unless the users regularly unplugs tons of other USB's devices and only the Maschine causes the BSOD but even then it could be the Port...

Maybe a USB port has bent pins and unplugging causes a short? maybe the cable? Maybe your BIOS needs update, maybe the chipset? theres a million variables in the windows world.

I'd start there, use a different port, hub, cable and see it it still happens.

Never had that frustration tbh, people can choose to update early and risk it all or be smart wand wait, or even downgrade back... while fixing a BSOD is a full on nightmare. Not to say that Mac's are perfect tho, they got issues aswell, each platform has it's pros and cons but none of my Mac's ever crashed, cant say the same for all the windows PC i owned including my current one.

Anyway, lets not start a Mac VS Windows thing, plz.

This happened to me, 3 years after building a PC where I didn't cheap on a single component, a high end system at the time (in the 'gaming segment' not server/workstation), it simply started to die and have more and more issues over time until a couple of weeks it became so bad I have to move on.

I too had BSOD's when unpluging USB's very rarely but not just with MAS, with anything. I could blame the USB thingy, but i could also blame my GPU, PSU, motherboard, bad drivers, firmwares, its really almost impossible to pinpoint the cause of the death of my current pc system... Switched to Mac Mini, which sucks because of the RAM prices but i dont want to deal with debugging a ton of components ever again.

I guess so but I went 3 years with no issues so it couldn't be incompatibility, I stress test and benchmark everything after building to ensure system stability, I'm no computer science major by any means but decently knowledgable and always have overkill cooling to rule out extra wear due to heat. The PC is still dying prematurely... It could just all be bad luck, or maybe i bumped into the case and that caused it, maybe it was due to overclocking altho I did pick a mobo with decent VRM's, who knows.

But how do you pick what "goes to the trash"? How do you debug? Remove every component for a other one untill you find the problem? Not viable unless you have free access to components. Or do you mean trow a full PC away because it's crashing?

Me neither but then again USB-B was created to stop people from connecting Host devices to a computer and "prevent damage", maybe the damage can only happen to the device connecting, but I am not sure.

Dont get angry with other users... there's no point. IMO if it was the audio driver then all users would have this issue and there should be hundreds of posts about it.

Let's focus on possible solutions, maybe another Audio driver is causing a conflict? Do you use anything hacky like say ASIO4ALL? Next time a crash happens upload the log here, maybe someone can find useful info about it or its culprit.

You're confusing ASIO with ASIO4ALL, the 4ALL part is important....

ASIO4ALL was invented to force non-ASIO interfaces to support it, there's zero reason to use it if your interface driver is already ASIO... It's meant for old, cheap interfaces... Back in the day, built-in motherboard 💩 interfaces, no interface at all, etc... Feel free to google it, top post here explains it pretty well.

Probably? 😆 They're not gonna explain it so bluntly the way I did on their own website or no one would be fooled to still use it today, many people just assume they have to install it, or do it out of an old habit, hence why I asked if that was the case... To help debug the folks having issues, but... it seems no one is interested in debugging the problem.