[resolved] Asus p6t deluxe - Core 0 on I7 always running high

I just put together my I7 920 vista 64 box.

I noticed that core zero always has load even if nothing is going on. The die temps all look like they are idle and I cannot find any processes that are taking cpu. Does it just mean that system idle process is being represented on core 0? If not how can I tell what is running on that logical core since i cannot find any processes doing this in process explorer.


Thanks



[b]resolution below[/b]


I have an asus p6t deluxe board which has a marvell controller on it. There was a marvell raid controller driver installed that was causing this. I am not sure at what point in my build did this get installed, but since the only thing i was using that chip for was my ide burner it wasn't required. Therefor, I think there was some contention going on with it, possibly it didn't have setting in bios for it to work right.

Bottom line disabling/uninstalling this storage controller from dev mngr showed immediate results. The most annoying thing with this issue was the troubleshooting process required to get the point where you start disabling random system components since there is no process info for this even using process explorer. I hope this info save someone else the hassle that I went through.

For some reason I always find most work on my last core (c1 at work, c3 at home)

I shouldn't worry, it'll just be windows sitting the twiddling it's thumbs!

well thats the first core that receives data right? if a process is not multi threaded the you can expect your first cores to always process more data.

Well seems when I reboot it comes back. any ideas?

it was on avg 80% but i found the root cause. I have an asus p6t deluxe board which has a marvell controller on it. There was a marvell raid controller driver installed that was causing this. I am not sure at what point in my build did this get installed, but since the only thing i was using that chip for was my ide burner it wasn't required. Therefor, I think there was some contention going on with it possibly it didn't have setting in bios for it to work right.

Bottom line disabling/uninstalling this storage controller from dev mngr showed immediate results. The most annoying thing with this issue was the troubleshooting process required to get the point where you start disabling random system components since there is no process info for this even using process explorer. I hope this info save someone else the hassle that I went through.

I'm a unix system admin so I guess it's a habit.


As for your comment, I agree, remember having issues with marvel and pci bus saturation in conjunction with creative xfi (huge topic within itself) on an older A8N board. I had to switch to the fake raid that nvidia provides. The p6t does have SAS provided by marvel so I wonder how that is. Since I have a velociraptor it may be not worth the effort to play with it. Was planning on getting 2 of them for raid 0 but decided to wait and just get a ssd next year. Also I read arguments that raid 0 isn't really as great as everyone thinks for a gaming pc.

Not really. RAID 0 is striped, which means that the data is in stripes that go across both disks. Unless your data is much smaller than one stripe, you can't have one disk seeking while the other reads. They will both be required to read any file of a significant size.