new XP Pro install, Task Mgr using 50-80% CPU

[wtigger]

I just did a new XP Pro install (SP-2 slipstreamed) on a Dell Dimension 3000, 2.8 Ghz CPU (533 Mhz FSB), 2GB DDR-333 RAM, 120GB HDD. RAM is new, the rest of the system is "used".

This is one of the SLOWEST systems I have ever encountered... This system runs like a Pentium 1 :-( NEVER seen anything like this before...

There is NO other software on the system at all, not even hardware drivers yet.

I go into Task Manager and the Task Manager process is eating 50-80% of the CPU... Only 16 processes are running at the moment....

Anyone ever seen this before??

Here's the history behind this:

The system (3000) ran fine before this... I had the hard drive in a Dimension 2400 previously. That also ran fine. The reason for the HDD swap is that the client wanted a system that ran at 2.8 Ghz for a program they own.

So, the RAM and HDD went from the Dell 2400 to the 3000. Of course that hosed the XP install (driver blue screen), so I do a Repair install for XP, that took 2 DAYS for the files to copy and install completely. Finally it boots, but SO SLOWWWW... They wanted to preserve the data and software, that is why I went through all this insanity.

Finally, I decided to slave the HDD to another system and copy off the data and reformat and reinstall XP. And that brings me to where we are now...

Do I need a priest and an exorcism?

Ideas?

 

[GamerX]

You might see if the bios needs to be updated, also check the to make sure there are no viruses or malware on the system. That can also slow down the system.

 

[NickCat11]

Does the problem exist in Safe Mode?

 

[Xtreme]

I dont know if this is why, but I had a problem before similar to this but with an Acer. When I was able to look in task manager I seen that it was the "SYSTEM" process that was eating up the CPU. It's been so long ago, but I think it was a bad battery and I may have updated the BIOS as well. What was weird is that it worked fine before the lady brought in to the shop, it only did this after the format/reload. But the problem was fixed. Maybe thats something you can try to look at.

 

[wtigger]

I think it is a motherboard issue... Safe mode is the same... This is a FRESH install of XP after a full format... I'm planning on getting a replacement motherboard for it ($30 on eBay).

I swapped the HDD to another system same model, problem eliminated... Motherboard is a strong candidate... It has the current BIOS... I haven't seen CMOS batteries cause this yet. But anything's possible these days

 

[wtigger]

I think it is a motherboard issue... Safe mode is the same... This is a FRESH install of XP after a full format... I'm planning on getting a replacement motherboard for it ($30 on eBay).

I swapped the HDD to another system same model, problem eliminated... Motherboard is a strong candidate... It has the current BIOS... I haven't seen CMOS batteries cause this yet. But anything's possible these days

 

[wimwauters]

I would try a clean Windows install and download the correct drivers (with another system, and stick them on a USB stick or CD-R): this might just be a cantankerous motherboard

Also doublecheck cable mode vs. master/slave setup of the IDE hard disk. Don't forget that the IDE cable must be correct too: the cable select version will have a notch or 'cut' strand in it.

 

[wtigger]

I did try a fresh install of Windoze, took many hours :-( I also put the IDE HDD on Master jumper.

When I put a slower CPU in it, it worked for a while, then went crazy slow again. That's why I think it's a motherboard issue. Will get one soon and let you know how it works out

 

[quake101]

What if you boot up with a "live" cd? (ubcd4win, ubuntu, etc)

 

[arrow_runner]

I think your turbo button is broken and that's why it worked 'ok' for a little bit with the old CPU. You also need to make sure you're replacing the oscillator crystal when you upgrade a cpu or it won't actually RUN at the full 33MHz your customer is looking for.

 

[zfrogz]

Check the motherboard for blown caps. I have also had problems with a fresh install because some of the data was corrupt when it was installing. Check the CD you used and maybe try a different cd-rom drive for the install.