This was a HP Pavilion zv5000 laptop with a 60GB drive and XP Home.

Event Viewer showed several things of note around the reboot times:
Got a bug check: 0x0000007a (0xc03dd9a4, 0xc000000e, 0xf7669130, 0x0737e860)

The error is The device .DeviceIdeIdePort0, did not respond within the timeout period.

An error was detected on device DeviceHarddisk0D during a paging operation.

Ran the whole chkdsk /r and chkdsk /f bit. Found 4KB in bad sectors–but more importantly, I heard the tell-tale sound of a hard drive beginning to fail.

Miraculously, Ghost 12.0 was able to make a disk copy of the hard drive (and properly resize) to an 80 GB hard drive. The only catch left is that the “bad sector” flags are copied as well. Not a big deal in this case, but here’s a page with a resolution: The $BadClus metatfile.

Because of the failing drive, the copy operation for 10 GB of data (4500 RPM drive) took close to two hours. I’d imagine the faster hard drive in better condition would have a significantly better transfer rate.

Once the disk copy was finished, I swapped hard drives out and the new drive booted almost exactly as old. One glitch: XP Pro/2003 boot option was added as a second option, in addition to the valid XP Home boot. No problem… I just had to edit the boot.ini.

At that time, I stumbled upon both the Microsoft Anti-Spyware Tool and Sunbelt CounterSpy. Both tools did an exceptional job, and went with CounterSpy because it was advertised as the creator of the engine for both products.

In two years of use, CounterSpy bogged down my 2.8Ghz P4 with Win2k and 1 GB RAM. I also had quite a few false positives in those two years. With a recent update, CounterSpy constantly disabled itself on my Win2k system.

I decided to switch over to one of the top recommendations from a Consumer Reports article… Webroot Spy Sweeper… as far as I can tell so far, Spy Sweeper is using only 8MB of RAM while not conducting a scan.