Kingston

Kingston 48GB DDR5-5600 ECC RDIMM

KSM56E46BD8KM
Kingston DDR5 RDIMMmemory48GBDDR5-5600RDIMM
$47.92/GB
$2,299.99
newIn Stock
This offer: sold by Custom Hardware · Amazon says New / Unknown
Prices refresh about once a day
Price updated
Price accurate as of Oct 22, 2026, 03:20 PM
Buy on Amazon

The Kingston 48GB DDR5-5600 ECC RDIMM is a 48GB DDR5 ECC server memory module in new condition. It is in stock at $2,299.99 - $47.92/GB.

Model context

Part of the Kingston line we track.

Quick Verdict

Kingston 48GB DDR5-5600 ECC RDIMM at $47.92/GB. Warranty varies by seller. Verify your server's QVL before purchase.

Share:WhatsAppFacebookPost on X

Specifications

Capacity48GB
Module TypeRDIMM
GenerationDDR5
Speed5600 MT/s
ECCYes
Rank / Org—
Warranty—
ASINB0CXPZD6CJ
Market context

Against every other module we have an in-stock price for today, this one is cheaper per gb than 3% of them (1 of 40). The cheapest we can currently buy is $4.92/GB; the middle of the market is $11.66/GB.

Compare against every 0.046875TB drive we track →Cheapest per terabyte, all categories →Category price trends →

Also appears in

Server memory
Other pages
Price trends

Frequently Asked Questions

Yes. At our last check it was $2,299.99 ($49,066.45 per terabyte at its 0.046875TB capacity), sold new under ASIN B0CXPZD6CJ. Amazon sets the final price at checkout.

This listing (KSM56E46BD8KM, ASIN B0CXPZD6CJ) carries no renewed, recertified, refurbished or pulled claim in its title, and Amazon reports it as new. On this site that is what "new" means: sold as factory-new.

This row (ASIN B0CXPZD6CJ) is stored as a DDR5 RDIMM at DDR5-5600. A DDR5 module fits only a DDR5 platform (the keying and voltage differ by generation), and registered and unbuffered modules are not interchangeable - check your board's memory specification for DDR5 RDIMM support.

Use Case Scenarios

🖥️
Virtualization Host Density
Proxmox, ESXi or Hyper-V host packing more VMs per socket.
✓ Excellent fit
RAM is the binding constraint on VM density long before CPU. Adding 48GB ECC modules lets a host carry more guests per socket, and ECC prevents a single bit-flip from corrupting a guest's memory.
💾
ZFS ARC Cache
TrueNAS or ZFS server where read performance depends on cache hit rate.
✓ Excellent fit
ZFS turns every spare gigabyte into ARC read cache — more RAM directly raises cache hit rates on active datasets. ECC is strongly recommended for ZFS, whose integrity guarantees assume trustworthy memory.
🗄️
Database Working Set
PostgreSQL, MySQL or in-memory analytics needing the working set resident.
✓ Excellent fit
Databases live or die on buffer pool size. Fitting the working set in memory converts disk reads into RAM reads — a latency improvement no storage upgrade matches. ECC protects against silent corruption in long-running instances.
🏠
Homelab ECC Upgrade
Home server or NAS build stepping up from consumer memory.
~ Good fit
For 24/7 homelab duty, ECC server memory at today's used/refurb prices is often cheaper per GB than new consumer RAM — with error correction included. Verify your board and CPU actually support ECC before buying.

Maintenance & Troubleshooting

Maintenance Checklist

On installRun a full memtest86+ pass
Boot memtest86+ and let it complete at least one full pass before trusting the module with production data. Catches infant-mortality defects and seating problems immediately.
On installVerify detected speed and channel population
Check BIOS/IPMI that the module runs at the expected MT/s and that channels are populated per the motherboard manual's DIMM order. Uneven population silently costs bandwidth.
MonthlyReview ECC error counters
Check IPMI/iDRAC/iLO event logs, or edac-util on Linux, for corrected ECC errors. Occasional corrected errors are normal; a climbing count on one DIMM predicts failure — replace it.
AnnuallyReseat and dust during maintenance windows
Airflow debris and socket oxidation cause intermittent errors. During planned downtime, blow out slots and reseat modules showing any corrected-error history.

Troubleshooting Guide

Cause: Unsupported module type (UDIMM vs RDIMM), wrong DDR generation, or incorrect slot population order.
Fix: Confirm the platform supports this exact type and generation (check the QVL), install in the manual's specified slot order, and reseat firmly until both latches click.