MoBo Probs?

  • Thread starter Thread starter LMO
  • Start date Start date
L

LMO

Aloha all. Sometimes when I hit the power button I only get a blip, but no
power. Takes maybe 20-30 presses to power up. Clock no longer keeps time. I
have to set every bootup. USB ports act funny. I'm thinking my 3 y/o MoBo my
be dying. Anything else I might check before istalling a new MoBo and chip?
Thanks!
 
Aloha all. Sometimes when I hit the power button I only get a blip, but no
power. Takes maybe 20-30 presses to power up. Clock no longer keeps time.
I have to set every bootup. USB ports act funny. I'm thinking my 3 y/o
MoBo my be dying. Anything else I might check before istalling a new MoBo
and chip?
Thanks!

Start with changing the battery on the motherboard. It's a small coin sized
unit held in place by a clip. The repeated power up issue could be an
indication of a problem in the power system. That could mean the power
supply or other circuitry for it.
 
LMO said:
Aloha all. Sometimes when I hit the power button I only get a blip, but no
power. Takes maybe 20-30 presses to power up. Clock no longer keeps time.
I have to set every bootup. USB ports act funny. I'm thinking my 3 y/o
MoBo my be dying. Anything else I might check before istalling a new MoBo
and chip?
Thanks!

1 or 2 things may going on. Power supply is degrading, or something on the
motherboard or attached devices is eating more current (degrading).

Rock told you about the keep alive cmos battery on the board.

Dave
 
Except the clock loses time even while the system is on. Would that still be
a battery problem?
 
Except the clock loses time even while the system is on. Would that still be
a battery problem?


No. It can *not* be the battery, because the battery isn't used while
the computer is running.

If the clock loses time while running, try this:

Open a command prompt window (Start | Run | cmd) and enter the
following commands:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
 
Except the clock loses time even while the system is on. Would that still
be a battery problem?

"Rock" wrote

Two separate problems. Start with replacing the battery since it looses
time when not turned on. Is there a reason you are reluctant to do this?
See Ken's reply for the problem when it is running.
 
I'm not reluctant to do this. Just want to fix the right problem. I just
installed my old MoBo in a new case and put in a new video card ($400).
Still have the startup prob and clock prob. Now the shop is saying I need a
new MoBo and processor, because that's the root of all these problems...at
$800+. So before I start nickel and diming things, I want to be sure what
the prob is.
Thanks.
 
Two separate problems. Start with replacing the battery since it looses
time when not turned on. Is there a reason you are reluctant to do this?
See Ken's reply for the problem when it is running.



Does it lose time both while running and while powered off? Sorry, I
missed that. That's unusual, but as you say, there could be two
separate problems, so I echo what you say about also replacing the
battery.
 
I will be sitting at the computer and close a program, and the time will go
back 2 hours. Or if idle, when going in to screensaver, the time will stay
at the time when the screensaver activated.
 
LMO said:
I will be sitting at the computer and close a program, and the time will go
back 2 hours. Or if idle, when going in to screensaver, the time will stay
at the time when the screensaver activated.

Trouble-shooting is an exercise in logic and a lesson in patience. Take
one problem at a time. A CR2032 CMOS battery is relatively inexpensive
and easy to replace. Rule out this component as a source of the problem
as each step does get more difficult or more complex via the piecemeal
disassembly and reassembly of a complete computer system.
 
Back
Top