Annoying problem after an windows xp update

[citimeta]

Last sunday, I encountered this annoying problem. My T41p GGU regularly stopped working for about 1 minute then resumes for about 15 seconds and so on and so forth. During the period when nothing responded, the hard drive seemed to stop completely as well. At first I thought it could be a HD problem. But I can't convince myself since the machine was running great just the night before. One thing then jumped into my mind: I did some windows updates the night before before I shut down the computer. So I performed a system restore. Everything worked properly after the restoration. I was happy about it. Then the next day I rebooted the computer and it was *ill* again just like before the restoration. If I did another restoration, it worked again.

How can I keep the restored configuration? Or How can I find out exactly what is causing the problem? I have all the updates information.

[citimeta]

Anyone knows how to keep restored configuration after a reboot? Thanks

[aki]

format c: maybe help ?

[qux]

I've run in to this problem on XP before. It's extremely hard to debug since you can't run any tools during the freeze, and before and after everything is fine.

Do you have automatic updates turned on? If so, maybe XP reinstalled the updates during that day you had it on and then they became effective after your reboot.

The first thing to do is to try to undo anything that's changed since the restore point you're using. Next I usually try updating my drivers and uninstalling anything I don't need. Also make sure you're running anti-spyware and antivirus. Finally if that doesn't work, it's time to do a full system restore, which I've had to do

[GomJabbar]

You can try the UPHClean service from Microsoft. It may solve your problem. User Profile Hive Cleanup Service

[davidspalding]

Under 2000 (and I'm suspicious of XP), the Content Indexing Service can use CPU cycles while I'm trying to be lord and master of my CPU. At times, I've found system performance to appear degraded, because the serivce was using CPU *and* hard drive resources to do it's little thing. (I always thought it was supposed to work in the background, when idle, but my systems have proved my assumption incorrect.)

To find out, right-click My Computer, select Manage, drill down to Services > Indexing service, and stop it. See if your problem persists or stops occuring.

Note: The service will start again if you reboot.