A7N8X fsb fluctuations ?

[Gordon Freeman]

Hi all. I noticed a strange issue on my A7N8X-Deluxe.
My system specs are:

A7N8X-D 1.04, bios 1006
AthlonXP 2100+@2700+ (166*13), Vcore set at 1.65 V but reported as 1.71 V
2*A-Data pc3200 ch-5 winbond chip ram (dual channel)
......
others are less important.

My system ran for about 10-11 hrs yesterday. A last check to MBM5 sensors
reported cpu frequency to be around 1999 MHz or less, instead of 2173, how
it should be. A quick check with Cpu-z confirmed that. The program reported
FSB randomly fluctuating in 140 - 155 range. And even Vcore was
fluctuating, but i know this is ok.
But Sandra 2004 and Xcpuid reported the "correct" cpu frequency and even
Wcpuid does, even using the "Real TIme Clock checker".
The system ran perfectly, anyway.

I rebooted and on next reboot Linux reported correctly the 2172 MHz cpu.
Don't know what to think.
I've searched on Google but found nothing similar (or maybe i used wrong
keywords)

Any help (or feedback) appreciated. TIA
Greetings

 

[Gordon Freeman]

L'incedente di Black Mesa e' stato nulla in confronto ai danni causati dai

Hi all. I noticed a strange issue on my A7N8X-Deluxe.

forgot to say: "FSB SPread Spectrum" is disabled in bios...

 

[Ben Pope]

Hi all. I noticed a strange issue on my A7N8X-Deluxe.
My system specs are:

A7N8X-D 1.04, bios 1006
AthlonXP 2100+@2700+ (166*13), Vcore set at 1.65 V but reported as 1.71 V
2*A-Data pc3200 ch-5 winbond chip ram (dual channel)
.....
others are less important.

My system ran for about 10-11 hrs yesterday. A last check to MBM5 sensors
reported cpu frequency to be around 1999 MHz or less, instead of 2173, how
it should be. A quick check with Cpu-z confirmed that. The program
reported FSB randomly fluctuating in 140 - 155 range.

Thats weird. When you say fluctuating... between boots or whilst the
program was running?

And even Vcore was fluctuating, but i know this is ok.

It's not ideal... VCore should be pretty solid, by all accounts.

But Sandra 2004 and Xcpuid reported the "correct" cpu frequency and even
Wcpuid does, even using the "Real TIme Clock checker".
The system ran perfectly, anyway.
Right.

I rebooted and on next reboot Linux reported correctly the 2172 MHz cpu.
OK.

Don't know what to think.

Neither do I. I suspect it's a software issue, as I don't think you're
likely to have the actual clock fluctuating that much without experiencing
much more weirdness.

Ben

 

[Gordon Freeman]

In date Mon, 20 Oct 2003 14:10:08 +0100, Ben Pope wrote:

Thats weird. When you say fluctuating... between boots or whilst the
program was running?

Ok, i noticed it sometimes at boot. MBM reported a wrong frequency. A check
with Sandra confirmed it was all ok. So i tought MBM was wrong. Yesterday
even cpu-z confirmed that, even while the program was running. Wcpuid
instead reported 2171.59 MHz fluctuating in a 0.01 MHz range. Nthing
important.

It's not ideal... VCore should be pretty solid, by all accounts.

Slight fluctuations, nothing to worry about (i hope).

Neither do I. I suspect it's a software issue, as I don't think you're
likely to have the actual clock fluctuating that much without experiencing
much more weirdness.

Yes, right. I should have noticed crashes or other problems if it was an
hardware related problem.
I found a post (after posting here) on a forum describing my same problem.
The guy there stated that it was a service from Sandra 2003-2004 messing
with clock readings. Now i just uninstalled it. Hope this fixes the issue.

Ben

Thanks for your reply. Greetings

E.

 

[Ben Pope]

In date Mon, 20 Oct 2003 14:10:08 +0100, Ben Pope wrote:



Ok, i noticed it sometimes at boot. MBM reported a wrong frequency. A
check with Sandra confirmed it was all ok. So i tought MBM was wrong.
Yesterday even cpu-z confirmed that, even while the program was running.
Wcpuid instead reported 2171.59 MHz fluctuating in a 0.01 MHz range.
Nthing important.

0.01MHz? Experimental error. Thats like 0.01 in 1000, which is 0.001%
variation, seriously, thats not fluctuation, thats considerably better than
you would normally expect from most experiments!

Slight fluctuations, nothing to worry about (i hope).

Well mine varies maybe 0.05V over the course of a day (MBM5 min/max)

Yes, right. I should have noticed crashes or other problems if it was an
hardware related problem.

Yeah, a dogy clock is likely to cause all sorts.

I found a post (after posting here) on a forum describing my same problem.
The guy there stated that it was a service from Sandra 2003-2004 messing
with clock readings. Now i just uninstalled it. Hope this fixes the issue.

Well lets hope it does.

Ben

 

[Gordon Freeman]

In date Mon, 20 Oct 2003 15:34:52 +0100, Ben Pope wrote:

0.01MHz? Experimental error. Thats like 0.01 in 1000, which is 0.001%
variation, seriously, thats not fluctuation, thats considerably better than
you would normally expect from most experiments!

yes, it was only to say that that's right

Well mine varies maybe 0.05V over the course of a day (MBM5 min/max)

so does mine, just checked (1.71 - 1.73)

Yeah, a dogy clock is likely to cause all sorts.
Right


Well lets hope it does.

So do i. I just deleted all non-pnp device drivers that could cause
problems (cpucool remnants etc. etc.). let's go on and see if this is fixed.

Ben

Thanks again. Greetings
E.

 

[Gordon Freeman]

In date Mon, 20 Oct 2003 11:25:26 +0200, Gordon Freeman wrote:

Maybe i found something useful here:

http://www.nforcershq.com/forum/vie...&postdays=0&postorder=asc&highlight=fsb+jumps

Perhaps i used wrong keywords in searches i've done until now.
Greetings