Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
In my system processes it tells me 100% cpu power is being used and 99% of it is in MSTask.exe! I cannot end the process, this problem happened a week ago then it went away for awhile but now its back and I think its a virus. Please there has to be a fix! This thing is annoying and it slows my system to a crawl unexpectedly.
Greets,
Just an Idea... Services originate from the services and Applications. Maybe check and see if there is a service that doesn't look fimillar. Try stopping through services should work. I've never been able to get services to stop though task manager either.
Hope this helps
Brian
0 
I had the same problem last night.I also thought maybe a virus.I installed service pack 2 for win2k.Its working ok for now.I'm in the process of downloading port scanning software just to check any intrusion.
0
Maybe I should just get the service packs and other updates and see if that helps. There seems to be no service for this problem since the problem exists in mstask and that is what is being used when i hit ctrl alt del. So I dunno.
0
I also see this sometimes. Only fix is a reboot. I'm running win2k SP2.
I found reference to a Denial of Service "virus" for mstask on NT4. I wonder if it's the same thing?
Sometimes I've also seen 99% cpu for LexBceS.exe service, which I think may be a print driver for my Lexmark printer?
0
I've been getting the same problem. (mstask.exe causint 100% cpu usage). I've also been getting high cpu usage for my Hewlett Packard printer .exe as well. I have the updates and service packs installed but the problem keeps coming up. Has anyone found a solution?
0
I also have the same problem, with Windows 2000 service pack 2. I installed Service pack 2 just recently, and have had some problems since. When looking into it, I discovered that mstask.exe was using almost all resources. I don't have a solution, but would very much appreciate it if anyone knows how to fix it!!
0
We just had the same problem (Windows NT 4.0 SP 6) after running port scanner against 'localhost'. Looks like mstask.exe listens on a local port and can 'get confused' by conncting to it.
=====
Windows NT 4.0 is vulnerable to a denial of service attack, due to a vulnerability in the Microsoft Task Scheduler (MSTask.exe). An attacker can send random characters to port 1026, where MSTask.exe listens, to consume 100% of the CPU resources and cause the system to freeze. The system must be restarted to regain normal functionality.
0
In my case, restarting the machine does not help. Just after restart, MSTask.exe is using 100% Cpu again.
0
I found a handy little program at http://www.iarsn.com/ that solved the above mentioned problem. (Taskinfo 2001)
0
If running a NT platform, your more vulnerable but can affect other OS platforms as well. Read the note at this sight to explain your problem. http://www.securiteam.com/windowsntfocus/6A00B150LY.html
0
As a previous response stated Iarsn Taskinfo 2000 (http://www.iarsn.com/) Does allow you to kill the offending MSTASK Thread.... Running NETSTAT -AN shows nothing either...
0
I had the same problem. I disabled the "task schuduler" service. This works provided you don't need the service. Now mstask.exe doesn't run.
0
I'm experiencing this as well. Currently mstask.exe hogs half of my cpu time, and my lexmark printer the rest (lexpps.exe) (although neither process should have anything do do). Very annoying!
0
This has happened to several of our W2K workstations. Only aid is re-install or disabling the Task scheduling service. I recommend the latter, as this is rarely used on workstations.
So, from Services, stop Task scheduler, then set it to startup manually.
0
I've installed service pack 2 for win2k. It didn't work for me. PC still freezes up and showing 100% used up on CPU. Someone mentioned that disable the Task Scheduling Service can help to solve the problem.
Can someone please tell me how to disable this Task Scheduling or any other solution to this problem. Thanks.
0
using Administrator tools, go to services, half way down the list you will find a task called task scheduler. Right click, and go to properties. Change the start-up from automatic to manual. Unless you are running server, or specificlly using this task, this should not be an issue for your system. Apply the change and exit.
when you reboot, the problem will not come back. If you can't reboot for what ever reason, then get Pstools from http://www.sysinternals.com
and use pskill and the task number from the task manager window. The problem will terminate.If someone figures out what is causing this, please let us know, and let Microsoft know so they will fix it!
LDS
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
