Adata Debuts XPG Spectrix D40 RGB DDR4

All the cool kids are adding RGB lighting to their products. Adata, not wanting to be left behind, announced the XPG Spectrix D40 RGB DDR4 line of enthusiast memory.

Adata offers both 8GB and 16GB memory modules and kits up to 64GB with speeds ranging from DDR4-2400 all the way up to DDR4-4000. Intel’s XMP 2.0 is supported, allowing overclocking and tuning from within the OS without making BIOS changes. Spectrix D40 has also been validated for use with AMD AM4 motherboards. These memory modules are built using 10 layer PCB. The “armor inspired” aluminum alloy heat spreaders are equipped with an integrated RGB LED strip capable of displaying 16.8 million colors.

As with most memory equipped with RGB lighting, Adata's complete line of XPG Spectrix D40 RGB DDR4 memory offers full color synchronized lighting effects that can be controlled through industry standard RGB lighting control software such as Asus’ Aura Sync.

Other features include Intel X299 platform compatibility, a 10-layer PCB that incorporates 2oz of pure copper in each module, and enhanced power efficiency with an operating voltage 20% lower than DDR3.

Adata’s XPG Spectrix D40 RGB DDR4 line of enthusiast memory is backed by a limited lifetime warranty. Information on pricing and availability was not available at press time.

Swipe to scroll horizontally
Adata XPG Spectrix D40 RGB DDR4
Memory TypeDDR4
Memory SeriesXPG SPECTRIX D40
Memory Size8GB - 64GB
Tested Speed2,400MHz / 4,000MHz
Tested Latency DDR4 2400 CL 16-16-16
Tested Voltage1.2V  /  1.35V
Memory ConfigurationDual / Quad Channel
Heat SpreaderAluminum Alloy
Package MemoryFormatDIMM
Package Memory Pin288
Performance ProfileXMP 2.0
  • sparkyman215
    speeds ranging from DDR4-2400 all the way up to DDR4-40000. Could you image 40k Mhz ram ;)
  • BulkZerker
    Call those 40K speed sticks "emperor edition?" Ram?
  • drwho1
    Wow 40K Ram!
  • FritzEiv
    OK OK, you've had your fun. Fixed :-) I am surprised nobody caught the editing error on our Phanteks post earlier. It's fixed, so kudos to anyone who can find a cached version . . . (and Joe would probably ban me if I told you the error here).