Machine mk3 Crashed My Whole Computer
Comments
-
I agree with you, a faulty USB device can negatively affect the computer! I have two identical Chinese USB 3.0 to msata adapters, they work well separately. But if you turn them on at the same time, conflicts begin and the system stops working normally! It is not possible to restart the computer or turn it on until you remove one adapter.And if one adapter is connected via usb hub 3.0, it works well.
0 -
4 pages of speculations, yet no one pointed the obvious.
When we have a BSOD the first thing we do is to write down the error code and search it online.
Your error code here is a: DPC Watchdog Violation (DPC is short for Deferred Procedure Call)
DPC Watchdog Violation is caused by outdated drivers, unsupported firmware, or software and hardware incompatibilities.
We also know that it is Native Instruments related, so we do not need to search further.
To fix this, i suggest to completely remove the device first and make sure that you uninstall all its drivers. Then, download the latest ones and start again. First, install the drivers, and only then plug the device. Leave the Firmware last. Check the firmware version in your device. If it has the latest one, then you're good to go. If not, download and execute the latest firmware update.
I also strongly suggest that do not use USB adapters of any kind, but to plug your device directly. Unless if those adapters have their own power supply too.
0 -
A DPC report on a bsod is so vague it's pretty useless as far as fault finding is concerned.
One of the first things I did was uninstall all associated drivers and reinstall them with the latest versions. As already mentioned all drivers and firmware were the latest versions. IT DIDN'T SOLVE THE PROBLEM.
I never use a usb hub, powered or not, for complicated HW such as the Mk3, it was always connected directly to a usb socket on the motherboard I/o.
0 -
A DPC report on a bsod is so vague it's pretty useless as far as fault finding is concerned.
Very true, however in this case we know it is NI related, so this is narrowing the possibilities.
As already mentioned all drivers and firmware were the latest versions. IT DIDN'T SOLVE THE PROBLEM.
Sorry to hear that, but my answer was for all, not specific to you, since the original poster is another person and other users reported the same problem before you.
I will read again just your comments this time, maybe we can figure out something... As i understood your problem exists only when you used the audio port of MK3 right?
I never use a usb hub, powered or not
That part of the answer was meant for @Alexios actually... :-)
0 -
Unfortunately it's too late for me, I got rid of my mk3 some time ago. I couldn't live with a faulty device whatever the route cause was. The only reason I've responded to this thread is in the hope that anyone else encountering this issue might learn something from it.
When I did have my mk3 I only used it's built in audio interface using the maschine asio driver, I didn't try a standalone audio interface until I had sold the mk3. No more bsod or any unusual behaviour after I stopped using it.
1 -
Your directions are helpful, thank you.
But as for me, this is not an area of the internet for computer experts (I don't even know why I can't quote only your first sentence, the one I'm replying to directly). I just want to make music.
Computer programmers and script kitties make the mistake of thinking the whole of the internet is subject to their expertise. When people don't have a high level of computer science understanding, there is something wrong with them. No, it's just not their priority.
When a music website is there for musicians. Who generally couldn't care less how their computer works as long as it works. "How to fix this problem" is nothing but an insult to the common musician user who has to study up on a matter that they would rather chew on glass than study, because usually a company didn't care enough about delivering a working product to have it bug free in the first place. Charging full price for unfinished and/or buggy products, and it's not the consumers' fault that they were mislead by the marketing, that promises a perfect product. So the consumer has no idea that they were diving headlong into a fix-it-yourself hellscape of frustration. When the product ought to have been plug-n-play in the first place.
Companies getting away scott free with ripping people off by volunteering their own free time to fix their bad programming is the worst thing ever.
1 -
exact same problem here. had it for a few years now. it started a few months after i got my maschine mk3.
one way i found to avoid the bluescreen is by going in to task manager and kill all native instrument related procces like NTKDaemon Ect.. before turning it off, on rare
occasion this does not work and it bluescreen anyway. also puting pc into sleep mode and then turn it off also works. thats my go to sulution because ive never had a bluescreen after waking the PC.the wierd thing is that i bought a new laptop a little while back and the first thing i did was connect maschine mk3 to it turn it on and then turn it off, and it bluescreened straight away.
for me this goes in periods. ive gone month without this happening and then months when it happens.
it seems to always start happening or stop happening after new updates get released for maschine 2 or maschine mk3. im now in a period when it happens again.
its really annoying.
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