F5F Stay Refreshed Hardware Desktop List all JEDEC profiles related to RAM

List all JEDEC profiles related to RAM

List all JEDEC profiles related to RAM

S
ssbmartin
Junior Member
6
10-10-2017, 03:17 AM
#1
Looking for a quick method to pull all RAM timings from memory using only JEDEC standards. The setup involves an updated MCPC with a 1600X and a new ASRock B450M Pro4 R2.0 board. I'm using Crucial 3200MHz RAM that follows the standard DDR4-3200AA profile but doesn't support XMP, so I can only apply the JEDEC settings manually. The BIOS restricts me to the 2666 profile and doesn’t let me override it, which makes things tricky. While I can adjust values by hand, trying to reach 3200 is risky because some specs aren’t fully visible online. Instead of relying on software, I’ll move the RAM into another machine and pull the timings from its BIOS, where the 3200AA profile is already set up correctly.
S
ssbmartin
10-10-2017, 03:17 AM #1

Looking for a quick method to pull all RAM timings from memory using only JEDEC standards. The setup involves an updated MCPC with a 1600X and a new ASRock B450M Pro4 R2.0 board. I'm using Crucial 3200MHz RAM that follows the standard DDR4-3200AA profile but doesn't support XMP, so I can only apply the JEDEC settings manually. The BIOS restricts me to the 2666 profile and doesn’t let me override it, which makes things tricky. While I can adjust values by hand, trying to reach 3200 is risky because some specs aren’t fully visible online. Instead of relying on software, I’ll move the RAM into another machine and pull the timings from its BIOS, where the 3200AA profile is already set up correctly.

T
Tico_32
Senior Member
680
10-10-2017, 04:53 PM
#2
Thaiphoon Burner must perform exactly as requested. Review the SPD documentation and list all compatible JEDEC timings in a clear table format. It can display the XMP profile too, but on devices lacking an XMP profile it will only show the JEDEC details.
T
Tico_32
10-10-2017, 04:53 PM #2

Thaiphoon Burner must perform exactly as requested. Review the SPD documentation and list all compatible JEDEC timings in a clear table format. It can display the XMP profile too, but on devices lacking an XMP profile it will only show the JEDEC details.

S
smag30
Member
140
10-16-2017, 01:41 AM
#3
Achieving a 3200 on tight timings on summit ridge will be tough. Typically they reach around 2933 C16, possibly hitting 3200 C20, though it might need significant voltage. Regarding clocks per latency, 3200 C20 (160) is less efficient than 2933 c16 (183). You aim for the most STABLE clocks per latency possible. That’s why 3600 c18 and 3200 c16 give comparable outcomes, both delivering 200 clocks per latency.
S
smag30
10-16-2017, 01:41 AM #3

Achieving a 3200 on tight timings on summit ridge will be tough. Typically they reach around 2933 C16, possibly hitting 3200 C20, though it might need significant voltage. Regarding clocks per latency, 3200 C20 (160) is less efficient than 2933 c16 (183). You aim for the most STABLE clocks per latency possible. That’s why 3600 c18 and 3200 c16 give comparable outcomes, both delivering 200 clocks per latency.

N
179
10-16-2017, 07:50 AM
#4
I believe my confusion comes from numerous timing details that appear either directly linked to those specs or influenced by the initial post. I thought the JEDEC profile covered everything. I entered as many timings as possible, left others at "AUTO," and it seems they’ve been adjusted accordingly. I follow discussions on Actually Hardcore Overclocking mainly for PCB analysis. My focus wavers when RAM overclock jargon is mentioned due to the sheer volume of characters. I was expecting simpler presets, but these should suffice. These DIMMs contrast with tighter timings like 3200C22; they were a spontaneous Amazon purchase aimed at testing Zen1’s compatibility with newer JEDEC 3200 DIMMs, though the BIOS seems to have other ideas. Interestingly, the same 1600X maintained 3200C14 (XMP) for a while (though slowly and quietly corrupting data), and it would likely have worked better at 3000C14 or 3200C16 if I had adjusted the settings.
N
NicknameNumber
10-16-2017, 07:50 AM #4

I believe my confusion comes from numerous timing details that appear either directly linked to those specs or influenced by the initial post. I thought the JEDEC profile covered everything. I entered as many timings as possible, left others at "AUTO," and it seems they’ve been adjusted accordingly. I follow discussions on Actually Hardcore Overclocking mainly for PCB analysis. My focus wavers when RAM overclock jargon is mentioned due to the sheer volume of characters. I was expecting simpler presets, but these should suffice. These DIMMs contrast with tighter timings like 3200C22; they were a spontaneous Amazon purchase aimed at testing Zen1’s compatibility with newer JEDEC 3200 DIMMs, though the BIOS seems to have other ideas. Interestingly, the same 1600X maintained 3200C14 (XMP) for a while (though slowly and quietly corrupting data), and it would likely have worked better at 3000C14 or 3200C16 if I had adjusted the settings.

J
jf_poli
Member
111
10-22-2017, 09:39 AM
#5
Other mentioned settings are managed completely by the motherboard itself. The memory profile for the stick doesn’t affect them. Focus only on tCL, tRCD, tRP, tRAS, tRC, tFAW, tRRD_S, tRRD_L. It’s unlikely there’s a tCCDL timing on Zen chips. All remaining parameters like tWR, tRFC, tCWL are determined by the motherboard and aren’t something to adjust manually.
J
jf_poli
10-22-2017, 09:39 AM #5

Other mentioned settings are managed completely by the motherboard itself. The memory profile for the stick doesn’t affect them. Focus only on tCL, tRCD, tRP, tRAS, tRC, tFAW, tRRD_S, tRRD_L. It’s unlikely there’s a tCCDL timing on Zen chips. All remaining parameters like tWR, tRFC, tCWL are determined by the motherboard and aren’t something to adjust manually.

A
A_chess
Member
58
10-23-2017, 12:24 PM
#6
Yeah, my 2600X would run above 2933 but it was a coin flip if it would boot correctly and not completely corrupt the windows installation with my LPX
A
A_chess
10-23-2017, 12:24 PM #6

Yeah, my 2600X would run above 2933 but it was a coin flip if it would boot correctly and not completely corrupt the windows installation with my LPX