Actually I am not getting any beeps - which probably indicates
something serious going on. I am getting just two codes - first FF just
as i press the start button and secondly 01 after that.
The system was working properly - it hanged once and then never came
up. So no changes were made.
I just looked up the code for 01 for award bios - it seems that this
one generally refers to processor test - for example this one (i am not
yet able to find out exactly this v6.00PG version's post code)-
"(01) Processor test 1;Processor status(1FLAGS) verification; Tests the
following
processor status flags carr y, zero, sign, overflow. The BIOS will set
each of these
flags, verify they are set then turn each flag off and verify it is
off."
Does that mean my processor has died? Also if I remove the processor
and then see the code - it still is 01.
I still have two months warranty on the Mobo and the processor.
Unless one of the following situations existed, it is not
"likely" to be the processor. You might be that one person
in a million that had the CPU fail but I would assume that
is not the problem until you have exhaustively tried
everything else _and_ tried the suspect CPU in another
system known able to support it.
- Heatsink fan failed and it ran for several minutes like
this. It would lock up the system while running, definitely
not getting too hot only on the next attempt to start the
system in that few seconds.
- Heatsink came unlatched (for whatever reason, perhaps
prior installation stress on the socket lug attachment
point) such that it is no longer making contact with the
processor core. That should be fairly obvious, and in most
cases of extreme CPU overheating, the CPU would have a dark
discoloration on the back (pin side), dark enough that even
on a brown Athlon carrier it would be reasonably easy to
see. On the old ceramic athlons it might not be but we're
not talking about one of those.
- Severe motherboard failure damaged the CPU. Very
unlikely, a visual inspection of the motherboard would tend
to show something this bad, like a mosfet having shorted out
and slid down the board shorting copper pads that it
shouldn't.
- Extreme overclocking with high overvoltage setting. It
would be evidenced by constant very high temperature.
Otherwise a moderate overclock could eventually cause the
board to fail to POST, but returning the system to default
settings, stock CPU speed should allow it to run again.
If you hadn't yet, try clearing CMOS. Inspect the
motherboard, particularly the larger capacitors. Another
common culprit is the power supply, take voltage readings.
You might also strip the system down to only bare
essentials- CPU, 1 memory module, video, heatsink/fan.
Clear CMOS again (with AC disconnected of course).
The odds are that this is a power supply or motherboard
failure. That's no guarantee, but chasing post codes is
often fruitless because it only tells you where the POST
stopped, not what caused it to stop.
