I think thats one too many.
Since you have window xp home you don't have the tasklist.exe command like
we do in professional. Seems crazy not to have included it for
troubleshooting problems.
However you can download it here.
http://www.computerhope.com/download/winxp.htm
I just downloaded it and ran a file compare with the one on my xp
professional sp1 system and its identical.
Put it in your \windows\system32 directory.
Now go into taskmanager/process tab
Click on the cpu column heading to sort the column into cpu usage order.
Make a note of the PID number for the svchost process using the cpu.
Now go to a command prompt, and run the newly downloaded tasklist command
tasklist /svc
This will list all the service tasks withing the svchost processes.
Find the PID number you made a note of.
Which service tasks are listed next to it. If there are none, its probably a
virus.
If you need help, the tasklist command can also have its output redirected
to a file
from a command prompt type
tasklist /svc > tasks.txt
You can now open tasks.txt with notepad and copy/paste a list of all your
tasks into a reply post.
The lsass.exe process, as you will see, houses 3 service tasks, or it does
on my system !
These are
Policy Agent
ProtectedStorage
SamsS
SERVICE_NAME: PolicyAgent
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : D:\WINDOWS\System32\lsass.exe
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : IPSEC Services
DEPENDENCIES : RPCSS
: Tcpip
: IPSec
SERVICE_START_NAME : LocalSystem
SERVICE_NAME: ProtectedStorage
TYPE : 120 WIN32_SHARE_PROCESS (interactive)
START_TYPE : 2 AUTO_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : D:\WINDOWS\system32\lsass.exe
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Protected Storage
DEPENDENCIES : RpcSs
SERVICE_START_NAME : LocalSystem
SERVICE_NAME: samss
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
One of these IS ipsec, so perhaps once we've fixed this svchost, we'll have
a look at what that ipsec error is you're getting.
Paul