What this checker decides
“ECC support” is not one yes-or-no specification. A useful purchase decision needs the exact CPU, the exact motherboard and any named revision, a board-vendor statement about ECC UDIMMs, firmware evidence, and an exact memory-module check. Corrected-error reporting in the deployed operating system is a further verification step.
This first catalog covers ASUS PRIME X670E-PRO WIFI, ASRock Rack B650D4U, and GIGABYTE MC13-LE0 revisions 1.x/3.x/4.x, paired with either the AMD Ryzen 9 9950X or AMD Ryzen 7 8700G. It gives a concrete outcome only at the level the sources support: an exact documented path, incomplete evidence that names the missing check, or a configuration the board vendor does not document.
DDR4 ECC is outside this checker
AMD’s Socket AM5 chipset page specifies DDR5 memory across the AM5 chipset families, and DDR4 and DDR5 modules don’t fit the same slot, so every row here is about DDR5 ECC UDIMMs. If you’re planning a DDR4 ECC build, start again from that platform’s exact CPU, socket, motherboard model and revision: read the board’s manual and memory QVL, and tell unbuffered ECC apart from registered memory before you buy a module. Don’t carry an AM5 result over to an AM4, workstation or server board.
How to use the result
Choose your CPU, then compare boards. Changing the motherboard keeps that processor selected when it is available. If the processor cannot be retained, the checker asks you to choose one before showing another verdict. A shared link records the exact board and CPU; Reset returns to the starting selection.
An exact documented path means the board vendor supplied an exact CPU row with ECC DIMM support. Incomplete evidence means board-level ECC and CPU-family evidence align but an exact board/CPU row, firmware version, or module confirmation is missing; the result names the vendor check to make before buying. Not documented is a stop sign for assuming support; it does not claim the hardware is physically incapable.
Even a documented result is not an injected-error test. Match the exact memory part number to the current vendor QVL, confirm firmware for the exact CPU and board revision, check that ECC is enabled, and verify how the deployed operating system reports corrected and uncorrected errors. Once the memory is in, the ECC home-server guide walks through checking that ECC is actually on and reporting.