• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

64GB (C)UDIMMs, where are they?

Joined
Feb 20, 2019
Messages
8,679 (3.99/day)
System Name Bragging Rights
Processor Atom Z3735F 1.33GHz
Motherboard It has no markings but it's green
Cooling No, it's a 2.2W processor
Memory 2GB DDR3L-1333
Video Card(s) Gen7 Intel HD (4EU @ 311MHz)
Storage 32GB eMMC and 128GB Sandisk Extreme U3
Display(s) 10" IPS 1280x800 60Hz
Case Veddha T2
Audio Device(s) Apparently, yes
Power Supply Samsung 18W 5V fast-charger
Mouse MX Anywhere 2
Keyboard Logitech MX Keys (not Cherry MX at all)
VR HMD Samsung Oddyssey, not that I'd plug it into this though....
Software W10 21H1, barely
Benchmark Scores I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000.
I'm actively trying to get confirmation on this from JEDEC, but I was informed by a vendor that JEDEC 6400 must be CUDIMM. 5600 and below can be UDIMM.

Good news is CUDIMM is backwards compatible, in the sense that if the Motherboard is not configured for CUDIMM it won't see it and acts like normal UDIMM. Downside would be 6400 JEDEC UDIMM is out of specifications if above is true.
Yeah, I found a reddit thread with an AMD employee confirming a few things about bypass mode. I've been unable to find any 64GB regular UDIMMS. In theory if they're making 6400 CUDIMMS there should be 5600, 5200, and 4800 UDIMMS available too but my searches came up empty.

https://www.reddit.com/r/Amd/comments/1gbm20a edit - how do I stop TPU's forum code from insisting that a reddit thread is media to be URL-hijacked, unfurled, and previewed (incorrectly)?
 
Last edited:
Joined
Jan 3, 2021
Messages
3,784 (2.53/day)
Location
Slovenia
Processor i5-6600K
Motherboard Asus Z170A
Cooling some cheap Cooler Master Hyper 103 or similar
Memory 16GB DDR4-2400
Video Card(s) IGP
Storage Samsung 850 EVO 250GB
Display(s) 2x Oldell 24" 1920x1200
Case Bitfenix Nova white windowless non-mesh
Audio Device(s) E-mu 1212m PCI
Power Supply Seasonic G-360
Mouse Logitech Marble trackball, never had a mouse
Keyboard Key Tronic KT2000, no Win key because 1994
Software Oldwin
edit - how do I stop TPU's forum code from insisting that a reddit thread is media to be URL-hijacked, unfurled, and previewed (incorrectly)?
I usually make the link part of a paragraph, like igormp did in post #16.
 
Joined
May 10, 2023
Messages
588 (0.92/day)
Location
Brazil
Processor 5950x
Motherboard B550 ProArt
Cooling Fuma 2
Memory 4x32GB 3200MHz Corsair LPX
Video Card(s) 2x RTX 3090
Display(s) LG 42" C2 4k OLED
Power Supply XPG Core Reactor 850W
Software I use Arch btw
FWIW, seems like the combo of 9950x + x670e ProArt does support CUDIMMs in bypass mode:

Expected, but seeing an actual example makes me happier with the decision.
 
Joined
Jan 3, 2021
Messages
3,784 (2.53/day)
Location
Slovenia
Processor i5-6600K
Motherboard Asus Z170A
Cooling some cheap Cooler Master Hyper 103 or similar
Memory 16GB DDR4-2400
Video Card(s) IGP
Storage Samsung 850 EVO 250GB
Display(s) 2x Oldell 24" 1920x1200
Case Bitfenix Nova white windowless non-mesh
Audio Device(s) E-mu 1212m PCI
Power Supply Seasonic G-360
Mouse Logitech Marble trackball, never had a mouse
Keyboard Key Tronic KT2000, no Win key because 1994
Software Oldwin
I'm actively trying to get confirmation on this from JEDEC, but I was informed by a vendor that JEDEC 6400 must be CUDIMM. 5600 and below can be UDIMM.
Does JEDEC also mean 1.1 volts in all cases? Even in MRDIMMs?
Good news is CUDIMM is backwards compatible, in the sense that if the Motherboard is not configured for CUDIMM it won't see it and acts like normal UDIMM. Downside would be 6400 JEDEC UDIMM is out of specifications if above is true.
Have you done, or are you planning, any compatibility tests? All the early announcements of CUDIMM indeed stated that it should be backwards compatible. And my optimistic expectation was that the clock driver would always have some positive effect because it amplifies and improves the clock signal.
 

ir_cow

Staff member
Joined
Sep 4, 2008
Messages
4,710 (0.79/day)
Location
USA
Expected, but seeing an actual example makes me happier with the decision.
I can show CUDIMM running bypass mode if you like and if you can run 6400 Dual-rank memory, this will be the same but higher density.

Besides actually testing the real kit, that might be the closest you'll get for now.
 
Joined
May 10, 2023
Messages
588 (0.92/day)
Location
Brazil
Processor 5950x
Motherboard B550 ProArt
Cooling Fuma 2
Memory 4x32GB 3200MHz Corsair LPX
Video Card(s) 2x RTX 3090
Display(s) LG 42" C2 4k OLED
Power Supply XPG Core Reactor 850W
Software I use Arch btw
I can show CUDIMM running bypass mode if you like and if you can run 6400 Dual-rank memory, this will be the same but higher density.

Besides actually testing the real kit, that might be the closest you'll get for now.
I'd love to see that, in case it's not a hassle for you!
Otherwise, the already-mentioned reports (specially from @Chrispy_) give me reasonable confidence already, but the 100% certainty mark will only happen once I actually grab the entire setup and build it haha
 

ir_cow

Staff member
Joined
Sep 4, 2008
Messages
4,710 (0.79/day)
Location
USA
Does JEDEC also mean 1.1 volts in all cases? Even in MRDIMMs?
I don't know about MRDIMM but 1.1v JEDEC up to 8800 is in the JEDEC paper.

Have you done, or are you planning, any compatibility tests? All the early announcements of CUDIMM indeed stated that it should be backwards compatible. And my optimistic expectation was that the clock driver would always have some positive effect because it amplifies and improves the clock signal.
Working on article, but it has been delayed for unrelated reasons. I want to see if it works on a bunch of different motherboards as well. Of course the higher speed won't boot because it's beyond what UDIMM can do (maybe the IMC as well). In theory if you had say 6400 CUDIMM, 6400 in bypass mode will work if the Motherboard/ CPU supports 6400 MT/s. That is what I'm testing right now.

The CKD JEDEC papers says unless the clock driver is enabled at startup (by protocols) it will be in bypass mode by default.
 
Top