VOGONS


First post, by tony359

User metadata
Rank Member
Rank
Member

Hi all

I am curious about something. I've been working on some Asus P5P800-VM boards and as a "restoration" process I always read and write the BIOS back on the chip, to prevent bit rotting.

Those boards have all the same BIOS version but I've discovered there is always a small difference between them. Always in the same place.

Given the boards are the same model and revision and the BIOS is the same version, what could possibly be that difference?

Attached a screenshot of the different bits.

Thanks!

My Youtube channel: https://www.youtube.com/@tony359

Reply 1 of 10, by MagefromAntares

User metadata
Rank Member
Rank
Member

Hi,

As these bytes are near the string "System Serial Number", I think it is logical to assume that one of them is the serial number, there is also a "System Version" string nearby, so the another one might be an internal version number which might differ from the BIOS version number.

If I had to guess the serial number is the larger block and the version the smaller one.

Obviously this is only conjecture on my part, but it seems logical for these values to be near their description strings.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 2 of 10, by tony359

User metadata
Rank Member
Rank
Member

Interesting I didn’t know the bios contained custom data. But that means that if I flash the bios with a programmer I lose that data? I’ll se if there is a valid SN in that bios.

My Youtube channel: https://www.youtube.com/@tony359

Reply 3 of 10, by MagefromAntares

User metadata
Rank Member
Rank
Member

The serial number is there so they can track if a board gets sent back with an error to know which manufacturing line it was produced. It is encoded into the ROM because then it cannot be as easily tampered with as written text on the board.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 4 of 10, by aVd

User metadata
Rank Member
Rank
Member

Hi, Tony.
I'm not 100% sure, but those little differences could be due to different data stored in DMI tables.

SvarDOS fan :: artificial "intelligence" bots - not a fan at all :: say NO to systemd :: is freeware a lie, when human freedom is a fundamental lie? :: f00ck €u!

Reply 5 of 10, by MagefromAntares

User metadata
Rank Member
Rank
Member
aVd wrote on 2026-05-08, 11:25:

I'm not 100% sure, but those little differences could be due to different data stored in DMI tables.

That is a definite possibility, DMI tables can contain different information, including a serial number. If tony359 uses Linux a utility named dmidecode is most likely available in the distributions package repository and the data can be checked to match.

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 6 of 10, by aVd

User metadata
Rank Member
Rank
Member

Hi, @MagefromAntares,
And thanks for confirming my suggestion! I'm keeping too much "useless" information in my mind, so often I'm nor sure, if it's correct 😀

Do you know some useful tool (for Linux, DOS or windows), that can read/write DMI data in BIOS dump files?

SvarDOS fan :: artificial "intelligence" bots - not a fan at all :: say NO to systemd :: is freeware a lie, when human freedom is a fundamental lie? :: f00ck €u!

Reply 7 of 10, by MagefromAntares

User metadata
Rank Member
Rank
Member
aVd wrote on 2026-05-08, 12:36:

Do you know some useful tool (for Linux, DOS or windows), that can read/write DMI data in BIOS dump files?

dmidecode has a command line option --from-dump to specify a file, however I don't know if it works on normal BIOS dumps, it might only work on the dumps made by dmidecode itself (--dump-bin option).

"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune

Reply 8 of 10, by aVd

User metadata
Rank Member
Rank
Member
MagefromAntares wrote on 2026-05-08, 12:58:

dmidecode has a command line option --from-dump to specify a file, however I don't know if it works on normal BIOS dumps, it might only work on the dumps made by dmidecode itself (--dump-bin option).

Just tried it with the BIOS dump I need to change some motherboard's serial number, but it can not find any DMI or SMBIOS "entry point", and the DMI table is there. Anyway, thanks for suggestion!

SvarDOS fan :: artificial "intelligence" bots - not a fan at all :: say NO to systemd :: is freeware a lie, when human freedom is a fundamental lie? :: f00ck €u!

Reply 9 of 10, by EduBat

User metadata
Rank Member
Rank
Member

Another possibility is the Ethernet MAC address, which should be different from machine to machine.

Reply 10 of 10, by HwAoRrDk

User metadata
Rank Newbie
Rank
Newbie
EduBat wrote on 2026-05-08, 15:47:

Another possibility is the Ethernet MAC address, which should be different from machine to machine.

Hmm, doubtful. MAC addresses are 6 bytes, and neither of those differing blocks are 6 bytes (one 4 and one 8 bytes). Although, I suppose it's likely that the OUI (i.e. manufacturer prefix) in the first 3 bytes would be constant and not change. But we don't have that either, because in that case there'd be a block of 3 bytes that differed.