Hardware Interrupts Using 30% of CPU
Last response: in CPUs
Hello, recently I bought an Antec earthwatts 500W PSU. When I turned on the computer after installing it CPU usage was about 30% at idle. According to Process Explorer, that 30% is Hardware Interrupts. I know this only popped up AFTER installing the new PSU. Unfortunately, in trying to find a solution on google no one else with the problem seems to have solved it in a way that works for me, and I've already checked my IDE ATA/ATAPI controllers in device manager, and they are all set to DMA if applicable. I tried the old PSU and the hardware interrupts is still there. Safe mode, it's still there, and I also tried the RAM, only using 1 stick at a time to test if one is broken but it didn't solve the problem.
Because of this, I'm guessing it is the CPU, hard drive, or motherboard. What comes to mind is I did remove the heat sink when I first put in the new PSU, and I had some troubles as one of the two sockets for the securing screws for the heat sink seemed to sink down lower than it should be, so that it was actually under the motherboard and I had to push on the other screw socket to push it back up above. In the course of this the heat sink would have rubbed against the CPU itself and I wonder if something was messed up, though I would think that would make the CPU not work rather than give this strange hardware interrupts. Is there anyone who has experienced this? Is there a way to test if it's the hard drive? Is it possible just to unplug it and run the computer without it?
I appreciate any help.
Because of this, I'm guessing it is the CPU, hard drive, or motherboard. What comes to mind is I did remove the heat sink when I first put in the new PSU, and I had some troubles as one of the two sockets for the securing screws for the heat sink seemed to sink down lower than it should be, so that it was actually under the motherboard and I had to push on the other screw socket to push it back up above. In the course of this the heat sink would have rubbed against the CPU itself and I wonder if something was messed up, though I would think that would make the CPU not work rather than give this strange hardware interrupts. Is there anyone who has experienced this? Is there a way to test if it's the hard drive? Is it possible just to unplug it and run the computer without it?
I appreciate any help.
More about : hardware interrupts cpu
Hi, I had the same problem a few years back. It turned out to be a bad sector on the hard drive that the system was trying to continuously read. I solved this by running "chkdsk" in dos mode. It moved the information on the bad sector to another location and my cpu usage was back to normal. Hope this helps you.
Related ressources
- Best Cpu cooler for ~40 - Forum
- Cpu temps - Forum
- CPU cooling - Forum
- CPU - Forum
- Question on Removing CPU and Reapplying Thermal Grease - Forum
I'm not sure what you mean by code to trap the hardware interrupts, but I know it's here from running Process Explorer, which tells me the CPU usage of it (it does not show up under Task Manager). I removed and put back the heatsink as it was blocking access to the motherboard power connector. Thanks for the replies, I will try to check the harddrive.
This is sometimes caused by a fault within the windows or IDE drivers.
The system goes into PIO mode, even though it says its running as DMA.
When you find this, go to control panel, system, device manager, and remove the IDE controllers, Primary and Secondary.
Reboot.
The devices will get re-installed back to DMA working state.
This happens because the driver detects a timing or crc type error when in use, and degrades the system to guarantee data integrity. Change / fix your cables/update the drivers.
AdmV
The system goes into PIO mode, even though it says its running as DMA.
When you find this, go to control panel, system, device manager, and remove the IDE controllers, Primary and Secondary.
Reboot.
The devices will get re-installed back to DMA working state.
This happens because the driver detects a timing or crc type error when in use, and degrades the system to guarantee data integrity. Change / fix your cables/update the drivers.
AdmV
It proves that the kernel is doing most of the work, i.e., interrupt handling, I/O, etc. You'll have to disconnect your hard disk and boot from a BartPE CD or DVD. Then check if you still have the hardware interrupt issue. I doubt the hard disk itself is the source of your problem, but disconnecting it should at least prove that all other components are not the source of the issue. Narrowing down the issue to the hard disk or software will be a step in the right direction.
Alright I couldn't find any blank CD's in my house, tomorrow I will buy a pack. Also the instructions mention using Windows XP installation files, not just the already installed windows data. Does that mean I need to have the original Windows XP installation CD, because my computer came with it pre-installed and HP doesn't give out backup CD's with their computers.
I should ask this ahead of time; how do you boot from the CD drive? If the CD is there and I turn on the computer without a hard drive, will it be automatic? Also how will I be able to tell if the interrupts is still there, since Process Explorer is saved onto the hard drive? I guess you can use task manager still?
Did you use this procedure: http://www.winsupersite.com/showcase/windowsxp_sp2_slip... It will work with SP2 and SP3 and it might be easier to follow.
Please explain how it will help the OP run Process Explorer. The OP most likely has no knowledge of Linux.
Thanks for the step by step guide, using it I got PE working. Anyway while booted using the CD I checked Task Manager, and sure enough the CPU idles at 40-60%. I didn't use process explorer but while idle the system idle process claims to be using 99% of the CPU but it obviously isn't so I guess we know the hard drive isn't the problem. I guess that means it must be the CPU itself or the motherboard. Is there any way to test that?
Before having the CPU and/or motherboard tested, you should remove the heat sink again, clean up the heat paste on the CPU and HSF with rubbing alcohol. If removing the HSF could dislodge the CPU from the socket (you didn't specify what CPU you have), remove it and reinstall it. Then use Artic Silver 5 (follow the instructions and use the required quantity) and reinstall the HSF. It might solve your issue.
It just seems odd, if the CPU is dislodged or something I would think it would simply not work. Though I'm not a computer expert of course. My CPU is AMD Athlon 4200+ x2, socket 939. Motherboard is MSI AMETHYST-M. I'll have to get some thermal paste, if you have any other suggestions I'd appreciate it.
In your initial post you wrote "What comes to mind is I did remove the heat sink when I first put in the new PSU, and I had some troubles as one of the two sockets for the securing screws for the heat sink seemed to sink down lower than it should be, so that it was actually under the motherboard and I had to push on the other screw socket to push it back up above."
How did you remove the heat sink before? It's no different this time around.
How did you remove the heat sink before? It's no different this time around.
Before taking it all apart try resetting the router + broadband modem.
They tend to use up most of the interupts if you have a busy network and/or problems within it.)
By switching off the Router (and release your IP. - then restart Windows)
I run XP and got the above issue with 16-30% used up by hardware interrupts. and it all sort itself after a router / modem restart.
Must be something recent with all the servicepacks because never had this problems before
To find out all you have to do is switch the router / modem off and run process explorer - check if the problem persist.
They tend to use up most of the interupts if you have a busy network and/or problems within it.)
By switching off the Router (and release your IP. - then restart Windows)
I run XP and got the above issue with 16-30% used up by hardware interrupts. and it all sort itself after a router / modem restart.
Must be something recent with all the servicepacks because never had this problems before
To find out all you have to do is switch the router / modem off and run process explorer - check if the problem persist.
!