mttc wrote:
> On Jul 2, 4:55 am, Paul <nos...@needed.com> wrote:
>> mttc wrote:
>>> Gigabyte EX58-UD4 Board, Clean XP SP3, disconnect from network.
>>> When I play mp3 with Microsoft MediaPlayer, the XPclockstartlagged
>>> about 3 sec per Minute! This happen only if EasyTune tools is also
>>> running (Gigabyte board tune tool).
>>> I try to play with VLC, and I not see anylagged.
>>> I try it again on win7 clean install and I got the same. I try also to
>>> replace the Power Supply or use with one Stick of memory. but all the
>>> same.
>>> Any Idea please?
>> Pretty simple. Stop using EasyTune.
>>
>> A potential mechanism to screw up a systemclock,
>> is described here.
>>
>> http://en.wikipedia.org/wiki/System_Management_Mode
>>
>> "and causeclockticks to get lost"
>>
>> Just a guess,
>> Paul
>
> Did you mean that ET6 run on System Management Mode?
> Did this Explain why I got Clock slow also after Sis Sandra BanchMark?
> why Sandra not cause me Lag on other boards systems?
>
> Thenks
>

To make the WinXP system time clock run slow, you need a mechanism which
causes clock tick interrupts to get lost. If the interrupt service
routine doesn't get to run in time, that is a mechanism.

Clock tick interrupts come from hardware, many times a second.
That particular interrupt has a high priority, and in a normal
system, no other activity would prevent the interrupt from being
serviced. To explain a slow running clock (where the time loss is
larger than can be explained by the accuracy of the quartz oscillator),
you need a mechanism which causes the loss of clock tick interrupts.

Software activity at the kernel level, works with sets of rules.
Such as not running at interrupt level for long period of time
and the like. (The hardware drivers added to the system, also have
to follow the rules.) If there was a problem with the design of the
OS itself, then time loss would be seen by many users.

There have been cases, where the problem is caused by a hardware
bug. For example, some motherboards with Nforce2 chipset, have
trouble with time keeping. The problem was only evident, when
some of the boards were overclocked (non-canonical operating
frequency for the chipset). The bug may have been in the
interrupt logic.

If you see the problem, with both WinXP and with Win7, that
tends to suggest there must be a hardware or driver component
to this problem.

You have a function in the BIOS called HPET, and you could
try disabling that for a test. I don't know why that would be
a problem, but it is all I can see that might be related,
in the BIOS.

http://web.archive.org/web/200407290.../mm-timer.mspx

Paul