My CPU is running at 100% even though it should be idle. The task manager shows that a single process called 'cpumin.exe' is causing this.
Could anyone please explain what I can do to stop this? As whenever I kill the process, it just starts again.
I have noticed kind of relationship between this process and network, because when I unplug the network cable the computer works well.
And there is something else when I give this process the order "Suspend process" and when you open the "Analyze Wait Chain" I found that this process have this message "One or more threads of cpumin.exe are waiting to finish network I/O".
Thanks...
Someone else had a similar problem here ...
What exactly is the 'cpumin.exe' process which runs in the background and takes up 100% of the CPU? It happens whenever I run a Java program
Probably best to do a full virus scan just in case. According to http://www.threatexpert.com/report.aspx?md5=dd6da7e7b46f199edc8e4a81b2ae5e1e, it could be some sort of mass mailer.
try the following:
Click Start > Run > (type "cmd.exe" without quotation) > Enter
a Command line (black screen will appear) type the following:
taskkill /fi "imagename eq cpumun.exe" /f /t
The above command will surely kill the task and all of its child processes and tree.
cpumin.exe appears to be a virus, see:
http://www.threatexpert.com/report.aspx?md5=dd6da7e7b46f199edc8e4a81b2ae5e1e
Related
I am using Scilab to access a software called LTSpice (XVIIx64.exe) and whenever I use wmic/taskkill/powershell.exe "Get-Process XVIIx64 | Stop-Process". or whatever killing commands, it doesn't actually kill the process (it does close the program, but it still is there in the memory as shown in the picture below). Once I repeat the code in scilab another instance of LTSPICe (XVIIx64.exe) is created in memory and with time there are so many of them that scilab shuts down as it cannot allocate more memory :(. How can I actually kill this process? It's also strange that in the error message it is mentioned PID XXXX "child process of PID 18208" could not be terminated, however PID 18208 does not show up in tasklist and only PID XXXX shows up (View the attachment).
Did you already checked if it is any malware or something? Do that.
If you've done it and got nothing, then get a backup and format your pc. I think that's the best option.
I know that when doing some ssh, I can use the nohup command to prevent a program execution from halting when I close the ssh session.
However, I need to run a program that takes some keyboard input at the beginning. When I run it, I am prompted with several questions that I need to manually answer, then the program will actually start doing what it is meant to do and then I would like to close my connection and let it run in the background.
How can I do this? My ideal solution would be some sort of "persistent ssh session" or so, something that would allow me to start a program, give it inputs via keyboard, the program gives me terminal output, then I close the connection, open it again and still see the program running, its output and so on, like if I just opened it without disconnecting and reconnecting.
Is there any way to do such a thing?
Thank you very much.
So I am trying to keep my Node server on a embedded computer running when it is out in the field. This lead me to leveraging inittab's respawn action. Here is the file I added to inittab:
node:5:respawn:node /path/to/node/files &
I know for a fact that when I startup this node application from command line, it does not get to the bottom of the main body and console.log "done" until a good 2-3 seconds after I issue the command.
So I feel like in that 2-3 second window the OS just keeps firing off respawns of the node app. I see in the error logs too in fact that the kernel ends up killing off a bunch of node processes because its running out of memory and stuff... plus I do get the 'node' process respawning too fast will suspend for 5 minutes message too.
I tried wrapping this in a script, dint work. I know I can use crontab but thats every minute... am I doing something wrong? or should I have a different approach all together?
Any and all advice is welcome!
TIA
Surely too late for you, but in case someone else finds such a problem: try removing the & from the command invocation.
What happens is that when the command goes to the background (thanks to the &), the parent (init) sees that it exited, and respawns it. Result: a storm of new instantations of your command.
Worse, you mention embedded, so I guess you are using busybox, whose init won't rate-limit the respawning - as would other implementations. So the respawning will only end when the system is out of memory.
inittab is overkill for this. I found out what I need is a process monitor. I found one that is lightweight and effective; it has some good reports of working great out in the field. http://en.wikipedia.org/wiki/Process_control_daemon
Using this would entail configuring this daemon to start and monitor your Node.js application for you.
That is a solution that works from the OS side.
Another way to do it is as follows. So if you are trying to keep Node.js running like I was, there are several modules written meant to keep other Node.js apps running. To mention a couple there are forever and respawn. I chose to use respawn.
This method entails starting one app written in Node.js that uses the respawn module to start and monitor the actual Node.js app you were interested in keeping running anyway.
Of course the downside of this is that if the Node.js engine (V8) goes down altogether then both your monitoring and monitored process will go down with it :-(. But its better than nothing!
PCD would be the ideal option. It would go down probably only if the OS goes down, and if the OS goes down then hope fully one has a watchdog in place to reboot the device/hardware.
Niko
i have one exe,when this exe is called ,some this is exe is already open in task manager,i want kill all previous exe not current exe,i am using VB.net
As previous commenters have noted, you really should make more of an effort to solve the problem yourself (and demonstrate you've tried already)
Saying that, here are a few hints:
taskkill.exe /F /IM myprocess.exe /FI "PID ne 555"
Process.GetProcessesByName
Process.GetCurrentProcess
Process.Kill
Be very careful killing processes. As Anton Kovalenko noted already, are you really sure you want to do it? It may be better to simply warn of the condition and provide instruction to the user/admin.
Set your program up to receive messaging. When the most current instance launches have it send a message to the previous instance to itself shutdown gracefully - and of course put the code in place to do this.
I'm looking for a way to run a program when locking the screen in Fedora 15 (linux). Basically I want to start running a motion detection program when the screen locks, or I manually hit Ctrl+Alt+L, but I don't know what commands are being run or where to alias my own intermediate step in. I assume it's:
gnome-screensaver-command --lock
but am not sure how to go about this. Anybody know how, or a direction to start looking in?
Edit, since link was in a comment:
This is done with dbus-monitor and described here.
The dbus system advertises screen locking; monitor for ActiveChanged on org.gnome.ScreenSaver. (see http://people.gnome.org/~mccann/gnome-screensaver/docs/gnome-screensaver.html )
e.g. (word-wrapped for clarity)
signal sender=:1.68 -> dest=(null destination)
serial=53 path=/org/gnome/ScreenSaver;
interface=org.gnome.ScreenSaver; member=ActiveChanged
boolean true
Unfortunately, this will require writing more code than just a shell script, I'm afraid; although I'd be curious if you could ask dbus to call your program as a handler for that signal, somehow; otherwise, I suppose you'd just start a daemon process and listen for that signal to be broadcast…