Dual core Task manager graph

[THCi]

Hi all,

Heres something thats been stumping me and a friend. The graphs on windows task manager seem to be b0rked running under a AM2 4600+ X2.


See image. Im presuming it should look something like this one linky.

I've tried installing the Dual Core optimizer from AMD's site. Didn't help at all.


Is there something I've missed?


Thanks for any help,

THCi

[teachmech]

Hi

What was running when you took the screen shot?

Have you set a program to run on one core only?

When I look at mine they tend to be about even.

[THCi]

No, all threads have thier affinity set to both cores.

[teachmech]

I have to agree then thats a strange graph.

[dave87]

Without knowing what he was running at the time, its hard to comment. Most Single threaded applications would default to CPU0 - as they are not able to make use of the second core. That is unless the affinity is set to the other core.

With my Core Duo (laptop - 2x2ghz) I see a pretty much identical graph on both cores, until I run an app that I have assigned to a single core. It may be that windows has decided to attribute some system processes to the second core, but i find it highly unlikely

Dave

[chuckskull]

My task manager often look like this. Unless it's doing it when theres nothing running dont worry about it.

If the machine is supposed to be doing nothing, then dump a screenie of the full processes tab and it'll be easy to stop the problem.

[THCi]

Processes. As you can see, there is just 4% of the cpu's time being used, but the overall graph (at time of screen dump) lists 33%.

[Steve]

Weird. Surely it's not something sinister like a rootkit, is it?

[THCi]

Wouldnt have thought so, anyway to check for the common ones?

[THCi]

Run the check from sysinternals (RootkitRevealer) and it listed the usual of AnyDVD, WinRAR and Alcohol120%.

[THCi]

Nobody got any further ideas?

[Clunk]

this same thing happened to me when an m-audio soundcard was conflicting with the pci-e bus on an nf4 motherboard, i was getting around 30% cpu usage and only managed to fix it by ditching the soundcard.