Actually, the original method, equipment and microcodes can be found (directly the AMI instructions), and in most cases, using this method does not pose any problems and has no pitfalls, but in my practice I regularly encountered the following problem:

Those. there was a banal lack of free space inside the image. When you modify the BIOS for yourself for a specific processor, you can ignore this, because You can always load just one microcode specifically for your processor, or delete some old microcode to free up space, but when you modify with a stream, you need to look for another solution, a compromise.

As a compromise, I chose the following solution - we take the latest versions of microcodes for all processors of the CORE generation in all designs (Celeron E, Pentium E, Core 2 Duo, Core 2 Quad, Xeon *3xxx/*5xxx) and replace with them everything that was before . The set of microcodes turned out to be as follows:

The volume of this set is only 76 kilobytes. This file was obtained by combining these files:

cpu00010676_plat00000001_ver0000060f_date20100929.bin
cpu00010676_plat00000004_ver0000060f_date20100929.bin
cpu00010676_plat00000010_ver0000060f_date20100929.bin
cpu00010676_plat00000040_ver0000060f_date20100929.bin
cpu00010677_plat00000010_ver0000070a_date20100929.bin
cpu0001067a_plat00000011_ver00000a0b_date20100928.bin
cpu0001067a_plat00000044_ver00000a0b_date20100928.bin
cpu000006f2_plat00000001_ver0000005d_date20101002.bin
cpu000006f6_plat00000001_ver000000d0_date20100930.bin
cpu000006f6_plat00000004_ver000000d2_date20101001.bin
cpu000006f7_plat00000010_ver0000006a_date20101002.bin
cpu000006f7_plat00000040_ver0000006b_date20101002.bin
cpu000006fb_plat00000001_ver000000ba_date20101003.bin
cpu000006fb_plat00000004_ver000000bc_date20101003.bin
cpu000006fb_plat00000010_ver000000ba_date20101003.bin
cpu000006fb_plat00000040_ver000000bc_date20101003.bin
cpu000006fd_plat00000001_ver000000a4_date20101002.bin

The modification procedure itself has also changed a little and has become, if not easier, then faster:

Step 1— open the BIOS image in the MMTool program:

Step 2— to check, go to the last tab (CPU PATCH) and look at the number of microcodes. Here, for example, there are 31 of them:

Step 3— go to the Replace tab and look for the “P6 Micro Code” item on it:

Step 4— having selected the “P6 Micro Code” item, press the Ikshtsyu button, select the ncpucode.bin file described above and replace it with the Replace button:

Step 5— to check, go to the last tab (CPU PATCH) and look at the number of microcodes. After replacing the microcodes, 17 remained, the latest version:

There is no fundamental difference with the modification procedure described on delidded.com. In most cases, the output is certainly not the same, but the processor receives the necessary microcode. Of the subjective positive aspects, I would only like to draw attention to the fact that the microcodes for all current processors are guaranteed to be updated, be it “civilian” or “server”, and there is practically no risk of receiving a message about lack of space. Although, in my practice, even for such a set of microcodes there was not enough space a couple of times, this was with the BIOS for the ECS P4M900T-M and ECS P4M900T-M2 boards, which are generally compatible with the Xeon E5450.

By tradition, I publish a link to the archive with tools - (zip, 234KB). The archive contains an executable file MMTOL.exe(version 3.22 BKMOD), file with microcodes for all 45/65nm processors of the core/xeon generation ncpucode.bin, as well as two files 45nm.bin And 65nm.bin with microcodes only for 45nm processors and only for 65nm. The use of these files can be useful in cases where it is necessary to free up additional space in the BIOS, for example, for new firmware of some controller, network, disk, etc.

!NB: Neither the ncpucode.bin file nor the 45nm.bin/65nm.bin files support Pentium 4, Celeron (without letter suffixes), Pentium D, Celeron D and Xeon W processors (Xeon 5080 for example). These are NetBrust generation processors.

Oh, guess the riddle: standing there, the hive is buzzing. But there is no smoke coming out of the chimney, because this is not a native factory, but a computer on which the BIOS is damaged. And he hums because that’s all he can do now. Without the BIOS, it's just a bunch of lifeless hardware. Is this worth worrying about? Of course not. After all, now you have a great bedside table!

System unit as a bedside table? Well, I do not! We know how to make it work. Today we’ll talk about how to restore the BIOS if it crashes.

What causes the BIOS firmware to crash?

There are not too many reasons for BIOS damage; in some cases they are obvious, in others they are not. Here is a list of the most common:

• During this time, the computer's power supply was cut off.
• The flasher program does not interact correctly with the firmware or flash memory chip.
• A BIOS version has been flashed that is not suitable for this motherboard. Yes, .
• If the update is carried out from a running operating system, there may be a system failure or software interference, for example, blocking by an antivirus.
• Incorrect user actions, for example, restarting the computer before the update installation is complete.
• Failure of the flash memory chip.
• Hidden BIOS firmware errors. Sometimes this explains spontaneous “gatherings” that occur for no apparent reason.
• Electrical problems with the motherboard.

How BIOS damage manifests itself

• When you press the PC power button, only the cooler is turned on, which immediately begins to rotate at maximum speed. Sometimes the LED indicators on the case and keyboard light up.
• One or several seconds after switching on, a cyclic reboot begins. Outwardly, this is manifested by a cycle of spinning up and stopping the cooler, which is repeated as long as power is supplied.
• When turned on, the power indicator lights up, the cooler does not spin.
• The computer shows no signs of life. This happens when the boot block, the BIOS bootloader, is damaged. This is the most difficult case.

There is no image on the screen. Even the manufacturer's screensaver does not appear.

There are also other forms of damage to the BIOS, more precisely, to its area that stores the configuration of the ME controller (an integral part of the chipset) on boards that work with Intel processors - the so-called ME region. If there is a problem in this area, the computer or laptop may:

• It won't load correctly or won't turn on at all.
• Shut down or restart at regular intervals.
• It is incorrect to regulate the rotation speed of the cooler, for example, turning it at high speeds regardless of the load.

Eliminating such failures involves reading a BIOS dump, replacing the ME region with a clean one, and re-flashing it using a programmer. Since this is usually done by repairmen, and not by computer owners, we will not dwell on this. It’s better to do what can be done at home without special equipment and the risk of finally sending your “iron pet” to the kingdom of eternity.

Restoring the BIOS without a programmer is only possible if you save the boot loader. It is sometimes possible to determine whether it has been preserved or not by indirect signs: blinking of the screen backlight, sound signals from the system speaker, the reaction of the motherboard to turning on without RAM (with sound or blinking indicators), etc. If the BIOS bootloader is intact, the first moments of operation computers run fine, the failure appears a little later.

How to restore functionality to a motherboard with a crashed BIOS

Asus

After downloading the firmware you need to rename it. For example, the file “Sabertooth X79” (model name) is renamed to “SABERX79.ROM”, the file “Sabertooth Z77” is renamed to “Z77ST.CAP”. Information on what the firmware file for your model should be named is most likely on the Asus website, but if you don’t find it, check on the forums or in support.

Next, save the renamed BIOS on a flash drive formatted in FAT32 and connect it to the USB port marked “ Flashback" or " ROG Connect" It is advisable to turn off the computer before this, this will increase the chance of successful recovery.

After connecting the flash drive, turn on the PC and press the “ BIOS" Hold it down for about 3 seconds until the indicator light on the board starts flashing. Blinking indicates that the file has been successfully read and is being flashed into memory. When the firmware process is completed, the indicator will turn off.

If your board is from the budget segment or is not very new, that is, it does not support USB Flashback, most likely you can restore it in another way. If your computer has a floppy drive or optical drive, write the renamed BIOS file to the root directory of a blank floppy disk or CD, place it in the drive, turn off and then turn on the PC. The firmware will be completed when the drive indicator goes off. If there is no drive, use a flash drive.

Gigabyte

Problems with starting a board with Dual_BIOS are possible in the following cases:

• The main chip is missing or faulty.
• The microcode in the main chip is completely erased.
• The contents of both microcircuits are damaged.

Some Gigabyte motherboards can boot from backup flash memory and use it as the main one. Another group of boards from this manufacturer uses a dedicated area on the hard drive as BIOS backup media. This is a less reliable option, but still better than nothing.

Restoring the Gigabyte BIOS from a backup is usually performed automatically, but if this does not happen, try turning off the computer from the outlet, wait a little and turn it on again.

MSI and others

On motherboards from MSI and some other brands that are more than 8-10 years old, flashing the BIOS is done from a floppy disk. The instructions for AWARD and AMI BIOS are slightly different.

To restore the AMI BIOS, do the following:

• Rename the BIOS file downloaded from the motherboard manufacturer's website to AMIBOOT.ROM.
• Transfer it to the root of a blank floppy disk. Place the floppy disk in the drive of the switched off PC.
• Press left Ctrl + Home on your keyboard and turn on your computer.

To restore AWARD BIOS:

• Place the firmware and BIOS files on a floppy disk (usually downloaded in one archive).
• Create a text document on a floppy disk that specifies the name of the BIOS file with the bin extension. Rename the document to autoexec.bat.
• Further actions are similar to those above.

By the way, some motherboard manufacturers post BIOSes on their websites only in exe format - in “one bottle” with a firmware program for updating from Windows. Sometimes such a file can be unpacked as an archive, but users often do not understand which of its contents is firmware. There is no universal solution for such problems. In order not to aggravate the problem, it is better to consult specialized forums or the manufacturer’s technical support.

On some boards, before restoring the BIOS, you also need to remove the real time clock (RTC) battery from the socket or reset (remove) the CMOS clear jumper. It is important to clarify these points before starting the procedure.

Features of BIOS recovery on laptops

The method for restoring a crashed BIOS on laptops is approximately the same as on desktops. The firmware file and flashing program downloaded from the manufacturer’s website (the latter is not always needed) are placed on a clean flash drive formatted in FAT32/16, connected to a de-energized device (simply turning off the laptop is sometimes not enough, you need to disconnect the power supply and remove the battery), insert a charged place the battery in place, turn on the device and press the key combination. Different laptops use different keyboard shortcuts for this, for example:

• Ctrl (left only or both) + Home
• Windows + B (this and other letters are given in the Latin layout)
• Windows + F
• Windows+M
• Windows + Esc
• Fn+B
• Fn+F
• Fn+M
• Fn+Esc.

The main job is to unpack and rename the BIOS files. Again, there is no single rule here. In most cases, you have to get the firmware from exe files, but! Many manufacturers include BIOSes for different revisions of one platform or a whole series of platforms, and choosing the only necessary file from them can be very difficult. To avoid mistakes, read the instructions for flashing the firmware of your particular model and platform revision on specialized forums. And don't be shy to ask questions.

How to extract Dell BIOS files?

Copy the BIOS.exe file to drive C:
Run Command Prompt in Administrator mode and write this:

cd\
bios.exe /writeromfile
bios.exe /writebinfile
bios.exe /writehexfile

» bios.exe is a file downloaded from the Dell website. "

The unpacked bios file will be copied to drive C:!

Unpacking the new Dell BIOS.

• Download the Python 2.7 interpreter.
  https://www.python.org/download/releases/2.7/
• Install Python 2.7 on your computer (exactly this version!).
• with Python script - DecompNewDell.py.
• Copy the DecompNewDell.py script extracted from the archive to the folder with the Python interpreter (usually C:\Python27).
• We also copy our downloaded bios from the dell website to the folder with the interpreter (usually C:\Python27). Rename it to biosupdate.exe. It should look like the photo below.

• Launch the Windows command line in administrator mode and write this:

cd\
cd Python27
python DecompNewDell.py biosupdate.exe

It should look like the photo below.

And in the folder with Python (usually C:\Python27), the file biosupdate.exe_decompressed.hdr will appear.

• with the PFSExtractor.exe program, extract the program to the same folder where we created the .hdr file (usually C:\Python27).
• On the Windows command line we write:

PFSExtractor biosupdate.exe_decompressed.hdr

It will turn out like in the photo below.

And the folder biosupdate.exe_decompressed.hdr.extracted will be created, inside which there are all extracted files from which you can collect a dump for flashing the firmware on the programmer. Ready!