My NIHardware service keeps on stopping even after resetting it to Automatic start

RonaldK · 2024-11-16T13:04:07+00:00

There was an error rendering this rich post.

My NIHardware service keeps on stopping even after resetting it to Automatic startand rebooting causing my Maaschine 1 and Maschine 2 hardware to stop working with Maschine software. Ik have already set the Windows PC power management settings "seletive USB interruption" and "PCI Express Lik state power management" to OFF, but it still happens.

Does anyone know how to fix this because this makes using Maschine hardware devices hard.

Thanks in advance!

Ronald Kerstens

Find more posts tagged with

Maschine Jam

Maschine MK1

Accepted answers

D-One

It's not supposed to ever stop, so it's probably crashing… Contact tech support.

All comments

D-One

It's not supposed to ever stop, so it's probably crashing… Contact tech support.

CiscoRey

Has anyone found a definitive answer to this problem?

I'm having a similar issue in which upon startup my NI services (NIHardwareService and NIHostIntegrationAgent) are disabled. I have to manually change the startup type on these services anytime I want to use my Maschine MK3 with the software. Even then, the services will end up becoming disabled again only minutes after explicitly enabling them. This has been happening for a long time now.

In another forum I read that it often has to do with antivirus and cleaning utilities (i.e.: CCleaner) that will disable the startup of these services in the background. At one point I believe that was the case with mine; as when I took the steps to disable CCleaner tasks and add NI processes to my firewall's exceptions list it seemed to have fixed the problem.

Fast-forward a few months and the problem has made its return. This time none of the steps I took before are resolving the issue. It really doesn't seem to be a matter of things crashing—at least that's what I'm gathering from everything I've read. Something is stopping the processes and changing their startup type to "Disabled". The hardware itself is still running; just not communicating with any software.

Any thoughts on how I can go about identifying what might be causing the processes to change?

Isom

I am having a similar issue, but the hardware freezes, with me still being able to control the software.

Quick links

Unanswered questions