M.2 and Memory Mystery in a 12-PC Lab Build
A school lab is assembling 12 identical desktop PCs: Intel i5-12400 on a Gigabyte H610M motherboard, 2 × 8 GB DDR4, a 512 GB NVMe SSD, a 1 TB SATA HDD and a 450 W PSU. In PC #7 the BIOS lists the NVMe drive but not the SATA HDD. The HDD is connected to SATA port 5, and the board manual states that the M.2 slot shares bandwidth with SATA port 5. In PC #9 both memory sticks are installed in slots A1 and B1, but BIOS reports only 8 GB; the manual recommends A2/B2 for two-DIMM operation. PC #12 completed Windows installation on the NVMe SSD, but on restart it shows ‘Reboot and select proper boot device’; a USB card reader is plugged in and the boot order is UEFI USB first, then NVMe. The lab has 90 minutes before students arrive and no spare motherboard.
1. For PC #7 and PC #9, state the most likely cause, the checks you would perform, and the order you would do them in. Justify why you would not immediately replace hardware.
Read the worked answer
The order matters because both faults point first to configuration and population, not failed components.
For PC #7, the manual’s shared-bandwidth note makes SATA port 5 the prime suspect: on many boards the M.2 slot disables or shares that port. Confirm the HDD is spinning and powered, then move its data cable to SATA port 3 or 4, keep AHCI enabled, and recheck BIOS. If it is still absent, swap the SATA cable and try the HDD in a known-good port before condemning the drive. A dead port or cable is cheaper to prove than a dead disk.
For PC #9, an 8 GB report means one module is not being trained. A1/B1 may be electrically valid but is not the recommended dual-channel pair on this board, and a partly seated stick is common after assembly. Power off, reseat both sticks in A2/B2, inspect for a stray screw or bent pin, then test one stick at a time in the required slot. Do not replace the motherboard until reseating and slot changes fail: that consumes the only spare and does not address the documented configuration. Record slot population and BIOS version on the build sheet.
2. PC #12 still fails after Windows setup. Explain the likely boot configuration problem and how you would correct it without reinstalling Windows. Include what you would record in the build sheet.
Read the worked answer
The message means firmware found no bootable entry, not that Windows is absent. The attached card reader can be enumerated as a removable USB device; with UEFI USB first, firmware may try it, fail, and stop, depending on boot settings. More likely the installation mode does not match current firmware: if Windows was installed with legacy/CSM and the board is now UEFI-only, or the Windows Boot Manager entry was written to the USB disk, the NVMe has no valid UEFI entry.
I would check the boot mode, temporarily disable USB boot, confirm the NVMe is first and that ‘Windows Boot Manager’ exists. If it is absent, boot Windows recovery media and run bcdboot to write the boot files to the NVMe EFI partition, then set the entry. Do not reinstall until partition style (GPT vs MBR) and firmware mode are verified; reinstalling in the same mismatch repeats the fault. Build sheet: firmware mode, final boot order, partition style, NVMe slot, SATA port map, and Windows build.
3. The school wants all 12 PCs imaged from PC #1 after fixes. What two checks must pass on PC #1 before cloning, and why is SATA port choice part of the image standard?
Read the worked answer
Before cloning, PC #1 must pass two checks: (1) BIOS/UEFI reports the full 16 GB in the correct dual-channel slots and all drives present; (2) it cold-boots three times into Windows from the NVMe with the final boot order and no USB media attached. A clone copies the partition table, boot entries and storage driver state, so a machine that only boots because a USB entry is first will produce 12 failing PCs.
SATA port choice is part of the standard because the image expects the same controller mode and, on this board, the M.2 slot can disable SATA port 5. If PC #1’s HDD is on port 3 and a clone is cabled to port 5, the drive may disappear even though the image is good. Standardize port 3, AHCI, UEFI/GPT and record it. Generalize the image only if Windows licensing and lab policy allow; otherwise use a proper deployment tool and keep the build sheet with each machine.