LabVIEW
NIMAX in background has high CPU usage
Greetings,
On a fresh installation of Windows XP, service pack 2, and on a laptop less than a year old, I just installed LabVIEW with the very late DAQmx 7.5.0f1. The computer was behaving rather sluggishly shortly thereafter, and NIMAX.exe is apparently hogging the CPU on boot, as evident in task manager. If I open up the Windows services (services.msc) and set the nidevldu service to manual instead of automatic, NIMAX.exe no longer starts up, and the computer behaves normally. This, unfortunately, causes LabVIEW to not start properly, but it points to the source of the problem. The nidevldu service is nipalsm.exe, which in turn seems to launch NIMAX.exe. On a working installation on a different computer, I notice that NIMAX does not run in the background.
Please note -- if I launch MAX myself, it does not affect the issue. The problem is caused by MAX as it runs in the background, started by a service.
I have uninstalled and reinstalled DAQmx, LabVIEW, and device drivers two or three times, with no change to what is occurring.
How can this issue be resolved?
Thanks very much in advance,
Jim
On a fresh installation of Windows XP, service pack 2, and on a laptop less than a year old, I just installed LabVIEW with the very late DAQmx 7.5.0f1. The computer was behaving rather sluggishly shortly thereafter, and NIMAX.exe is apparently hogging the CPU on boot, as evident in task manager. If I open up the Windows services (services.msc) and set the nidevldu service to manual instead of automatic, NIMAX.exe no longer starts up, and the computer behaves normally. This, unfortunately, causes LabVIEW to not start properly, but it points to the source of the problem. The nidevldu service is nipalsm.exe, which in turn seems to launch NIMAX.exe. On a working installation on a different computer, I notice that NIMAX does not run in the background.
Please note -- if I launch MAX myself, it does not affect the issue. The problem is caused by MAX as it runs in the background, started by a service.
I have uninstalled and reinstalled DAQmx, LabVIEW, and device drivers two or three times, with no change to what is occurring.
How can this issue be resolved?
Thanks very much in advance,
Jim
Message Edited by CT_JIM on 10-12-2005 03:10 PM
Hello Sean, and thank you for your input.
Yes, I have reinstalled MAX with each reinstallation of LabVIEW and DAQ. I have had the exact same installation on several XP SP2 machines, and as you said, I haven't seen this behavior before, either.
Oddly enough, after some trial and error that I'll explain, the problem disappeared mysteriously, and NIMAX.exe is no longer present as a process in the background.
I'm not sure what happened here -- for anyone else who encounters this, here's what I tried just before achieving "success:" I performed a system restore back to an earlier point and tried another reinstallation. With no apparent success, I rolled back to the original restore point (supposedly the same state the machine was in before I tried a system restore). After reverting back to before the system restore, both LabVIEW and MAX appeared to have corrupt installations, as evident by dialogs complaining of missing resources. With little choice, I reinstalled LabVIEW, MAX, and DAQ, and the problem was magically gone. I've never seen this situation before, but that's what happened, for what it's worth.
Thanks again, Sean.
Yes, I have reinstalled MAX with each reinstallation of LabVIEW and DAQ. I have had the exact same installation on several XP SP2 machines, and as you said, I haven't seen this behavior before, either.
Oddly enough, after some trial and error that I'll explain, the problem disappeared mysteriously, and NIMAX.exe is no longer present as a process in the background.
I'm not sure what happened here -- for anyone else who encounters this, here's what I tried just before achieving "success:" I performed a system restore back to an earlier point and tried another reinstallation. With no apparent success, I rolled back to the original restore point (supposedly the same state the machine was in before I tried a system restore). After reverting back to before the system restore, both LabVIEW and MAX appeared to have corrupt installations, as evident by dialogs complaining of missing resources. With little choice, I reinstalled LabVIEW, MAX, and DAQ, and the problem was magically gone. I've never seen this situation before, but that's what happened, for what it's worth.
Thanks again, Sean.
