![spi programmer for intel bios chip spi programmer for intel bios chip](https://i.ibb.co/f8Z6dgZ/OTJi-NTBl-Mj-Nj-Mj-Mx-ZDYz-Njlk-OGMz-NTFi-OTcx-YWUx-N2-Vi-NTg1-ZWU2-OTg4-NDEz-OWZi-Zj-Vl-Nz-Iw-MTA0.jpg)
I replaced the chips into the R5E and they are both posting nicely. DF44Editor showed that the newly cloned BIOS1 chip had correct MAC, UUID and S/N. The checksums of BIOS2 and BIOS1 matched. I erased the replacement chip, checked for blank, loaded the bin file from BIOS2 into the programmer buffer and wrote/verified to BIOS1 chip.
![spi programmer for intel bios chip spi programmer for intel bios chip](https://www.doxconnect.com/ebay/MSI_P6NSLI.png)
So to avoid problems with Windows authentication or any other system that uses those unique mobo identifiers, I used the SPI programmer to clone the contents of the OEM BIOS2 chip to the replacement BIOS1 chip. The chip from arrived flashed with latest BIOS vers 3701, however, DF44Editor revealed no settings for MAC, UUID and S/N.
#Spi programmer for intel bios chip serial#
Using a GQ-4x4 SPI programmer, I read the contents of the good BIOS2 chip into a bin file and used the DF44Editor program to verify the presence of my unique MAC address, motherboard serial number, and BIOS UUID (thanks to all who developed FD44Editor!). Device_ID was "FFFFFF" while it should have been "EF4018". My SPI programmer couldn't read Device_ID, Manufacturer or chip Device Type, which are always present from the chip manufacturer. To replace the corrupted BIOS1 chip, I was able to clone my good BIOS2 chip to a new BIOS1 chip that I ordered from They are both Windbond 25Q128FVIQ EEPROMs. It would enter an on/off post loop with Q-code “00”, a situation others have experienced. On my dual BIOS R5E, I used the COPY BIOS2 to BIOS1 command, which corrupted the BIOS1 chip. Sorry for my previous questions but I found a solution with help from the good technical info on the forum.