Memory gets quoted against the board

A memory request written as a capacity and a speed looks finished and usually is not. The module has to be one the board accepts, at a population it will run, at a speed it will actually train.

Registered, unbuffered and load-reduced modules are not interchangeable. Server boards refuse unbuffered outright; desktop boards refuse registered. That filter is absolute and it comes first.

Rank and population come next. Boards derate memory speed as more ranks land on each channel, so a kit rated well above the platform's base speed can train down once every slot is full. The number printed on the module is a ceiling.

The vendor qualification list settles most arguments. Where a platform publishes one, buying from it removes a whole category of post-delivery problems. Where it does not, matching modules already proven in the same board is the next best thing.

The useful version of the request, then, is the capacity and speed you want plus the board, plus how many slots you are filling, plus whether this is a fresh build or an addition to modules already installed. Mixing new sticks into an existing population is a decision worth making before the order rather than after it.