2nd P4C800 killed?

[Odile Georgallides - Scheurer]

I was updating the BIOS of my P4C800 (1015->1016) using the latest ASUS
update utility in Win2K. The update freezed the machine at 26% complete. My
only choice was to reset it.
After the reset the system was completely dead.

I tried turning it on while pressing DEL, then ALT+F2, then INS, nothing
happens.
I tried to clear the CMOS, nothing.
The keyboard lights won't come on.
The green LED is lit on the motherboard.

I had another P4C800 go dead on me in the same manner some months ago.

I GETTING FED UP.
If there are such risks when using the ASUS update utility why doesn't ASUS
warn the users?
What can I do to recover the system, any ideas welcome.

Thanks a million.

 

[Guardian]

I was updating the BIOS of my P4C800 (1015->1016) using the latest ASUS
update utility in Win2K. The update freezed the machine at 26% complete. My
only choice was to reset it.
After the reset the system was completely dead.

Where did you download the 1016 bios for your P4C800 ? I do not see a bios
version greater than 1015 on the Asus web site.....however, there is a 1016
recently released for the P4P800... btw..... it's probably best to flash
your bios in a clean boot of DOS rather than Windows. I've read all too many
times where people do it in Windows and end up with problems afterwards.
Myself, I've done it in Windows without ever having a problem....I've always
made sure all running programs (virus scanners, utilities, etc) were shut
down prior to that.

 

[Odile Georgallides - Scheurer]

The file is available on ftp.asuscom.de and anyway its compatibility is
checked by the utility prior to the update.

If using ASUSupdate is so dangerous why aren't we warned?
Why does ASUS recommend using it rather than the DOS based version?

 

[DaveW]

Time for a new motherboard, I'm sorry to say. And, since you're just
thinking of this: Do NOT Upgrade The BIOS!

 

[Paul]

The file is available on ftp.asuscom.de and anyway its compatibility is
checked by the utility prior to the update.

If using ASUSupdate is so dangerous why aren't we warned?
Why does ASUS recommend using it rather than the DOS based version?

If you download the 1016c.zip file from ftp.asuscom.de, there is a
warning file entitled "flash.txt" inside the ZIP. It says to use

- ASUS LiveUpdate v5.23.01 or later
- ASUS AFUDOS v2.07 or later

Did you meet this requirement ? Note that a copy of AFUDOS is
included with the ZIP file.

Any time Asus fools with the "Boot Block", you lose the benefit
of "CrashFree". If the Boot Block is corrupted by the attempt
to flash, then there is no simple recovery procedure. On BIOS
releases where the Boot Block is not updated, then Crashfree
can be used.

Paul

 

[Stephan Collet]

In Nachricht

I was updating the BIOS of my P4C800 (1015->1016) using the
latest ASUS update utility in Win2K. The update freezed the
machine at 26% complete. My only choice was to reset it.
After the reset the system was completely dead.

I tried turning it on while pressing DEL, then ALT+F2, then
INS, nothing happens.
I tried to clear the CMOS, nothing.
The keyboard lights won't come on.
The green LED is lit on the motherboard.

Someone adviced me this and it worked for me well on similar problem:

| I had the same problem. I have found a solution for me.
|
| 1. copy on another pc the file P4C800ED.ROM of the asus-cd on an empty
| formatted diskette
| 2. remove now all hard disk cables of the motherboard and pci-cards but
| not the graphics card of the motherboard. The diskette drive cable may
| only and alone only be connected to the controller.
| 3. switch on the computer and you immediately push these to buttons <
| Ctrl+Home > (this is < Strg+Pos1>) for at least 4 seconds
| simultaneously now for again one. The Eprom should now find the file
| P4C800ED.ROM and feed these automatically.
| 4. turn off the PC after successful and after approx. 5 sec now.
| that 's all

You have to try this procedure several times!!!

 

[rstlne]

Someone adviced me this and it worked for me well on similar problem:

| I had the same problem. I have found a solution for me.
|
| 1. copy on another pc the file P4C800ED.ROM of the asus-cd on an empty
| formatted diskette
| 2. remove now all hard disk cables of the motherboard and pci-cards but
| not the graphics card of the motherboard. The diskette drive cable may
| only and alone only be connected to the controller.
| 3. switch on the computer and you immediately push these to buttons <
| Ctrl+Home > (this is < Strg+Pos1>) for at least 4 seconds
| simultaneously now for again one. The Eprom should now find the file
| P4C800ED.ROM and feed these automatically.
| 4. turn off the PC after successful and after approx. 5 sec now.
| that 's all

You have to try this procedure several times!!!

If the bios update went over the boot block then it wouldnt work..

 

[rstlne]

I had another P4C800 go dead on me in the same manner some months ago.


Why didnt U learn ur lesson then?

I GETTING FED UP.
If there are such risks when using the ASUS update utility why doesn't ASUS
warn the users?
What can I do to recover the system, any ideas welcome.

Thanks a million.

Your using windows (god forbid) to put a perm update into your hardware..
Anyone who has used windows should know that there is a large risk to it!..
Your going to need a new bios chip (or have yours reflashed)

 

[Tim]

Hi,

There are people who advertise / post to this news group bios fixing
services. You can also order replacement bios chips online.

If you have a really cooperative local h/w assembler / seller / geek they
may re-flash a chip for you. This is not an everyday task, so don't expect a
person without electronics skills to leap into this.

I suggest you gain a better understanding of the issues. If your system is
not running 100% then you should never use Windows to flash a bios chip. You
should resolve the issues first before updating the bios. Always read the
instructions first and always take the most cautious router when flashing.
It does sound like there is something else wrong with the motherboard /
configuration and you should resolve that post haste! When you get the board
back up and running, if you are experiencing any issues with reliability
post back here with an accurate defintion + details of your system as others
do and seek help...

Ignore the snooty posters... you have made a potentially expensive mistake
and no one will be more annoyed than you, so you don't need to be abused..
(Self confessed killer of 2 athlon XP chips).

- Tim

 

[Philip Callan]

(Self confessed killer of 2 athlon XP chips).

- Tim

Post that in a intel group and you wouldnt have to put it at the bottom