PC wont turn on after adding new cpu

D

dave xnet

Hello, I've seen many variations of this problem,
but none quite the same.

I upgraded from an AMD64 3200+ (singe core) to a
AMD64 4200 x2 (dual core) .

When I shutdown windows and later on try to start the pc,
the only thing that happens is the power LED lights up.
No fan, HD or other activity.
Power supply is an Antec Truepower 430W.

I'm using no add on cards, motherboard
audio,video and nic (Biostar geforce 6100 M9)
2 HD, 2 optical drives.

But if I switch off at the power supply, wait 10 seconds,
turn on again - it will now start normally from the front
switch as if nothing had happened.

What do you infer from this behavior?
Thanks,
Dave
 
F

Frank McCoy

Hello, I've seen many variations of this problem,
but none quite the same.

I upgraded from an AMD64 3200+ (singe core) to a
AMD64 4200 x2 (dual core) .

When I shutdown windows and later on try to start the pc,
the only thing that happens is the power LED lights up.
No fan, HD or other activity.
Power supply is an Antec Truepower 430W.

I'm using no add on cards, motherboard
audio,video and nic (Biostar geforce 6100 M9)
2 HD, 2 optical drives.

But if I switch off at the power supply, wait 10 seconds,
turn on again - it will now start normally from the front
switch as if nothing had happened.

What do you infer from this behavior?
Thanks,
Dave

I'd try a different power-supply myself.
Having a spare known-good PSU is *always* a good idea anyway.
 
D

dave xnet

I'd try a different power-supply myself.
Having a spare known-good PSU is *always* a good idea anyway.
Well this was a "known-good" PS until I put in this cpu about
3 weeks ago! Only 9 months old, possibly some warranty left,
(I'll have to check Antec's site)

In the meantime I have also sent an email to Antec tech support
and described the problem there - let's see what the response is.

The OEM cpu comes with a 30 day warranty of which there are about
5 days left. I may call that vendor to see if they have any idea.
I don't want to be in a situation where the PS is good and the cpu has
a problem, because the cpu 30 warranty period clock is ticking...

Thanks,
Dave H.
 
W

w_tom

Could be any part of the power supply system, or could be .... well
this is why numbers from a 3.5 digit multimeter are necessary to
obtain useful replies. Two minutes would answer your questions
immediately. Without those numbers, every suggestion will only be
speculation.

Two minute procedure was posted as "When your computer dies without
warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
at:
http://tinyurl.com/yvf9vh

In your case, most important are voltages on purple, green, and gray
wires before and when power switch is pressed; and immediately after
computer powers off in a 'no yet restartable' state.

What does that behavior imply? A power supply controller problem
which is another component of a power supply 'system'. Your responses
will only be as useful as information posted. Two minutes with a tool
that is sold even in K-mart.
 
F

Frank McCoy

Well this was a "known-good" PS until I put in this cpu about
3 weeks ago! Only 9 months old, possibly some warranty left,
(I'll have to check Antec's site)
The new CPU might have put extra stress on the PSU; causing it to fail.
And yes, I've seen power-supplies fail in far less time than that.

Like I said, I'd BUY a new power-supply; then, if the old one *is* bad,
I'd return it under warranty (though most warranties are only 90 days.)

If bad and warranted, then you'd have a good spare (which I recommend
anyway). If good, then you'd have a spare.

If bad and *not* warranted, I'd still recommend buying an extra one.
There's nothing as completely annoying as having a commonly fragile yet
comparatively inexpensive part (Like a power-supply) go bad when you
need it most and can't get to a store to replace the thing.
In the meantime I have also sent an email to Antec tech support
and described the problem there - let's see what the response is.

The OEM cpu comes with a 30 day warranty of which there are about
5 days left. I may call that vendor to see if they have any idea.
I don't want to be in a situation where the PS is good and the cpu has
a problem, because the cpu 30 warranty period clock is ticking...
I doubt VERY much if it's the CPU.
The motherboard itself would be far more likely; and I don't suspect
that either. Too many other suspects.

Video-board, Disks, memory ....
So *many* things that can make a PSU shut down in the manner you
describe.

But the power-supply is by *far* the most likely suspect; especially
after having installed a CPU that puts a much bigger load on it.

MY guess is that the PSU isn't exactly BAD, per-se; just a bit
underpowered for your new CPU.
 
D

dave xnet

Could be any part of the power supply system, or could be .... well
this is why numbers from a 3.5 digit multimeter are necessary to
obtain useful replies. Two minutes would answer your questions
immediately. Without those numbers, every suggestion will only be
speculation.

Two minute procedure was posted as "When your computer dies without
warning....." starting 6 Feb 2007 in the newsgroup alt.windows-xp
at:
http://tinyurl.com/yvf9vh

In your case, most important are voltages on purple, green, and gray
wires before and when power switch is pressed; and immediately after
computer powers off in a 'no yet restartable' state.

What does that behavior imply? A power supply controller problem
which is another component of a power supply 'system'. Your responses
will only be as useful as information posted. Two minutes with a tool
that is sold even in K-mart.

I took a look at the kmart website, since I 'm not familiar with
digital volt meters. Do you meen the Craftsman Digital Multimeter
with AC Voltage Detector for $24.99.
Kmart item# 9990000031937611 Mfr. model# 31937611

I'll pick one up today and post back in here.
 
D

dave xnet

The new CPU might have put extra stress on the PSU; causing it to fail.
And yes, I've seen power-supplies fail in far less time than that.

Like I said, I'd BUY a new power-supply; then, if the old one *is* bad,
I'd return it under warranty (though most warranties are only 90 days.)

If bad and warranted, then you'd have a good spare (which I recommend
anyway). If good, then you'd have a spare.

If bad and *not* warranted, I'd still recommend buying an extra one.
There's nothing as completely annoying as having a commonly fragile yet
comparatively inexpensive part (Like a power-supply) go bad when you
need it most and can't get to a store to replace the thing.

I doubt VERY much if it's the CPU.
The motherboard itself would be far more likely; and I don't suspect
that either. Too many other suspects.

Video-board, Disks, memory ....
So *many* things that can make a PSU shut down in the manner you
describe.

But the power-supply is by *far* the most likely suspect; especially
after having installed a CPU that puts a much bigger load on it.

MY guess is that the PSU isn't exactly BAD, per-se; just a bit
underpowered for your new CPU.
This is the thing - does the new cpu put a bigger load?
According to AMD's info they both consume 89W.

Is there someother "load"

Dave
 
B

Bob M

dave said:
Well this was a "known-good" PS until I put in this cpu about
3 weeks ago! Only 9 months old, possibly some warranty left,
(I'll have to check Antec's site)

In the meantime I have also sent an email to Antec tech support
and described the problem there - let's see what the response is.

The OEM cpu comes with a 30 day warranty of which there are about
5 days left. I may call that vendor to see if they have any idea.
I don't want to be in a situation where the PS is good and the cpu has
a problem, because the cpu 30 warranty period clock is ticking...

Thanks,
Dave H.

Is the motherboard an Asrock by any chance? I've had two of them in
the past. Anytime you make a change in BIOS settings or a major change
like you did the board requires you to switch off the PSU and then back
on again. Not sure if it's just a fluke with the boards or it's a built
in protection thing. I learned this by reading the overclockers forums
in the Asrock MB section. There may be other brands of boards that do
the same thing. I'm not sure. But if it's an Asrock it's working fine.

Bob
 
B

Bob M

dave said:
Well this was a "known-good" PS until I put in this cpu about
3 weeks ago! Only 9 months old, possibly some warranty left,
(I'll have to check Antec's site)

In the meantime I have also sent an email to Antec tech support
and described the problem there - let's see what the response is.

The OEM cpu comes with a 30 day warranty of which there are about
5 days left. I may call that vendor to see if they have any idea.
I don't want to be in a situation where the PS is good and the cpu has
a problem, because the cpu 30 warranty period clock is ticking...

Thanks,
Dave H.
Sorry. I just reread where I think you said it's a Biostar.

Bob
 
D

dave xnet

dave xnet wrote:
Sorry. I just reread where I think you said it's a Biostar.

Bob
Even if it's a BIOSTAR, I have to do this Everytime
the pc is shutdown restarted. You don't do this wth
yours do you ? That's madness.

Dave
 
F

Franc Zabkar

Hello, I've seen many variations of this problem,
but none quite the same.

I upgraded from an AMD64 3200+ (singe core) to a
AMD64 4200 x2 (dual core) .

When I shutdown windows and later on try to start the pc,
the only thing that happens is the power LED lights up.
No fan, HD or other activity.
Power supply is an Antec Truepower 430W.

I'm using no add on cards, motherboard
audio,video and nic (Biostar geforce 6100 M9)
2 HD, 2 optical drives.

But if I switch off at the power supply, wait 10 seconds,
turn on again - it will now start normally from the front
switch as if nothing had happened.

What do you infer from this behavior?
Thanks,
Dave

I have startup issues with an Athlon XP 2500+ in an ECS L7S7A2
motherboard. My original PSU was a 200W fake claiming to be a 400W.
Replacing it with a 350W Antec left me with exactly the same problem.
:-(

I suspect that something in my motherboard's standby circuitry doesn't
get initialised properly. There are two rails, +5VSB and +3.3VSB. The
latter is generated on the motherboard. Maybe the +3.3VSB doesn't come
up fast enough ??? Note that my problem only occurs after the AC power
is cycled. Once the machine has powered up successfully, you can shut
it down from the front switch and restart it as many times as you like
.... until you cycle the AC power again. Even then, the problem doesn't
always happen. When it does happen, I can nearly always get it to
start by powering off and on from the front switch. The reset switch
has no effect.

I suspect that there may be nothing wrong with your PSU. Instead it
could be the motherboard's standby circuitry that is at fault.

- Franc Zabkar
 
D

dave xnet

On Tue, 22 May 2007 07:51:06 +1000, Franc Zabkar

I have startup issues with an Athlon XP 2500+ in an ECS L7S7A2
motherboard. My original PSU was a 200W fake claiming to be a 400W.
Replacing it with a 350W Antec left me with exactly the same problem.
:-(

I suspect that something in my motherboard's standby circuitry doesn't
get initialised properly. There are two rails, +5VSB and +3.3VSB. The
latter is generated on the motherboard. Maybe the +3.3VSB doesn't come
up fast enough ??? Note that my problem only occurs after the AC power
is cycled. Once the machine has powered up successfully, you can shut
it down from the front switch and restart it as many times as you like
... until you cycle the AC power again. Even then, the problem doesn't
always happen. When it does happen, I can nearly always get it to
start by powering off and on from the front switch. The reset switch
has no effect.

I suspect that there may be nothing wrong with your PSU. Instead it
could be the motherboard's standby circuitry that is at fault.

- Franc Zabkar
Thanks for the info Franc.
My case is slightly different; it occurred after I upgraded the cpu.
Some have said well perhaps the load increased, but both cpu's
consume 89W according to AMD.

Also, mine occurs when ever the PC is shutdown.
If I recycle my AC, it works first time.

I sent a message to Antec to see if they have any clues.

Also left a message with the CPU vendor, but haven't heard
from them yet
I have purchased a digital multimeter and I'm going to measure
the voltages as mentioned in an earlier post.
Dave
 
D

dave xnet

Thanks I took a look at this

Picked up the meter in Kmart.

Here's the results, machine off, after using shutdown in windows:
purple 5, green 5 grey 0

I waited 5 minutes and without touching any buttons, tested again,
purple 5, green 5, grey 0

Pressed the front power switch, green power LED lights but
machine does not power on. Got these voltages as fast as I could
(within about 30 seconds anyway)
purple 5, green 4.9 grey 0

I'm not sure if I full understood your instructions regarding the
"when" to test- if I should do more, please let me know.
Likewise, if you see a glaring problem already.
Thanks very much -
Dave H.
 
D

dave xnet

Thanks I took a look at this


Picked up the meter in Kmart.

Here's the results, machine off, after using shutdown in windows:
purple 5, green 5 grey 0

I waited 5 minutes and without touching any buttons, tested again,
purple 5, green 5, grey 0

Pressed the front power switch, green power LED lights but
machine does not power on. Got these voltages as fast as I could
(within about 30 seconds anyway)
purple 5, green 4.9 grey 0

I'm not sure if I full understood your instructions regarding the
"when" to test- if I should do more, please let me know.
Likewise, if you see a glaring problem already.
Thanks very much -
Dave H.
I reset it at the back, then put the probe on the grey wire.
Pressed the front button, got 4.1V on the grey wire,
PC turned on.

Power supply bad?
 
P

Paul

dave said:
Thanks I took a look at this


Picked up the meter in Kmart.

Here's the results, machine off, after using shutdown in windows:
purple 5, green 5 grey 0

I waited 5 minutes and without touching any buttons, tested again,
purple 5, green 5, grey 0

Pressed the front power switch, green power LED lights but
machine does not power on. Got these voltages as fast as I could
(within about 30 seconds anyway)
purple 5, green 4.9 grey 0

I'm not sure if I full understood your instructions regarding the
"when" to test- if I should do more, please let me know.
Likewise, if you see a glaring problem already.
Thanks very much -
Dave H.

To help with the wire colors, you can get ATX power supply specs
from formfactors.org . The first two are for 20 pin supplies, and
will give you a historical perspective (i.e. what happened to pin 18).
The third one is for a 24 pin supply and is the most recent. You can
pick the spec that best matches what kind of supply you have.

http://web.archive.org/web/20030424...org/developer/specs/atx/ATX_ATX12V_PS_1_1.pdf
http://www.formfactors.org/developer/specs/atx/ATX12V_1_3dg.pdf

http://www.formfactors.org/developer/specs/ATX12V_PSDG_2_2_public_br2.pdf

The green wire is PS_ON# and when you push the front button, it should
drop from 5V to close to zero. Perhaps a value of 0.4V or so. That might
be a saturated transistor driving the line. So it appears the motherboard
is not sending PS_ON#.

So the question would be, what is gating (preventing) PS_ON# from going low ?
It is interesting that you say you "cycle the A.C." and the thing is then
startable. It implies that removing +5VSB and then making +5VSB available
again, is enough to clear the problem and allow PS_ON# to pass. A person
could blame the motherboard for this, except in situations where some
external influence upset the operation of the motherboard. I cannot
see the relationship between the new processor and old, which would
do this. (Unless the motherboard was mechanically damaged, or the
motherboard shifted and a mounting screw or standoff is shorting
something.)

The fact that your power LED comes on, on the front panel (?), says
the front panel LED is powered by +5VSB, and it also says that the
motherboard logic thinks it is driving PS_ON# active as well. In
other words, the decision to turn on the LED on the front of the
computer case, implies the motherboard also wanted the PS_ON# signal
to be active too.

In the spec, PS_ON# requires the motherboard driver to sink 1.6 milliamps.
Which is not really a lot of current, as drivers go. Pad drivers on logic
ICs, typically might have 8, 12, or 16mA drive, for general purpose I/O.
If there wasn't an open collector logic device available, Biostar could also
use a transistor, which could drive way more than that.

I downloaded the manual, and the section on "CPU overheat", describes
a function where the computer will not turn on - until the A.C. is
cycled. Maybe this is a "feature" ? (PDF page 20 - CRU51M9_0829C.pdf)
Again, it is a mystery as to why a change in processor, could lead
to this feature running amok.

http://www.biostar.com.tw/products/mainboard/board.php?name=GeForce 6100-M9
http://www.biostar.com.tw/products/mainboard/socket_939/geforce 6100-m9/m_geforce 6100-m9.exe

Just out of curiosity, what does the hardware monitor read for a CPU
temperature, when the motherboard does manage to run ? Is the temp
normal or is it out of whack (like 255C) ?

Paul
 
P

Paul

dave said:
I reset it at the back, then put the probe on the grey wire.
Pressed the front button, got 4.1V on the grey wire,
PC turned on.

Power supply bad?

The grey wire is PWR_OK. Since the power supply turned on, PWR_OK is
going high as a means of the power supply saying that all rails
are ready. That is pretty normal. We know your other situation is
abnormal, because no fans spin. Which means it isn't likely the grey
wire will rise from zero volts in that case - no fans, no +12V, no
reason for PWR_OK to be asserted.

Paul
 
W

w_tom

Picked up the meter in Kmart.

Here's the results, machine off, after using shutdown in windows:
purple 5, green 5 grey 0

I waited 5 minutes and without touching any buttons, tested again,
purple 5, green 5, grey 0

Pressed the front power switch, green power LED lights but
machine does not power on. Got these voltages as fast as I could
(within about 30 seconds anyway)
purple 5, green 4.9 grey 0

I'm not sure if I full understood your instructions regarding the
"when" to test- if I should do more, please let me know.
Likewise, if you see a glaring problem already.

A meter should be reporting at least three digits. Reason why an
analog meter is insufficient: we need more than one digit. If only
one digit displayed, then the meter switch should be switched to 20
volt DC range. 0 could be OK or too high. Is zero 0.2, 0.6, or 0.75?

Assuming those numbers are 5.00, 4.90, 0.00, etc: When power switch
is pressed, then power supply controller should drop green wire
voltage to near zero (well below 0.80 volts). Power supply controller
is not telling power supply to power on if voltage remains well above
2 volts.

Power supply controller has to inputs: power switch and purple
wire. Purple wire remaining at 5.00 volts is OK. Now connect meter
to two points where power switch connects to motherboard. Voltage
between those two points should measure something less than 5.00
volts. When switch is pressed, then that voltage should drop to zero
(well less than 0.80 volts). If yes, then other power supply
controller is getting good inputs. We move on.

If both power supply controller inputs are OK, then power supply
controller is somehow defective OR something inside power supply is
creating so much current as to hinder (overwhelm) the controller's
'Power On' request. Final test is to use meter in current mode. This
typically means moving a lead from the Volt-Ohm hole to the Ampere
hole; and setting meter in a maximum current range (2 amps?).

Remove AC power cord. Then disconnect that 20 something pin
connector and other power connector (near CPU) from motherboard.
Attach meter leads to green and any black wire. Restore AC power to
power supply. Power supply will probably power on fans, disk drive,
etc

Now slowly reduce meter range switch so that zero increases to a
useful multidigit number. If that current is less than 0.01 amperes
(10 milliamps), then power supply is not overwhelming power supply
controller output - a good condition. Therefore problem is isolated
to the power supply controller located on motherboard.

Sidenote. Note when purple wire is and is not at 5 volts. Only
time you can add or remove hardware is when purple wire is zero
volts. That means removing power cord from power supply or AC wall
receptacle every time before making any changes. When power cord is
restored, then safety circuits on power supply controller are reset.
IOW if green wire responds to power switch right after power cord is
reconnected, then one possible suspect is the 'reset' safety lockout
circuit inside power supply controller. Removing and reconnecting
power cord resets that safety lockout circuit.

Learn what does and does not permit power switch to cause green wire
voltage to drop below 0.8 volts. Is it an intermittent switch? Does
purple wire voltage sometimes dip slightly below 5.00 volts? Or does
green wire drop for only one second after power switch if pressed?
Symptoms, when posted here, may also result in more useful
information.
 
D

dave xnet

To help with the wire colors, you can get ATX power supply specs
from formfactors.org . The first two are for 20 pin supplies, and
will give you a historical perspective (i.e. what happened to pin 18).
The third one is for a 24 pin supply and is the most recent. You can
pick the spec that best matches what kind of supply you have.

http://web.archive.org/web/20030424...org/developer/specs/atx/ATX_ATX12V_PS_1_1.pdf
http://www.formfactors.org/developer/specs/atx/ATX12V_1_3dg.pdf

http://www.formfactors.org/developer/specs/ATX12V_PSDG_2_2_public_br2.pdf

The green wire is PS_ON# and when you push the front button, it should
drop from 5V to close to zero. Perhaps a value of 0.4V or so. That might
be a saturated transistor driving the line. So it appears the motherboard
is not sending PS_ON#.

So the question would be, what is gating (preventing) PS_ON# from going low ?
It is interesting that you say you "cycle the A.C." and the thing is then
startable. It implies that removing +5VSB and then making +5VSB available
again, is enough to clear the problem and allow PS_ON# to pass. A person
could blame the motherboard for this, except in situations where some
external influence upset the operation of the motherboard. I cannot
see the relationship between the new processor and old, which would
do this. (Unless the motherboard was mechanically damaged, or the
motherboard shifted and a mounting screw or standoff is shorting
something.)

One thing did happen during the course of the cpu transplant.
There are 4 or 5 capacitors in a row next to the heatsink/fan
The side of my hand accidentally applied a little pressure to the one
on the end of the row when I was negotiating with the HSF retaining
clips.
It seems so minor that I had all but dismissed it.
Perhaps I dislodged or loosened one of it''s connectrs
I can check it, but I'll have to remove the motherboard and look at
the back - perhaps resolder it.
The fact that your power LED comes on, on the front panel (?), says
the front panel LED is powered by +5VSB, and it also says that the
motherboard logic thinks it is driving PS_ON# active as well. In
other words, the decision to turn on the LED on the front of the
computer case, implies the motherboard also wanted the PS_ON# signal
to be active too.

In the spec, PS_ON# requires the motherboard driver to sink 1.6 milliamps.
Which is not really a lot of current, as drivers go. Pad drivers on logic
ICs, typically might have 8, 12, or 16mA drive, for general purpose I/O.
If there wasn't an open collector logic device available, Biostar could also
use a transistor, which could drive way more than that.

I downloaded the manual, and the section on "CPU overheat", describes
a function where the computer will not turn on - until the A.C. is
cycled. Maybe this is a "feature" ? (PDF page 20 - CRU51M9_0829C.pdf)
Again, it is a mystery as to why a change in processor, could lead
to this feature running amok.

http://www.biostar.com.tw/products/mainboard/board.php?name=GeForce 6100-M9
http://www.biostar.com.tw/products/mainboard/socket_939/geforce 6100-m9/m_geforce 6100-m9.exe
I saw this, it says either remove the power line or reset the cmos.
But is it safe to reset the CMOS while the power line is attached?
If not, surely one implies the other.
if it is I'll try this/
Just out of curiosity, what does the hardware monitor read for a CPU
temperature, when the motherboard does manage to run ? Is the temp
normal or is it out of whack (like 255C) ?
The items I've looked at to check temps are in the Bios PC Health
page.
Also a program called Aida32, which I think is an earlier version of
Everest. The idle temps are about 34C, while about 46 under load.
I've touched the side of the HSF it's generally cool to the touch.
It is certianly making contact with the processor.
I don't see the cpu overheating, perhaps the sensor is bad?
aida32 doesn't report this. What else can I check it with?

I don't have the necessary expertise, knowledge or experience to do
much more of this diagnosis that you and w_tom have suggested.

At this point, I'm getting ready to put back the old cpu and see if it
still occurs. If it does, at least then I'll know that either the
mobo or power supply is bad( I think)
However, what if I put in the old cpu and it's working
perfectly?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top