200 words — 1 minutes read

CPU pegged at 100%, Who to blame? (Part 1)

In preparation for the project ahead I decided to install IIS and the latest fixes on this Windows XP SP1 machine. Then I got ActiveState Python to work as a handler to .py files (something that Microsoft Knowledgebase helps you with.

I was rewarded with a working IIS con Python server and an unbelievable slow machine. Bringing up the Task Manager shows my CPU pegged at 100% - but none of the processes running seem to be responsible for it. Firing up ProcessExplorer by SysInternals shows a lot more information about the running processes, but no culprit.

Googling with this query brings some interesting reads, but no definitve answer.

It’s rebooting madness at the moment. Killing processes to see if they are guilty of eating my CPU, deinstalling XP Fixes (811493), deinstalling IIS - but nothing has helped so far.

My system is a bit more responsive than when this started, but it takes about three times as long to boot or shutdown. The CPU is still pegged at 100%, the fans on my Inspiron 8200 blow as if there was no tomorrow and I’m without a clue… Has the time come to reinstall Windows XP in 5 hours? Shudder

Jens-Christian Fischer

Maker. Musician