About 2 weeks ago, my computer suddenly starting hiccuping. It will run for about 15-20 seconds, then freeze for 2-3 seconds. I’ve scanned for viruses and spyware, nothing there. Watching the Windows Task Manager looking at CPU activity does not reveal any wierdo process coming up and running. There are no background tasks running that shouldn’t be.
As you might imagine, this really throws a kink into my gameplaying. Watching my armies march across the screen and pause every 15 seconds or so is really starting to suck bigtime. Any suggestions?
The only time I saw this kind of behavior it turned out someone’s wife had secretly installed a background website and keystroke logging program on the PC.
Keystroke logging or bad memory pages does sound possible.
In the case of an overheating processor, generally you’ll get spontaneous shut downs or reboots of the system, not just a slowdown.
Another suggestion:
Might be the hard drive itself. Either bad sectors, or just corrupt data. Run a full scandisk with physical scanning, followed by a defragmentation of the HD, and see if that improves the situation.
There’s no HD activity, so it’s not swapping itself to death, and the event viewer doesn’t show anything out of the ordinary.
I followed up on the heat idea from N&I Scott, to the point where I shut down, opened the case and blew any accumulated dust off the heatsink vanes. The fan’s working ok, so it’s not a circulation problem. However, cleaning the vanes was done in vane (heh, heh), as The Damn Thing ™ is still hiccupping.
I think it’s time for an upgrade and my computer is telling me so. Now if it would only tell me where to find the money to perform said upgrade…
Like I said, generally. Rebooting is one of the most common (IME) responses to overheating, but by no means the only possible one.
Just for ha-has, how much was your temp monitored system overheating? Are we talking a minor temp increase (two degrees or so), or catastrophic heat sink failure, here?
An update, with a happy ending. I’m posting this in case someone else has this problem occur.
I had tried rebooting numerous times and could not get the problem to clear up. Today, for no good reason other than sheer desperation, I powered down. And I mean down - after the shutdown finished, I turned the whole nine yards off with the master switch on the power strip.
Powered up, and voila - problem is gone. Ain’t that wierd?