Services.exe strange behaviour

I had a virus infection on my Windows XP Pro SP2 installation a month
ago. I have successfully removed the infection, but I have noticed
some strange behaviour on my system ever since. I cleaned the
infection and have rescanned my system with at least 3 different virus
scanners and a couple spyware/malware removers. All show no signs of
infection now.

Upon startup, maybe 25% of the time, services.exe will die, causing my
system to shutdown after a 1 minute timeout.

Also, if my wireless network connection is enabled, services.exe will
enumerate every single file on my hard drive, in alphabetical, depth
first order. This can take upwards of 1 hour, and is only noticable
because I was using sysinternals filemon utility to trace another
problem. About every 30 minutes, the services.exe will hit 100% CPU
usage for about 15-30 seconds. Interestingly, if I am connected to a
network with the wired network adapter, or if I am not connected to any

network, services.exe does not enumerate the files or takeu up the CPU
time.

There are no suspect ports open on my machine. I have verified that
the services.exe file is the same (with a file compare) as the one
provided with SP2, and that the services.exe that is running is indeed
running out of the c:\windows\system32 directory and not some rogue
directory.

I have only minimal services running on this machine. The only two
running services listed to run under the services.exe are Event Log and

Universal Plug and Play.

It seems to me that this is not appropriate behaviour. My question,
then, is: should I expect this behaviour from services.exe? How can I
troubleshoot further to determine if this is a problem or not?

Thanks,
Sam