This tiny chip almost had me with­out my com­put­er for at least a week.

It stores the BIOS, or Basic Input / Output System, in flash mem­o­ry on my moth­er­board. The very first thing that hap­pens when a com­put­er is boot­ed is the decom­press­ing of the BIOS into main mem­o­ry, which then ini­tial­izes the com­put­ers hard­ware com­po­nents, includ­ing crit­i­cal devices such as disk dri­ves and I/O ports. This allows a user to recieve feed­back (through video), input com­mands (through a mouse or key­board), and install or run oper­at­ing sys­tems (from a hard dri­ve).

Without a BIOS, none of this would be pos­si­ble. In the past, moth­er­board man­u­fac­tur­ers have made it a has­sle to fool around with the pro­gram burned onto the small chip, because improp­er steps in the repro­gram­ming process could poten­tial­ly ren­der the chip use­less. To update the BIOS, one would have to boot to DOS with a flop­py and run a flash pro­gram off the disk. Modern moth­er­boards now offer the flex­i­bil­i­ty to update through spe­cial soft­ware in Windows, although this process is nowhere near as sta­ble as run­ning through DOS.

Which is some­thing I had to learn the hard way last night.

Recent ran­dom reboot­ings had giv­en me rea­son to start run­ning the lat­est BIOS ver­sion. Unfortunately, I did­n’t have a flop­py dri­ve (I opt­ed not to buy one with my new com­put­er because I haven’t used a flop­py in years), which meant that I was stuck with the Windows flash soft­ware. The soft­ware hap­pened to crash at a very ear­ly part of the flash­ing process, which meant that I did­n’t even have basic boot­up code to get a dri­ve run­ning. At next boot — noth­ing. No BIOS POST beep, no screen sig­nal, no response from the key­board. I quick­ly pur­chased a flop­py dri­ve at the near­est deal­er, scram­bled to find a disk, put a boot sec­tor on it, but to no avail. There was­n’t even enough code burned onto the chip to get pow­er to the flop­py dri­ve.

Normally, when some­thing like this hap­pens, such as the pow­er going out or the flop­py being removed dur­ing a flash, the BIOS gets cor­rupt­ed and the chip is dead. The options are to get the moth­er­board RMA’d, which means send­ing the board back to the man­u­fac­tur­er before they send a new one back, or pur­chas­ing a new BIOS chip with a good BIOS image on it, which means spend­ing more mon­ey and wait­ing for a replace­ment. Both choic­es would take at least a week, if lucky.

Neither option was sat­is­fac­to­ry. I could­n’t wait until who-knows-how-long for some­thing to be sent back to me. Being with­out my com­put­er is like being with­out my com­fort zone, the place where I can lis­ten to music and write, play games to get away, com­mu­ni­cate with the rest of the world, or even work on my busi­ness with Aaron when I feel so inclined. I looked around the net for a faster solu­tion, and dis­cov­ered some­thing called hot flash­ing.

Unfortunately, faster also means riski­er. Hot flash­ing involves swap­ping two BIOS chips while the com­put­er is run­ning. All that’s need­ed is a healthy chip, an iden­ti­cal moth­er­board (which I have at work), a boot disk with appro­pri­ate flash­ing software/image, and nat­u­ral­ly, the cor­rupt­ed chip. A com­put­er is boot­ed to flop­py with a good BIOS chip, and after get­ting to a DOS prompt where a BIOS flash can be per­formed, the cor­rupt­ed chip is swapped and re-flashed. As a per­son who’s already squea­mish about run­ning a com­put­er with just a side pan­el miss­ing (in case water may hap­pen to splash into the case and cause a short, or a for­eign object falls in and jams a fan), this was an extreme­ly daunt­ing process. Playing around with chips while a com­put­er is hot means that there’s the risk of elec­tro­cu­tion, or short cir­cut that could per­ma­nent­ly dam­age the oth­er com­po­nents. Theoretically, after the BIOS is fin­ished run­ning, the board stops sup­ply­ing pow­er to the chip since it’s no longer need­ed.

I decid­ed to my faith in such a the­o­ry. Going on this faith meant that I could pry the chip out with a pair of mod­i­fied paper clips with­out hav­ing to wor­ry too much about caus­ing a short (spe­cial PLCC-sock­et tongs are avail­able, but rare, and would prob­a­bly take just as long to arrive after pur­chase as get­ting a new board). After a few prac­tice pulls, which, I dis­cov­ered, loosens the sock­et and gets pro­gres­sive­ly eas­i­er, I seat­ed the good chip with just enough pres­sure to make the con­nec­tions in the sock­et. After boot­ing suc­cess­ful­ly, I pried the chip off the board and ran the flash.

The first attempt was unsuc­cess­ful, and after try­ing to boot with a cor­rupt­ed BIOS, some­thing unex­plain­able hap­pened. The LED on the moth­er­board that shows that there’s a con­nect­ed pow­er sup­ply would­n’t go out. I pulled the pow­er plug, turned off the ATX switch, undid both the 24-pin EATX and 4‑pin 12-volt con­nec­tors, and even pulled out the CMOS bat­tery, but the light refused to turn off. My only guess was that the capac­i­tors still had enough ener­gy stored to keep the light on. After reset­ting the CMOS, and anoth­er hot flash attempt, the com­put­er boot­ed with the cor­rupt­ed chip run­ning the lat­est BIOS. My Windows instal­la­tion was fucked (it would­n’t even boot into safe mode), but after a recov­ery install, every­thing was up and run­ning again.

I was down for less than 24 hours.