K7N2 Delta won't keep time

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

I have a K7N2 Delta running an XP2200+ that will not keep time. It gains
about 10+ minutes in for every hour that it is run and it throws the clock
in the windows tray and the bios off. This used to not be a problem, it has
just started within the last couple of days, so I am not sure what is wrong.
I have not installed new hardware or software (other than the usual virus
pattern updates), so does anyone have an idea? I have heard of them slowing
down from a dead battery, but speeding up?

S

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"sbb78247" <sbb78247@hotmail.com> wrote in message
news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
> I have a K7N2 Delta running an XP2200+ that will not keep time. It gains
> about 10+ minutes in for every hour that it is run and it throws the clock
> in the windows tray and the bios off. This used to not be a problem, it
has
> just started within the last couple of days, so I am not sure what is
wrong.
> I have not installed new hardware or software (other than the usual virus
> pattern updates), so does anyone have an idea? I have heard of them
slowing
> down from a dead battery, but speeding up?
>
> S
>
>
Oh man, I've had the exact same problem and it drove me nuts. The first
time it lasted about 2 weeks, then it started up for a day or so last week.
I'm not sure if it went away on it's own or what, but you could try
disabling "Windows Time" in the services section and see if that helps.

Good luck...

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Kill Bill" <a@b.c> wrote in message
news:svxOc.58557$ju5.20198@twister.socal.rr.com...
>
> "sbb78247" <sbb78247@hotmail.com> wrote in message
> news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
> > I have a K7N2 Delta running an XP2200+ that will not keep time. It
gains
> > about 10+ minutes in for every hour that it is run and it throws the
clock
> > in the windows tray and the bios off. This used to not be a problem, it
> has
> > just started within the last couple of days, so I am not sure what is
> wrong.
> > I have not installed new hardware or software (other than the usual
virus
> > pattern updates), so does anyone have an idea? I have heard of them
> slowing
> > down from a dead battery, but speeding up?
> >
> > S
> >
> >
> Oh man, I've had the exact same problem and it drove me nuts. The first
> time it lasted about 2 weeks, then it started up for a day or so last
week.
> I'm not sure if it went away on it's own or what, but you could try
> disabling "Windows Time" in the services section and see if that helps.
>
> Good luck...
>
>

Well, now the stupid thing is only 6 minutes fast after running folding@home
all day. Yesterday and the preceding couple, it would really gain the time,
but today it setteled a bit. Freakin' weird.

S

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"sbb78247" <sbb78247@hotmail.com> wrote in message
news:qcAOc.21760$Gk4.10821@fe1.texas.rr.com...
>
> "Kill Bill" <a@b.c> wrote in message
> news:svxOc.58557$ju5.20198@twister.socal.rr.com...
> >
> > "sbb78247" <sbb78247@hotmail.com> wrote in message
> > news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
> > > I have a K7N2 Delta running an XP2200+ that will not keep time. It
> gains
> > > about 10+ minutes in for every hour that it is run and it throws the
> clock
> > > in the windows tray and the bios off. This used to not be a problem,
it
> > has
> > > just started within the last couple of days, so I am not sure what is
> > wrong.
> > > I have not installed new hardware or software (other than the usual
> virus
> > > pattern updates), so does anyone have an idea? I have heard of them
> > slowing
> > > down from a dead battery, but speeding up?
> > >
> > > S
> > >
> > >
> > Oh man, I've had the exact same problem and it drove me nuts. The first
> > time it lasted about 2 weeks, then it started up for a day or so last
> week.
> > I'm not sure if it went away on it's own or what, but you could try
> > disabling "Windows Time" in the services section and see if that helps.
> >
> > Good luck...
> >
> >
>
> Well, now the stupid thing is only 6 minutes fast after running
folding@home
> all day. Yesterday and the preceding couple, it would really gain the
time,
> but today it setteled a bit. Freakin' weird.
>
> S
>
>
I would gain about 6 sec. a minute which really adds up. I spent a week
trying to figure out why every 1 hr. recording using my TV tuner card ended
up with a file only 53 min. long. Because the clock was ticking off seconds
too fast!
This http://www.thinkman.com/dimension4/index.htm is a good program but I
was much more interested in figuring out the real problem.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

On 7/30/2004 4:27 PM Kill Bill brightened our day with:

>
>I would gain about 6 sec. a minute which really adds up. I spent a week
>trying to figure out why every 1 hr. recording using my TV tuner card ended
>up with a file only 53 min. long. Because the clock was ticking off seconds
>too fast!
>This http://www.thinkman.com/dimension4/index.htm is a good program but I
>was much more interested in figuring out the real problem.
>
>
>
>
I don't know what the real problem is either, I've been running a
program that updates the clock once an hour.
I don't know if it's 6 seconds a minute.

--
Steve [Inglo]

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

Is anybody running the Service Pack 2 betas for Windows XP? My
Delta-L was gaining time on at least 2 of the betas - can't remember
which ones. The problem was very obvious after about 30 minutes. The
current build (2162) seems to be OK.

On Sat, 31 Jul 2004 01:58:45 GMT, Inglo
<ingloogoo@zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz.xcc> wrote:

>On 7/30/2004 4:27 PM Kill Bill brightened our day with:
>
>>
>>I would gain about 6 sec. a minute which really adds up. I spent a week
>>trying to figure out why every 1 hr. recording using my TV tuner card ended
>>up with a file only 53 min. long. Because the clock was ticking off seconds
>>too fast!
>>This http://www.thinkman.com/dimension4/index.htm is a good program but I
>>was much more interested in figuring out the real problem.
>>
>>
>>
>>
>I don't know what the real problem is either, I've been running a
>program that updates the clock once an hour.
>I don't know if it's 6 seconds a minute.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Kevin" <kkehoe@NOSPAMns.sympatico.ca> wrote in message
news:k49og0lp2c7mmcqmnskt7gq4v5dtdq32a8@4ax.com...
>>
> On Sat, 31 Jul 2004 01:58:45 GMT, Inglo
> <ingloogoo@zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz.xcc> wrote:
>
> >On 7/30/2004 4:27 PM Kill Bill brightened our day with:
> >
> >>
> >>I would gain about 6 sec. a minute which really adds up. I spent a week
> >>trying to figure out why every 1 hr. recording using my TV tuner card
ended
> >>up with a file only 53 min. long. Because the clock was ticking off
seconds
> >>too fast!
> >>This http://www.thinkman.com/dimension4/index.htm is a good program but
I
> >>was much more interested in figuring out the real problem.
> >>
> >>
> >>
> >>
> >I don't know what the real problem is either, I've been running a
> >program that updates the clock once an hour.
> >I don't know if it's 6 seconds a minute.
>
Is anybody running the Service Pack 2 betas for Windows XP? My
> Delta-L was gaining time on at least 2 of the betas - can't remember
> which ones. The problem was very obvious after about 30 minutes. The
> current build (2162) seems to be OK.

Not me.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

Kevin wrote:
> Is anybody running the Service Pack 2 betas for Windows XP? My
> Delta-L was gaining time on at least 2 of the betas - can't remember
> which ones. The problem was very obvious after about 30 minutes. The
> current build (2162) seems to be OK.

<snip>

No, I do not have the SP2 Betas installed.

S

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"sbb78247" <sbb78247@hotmail.com> wrote in message
news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
> I have a K7N2 Delta running an XP2200+ that will not keep time. It gains
> about 10+ minutes in for every hour that it is run and it throws the clock
> in the windows tray and the bios off. This used to not be a problem, it
has
> just started within the last couple of days, so I am not sure what is
wrong.
> I have not installed new hardware or software (other than the usual virus
> pattern updates), so does anyone have an idea? I have heard of them
slowing
> down from a dead battery, but speeding up?
>
> S
>
My K7N2 Delta board also started gaining time a while ago - not so much as
yours though (only about 5 mins per day), so I worked around by syncing it
with an ntp internet time server more often.
However, I have just searched on google and found an interesting post which
suggested that enabling "FSB Spread Spectrum" in the bios can cause the
clock to gain time.
I shall try disabling it on mine and see if it makes any difference.
Otherwise, if yours still gains even when just booted into the bios screen,
then you could check the voltage of the lithium battery and change it if
below 3 volts.
If that does not cure it, then the board may be faulty.

Dave

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

On 8/1/2004 1:14 AM logized brightened our day with:

>"sbb78247" <sbb78247@hotmail.com> wrote in message
>news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
>
>
>>I have a K7N2 Delta running an XP2200+ that will not keep time. It gains
>>about 10+ minutes in for every hour that it is run and it throws the clock
>>in the windows tray and the bios off. This used to not be a problem, it
>>
>>
>has
>
>
>>just started within the last couple of days, so I am not sure what is
>>
>>
>wrong.
>
>
>>I have not installed new hardware or software (other than the usual virus
>>pattern updates), so does anyone have an idea? I have heard of them
>>
>>
>slowing
>
>
>>down from a dead battery, but speeding up?
>>
>>S
>>
>>
>>
>My K7N2 Delta board also started gaining time a while ago - not so much as
>yours though (only about 5 mins per day), so I worked around by syncing it
>with an ntp internet time server more often.
>However, I have just searched on google and found an interesting post which
>suggested that enabling "FSB Spread Spectrum" in the bios can cause the
>clock to gain time.
>I shall try disabling it on mine and see if it makes any difference.
>Otherwise, if yours still gains even when just booted into the bios screen,
>then you could check the voltage of the lithium battery and change it if
>below 3 volts.
>If that does not cure it, then the board may be faulty.
>
>Dave
>
>
>
>
I've never had FSB Spread Spectrum enabled.

--
From Yahoo's TV Listings,

The Brain From Planet Arous (1958):
"Bad alien Gor takes over scientist Steve's brain; good alien Vol takes over Steve's dog's brain."


Steve [Inglo]

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Inglo" <ingloogoo@zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz.xcc> wrote in message
news:bN7Pc.3136$gK1.261@newssvr27.news.prodigy.com...
> On 8/1/2004 1:14 AM logized brightened our day with:
>
> >"sbb78247" <sbb78247@hotmail.com> wrote in message
> >news:2YwOc.22149$gu2.4604@newssvr23.news.prodigy.com...
> >
> >
> >>I have a K7N2 Delta running an XP2200+ that will not keep time. It
gains
> >>about 10+ minutes in for every hour that it is run and it throws the
clock
> >>in the windows tray and the bios off. This used to not be a problem, it
> >>
> >>
> >has
> >
> >
> >>just started within the last couple of days, so I am not sure what is
> >>
> >>
> >wrong.
> >
> >
> >>I have not installed new hardware or software (other than the usual
virus
> >>pattern updates), so does anyone have an idea? I have heard of them
> >>
> >>
> >slowing
> >
> >
> >>down from a dead battery, but speeding up?
> >>
> >>S
> >>
> >>
> >>
> >My K7N2 Delta board also started gaining time a while ago - not so much
as
> >yours though (only about 5 mins per day), so I worked around by syncing
it
> >with an ntp internet time server more often.
> >However, I have just searched on google and found an interesting post
which
> >suggested that enabling "FSB Spread Spectrum" in the bios can cause the
> >clock to gain time.
> >I shall try disabling it on mine and see if it makes any difference.
> >Otherwise, if yours still gains even when just booted into the bios
screen,
> >then you could check the voltage of the lithium battery and change it if
> >below 3 volts.
> >If that does not cure it, then the board may be faulty.
> >
> >Dave
> >
> >
> >
> >
> I've never had FSB Spread Spectrum enabled.
>
Yeah, that's a BIOS setting that never needs to be on. But on mine the BIOS
clock was spot on, it was only fast in windows. It's hard for me to blame
the board, but I'm sure anything's possible.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

On 8/1/2004 8:28 AM Kill Bill brightened our day with:

>"Inglo" wrote in message
>
>
>>I've never had FSB Spread Spectrum enabled.
>>
>>
>>
>Yeah, that's a BIOS setting that never needs to be on. But on mine the BIOS
>clock was spot on, it was only fast in windows. It's hard for me to blame
>the board, but I'm sure anything's possible.
>
>
>
>
? How can the BIOS clock be spot on and fast in windows? They're
synchronized. Are you saying that it gets 5 minutes fast in windows,
you reboot, go into BIOS and the clock is correct again?
Or are you saying you let your computer sit in BIOS for an hour and it
doesn't gain a second.
If you haven't done that, is anyone willing to try that.

--

Steve [Inglo]

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Inglo" <ingloogoo@zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz.xcc> wrote in message
news:7m8Pc.102592$fP7.89005@newssvr29.news.prodigy.com...
> On 8/1/2004 8:28 AM Kill Bill brightened our day with:
>
> >"Inglo" wrote in message
> >
> >
> >>I've never had FSB Spread Spectrum enabled.
> >>
> >>
> >>
> >Yeah, that's a BIOS setting that never needs to be on. But on mine the
BIOS
> >clock was spot on, it was only fast in windows. It's hard for me to
blame
> >the board, but I'm sure anything's possible.
> >
> >
> >
> >
> ? How can the BIOS clock be spot on and fast in windows? They're
> synchronized. Are you saying that it gets 5 minutes fast in windows,
> you reboot, go into BIOS and the clock is correct again?
> Or are you saying you let your computer sit in BIOS for an hour and it
> doesn't gain a second.
> If you haven't done that, is anyone willing to try that.
>
> --
>
> Steve [Inglo]

I sat with the BIOS open and a stopwatch, one minute equaled one minute.
In windows, 1 real minute equals 1 min. 5 sec.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

> > --
> >
> > Steve [Inglo]
>
> I sat with the BIOS open and a stopwatch, one minute equaled one minute.
> In windows, 1 real minute equals 1 min. 5 sec.
>
>

A google search found this fix for problems where time is wrong ONLY in
windows -

If it is running fast while Windows is running, try this:
It appears to result from a conflict with the BIOS over the interval
between 'timer interrupts'. Windows maintains the clock by counting
these, so if the interval is not the expected one, the rate is grossly
out in this manner.

Try these steps:

1. Start->Run cmd.exe
2. net stop w32time
3. w32tm.exe /unregister
4. w32tm.exe /register
5. net start w32time


Dave

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"logized" <no-one@nowhere.com> wrote in message
news:cel0i2$kt5$1@hercules.btinternet.com...
>
> > > --
> > >
> > > Steve [Inglo]
> >
> > I sat with the BIOS open and a stopwatch, one minute equaled one
minute.
> > In windows, 1 real minute equals 1 min. 5 sec.
> >
> >
>
> A google search found this fix for problems where time is wrong ONLY in
> windows -
>
> If it is running fast while Windows is running, try this:
> It appears to result from a conflict with the BIOS over the interval
> between 'timer interrupts'. Windows maintains the clock by counting
> these, so if the interval is not the expected one, the rate is grossly
> out in this manner.
>
> Try these steps:
>
> 1. Start->Run cmd.exe
> 2. net stop w32time
> 3. w32tm.exe /unregister
> 4. w32tm.exe /register
> 5. net start w32time
>
>
> Dave
>
>
Yeah, I tried that at the time. I'm afraid it didn't help. I'm pretty sure
disabling the windows time "service" helps though.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

On 8/2/2004 8:15 AM Kill Bill brightened our day with:

>"logized" <no-one@nowhere.com> wrote in message
>news:cel0i2$kt5$1@hercules.btinternet.com...
>
>
>>>>--
>>>>
>>>>Steve [Inglo]
>>>>
>>>>
>>>I sat with the BIOS open and a stopwatch, one minute equaled one
>>>
>>>
>minute.
>
>
>>>In windows, 1 real minute equals 1 min. 5 sec.
>>>
>>>
>>>
>>>
>>A google search found this fix for problems where time is wrong ONLY in
>>windows -
>>
>>If it is running fast while Windows is running, try this:
>>It appears to result from a conflict with the BIOS over the interval
>>between 'timer interrupts'. Windows maintains the clock by counting
>>these, so if the interval is not the expected one, the rate is grossly
>>out in this manner.
>>
>>Try these steps:
>>
>>1. Start->Run cmd.exe
>>2. net stop w32time
>>3. w32tm.exe /unregister
>>4. w32tm.exe /register
>>5. net start w32time
>>
>>
>>Dave
>>
>>
>>
>>
>Yeah, I tried that at the time. I'm afraid it didn't help. I'm pretty sure
>disabling the windows time "service" helps though.
>
>
>
>
I wonder if it has anything to do with some of the extensible counters
windows runs.
And thanks for the info about how the BIOS clock is running.

--
Steve [Inglo]

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

On 8/2/2004 8:15 AM Kill Bill brightened our day with:

>"logized" <no-one@nowhere.com> wrote in message
>news:cel0i2$kt5$1@hercules.btinternet.com...
>
>
>>>>--
>>>>
>>>>Steve [Inglo]
>>>>
>>>>
>>>I sat with the BIOS open and a stopwatch, one minute equaled one
>>>
>>>
>minute.
>
>
>>>In windows, 1 real minute equals 1 min. 5 sec.
>>>
>>>
>>>
>>>
>>A google search found this fix for problems where time is wrong ONLY in
>>windows -
>>
>>If it is running fast while Windows is running, try this:
>>It appears to result from a conflict with the BIOS over the interval
>>between 'timer interrupts'. Windows maintains the clock by counting
>>these, so if the interval is not the expected one, the rate is grossly
>>out in this manner.
>>
>>Try these steps:
>>
>>1. Start->Run cmd.exe
>>2. net stop w32time
>>3. w32tm.exe /unregister
>>4. w32tm.exe /register
>>5. net start w32time
>>
>>
>>Dave
>>
>>
>>
>>
>Yeah, I tried that at the time. I'm afraid it didn't help. I'm pretty sure
>disabling the windows time "service" helps though.
>
>
>
>

Hey is your BIOS settings at auto or manual (are you overclocking)? I am.

--
The Brain From Planet Arous (1958):
"Bad alien Gor takes over scientist Steve's brain; good alien Vol takes over Steve's dog's brain."


Steve [Inglo]

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)

"Inglo" <ingloogoo@zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz.xcc> wrote in message
newsotPc.5570$AY5.3482@newssvr21.news.prodigy.com...
> On 8/2/2004 8:15 AM Kill Bill brightened our day with:
>> >news:cel0i2$kt5$1@hercules.btinternet.com...
> >>>I sat with the BIOS open and a stopwatch, one minute equaled one

> >minute.
> >>>In windows, 1 real minute equals 1 min. 5 sec.
> >>A google search found this fix for problems where time is wrong ONLY in
> >>windows -
> >>
> >>If it is running fast while Windows is running, try this:
> >>It appears to result from a conflict with the BIOS over the interval
> >>between 'timer interrupts'. Windows maintains the clock by counting
> >>these, so if the interval is not the expected one, the rate is grossly
> >>out in this manner.
> >>
> >>Try these steps:
> >>
> >>1. Start->Run cmd.exe
> >>2. net stop w32time
> >>3. w32tm.exe /unregister
> >>4. w32tm.exe /register
> >>5. net start w32time
> >>
> >>
> >>Dave
> >Yeah, I tried that at the time. I'm afraid it didn't help. I'm pretty
sure
> >disabling the windows time "service" helps though.
> Hey is your BIOS settings at auto or manual (are you overclocking)? I am.
>
> --
>
> Steve [Inglo]

Well, sort of. I call it "re-clocking". Running an 2400+ XP mobile chip at
200x12 vs. 133x14 default. So the FSB isn't o/c'ed but the CPU is. Memory
is PC3200....I think I reconfigured it stock once and saw no change but I
can't quite remember. I wasn't willing to give up my overclock anyway.