Machine mk3 Crashed My Whole Computer
Comments
-
All I can tell you is since I ditched my maschine MK3 with it's built in audio interface and now use a standalone audio interface I've not had a single blue screen. What does this tell you?
1 -
That the built-in audio interface (for some), and or drivers for some windows users on the MK3 is buggy trash? Or that even IF the issue was discovered to be a bug (for some) with either, and crash logs/proof sent to NI, nothing would get fixed?
Rule no. 1- It’s always the customers problem/fault never NI’s fault
Only if hundreds of people have this issue will NI even begin to look into the matter anyways… so What’s the point of even trying to debug this issue? Happens very rarely, and is not reproducible at all. What is a bunch of forum addicts going to do? Play mental gymnastics, and pat their egos?
Back to rule no. 1
it’s our fault, so deal with it, as this posts get buried amongst hundreds of other issues that go no where, and never get fixed. bUt tHeY cAnT FiX wHaT tHeY dOnT kNoW! Ya…No…NI knows. They just don’t care. They would have to admit a huge fault with the MK3 device, and you know that ain’t happening.
good old NI. Keeping the hamster wheel alive.
Avoid this company like the plague.
-1 -
Do you also unplug your new audio interface as often as you do your MK3? If you do then that does point to the issue possibly being the Mk3. To me this would be a fair comparison, not 100% scientific but as close as we can get... to me this is just basic logic, but some people will view this as me being a forum fanatic, fanboy, etc... to a company I criticise a lot, i mean... a lot. 🤷♂️
Anyway, theres nothing i can do to help so I'll exit the conversation, good luck yall.
0 -
Could be a driver issue with usb or an overload of power
try a different usb port and see if there’s updated drivers or bios update from the motherboard/pc manufacturer.
i once was getting bsods and it was a staple that fell in the keyboard that was shorting out the usb connection. It could even be a bad cable with a bent pin on it causing a short
good luck.
1 -
"Only if hundreds of people have this issue"
But they're not, so what does that tell you? If the Maschine or the driver were to blame, there wouldn't just be one person getting a BSOD...
0 -
I get where your coming from but I have many other usb devices that don't cause bsod when I unplug or turn them off. Out of interest I have just cycled about 10 unplugs/replugs on my audio interface and no bsod.
0 -
I can plug and unplug MK3 100 times and no BSOD. Even no crash of program using it. Clear proof MK3 is OK.....
Of course, my "proof" is not proof of anything, as well as your "proof". Only tests on many computers, many configurations of SW and HW may tell....
If unplugging USB device causes BSOD on your computer, the problem is on 99.9999% in your system. Either SW or HW or combination of the both. And it may be on 0.0001% caused by MK3 HW or its drivers.
1 -
Just because it works perfectly for you doesn't mean it's 100 percent ok for everyone. Anymore than if its not working ok for some others means it's 100 percent faulty. It just means in some situations it is causing a problem. For me it was enough to sell it and find another solution which for me has worked well.
I think it's safe to say there's nothing wrong with my computer as the only issue I've ever had with it was when using the mk3. That's good enough for me.
Time to move on.
0 -
you gotta laugh at the many possible culprits for the BSOD....
heres some others just for good measure...
mini surge of power when substations down the road switched over...
the sudden fluxation of ambient operating temparature caused a malfunction of a single faulty capacitor on the motherboard!!
the USB cable ends doesnt sit correctly in the slots.. causing a miniature short causing the BSOD to come alive!
Windows update did it!!
a solar flare passed over the region disrupting the power-station causing to send a sudden surge for a brief second LOL
and on & on!! yes i know im just being a silly bugger haha!!
0 -
He just cannot accept, that he has faulty/nonstandard computer.... And it happens that MK3 or something around it seems to cause BSOD. I bet that the very same MK3 would not crash 1000 other computers, just this single one....
Simply USB HW like MK3 cannot cause BSOD on healthy computer.
0 -
I can't unbookmark my own post. If I remove email notifications I won't get any from elsewhere either.
Stop talking about this. One bug report posted one time doesn't matter.
0 -
So why is it that when I turned off the mk3 I immediately got the bsod, just coincidence? Why is it that at no other time, with any other hardware attached via usb I ever got a bsod? You NI fan boys are hilarious.
I now have a push 2 plugged into the same usb port and guess what, not 1 bsod.
And let's not even mention the fiasco surrounding the kontrol mk3 keyboards lol.
Not saying I'll never purchase N I hardware again but I wouldn't purchase anything from them at the moment.
0 -
If computer goes to BSOD because of USB device problem is in computer, not the device. Computer may not be forced to BSOD by USB device, it should handle even malicious behaviour. If it is forced to BSOD, the problem lies in computer OS, SW, HW, not USB device.
So in your case. MK3 simply does something that your computer is not able handle even thought it should be able to handle it. Thousands and thousands of other computers do not crash or even force computer to BSOD when using MK3.
MK3 works just fine with four of my computers. Different versions of Win. And you are the first person I know about, who claims MK3 is forcing computer to BSOD.
0 -
There were a few others having the same issue as mine including the original poster to this thread so i'm not alone. Having not had any issues with any other device connected to this pc I'm inclined to think now that perhaps the mk3 I had was faulty. I don't agree with your statement that a usb device plugged into a computer can't ever cause a bsod to occur on an otherwise healthy system, in fact it's complete rubbish. I once had a faulty brand new mouse that would cause a bsod every time it was plugged in and wouldn't even let the pc boot if it was already plugged in. Got a replacement sent and it was fine.
My pc is pretty standard (intel i7 12700k, Asus B660 motherboard, 32 gig ddr4 Corsair RAM, 2x 2tb nvme m.2 pcie x4 hard drives, Radeon 6700xt GPU, Corsair m750w gold PSU). Home built by myself (been building PC's for over 2 decades). All up-to-date bios, drivers, firmware and windows updates. Not over clocked.
I tried moving the USB to another socket, replaced the cable, made some changes in the bios / windows etc. It was difficult to diagnose due to the bsod crashes happening randomly sometimes more than a week apart but nothing I tried rectified it.
Everything worked as it should while using it until occasionally when I switched it off it would immediately cause windows 10 to blue screen.
Sent 2 or 3 tickets to NI about it but they were unable to offer a solution that stopped the problem. In the end I just got frustrated and got rid of it. Much prefer the workflow of Ableton Live with push 2 now that I'm more familiar with it.
I still use a komplete kontrol s61 mk2 as my keyboard which I'm more than happy with and will probably do so until NI end of life it like they recently did with the mk1. I also own komplete 14, not sure if I'll be upgrading that any time soon, but that's another story.
I'm of the opinion that the maschine franchise is rapidly moving towards its finale. No meaningful updates to the maschine software other than a few minor bug and compatibility releases in ages, the last being the addition of clips and how long ago was that? Maschine mk 3 itself is long overdue a successor but nothing from NI to indicate as to when that might happen. Fewer and fewer expansions being released and now the new komplete kontrol mk3 having ditched any association with maschine.
1 -
@Mark Oxley I understand your frustration, but still.... Those things happen, here and there on Win PC. The PC HW is diverse, you have built it yourself, so there may be some kind of subtle HW/SW incompatibility. I know there should not be using standard HW. But the world is not ideal.
I have built several PCs, I even made microcomputer from scratch. Designed PCB (by hand, no computer routing), made PCB, soldered pieces on and so on. I have written drivers, even programmed in pure maschine code, no assembler, just numbers. So, I have some experience with HW and SW. Even very low level.
The root cause of BSOD must be somewhere else than MK3. It may happen that MK3 just hits that weak point of your setup. And if it is ocasional, random and nonreproducible even on your system, no-one can help you.
OK, there are few cases out of many thousands. I have no idea, how many MK3s has been sold...
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 62 NI News
- 785 Tech Talks
- 4.1K Native Access
- 16.6K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 380 Battery 4
- 846 Guitar Rig & FX
- 429 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators