8 GB DDR4-2666 PC4-21300 ECC registered RDIMM, 1Rx4, 1.2 V, 288-pin; four ordering codes from M393A1G40EB2-CTD60 to -CTD7Q
| Capacity | 8 GB |
|---|---|
| Memory Type | DDR4 |
| Speed | 2666 MT/s |
| Form Factor | RDIMM |
| Rank | 1Rx4 |
| ECC | ECC |
| Voltage | 1.2 V |
| Module Height | Standard |
| Condition | New · Used |
Samsung 8 GB DDR4-2666 ECC registered RDIMM, single rank of x4 devices on a standard 288-pin registered module at 1.2 V. Rated PC4-21300 with CAS latency 19, 14.25 ns at the 1,333 MHz clock, and 21.3 GB/s peak per 64-bit channel.
The speed block is TD, which is 2,666 — the clock the second-generation Xeon Scalable parts were mostly specified with, and the highest rate a single-rank x4 8 GB module reaches without moving to a heavier organisation. Against the 2,400 version of the same module it buys about eleven percent more bandwidth per channel for a latency that is essentially unchanged, which is why 2,666 became the default population for that generation.
Four ordering codes ship against it, all on the same catalogue code, and they are listed further down. The organisation is x4, eighteen devices per rank rather than nine, so the population guide's x4 table applies rather than the generic capacity line.
| Part number | M393A1G40EB2-CTD, with the four ordering codes listed under Ordering codes (catalogue code M393A1G40EB2) |
|---|---|
| Capacity | 8 GB per module, single module |
| Organisation | 1Rx4 — one rank of x4 devices, eighteen devices for the 72-bit path, sixteen for data and two for the check bits |
| Speed | DDR4-2666, PC4-21300, 2,666 MT/s, 21.3 GB/s peak per 64-bit channel |
| Timings | CL19 at 1,333 MHz, 14.25 ns; JEDEC 2666V bin |
| Voltage | 1.2 V nominal |
| Form factor | 288-pin RDIMM, standard height 31.25 mm, bare PCB with no heatspreader |
| Register | On-module register buffers the command and address bus, so the module needs a controller that supports registered memory |
| Error handling | ECC across the 64-bit data path, plus parity on the registered command and address path |
| Manufacture | Samsung; assembly site and date code vary by production run and are printed on the module, not fixed by the part number |
| Condition | New and tested pulls, both stocked |
Read left to right, a Samsung RDIMM label gives 8 GB first, then 1Rx4, then the PC4-21300 code whose V suffix fixes CL19. What follows belongs to the batch rather than the part number, so it is decoded below rather than stated as fact.
| Printed as | Means | Why it decides a purchase |
|---|---|---|
| 8GB | Capacity of this one module | Sets how many slots are needed for the target memory size, and it is the one number a platform setting cannot change |
| 1Rx4 | Single rank, x4 device width | One rank is the lightest load a channel can carry, but x4 devices mean twice as many of them as x8, so the rank is not as light as its name suggests |
| PC4-21300V | DDR4-2666, JEDEC bin V, which is CL19 | The bin letter is the timing grade, not a vendor code; a listing that says PC4-2666 without the letter has not specified latency |
| -R | Registered, not unbuffered | An unbuffered module of the same capacity looks similar from above and will not post in a registered-only board |
| EB2 | Die revision, the block between the density field and the speed code | Same capacity, rank and speed as the neighbouring revisions; it records which component generation the module was built from |
| CTD60 … CTD7Q | Ordering tail, the last two characters of the code | The field a BOM or an invoice names. It does not change capacity, rank or speed, all of which are fixed earlier in the code |
| Raw card block | Revision and raw card design, the characters before the SPD number | Matters where a platform qualification list names a specific raw card for a slot population |
| SPD revision | Two-digit JEDEC SPD revision level | Older firmware reads lower revisions more reliably; this generation is old enough that the difference still shows up |
| YYWW | Date code, year and week | Age of the stock; on pulls it is the first evidence of how long the module has been in service |
A rank is exactly 72 bits wide — 64 for data, 8 for check — and an x4 device carries four of them, so eighteen devices make one rank. That is why 8 GB at 2,666 sits in a single rank on an x4 build: the 2Rx8 version of the same capacity uses the same eighteen devices as two ranks of nine wider parts.
The electrical cost is the flip side: eighteen x4 devices hang off one rank at 2,666 where nine x8 devices would do, roughly doubling the capacitance charged on each transfer. The register absorbs part of that on the command and address side, but guides still publish separate x4 and x8 tables — and this part is governed by the x4 one.
At 2,666 the point where x4 starts to cost a speed step sits lower than at 2,400, because the timing budget per transfer is shorter. One module per channel is safe almost everywhere; with two or three modules per channel, check the guide's x4 row for this speed rather than assuming the x8 number holds.
Eight gigabytes per slot at 2,666 is the shape of a second-generation Scalable machine built to a price: one module per channel on an eight-slot board is 64 GB, twelve slots is 96 GB, sixteen is 128 GB and twenty-four is 192 GB, all at the rated clock because every channel carries a single rank.
It is also the natural replacement unit. Where a machine was populated with 8 GB modules at this speed, matching capacity, rank and revision keeps the channel uniform, and a single failed module is a cheap swap rather than a reason to re-plan the population.
Against the other two speeds in this family, the trade is straightforward. The 2,400 version costs a little less per module and gives up about eleven percent of channel bandwidth; the 2,133 version is the fallback for platforms that will not train higher. Both are on their own pages.
Generation and signal type come first — DDR3 does not fit, unbuffered does not post in a registered board, DDR5 uses another notch — and only then do the variables matter: for this 2,666 1Rx4 module they are capacity, rank and the clock the host applies.
Speed is the variable that catches people here. A 2,133 or 2,400 module added to a 2,666 channel pulls the whole channel down to the slower rate, and nothing announces it: the machine posts, the capacity is right, and only the firmware log or a benchmark shows the step. Where a population has been mixed by accident, the slower module is the one to remove.
Device width matters as well. Mixing x4 with x8 modules in one channel makes the channel run on the timing derived from the heavier module, which is the x4 one, and the combination sits outside both of the guide's tables. One matched module per channel, then a second matched set, with rank, revision and width uniform inside a channel, is the pattern that behaves predictably.
2,666 MT/s is the second-generation Scalable clock, and later parts take a 1Rx4 module at this speed at a derate rather than refusing it. Three pages in the catalogue are the natural counterparts:
Compatibility is not the question with this 2,666 1Rx4 part — clock and population are. Treat the 2,666 figure as the module's ceiling and the platform guide as the authority on what it will run at.
Every code in the table below is the same 8 GB 1Rx4 module at 2,666 MT/s. The block before the dash fixes family, device width and die revision; the dash and its tail are what a purchase order or an invoice actually names, and Samsung publishes no public decoder for them.
| Code | Type | Build tail | Condition | Quote |
|---|---|---|---|---|
| M393A1G40EB2 | Catalogue code | Family code without a speed block; the V build listed here is the PC4-21300 / 2,666 MT/s one | New / used | Enquire |
| M393A1G40EB2-CTD | Ordering code | Base ordering code, tail not appended | New / used | Enquire |
| M393A1G40EB2-CTD60 | Ordering code | 60 | New / used | Enquire |
| M393A1G40EB2-CTD6Q | Ordering code | 6Q | New / used | Enquire |
| M393A1G40EB2-CTD7Q | Ordering code | 7Q | New / used | Enquire |
The M393A1G40EB2-CTD line carries one year of cover from dispatch, new or pulled, recorded per part number and batch. Every pull is tested as a matched set before packing and that result ships with the module; orders leave in three to seven working days, two pieces minimum.
Pricing here is per enquiry, not per page. Send the exact 2,666 1Rx4 code, the quantity and the platform and the answer arrives the same working day; a set quote beats piecemeal orders because the channel population can be validated first.
Tell us who you are — we reply within one working day with a firm quote, stock status and lead time. Volume discounts available.
16 GB DDR4-2933 PC4-23400 ECC registered RDIMM, 2Rx8 on eighteen 8 Gb x8 packages, 1.2 V, 288-pin; six ordering codes under M393A2K43CB2-CVF with BY, CO, BQ, C0 and GQ tails
16 GB DDR4-2400 PC4-19200 ECC registered RDIMM, 2Rx8 on eighteen 8 Gb x8 packages, 1.2 V, 288-pin; eighteen ordering codes under the M393A2K43BB1 and M393A2K43CB1 revisions
16 GB DDR4-2133 PC4-17000 ECC registered RDIMM, 2Rx8 on eighteen 8 Gb x8 packages, 1.2 V, 288-pin; nine ordering codes from M393A2K43BB1-CPB through the CPBQ tail
16 GB DDR4-2666 PC4-21300 ECC registered RDIMM, 2Rx8 on eighteen 8 Gb x8 packages, 1.2 V, 288-pin; six ordering codes under M393A2K43BB1-CTD with 6Q, 6Y, 7Q, 7Y and 8Q tails