A technician verifies an MB-760X motherboard revision and checks its support page and drivers at a workbench.
Knowing which motherboard is in your PC takes about a minute. Skipping the check is how people end up flashing a BIOS file meant for a different board. This guide covers the built-in tools on Windows, Linux and macOS, what to do when they return junk, and how to match the result to the right support page.

A technician verifies an MB-760X motherboard revision and checks its support page and drivers at a workbench. Why the exact model matters​

Microsoft's support guidance says there is no single "latest BIOS" for Windows 11. Firmware belongs to a specific manufacturer, model and board, and the wrong file can leave a machine unable to start. A vague description like "an Intel board from a few years back" doesn't help. You need the vendor, model and, where relevant, revision before you touch a BIOS download, a memory compatibility list or a chipset driver.

The same identifiers matter in four common situations:

  • Upgrades: a new CPU or memory kit only works if the board and its firmware support it.
  • Troubleshooting: stability bugs are often fixed in a board-specific BIOS release.
  • Security: vendors list affected products by model in their advisories.
  • Resale or warranty: a buyer or support agent will ask for the exact model first.

Where the data comes from​

Windows, Linux and macOS all read the same firmware tables, SMBIOS (System Management BIOS). DMTF maintains the specification as DSP0134. The older name DMI survives in Linux paths such as /sys/class/dmi/id and in the dmidecode tool's name.

The firmware maker fills these tables in, so quality varies. Some boards ship with factory placeholder text. Virtual machines report the hypervisor instead of real hardware. SMBIOS also doesn't guarantee a dedicated chipset field, so you can't count on any tool to name the chipset.

One version correction to the source guide: it calls SMBIOS 3.8.0 the latest release. DMTF's SMBIOS page lists version 3.10.0 as the current standard, dated 07 Sep 2026. Its specification document says 3.10.0 supersedes 3.9.0. You don't need a particular version to read your board model, but anything calling 3.8.0 "the latest" is out of date.

Step 1: Decide whether the PC is prebuilt or custom​

This decides which name you search for.

  • Custom build: the board came from a board maker. Search the board vendor, model and revision.
  • Prebuilt desktop or laptop (Dell, HP, Lenovo, Acer and similar): the board was made for that system maker, who supports the machine as a whole. Search the system model, or the service tag, not the board code.

Check the sticker on the chassis or the bottom of a laptop, then the receipt or order page. Write down one line, such as "prebuilt, vendor, sticker text". Most laptop boards aren't sold separately, so for a laptop, search the full model from the sticker. Use the board code only as a cross-check. A mismatch between the label and the software can point to a replaced board or a refurbished unit.

Step 2: Windows System Information (msinfo32)​

  1. Press Windows+R, type msinfo32 and press Enter.
  2. On System Summary, read BaseBoard Manufacturer, BaseBoard Product and BaseBoard Version, if your system shows them. Also note System Manufacturer, System Model and BIOS Version/Date.

Microsoft describes this tool as gathering information about your computer and showing your hardware, system components and software environment. Two caveats from Microsoft:

  • Run without administrator privileges, it may show some drivers as stopped when they are not. That matters for driver status, not for board identification.
  • It can't provide hardware information in Safe Mode. If the board rows are missing, check whether you booted into Safe Mode.

You can also save a text report from the command line. Microsoft documents msinfo32 /report followed by a path, and /nfo for an .nfo file. For example, msinfo32 /report "%USERPROFILE%\Desktop\sysinfo.txt" writes the summary to a text file. Search the file for "BaseBoard". Remove serial numbers and your user name before sending it to anyone.

System Information is not a reliable source for the chipset. Don't read the chipset from this window.

Step 3: PowerShell​

PowerShell returns the same values in a copyable form. Use the CIM cmdlets, not the deprecated wmic:

Code:
Get-CimInstance Win32_BaseBoard | Format-List Manufacturer, Product, Version, SerialNumber
Get-CimInstance Win32_BIOS | Format-List Manufacturer, SMBIOSBIOSVersion, ReleaseDate
Get-CimInstance Win32_ComputerSystem | Format-List Manufacturer, Model

Microsoft's documentation says the Win32_BaseBoard class represents a baseboard, also known as a motherboard or system board. It describes the Product property as the baseboard part number defined by the manufacturer and SerialNumber as a manufacturer-allocated number used to identify the physical element. The class is documented as supported from Windows Vista onward.

On a prebuilt, the Win32_ComputerSystem model will show the system name and differ from the board product. That difference tells you which name to trust. systeminfo in Command Prompt prints the system manufacturer, model and BIOS version, but not the baseboard fields.

Run the commands again after a BIOS update. Only the BIOS version should change. If the board product changes, you're looking at different hardware, often a repaired or swapped board.

Step 4: Linux​

Linux exposes SMBIOS data as plain files. This read-only loop works on most x86 desktops and laptops:

Code:
for f in board_vendor board_name board_version bios_vendor bios_version bios_date sys_vendor product_name; do
  printf '%-14s %s\n' "$f" "$(cat /sys/class/dmi/id/$f 2>/dev/null)"
done
  • board_serial needs root.
  • sudo dmidecode -t baseboard prints the full Base Board block.
  • sudo dmidecode -s baseboard-product-name prints a single value, which suits scripts.
  • sudo lshw -class bus -short often shows a motherboard line.
  • If /sys/class/dmi/id doesn't exist, the machine may lack SMBIOS, as on some ARM boards. Try cat /proc/device-tree/model.

On a virtual machine, every field names the hypervisor or hosting provider. The source guide's test on a cloud server showed "DigitalOcean" and "Droplet" throughout. That is not a physical board you can look up.

Step 5: Mac​

A Mac has no swappable board, so the useful identifiers are the model identifier and the chip. Run system_profiler SPHardwareDataType in Terminal, or open About This Mac. Support pages for Macs key off the model identifier, serial number or year and size. Don't post the serial number publicly.

Step 6: The chipset is not the board model​

The chipset sets which features the board offers and which driver package you need. Many board names embed a chipset code, but only the vendor's specification page for your exact model confirms it. Cross-check in this order:

  1. Read the chipset code in the board model, then confirm it on the vendor's spec page.
  2. On Windows, look in Device Manager under System devices for an LPC or eSPI controller entry. This is often informative on Intel systems, but it is only a hint.
  3. On Linux, run lspci | grep -Ei 'isa bridge|lpc'.
  4. Use a hardware monitor with a mainboard tab, such as CPU-Z or HWiNFO, as a visual second opinion.

If the board model code disagrees with the vendor page, don't trust either until you've photographed the board label.

Step 7: Read the board itself​

If the PC won't boot, power it down, switch off and unplug the power supply, and touch bare metal on the case to discharge static. Open the side panel and look for white printed text near the CPU socket, between the expansion slots or beside the memory slots. The revision usually appears as "REV" and a number.

Photograph each label and copy the text exactly, including any suffix such as a Wi-Fi mark, since a suffix can denote a different product. As a no-screwdriver fallback, boot a live Linux USB stick and run the Step 4 loop. It reads firmware tables without touching your installed system.

Step 8: Confirm in UEFI setup​

Restart and press the setup key shown at the logo screen, often Delete or F2. Many boards show the model and BIOS version on the first page, though some bury it on a system information tab. The BIOS version should match what Windows or Linux reported. Exit without saving. You only came to read.

Step 9: Match the board to the right support page​

Search for the vendor, model and the word "BIOS" or "support", and prefer the manufacturer's own site. On the product page, look for:

  • a revision selector or a note on which hardware revisions the downloads cover
  • the CPU support list for each BIOS version
  • the memory compatibility list (QVL)
  • the BIOS release notes

Do a three-way check: the OS value, the UEFI value and the board label should agree on vendor and model. If only one matches, you may be reading a prebuilt system name or a virtual machine. If you can't match your revision, ask the vendor instead of guessing. Follow each maker's own model and revision instructions. Policies vary, so don't assume every board has revision-specific files.

Common pitfalls and fixes​

SymptomLikely causeFix
"To Be Filled By O.E.M." or "Default string"The maker never wrote that fieldRead UEFI or the silkscreen, or check the box
No BaseBoard rows in msinfo32No base board table (some laptops and VMs), or Safe ModeUse System Model, or the laptop sticker; boot normally
Hosting provider shown as boardYou're in a virtual machineLook at the physical host instead
Board and system vendor differPrebuilt with a custom-made boardSearch the system model
Permission denied on board_serialLinux restricts the serial to rootUse sudo, or skip the serial
dmidecode: command not foundPackage not installedInstall it, or use the sysfs files
wmic not recognizedDeprecated tool removedUse Get-CimInstance
BIOS version differs between UEFI and OSPending update, stale cache or swapped boardReboot, recheck, and treat the UEFI value as authoritative

Containers add a quieter version of the VM problem. They share the host kernel, so a script inside one may read the host's tables or nothing at all. Treat container output as unverified.

About the source guide's Python script​

The original guide includes a roughly 150-line Python script, mobo_id.py. It reads Windows through PowerShell, Linux through sysfs and macOS through system_profiler. It strips placeholder text, masks serial numbers, flags VMs and prebuilt vendors, and prints a support search phrase. Its author says it was run on one cloud server, and that its VM detection missed that server at first until the provider name was added to the hint list.

That is a fair disclosure, but it means the script is a starting point, not a proven cross-platform tool. I haven't run it. If you adapt it, test it on real Windows, Linux and macOS machines. Check how it behaves when fields are blank, commands are missing or the system is virtual. For a single PC, the manual steps above are enough.

Admin and upgrader tips​

  • Fleet inventory: collect board and BIOS data through your existing management tool. Many inventory tools already gather it.
  • Upgrade planning: on Linux, sudo dmidecode -t processor and -t memory show the socket, CPU and each memory slot.
  • Before a BIOS change: save your report, photograph your settings screens, and note boot mode, memory profile and fan curves. Updates can reset them.
  • Advisories: when a vendor publishes a BIOS security notice, search it for the model and revision from your saved report.
  • Privacy: serial numbers can identify a unit and its warranty record. Share only the vendor, model and revision.

Bottom line​

Check whether the machine is prebuilt or custom first. Then read the model from msinfo32 or PowerShell, confirm it in UEFI or on the board label, and trust the vendor's support page over any guess. Blank, generic or virtualized results mean there is no model to look up, so go to the physical label.

 

References

  1. What Motherboard Do I Have: 12 Steps, 20 Min (2026) - shattered.io shattered.io 2026-11-17T17:28:39+00:00
  2. 1 SMBIOS Specification 2 Version: 3.10.0 3 Document Identifier: DSP0134 4 dmtf.org
  3. Description of Microsoft System Information (Msinfo32.exe) Tool | Microsoft Support support.microsoft.com