Winlogon.exe consumes lot of CPU

[vgvgf]

Recently I have noticed that the procces Winlogon.exe(I have Win XP SP3) was consuming lot of CPU, like 20-50% without any reason. The problems appears each time I start the computer and never stops. Also with Proccess Explorerm I have seen that the thread causing all of this was: "kernel32.dll!CreateThread+0x22", which appeared in Winlogon.exe and Services.exe(Which is a sub thread of Winlogon.exe). I have scanned my computer for viruses and all with nod and with spybot and I got no result.
Maybe I have this problem, because time ago I disable SFC(Windows File Protection) editing the registry, because after installing SP3 I was getting all the time pop-ups saying that I had to insert the Windows CD(Which I no have) for checking the dll cache.
I have searched around the web about this, and some people seem to have the same problem, but I haven't found anything useful for my computer. Can someone help me?

 

[skirtboy]

How was XP installed on your machine? Is it a standard XP install updated to SP3 or a nLite install with SP3 slipstreamed into the installation?

 

[Tohsaka]

Are you using a custom uxtheme.dll?

 

[vgvgf]

How was XP installed on your machine? Is it a standard XP install updated to SP3 or a nLite install with SP3 slipstreamed into the installation?

I have had the same computer with Windows XP SP2(installed from a CD) for over a year, and worked well. Like one-two month ago I installed SP3 from "Windows XP Service Pack 3 Network Installation Package for IT Professionals and Developers", and the only problem I found, was the SFC popup from Winlogon.exe. Like 2 weeks ago I disable SFC, and the popup stop appearing and all seemed to work fine, but some days ago Winlogon started consuming lot of the CPU, and also 20-30mb of RAM, insteand the 2-3mb which normaly consumed.

Are you using a custom uxtheme.dll?

No, I have the default ugly theme.

 

[___]

Usually winlogin trouble is due to your windows copy not being properly authenticated. If you have a legitimate copy of windows and you're only using your key on one PC, I would suggest contacting Microsoft tech support to see if your authentication has been revoked. If you're using a pirated copy, well, I can't give you direct instructions but I would suggest getting a 'better' copy.

 

[skirtboy]

It sounds like excess garbage data in the computer to me. Often, installing a service pack on an old installation causes more trouble than it's worth. If you reinstall clean first, it will work better.

 

[___]

One way to go is to grab a copy of your Win version of choice with the latest stuff slipstreamed and doing a clean reinstall when new service packs come out.  This is of course illegal to download, but fuck 'em, if you put your own key into the config file before burning it and running it and then go through the authentication process I don't see why they have the right to complain. I have built several of these during my time as a technician to speed up the installation process for new systems, which /is/ legal to do, but you can save a lot of time grabbing someone else's prebuilt package.

 

[vgvgf]

Well, I have rehabilited SFC, and now Winlogon stopped consuming all CPU, but now I have the ugly pop up again, it seems I will need to get a "ilegal" Windows XP CD. Thanks for all the help.

 

[___]

Before you resort to piracy, try calling Microsoft, it really is a painless process if you have a legitimate copy and having a validated version of windows can be occasionally helpful vs. a cracked version. Either way though good luck, and if you do go pirated keep an eye out for the "Performance Edition" - really fast download & install, I use it to do quick reinstalls and then change the key fairly often.