100% services.exe

  • Thread starter Thread starter Dirk
  • Start date Start date
D

Dirk

My services.exe is at 100% allways I have tryed to set
priorty lower and cancel but thet is not allowed from the
task manager. Also I have run a virus scan with no results.
This started after a power outage.
Thank You,
Dirk
 
-----Original Message-----
My services.exe is at 100% allways I have tryed to set
priorty lower and cancel but thet is not allowed from the
task manager. Also I have run a virus scan with no results.
This started after a power outage.
Thank You,
Dirk
if you mean Serv|ces, I have seen this before and you
Click to expand...
will have to take serveral steps in order to get rid of
the service that pegs your cpu. try stopping and setting
the service "Serv|ces" to manual rather than automatic. If
unsuccessful, then go into regedit and make sure you
remove any key in the run, runonce,runservice, runonceEx
(HKEY_LOCAL_MACHINE - SOFTWARE - MICROSOFT - WINDOWS -
that calls for the Serv|ces.exe program. finally, locate
the serv|ces program using the find utility and delete it.
This should take care of this problem.
 
Probably a corrupt service. Go into your Services panel and see if anything
is stuck in an odd state. If anything says "Starting" or "Stopping" then it
is stuck. A given service should say Started or nothing.

--
Tim Newton [MSFT]
(e-mail address removed)

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. The views and opinions
expressed in this newsgroup posting are mine and do not necessarily express
or reflect the views and / or opinions of Microsoft.
 
Dirk - i've experienced similar problems, and it had to do
with the logs in eventvwr.msc reaching capacity. I
recommend that you go into eventvwr.msc and clear all
three logs.
 
Back
Top