PC no longer booting

  • Thread starter Thread starter barrowhill
  • Start date Start date
SC Tom,

We've all made those mistakes...............Now get your head round this....

Last thought was perhaps PSU is after all faulty. Thinks......Somehow fires
up fans and fan lights come on but other wise does nothing. Fortunately
have spare so replaced. Note: new PSU tested and voltage measured off board
by shorting pins14 (Power Supply On) to Ground (COM). All Good.

Install main board molex connectors. Do not connect power to DVD's. Press
ON button ----- nothing ??? Old PSU starts fans/lights when ON button
pressed (?) . What's happening (?) Remove 20 pin molex, short pin 14 to
ground fans start and fan lights come on. Now my understanding is pin 14
(power supply on) is only active (low) when PSU receives motherboard OK
signal

Why should one PSU 'fire' up when ON is pressed and the other not??. Do I
have a faulty motherboard ?? I suspect I have but.......... some rational
behind what's happening with PSU's is welcome
 
barrowhill said:
SC Tom,

We've all made those mistakes...............Now get your head round
this....

Last thought was perhaps PSU is after all faulty. Thinks......Somehow
fires up fans and fan lights come on but other wise does nothing.
Fortunately have spare so replaced. Note: new PSU tested and voltage
measured off board by shorting pins14 (Power Supply On) to Ground
(COM). All Good.

Install main board molex connectors. Do not connect power to DVD's.
Press ON button ----- nothing ??? Old PSU starts fans/lights when ON
button pressed (?) . What's happening (?) Remove 20 pin molex, short pin
14 to ground fans start and fan lights come on. Now my understanding is
pin 14 (power supply on) is only active (low) when PSU receives
motherboard OK signal

Why should one PSU 'fire' up when ON is pressed and the other not??. Do
I have a faulty motherboard ?? I suspect I have but.......... some
rational behind what's happening with PSU's is welcome

I would start by checking whether you still had data cables connected
from the DVD. If you're going to disconnect a drive, it would be
better to disconnect both power and data. A data connector can be left
connected if an I/O pad is known as "failsafe", but we don't know whether
that is the case or not. So when the characteristics of a device are
unknown, it is best to disconnect both data and power to it at the same
time, just in case.

The motherboard has an open collector driver, to pull to ground the
PS_ON# signal (pin 14). The power supply end has a pullup, and it is weak and
easy for PS_ON# to overcome and pull to ground. A logic low level,
is what triggers the power supply into the ON state.

The front panel POWER button (soft power), gives a momentary low pulse
at logic levels. The front power button doesn't actually gate the
flow of power directly. It sends a logic signal to the motherboard.
The motherboard "latches" the front panel signal and converts in into
a steady level.

The motherboard logic has many inputs into that circuit.

1) The Southbridge and SuperI/O have a number of "Wake On" conditions,
that they accept and use to turn on the computer when you want to
wake it up. For example, if you enable "Wake On LAN" on your system,
when a LAN packet arrives, it asserts PME, which is then used to
(eventually) turn on PS_ON#.

2) Certain safety features on the motherboard, work in the opposite
sense. Modern motherboards (both AMD and Intel) have THERMTRIP.
If the processor asserts THERMTRIP during an overheat event,
the motherboard logic de-asserts PS_ON# immediately, and that
causes the power supply to go off.

Some of those safety features are "latching", and you must turn off
the main power switch on the back of the computer, before your next
attempt to turn on the computer again via the front (soft) power switch.

On some older Asus motherboards, the "AGP Warn" circuit did something
similar. It prevented power from coming on, when a 3.3V only video
card was inserted into a 1.5V only motherboard AGP slot. That would
not be a concern on a PCI Express motherboard.

When your system refuses to respond, you can see there are a couple kinds
of logic inputs, that are presented to the motherboard. There can also
be situations where "accidental" things happen. For example, on my old
440BX motherboard, if the IDE connector was installed crooked (only
half the pins touching), the resulting electrical stress on the
Southbridge would cause the power to come on, on its own, without
touching the button on the front of the computer.

On some motherboards, if the CMOS battery is flat, and reads zero volts
with a multimeter, that can prevent PS_ON# from working. A possible
theory is, it happens at the SuperI/O chip, as it can have a connection
directly to the CMOS battery. And in that case, perhaps the SuperI/O isn't
passing a logic signal from somewhere else on the motherboard, until
the battery is replaced.

The chip driving PS_ON# can become weak. Or, the power supply end
can do a poor job of dealing with the logic level on the PS_ON#
signal. The power supply doesn't use a logic chip, but can use a
discrete transistor circuit for the job.

The system is relatively complicated (and really deserves a better
treatment than I can give it).

The circuitry of this type, might be referred to as "Supervisory"
circuitry. On the motherboard, the +5VSB rail from the power supply,
powers the Supervisory circuits. If your power supply has a weak
or glitchy +5VSB, then that can cause problems turning on the computer.
On an Asus motherboard, they put a green LED on the motherboard wired
directly to +5VSB. On such a motherboard, you visually check that LED,
to make sure it remains lit as long as the switch on the back of the
computer is in the ON position. If that supply rail is overloaded
(+5VSB has a weak rating in amperes), the LED can go on and off rapidly,
or blink. And that would tell you that between the motherboard and
the power supply, something is happening to the ability to maintain
a steady 5V on the +5VSB (StandBy) rail. A weak supply can do that,
as could a short on +5VSB from say, a USB load or PS/2 load.

Paul
 
Paul,

Thanks for this reply. Performed re-test using both PSU's having first
checked, off board, both working and all connectors showing correct
voltages. Tested both with data and power connectors to 2 x DVD connected,
then again with data and power connectors disconnected.
Original fitted PSU powers up (well fan and fan lights at least) when ON
button pressed in both test cases. Spare PSU doesn't !!! (again in both
cases)

I can't think of any reason why this is the case as both tested fine off
board.

I've run out of ideas now in trying to resolve original problem other than
coming to conclusion that the moth board is faulty.
 
barrowhill said:
Paul,

Thanks for this reply. Performed re-test using both PSU's having first
checked, off board, both working and all connectors showing correct
voltages. Tested both with data and power connectors to 2 x DVD
connected, then again with data and power connectors disconnected.
Original fitted PSU powers up (well fan and fan lights at least) when ON
button pressed in both test cases. Spare PSU doesn't !!! (again in both
cases)

I can't think of any reason why this is the case as both tested fine
off board.

I've run out of ideas now in trying to resolve original problem other
than coming to conclusion that the moth board is faulty.

I hesitate to suggest this, but the PS_ON# signal can be activated,
while the main connector is connected to the motherboard. Since
PS_ON# is open collector, grounding it can turn on the supply and help
verify the rest of the motherboard is operational.

The problem with doing this, is it defeats safety systems on the
motherboard. For example, say your processor heatsink/fan fell of
the processor. On a normal computer, that would trigger THERMTRIP
(sent from processor to motherboard). The motherboard would
respond, by turning off PS_ON#. If you ground PS_ON# (effectively
jamming the setting in the ON position), then a THERMTRIP event
will not result in the power supply being turned off, and the processor
would be "cooked".

So using that test case, grounding PS_ON# while main power is connected,
can be used to verify the computer actually boots, but it does not
solve the problem of why the motherboard logic is not currently
driving the signal itself. As you say, it could be a defective
motherboard, but you also have to look at the circumstances, and
whether there were similar behaviors (difficult to get system
to turn on), before this happened.

*******

There are various versions of power supply standards, to help
you determine pinout on the cabling. While cable colors are
relatively standardized, I have at least one extension cable
here, that doesn't follow the rules on color. And when I'm using that
cable, I have to "count pins" to find the right signal.

http://web.archive.org/web/20030424...org/developer/specs/atx/ATX_ATX12V_PS_1_1.pdf (page 27)

http://www.formfactors.org/developer/specs/atx/ATX12V_1_3dg.pdf (page 30)

http://www.formfactors.org/developer/specs/ATX12V_PSDG_2_2_public_br2.pdf (page 37)

Paul
 
Paul,

Again thanks for the useful information.

I had thought about forcing /PS-ON but decided against doing this for
reasons you mention. As you concur, the motherboard could be a defective,
and, as you say, one needs to look at the circumstances, and whether there
were similar behaviors' (difficult to get system to turn on), before this
happened.

On this point, there was a problem with the USB KB and mouse (reason why I
was looking at PC). I'd got PC working (and updated) by virtue of using
PS/2 KB and mouse. As stated earlier, all working fine when switched off.
Having started up the following day, not with PS/2 KB and mouse attached but
with USB ones I got an immediate unrecoverable hardware error. I believe
this is the crux of the problem. I think connecting the USB devices tip the
scales on a pre existing problem and has finally zeroes the motherboard.

I think all avenues have been exhausted and a new motherboard (or PC) is
required. Thanks for your (and others) input on this. Much appreciated.
 
Do you by chance have another USB keyboard and mouse you can connect to the
faulty PC? Or have you tried that keyboard and mouse on a different PC?
Maybe it's one of them that's causing the issue, and not necessarily the
mobo (although I'm leaning towards a faulty mobo).
 
Back
Top