WHEW!! Fixed It (was: What did BIOS 2205 do to my motherboard?)




"Ron Krebs" <rkrebs11@xxxxxxxxxxx> wrote in message
news:Xwkqi.16543$Nf4.3813@xxxxxxxxxxx
I have a P5WDH Deluxe and recently flashed to the 2205 BIOS. After
experiencing a good amount of crashes I found a website that lists all the
current and previous versions of ASUS mobo BIOS'. However, they removed
the 2205 "due to instability". I wish I would have seen this before I
flashed. So now I want to downgrade back to 2004 but no method of flashing
will allow this. I tried EZ Flash through the BIOS, but after it reads the
BIOS, it reports that it is older than current and will not allow the
flash. I tried Alt-F2, but after it found the BIOS on the floppy and read
it (said "Completed"), it just hanged. I tried ASUS update (the latest),
but it gave me a message that the eeprom was somehow incompatible with ANY
of the prior BIOS I tried. Then I tried an older version of Update but
after removing the current Update app, I couldn't even install an older
version. I got some sort of BIOSINFO error message. So after doing some
research, I found that some recommend clearing the CMOS, which I did, but
again same error messages. And yes, in ASUS update I had the downgrade
option ticked. I can't even go back to the original BIOS that came WITH
the motherboard. I have XP Pro SP2, E6600, 2GB DDR2, Radeon X1900XTX, 4 WD
Caviars in 2X2 SATA II RAID 0, and a single WD in JMicron AHCI IDE mode.
What in the hell is going on here? TIA,

Ron


Ok, I did some more googling on flashing the P5WDH to 2205 and found one
thread where some guy had exactly the same problems I did with the unknown
PCI device, etc. His solution was to reflash the BIOS with the same 2205
since anything prior to that was older and the process failed. BUT, the goal
here was NOT to flash to fix but to CORRUPT the BIOS!! IOW, he began the
flashing and just as the ROM was erased, he stopped the application (ASUS
Update) via the task manager and basically ruined the BIOS. He then
rebooted with the original CD in and was able to flash back to 0801. Well,
I don't need to tell you how scary that sounds, deliberately blasting your
BIOS to bits. I took a deep breath and stopped the flash process after the
progress indicator showed the ROM ERASED!! "Bang", "bang", "bang", "bang"
boomed out of my speakers and I nearly had a heart attack. I rebooted and
instead of the original CD, I used a floppy with the 2004 BIOS renamed to
P5WDH.ROM on it and crossed my fingers. It worked and I'm now back to 2004.
Btw, 2103 is botched too according to the poster from this website so take
heed. Thanks to all who responded.

Ron


.



Relevant Pages

  • Re: Need Help - Computer Only Operatres (limited too!) in Safe Mode
    ... The flash is a BIOS update provided by HP. ... floppy allow me to flash from DOS? ... I don't know where I would find a DOS flasher for my BIOS. ... Computer and pointer froze so I held the power button down ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Need Help - Computer Only Operatres (limited too!) in Safe Mode
    ... If you can't flash it out, you will probably need BIOS ... Computer and pointer froze so I held the power button down ... control panel and use another computer here to research this error message ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Random Restarts - Please Help
    ... the fan is working too and no unusual sounds at any re-starts.) ... About the only thing I have left to check is to see if my RAM is ... my BIOS. ... What ever happen don't interrupt the BIOS Flash procedure read on how ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Random Restarts - Please Help
    ... the fan is working too and no unusual sounds at any re-starts.) ... About the only thing I have left to check is to see if my RAM is ... my BIOS. ... What ever happen don't interrupt the BIOS Flash procedure read on how ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Strange BIOS behavior
    ... > before I could flash to 1.16. ... > and that bios chip was dead. ... Probing it with Asus Update only resulted ...
    (alt.comp.periphs.mainboard.asus)