pek wrote:

> Well, the Everest log, up to the freeze point, anyway, shows less that
> 70% on one core and about 5% on the other, so unless something snuck in
> there between one log update and the freeze, I don't _think_ that's it.
> I've never seen the dual core maxed out on both cores unless I'm running 2
> compute intensive things. The file transfer just hits one heavy and the
> other normally stays less than 30%. I'm not ruling it out, but I think
> that's lower on the probability list. I wish Biostar had a northbridge temp
> sensor, they monitor the shipset voltage for some resaon, but not the temp.
> Really threw me at first, Everest reads it as the 2.5vdc mem voltage sensor
> but says that it's 1.6 vdc, the chipset voltage.
>
> pek

what does your hand say about northbridge temp? I cant say I have the
greatest faith in these hw test suites, they have their uses but
routinely give wrong results.

When an endless loop occurs, logging wont log, the cpu will be too busy
with the player app and the looping app. If taskman is already running
and on performance page, you should still see retraces of cpu use, just
very slow. So this may tell you either way re cpu.


NT