Machine mk3 Crashed My Whole Computer

SuperTRev · 2024-01-09T20:57:07+00:00

There was an error rendering this rich post.

I switched off the Mk3 and suddenly my entire computer crashed. In thirty years of using computers I've never seen a device crash a computer like this before. Was running it with the Machine 2 stand alone. Windows 10 PC. Was running the FLS ASIO sound driver, and my external Onyx 8 driver on windows.

Was able to snip a pic of it right before it rebooted:

Find more posts tagged with

Comments

D-One

Does it happen consistently, often, rarely, only once?

SuperTRev

It only happened once. But is a bad enough event for me to report it.

It needs to not be threatening the health of my entire computer; that's crossing the line.

D-One

Considering BSOD's in Windows can happen due to a million things I'd look for a crash log or something you can send support to have it investigated otherwise they can't fix what they don't know.

It can't just be the Mk3 fault or everyone would be reporting this, could be a conflict due to driver conflicts, specific to your PC hw, faulty USB port, cable.... impossible to tell without a lot of debugging.

PK The DJ

Yeah, 30 years of computer experience should be enough to know that BSOD are caused by serious system errors.

SuperTRev

https://community.native-instruments.com/discussion/comment/124646#Comment_124646

Thanks for that. I had no idea there was a serious system error while my computer was crashing.

SuperTRev

https://community.native-instruments.com/discussion/comment/124641#Comment_124641

It can just be the Mk3's fault when in thirty years no other device has ever crashed a computer of mine when switching them off. That is the isolated variable that drove me to make a post about it.

Unless it happens again I won't spend time on troubleshooting it.

D-One

https://community.native-instruments.com/discussion/comment/124793#Comment_124793

Yes it could be, like a said a driver conflict from caused by the MK3 with something else, or not... If you dont want to spend time providing more details or troublehsoot then the thread is kind of pointless.

Either way for me it's fine, at the end of the day it's your problem, so your call.

SuperTRev

https://community.native-instruments.com/discussion/comment/125032#Comment_125032

It's not pointless. It's a bug report. If other people start having this issue then the first mention of it was pointless?

It's also a public record that their product affected my property. With a timestamp on the record. So in the future if this has caused an undetected fault that later destroys my expensive computer, at least I have proof of the genesis of it.

But what is pointless is trying to troubleshoot it unless it happens again, or something like it happens. I don't have proof that my computer didn't already correct the issue by itself. If I can't reproduce the issue, then pursuing a fix is likely a waste of time.

D-One

Like i said it's up to you if you want to investigate this further or not.

It's not pointless. It's a bug report. If other people start having this issue then the first mention of it was pointless?

Sorry, I am not trying to argue... I'm trying to help, keep in mind I am the only one commenting here.

A bug report needs to be reproducible, if the team has no ideia what caused it, they cant fix it, since you have no interest in proving logs, testing anything or give any sort of info this thread will get buried after a while... That's what i meant by "pointless".

So far theres no other people, just you.

I see, fair enough... that makes sense.

Just keep in mind you might have to prove it was the MK3's fault and not something else if compensation is the goal. Anyway, I feel like I annoyed you, if I did I apologize and will just exit the conversation. Good luck.

Kubrak

If USB device crashes system, it is problem in system, not in the device... In most cases. Or HW problem of computer, RAM, disc, motherboard, ... IMHO, system crashes the most because of HW or SW problem in connection to GPU.

I do not think Maschine has drivers that go so lowlevel that it could make BSOD, if everything else is working OK.

Anyway, Maschine has not crasched any of my four, five Win computers (Win7 and Win10) even once in past seven years. And I have had several Maschines (Mikro, Studio, Jam, MK2, Mk3)....

Bbdrmz

https://community.native-instruments.com/discussion/21267/machine-mk3-crashed-my-whole-computer

This has happened to me approximately 4-5 times in the past week and a half. I'm new to maschine and thought I'd done something at first. It's bsod at least 3 times. The hardware unit shuts down every other hour maybe half hour. It's a used machine. I thought I got juked. Reason I am here is checking for a solution. Perhaps because I didn't register? Doubtful, you tell me.

John Curry

https://community.native-instruments.com/discussion/21267/machine-mk3-crashed-my-whole-computer

I have had this same exact issue as a windows 10 and 11 user on two different brand name computers. When turning off the MK3 device VERY RARELY will it blue screen the computer, and cause a major reboot. On one of my computers it actually bricked the device making it completely unusable. I wish I could have gotten proof to seek out compensation from NI. This bug is definitely in the audio driver for the MK3 for windows users. As I said it happens very rarely, but it does happen, and HAS happened to a few users on these forums. I have seen 3-4 posts on this matter but nothing becomes of it. Hard to reproduce, otherwise next time it does happen I will get proof, and crash logs to send to NI. I highly doubt NI will do anything about it because it is not highly reproducible, and it doesn’t happen to every windows users only a handful of people.

6xes

The BSOD's are a random anomaly that can occur in the rarest of circumstances....

expect them to occur randomly without rhyme or reason, the fact it hasn't occurred in 30 years... is a good thing!! you've been fortunate!

I'd get the BSOD's occur probably about 10 times a year, sometimes it could be a software issue... sometimes a hardware one... I've resigned to the fact that it occurs

if you are smart you will learn to make clones of your system drive... becos experience has told me... BSOD's eventually wreck system files... something you learn to deal with by anticipating such things and having a cloned system c: drive

been down this road long enough to know, having a cloned system drive saves headaches!!

converted Mac user now, but still have a all-in-one PC for compatibility reasons

SuperTRev

I've read all the comments here and voted up to tag as read. But since I have no idea what to do about it and is a one-time issue for me, I have nothing helpful to add.

LostInFoundation

Just for the records…it’s not a singular isolated case.

Other users are already reporting it here and have reported it in the past.

https://community.native-instruments.com/discussion/8695/turning-off-maschine-mk3-causes-windows-10-to-blue-screen

https://community.native-instruments.com/discussion/12609/komplete-audio-6-mk1-bsod-on-windows-11

https://community.native-instruments.com/discussion/15225/blue-screen-created-when-maschine-is-shut-down-with-mk3-in-usb

https://community.native-instruments.com/discussion/comment/58648#Comment_58648

https://community.native-instruments.com/discussion/16682/gr7-0-1-repeatedly-causing-bsods

https://community.native-instruments.com/discussion/18575/bsod-using-komplete-1

https://community.native-instruments.com/discussion/19973/access-violation-issues-for-all-installs-after-bsod-while-installing-maschine-2

…and I stop here because the links would be too much…

We cannot know if those issues are created only by NI products…but I will take my case as an example, even if other users are saying the same: I can make music on my studio computer for days in a row if I’m using Studio One, Ableton, Cubase, Bitwig,… or any plugin from any brand. The only times I had BSODs were while I was using Maschine. Causality? Maybe…surely this is not a proof…but it is for sure at least a strong clue

Unluckily, presuming that NI had a look at this just because it has been already reported is just a guess.

Therefore…yes…I think reporting it is important. And reporting it every time, since big companies tend to move only when a lot of users get affected. Isolated cases are seen more like “your business/your fault” cases…

Quick links

Unanswered questions