8 GB DDR4-2400 PC4-19200 ECC registered RDIMM, 1Rx4, 1.2 V, 288-pin; eighteen ordering codes under the DB1 and EB1 die revisions
| Capacity | 8 GB |
|---|---|
| Memory Type | DDR4 |
| Speed | 2400 MT/s |
| Form Factor | RDIMM |
| Rank | 1Rx4 |
| ECC | ECC |
| Voltage | 1.2 V |
| Module Height | Standard |
| Condition | New · Used |
Samsung 8 GB DDR4-2400 ECC registered RDIMM, single rank of x4 devices on a standard 288-pin registered module at 1.2 V. Rated PC4-19200 with CAS latency 17, 14.17 ns at the 1,200 MHz clock, and 19.2 GB/s peak per 64-bit channel.
What separates this module from the 8 GB parts that use x8 devices is the device width. Eight gigabytes in a single rank means eighteen x4 devices per rank — sixteen carrying the 64 data bits and two carrying the check bits — where an equivalent x8 rank would use nine wider devices. Same capacity, same speed, different electrical load and a different place in a population guide.
It is supplied under two die revisions, M393A1G40DB1 and M393A1G40EB1, and eighteen ordering codes in total. Both revisions are the same module electrically; the code on the BOM decides which one ships. The table further down lists all of them so an exact code can be matched without eight near-identical pages competing with each other.
| Part number | M393A1G40DB1-CRC and M393A1G40EB1-CRC — two die revisions of the same module (catalogue codes M393A1G40DB1, M393A1G40EB1) |
|---|---|
| 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-2400, PC4-19200, 2,400 MT/s, 19.2 GB/s peak per 64-bit channel |
| Timings | CL17 at 1,200 MHz, 14.17 ns; JEDEC 2400T 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 |
Three fields on this label come from the part number: capacity, the 1Rx4 organisation and the PC4-19200 bin, whose T letter fixes CL17. The rest describe the run it came from — revision letters, SPD level and the YYWW date all move between runs — so they are decoded below rather than printed as facts.
| 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-2400T | DDR4-2400, JEDEC bin T, which is CL17 | The bin letter is the timing grade, not a vendor code; a listing that says PC4-2400 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 |
| DB1 / EB1 | Die revision, the block between the density field and the speed code | Same capacity, rank and speed either way; the revision records which component generation the module was built from |
| CRC00 … CRC4Y | 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,400 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,400 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.
Practically this means one thing to check before ordering: whether the platform guide accepts x4 registered modules in the population you intend. Almost every DDR4 server does at one module per channel; the difference appears at two or three modules per channel, where some boards drop a speed step earlier with x4 than with x8.
Eight gigabytes per slot is the middle of the DDR4 range and the usual choice for a machine that needs capacity without going to two-rank modules. 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, and at one module per channel the rank load stays low enough that the rated 2,400 is normally held.
It is also the like-for-like replacement. Where a machine was populated with 8 GB 1Rx4 modules at 2,400, matching capacity, rank and revision keeps the channel uniform; a 2Rx8 part of the same capacity would add a rank the firmware is not expecting.
Count the slots before choosing a module: an 8 GB 1Rx4 population at 2,400 gives 64 GB across eight slots, 96 GB at twelve, 128 GB at sixteen and 192 GB at twenty-four. The same sixteen slots filled with 32 GB parts is 512 GB — this module is the balanced line, not the dense one.
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,400 1Rx4 module they are capacity, rank and the clock the host applies.
Mixing x4 and x8 modules in one channel is the case to avoid on this part. Both are single rank, both are 8 GB at 2,400, and the machine will usually post — but the channel runs on the timing the controller derives from the heavier-load module, which is the x4 one. Where a guide publishes separate tables for x4 and x8, mixing them is outside both tables.
Mixing speeds drops the channel to the slowest module present. Mixing capacities leaves the channel interleaving at the smaller size. The safe pattern is one matched module per channel, then a second matched set, with rank, die revision and device width uniform inside a channel.
This clock sits in the middle of the DDR4 range: native to the first two Scalable generations, tolerated by everything above them. The pages that pair with this 1Rx4 build:
Compatibility is not the question with this 2,400 1Rx4 part — clock and population are. Treat the 2,400 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,400 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.
On the two revisions: Samsung's own module page lists the same density, speed, rank and component count for DB1 and EB1, and no functional difference is published between them. They are successive component generations of one design, which is why they are sold here as one line with two build families rather than two products. Where a BOM names one of them, quote that family; where it names neither, either revision satisfies the line, and mixing the two inside one channel is the same situation as mixing any two revisions — it will usually train, but matched revision per channel is the pattern that behaves predictably.
Samsung also marks the EB1 revision end-of-life on its product page, which is what secondary-market supply of this module looks like: remaining new stock, and pulls that have been tested. Both are stocked, and both carry the same one year of cover.
| Code | Build | Build tail | Condition | Quote |
|---|---|---|---|---|
| M393A1G40DB1 | DB1 catalogue | Family code without a speed block; the T build listed here is the PC4-19200 / 2,400 MT/s one | New / used | Enquire |
| M393A1G40DB1-CRC | DB1 | Base ordering code, tail not appended | New / used | Enquire |
| M393A1G40DB1-CRC00 | DB1 | 00 | New / used | Enquire |
| M393A1G40DB1-CRC0Q | DB1 | 0Q | New / used | Enquire |
| M393A1G40DB1-CRC0Y | DB1 | 0Y | New / used | Enquire |
| M393A1G40DB1-CRC30 | DB1 | 30 | New / used | Enquire |
| M393A1G40DB1-CRC3Q | DB1 | 3Q | New / used | Enquire |
| M393A1G40DB1-CRC40 | DB1 | 40 | New / used | Enquire |
| M393A1G40DB1-CRC4Q | DB1 | 4Q | New / used | Enquire |
| M393A1G40DB1-CRC4Y | DB1 | 4Y | New / used | Enquire |
| M393A1G40EB1 | EB1 catalogue | Family code without a speed block; the T build listed here is the PC4-19200 / 2,400 MT/s one | New / used | Enquire |
| M393A1G40EB1-CRC | EB1 | Base ordering code, tail not appended | New / used | Enquire |
| M393A1G40EB1-CRC00 | EB1 | 00 | New / used | Enquire |
| M393A1G40EB1-CRC0Q | EB1 | 0Q | New / used | Enquire |
| M393A1G40EB1-CRC0Y | EB1 | 0Y | New / used | Enquire |
| M393A1G40EB1-CRC30 | EB1 | 30 | New / used | Enquire |
| M393A1G40EB1-CRC3Q | EB1 | 3Q | New / used | Enquire |
| M393A1G40EB1-CRC40 | EB1 | 40 | New / used | Enquire |
| M393A1G40EB1-CRC4Q | EB1 | 4Q | New / used | Enquire |
| M393A1G40EB1-CRC4Y | EB1 | 4Y | New / used | Enquire |
The M393A1G40DB1-CRC 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.
The figure above is the starting price per module at the minimum quantity. Above a single tray the M393A1G40DB1-CRC line is quoted, since per-piece pricing tracks volume and condition; the same-day answer applies at any quantity once the code and platform are known.
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