Flashed my BIOS

Recently, my Intel Matrix RAID BIOS started taking about a minute to initialize. I attributed this to having re-configured my drive arrangement and (possibly) having not reset a disk. My board is (was) an Asus that supports MyLogo, so I used the excuse of changing the boot logo to flash my BIOS, hoping this would correct the slow init of the Intel component.

The result was the loss of the BIOS data and CrashFree BIOS3 will not recover. The process just yields a a screen stuck at "Reading BIOS file P5BD.ROM"

I am now using an old socket 478 3.20E on a BioStar M900-M4 board.

The cool part - I had only recently grabbed the BioStar board from NewEgg for $26 (open box) and it arrived about an hour after I realized the Asus board was a goner.

Night Hawk said:

The board isn't what is toast! The bios should have been backed up first in case of a bad flash.

The solution for seeing that mess corrected would likely be shipping the board into Asus and have them reflash the bios with the latest version for a price along with S & H fees. The total would likely be about what you paid for the Biostar board you're running now at $25 plus.

The BIOS was, and remains, backed up. I cannot flash the chip anymore. My mistake was adding a JPEG to the MyLogo routine. I was supposed to use a BMP. It would have been nice if the MyLogo utility had refused to add such a large file. My bad, nonetheless. Asus informs me that they likely need to replace the CMOS chip. Or something like that.

It is interesting to play with this BioStar board. An old socket 478 with PCIe and DDR2 667 (PC5300) RAM running single channel. The board does strange things when a thumb drive is attached during boot.

I just noticed that someone modified my thread title.

I wrote "frashed" - flashed, fried, crashed.

Don't you guys make notations in threads where input has been modified?