services.exe has high cpu
I had to get this out there. If your windows server is running piss poor, the "Event Log" stays in a starting state, and "services.exe" is running high; you have a corrupt event viewer file. I spend nearly 30 hours trying to fix this problem one weekend. Just recently I came upon it the other day, and fixed it within minutes. It's easy to fix.
Try this...
Or Just boot to a command prompt from the windows CD and rename or move the corrupt *.evt file from the following location:
%SystemRoot%\System32\Config
Its that simple! Just think of this first....
-do you care if you lose all your event log files?
-are you sure you don't have a virus?
-Are all services starting up?
Think about buying me a shot! Maybe even two :)
Try this...
1. Click the Start button, point to Settings, click Control Panel, and then double-click Services.
2. Select the EventLog service and click Startup. Change the Startup Type to Disabled, and then click OK. If you are unable to log on to the computer but can access the registry remotely, you can change the Startup value in the following registry key to 0x4:
HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Services\Eventlog
3. Restart Windows.
NOTE: When the system starts up, several services may fail; a message informing the user to use Event Viewer to review errors may appear.
4. Rename or move the corrupt *.evt file from the following location:
%SystemRoot%\System32\Config
5. In Control Panel Services tool, re-enable the EventLog service by setting it back to the default of Automatic startup, or change the registry Startup value back to 0x2.
Or Just boot to a command prompt from the windows CD and rename or move the corrupt *.evt file from the following location:
%SystemRoot%\System32\Config
Its that simple! Just think of this first....
-do you care if you lose all your event log files?
-are you sure you don't have a virus?
-Are all services starting up?
Think about buying me a shot! Maybe even two :)





3 Comments:
Thanks for this. You saved me a lot of time and wasted effort. My PC was running with CPU at 99% for services.exe. It was indeed a corrupted event log file.
Thank you sir.
Thanks for this!!! I just restored a very important server using your advice. THANKS!!!
Dude, you are a genius! Spent all day with this issue 99% cpu. Googled and fiund yur post and sorted in minutes. Thanks
Post a Comment
Links to this post:
Create a Link
<< Home