I'm desperate - System Interrupts (Windows 7)

[OS-Wiz]

If they are true system interrupts: could be CPU having problems. Temps OK? Might be memory: Memtest each stick separately.

[SE_Saga]

I don't think it's viral or spyware related because, as I said, no program detected anything, and I've done fresh windows installs, after full formats.

Temps are around high forties when idle, but go into the fifties when the System Interrupts raise the 2 cores to high CPU usage.

I'll test the ram with memtest tomorrow and report back here. Thanks.

EDIT: By the way, what do you mean by "true" system interrupts? There are others that aren't true? I'm confused by that statement.

[OS-Wiz]

I don't think it's viral or spyware related because, as I said, no program detected anything, and I've done fresh windows installs, after full formats.

Temps are around high forties when idle, but go into the fifties when the System Interrupts raise the 2 cores to high CPU usage.

I'll test the ram with memtest tomorrow and report back here. Thanks.

EDIT: By the way, what do you mean by "true" system interrupts? There are others that aren't true? I'm confused by that statement.

Sometimes thrown error messages aren't *the real deal* as the OS sometimes gets confused when the more nasty beasties occur.

[ua549]

I don't think it's viral or spyware related because, as I said, no program detected anything, and I've done fresh windows installs, after full formats.

Temps are around high forties when idle, but go into the fifties when the System Interrupts raise the 2 cores to high CPU usage.

I'll test the ram with memtest tomorrow and report back here. Thanks.

EDIT: By the way, what do you mean by "true" system interrupts? There are others that aren't true? I'm confused by that statement.

Have you added any non-whql certified drivers?

Do you get this condition before you install any apps after the clean OS install?

[SE_Saga]

Update on the situation:

I used Memtest 4.00 to test the RAM, and it passed without a single error.

As I said earlier, the problem persists even after a fresh Windows install where nothing else was installed, other than some windows updates.

Regarding the whql certified drivers, as I said, I downloaded the drivers directly from the official website so I believe they qualify, but correct me if I'm wrong.

Are there any viruses that survive a full format by staying in the boot sector of a drive, or infecting the BIOS? Could that explain the issue? If so, how do I clean it?

ICould it be anything else? Like a fried mobo? Fried CPU? PSU going dead? Defective cables? I mean, if I had extras of these things, I'd try them out, but I don't, and it's a shame if I start buying stuff only to find the problem is still there

My last and final resort will be to build a whole new PC from scratch... but that's an expensive solution, which I really want avoid.