queue CPU usage 100%

[km76107]

Dear Matt,

I have tried that as well.  I tried "HijackThis" and "Killbox" to get rid of the Winlogon.exe.  Both of them failed to detect the Winlogon.exe.  I followed the steps from a google hit. Before starting up LabVIEW, the winlogon.exe is about 2%.  After I run my program in LabView, the winlogon increases to about 50%.  So I am sure that LV is affecting the winlogon process.  But why? Any suggestions/alternatives?

Thanks.

Regards,

KM

[Eric A.]

Hi KM,
The only thing LabVIEW might do to affect winlogon is access the database.  It is hard to tell what the problem might be without the entire program to recreate it.  Are there any loops that don't have delays in any of your sub VI's?  Does the cpu usage remain high even after the program has stopped running?  It might help to more specifically isolate where the problem starts.

[ww.brown]

I have noticed a winlogon/LabVIEW conflict for over 2 years.  We are currently using LabVIEW 8.2.1 and occasionally get into a situation where a running LabVIEW program seems to cause Winlogon.exe to consume 50% or more of our CPU.  The over-consumption stops once we stop the LabVIEW program.  We do some DAQ, control a target using the Ethernet, write some files, but nothing particularly unusual.  We have also noticed this phenomenon when we run a LabVIEW program uninterrupted for many days.  The workaround has been to stop, reboot and restart the program.

Has anyone else seen this kind of problem?

[Eric A.]

Hi wwwbrown,
You said that stopping the LabVIEW program solves the problem but then you say that the solution is to stop everything and reboot the computer.  If you have to reboot the computer there might be something else causing the problem.  As was stated earlier on this thread, viruses can sometimes cause this behavior.  It sound like this might be the cause if stopping the LabVIEW program has no effect.  Other customers have said they have been able to isolate the problem to LabVIEW but I have been unable to reproduce the issue here.