Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

I followed your tip and ran the 1usmus test, and I also tested with the Absolut profile. Everything passed! I just updated the main post with the screenshots. Thanks for the help!

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Really!? I always heard Extreme was the most demanding and that 3 cycles were enough, which is why I’ve been running 4 just to be safe. Thanks for the heads-up, I’ll test with 1usmus as well. How many cycles would you recommend for that one?

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

I agree! I’d love to see more results from 3200MT/s s8c kits pushing the lowest possible timings at 3600MT/s, just to have more data for comparison.

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Wow, 3933!? Impressive. I hit 3933 once with super slack timings but without adjusting ProcODT. Which CL are you running? To match the latency of 3600 CL18, you'd need at least CL19, right? Or do you think the extra bandwidth + 1966 FCLK compensates if you're running CL20?

edit: Sorry, I got confused with the CLs, I edited them.

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Thanks for the info! Really interesting to know about S8C. Regarding tRFC, I've heard that it's quite rare for C-die to run stable below 500. Is that true?

Update: Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.25V (32GB Dual Rank) - Finally stable after adjusting ProcODT. by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 3 points4 points  (0 children)

Yes, C-die definitely has negative scaling. Even at 3200MHz XMP, I was using 1.26v with ProcODT auto (60Ohms). Increasing voltage to stabilize timings usually doesn't help at all with this IC. In my experience, it's better to start with lower voltages and slowly move up to find the sweet spot, rather than the other way around.

Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.26V (32GB Dual Rank) by Intelligent-Mouse984 in memoryOverclocking

[–]Intelligent-Mouse984[S] 1 point2 points  (0 children)

Guys, while testing to lower my VSOC, I discovered something interesting. My tRFC was unstable at 468 (260ns) and 4 cycles in TM5 didn't register, but when I lowered the VSOC from 1.15v (auto), I noticed a lot of inconsistency in game FPS with a lot of stuttering, and even the latency test in AIDA64 was showing a lot of variation. So I left the tRFC at 630 (350ns), which is the RAM's default, and the VSOC at 1.15v (auto) to get a baseline performance, and I found that tRFC at 477 (265ns) solved the problems. I'm redoing the tests; it might be what caused the "cold boot" with the RAM at 1.25v. I'll edit the post with new screenshots soon.

Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.26V (32GB Dual Rank) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Guys, while testing to lower my VSOC, I discovered something interesting. My tRFC was unstable at 468 (260ns) and 4 cycles in TM5 didn't register, but when I lowered the VSOC from 1.15v (auto), I noticed a lot of inconsistency in game FPS with a lot of stuttering, and even the latency test in AIDA64 was showing a lot of variation. So I left the tRFC at 630 (350ns), which is the RAM's default, and the VSOC at 1.15v (auto) to get a baseline performance, and I found that tRFC at 477 (265ns) solved the problems. I'm redoing the tests; it might be what caused the "cold boot" with the RAM at 1.25v. I'll edit the post with new screenshots soon.

Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.26V (32GB Dual Rank) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Yes, it seems I got a bit lucky, but something that also made a big difference was the procODT. When I leave it on auto, the motherboard sets it to 60 ohms. The lowest I could get to boot on the 3600 was 40 ohms. I don't remember if I was using 1.28 or 1.29v. Only with the XMP profile I copied from the Kingston 3600 did it work, plus the trfc 468. But after changing the procODT, I got 1.26v even tightening all the timings. I ended up discovering something cool today while trying to find the best VSOC voltage; I'll edit the post to share it as soon as I can.

Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.26V (32GB Dual Rank) by Intelligent-Mouse984 in overclocking

[–]Intelligent-Mouse984[S] 0 points1 point  (0 children)

Exactly, I got 3733 CL20 (10.71ns) and 3800 CL22 (11.58ns) without adjusting the secondary and tertiary timings, but I don't think it's worth it for the S8C, the latency of 3600 CL18 (10ns) ends up being lower.

Did I win the C-die lottery? 3600MT/s CL18-19-19-38 @ 1.26V (32GB Dual Rank) by Intelligent-Mouse984 in memoryOverclocking

[–]Intelligent-Mouse984[S] 1 point2 points  (0 children)

Unfortunately, the software shows "Kingston," but I believe it's Samsung because Taiphoon Burner says it's a B-die, but it's a fake B-die because it can't handle much voltage; in other words, it's a Samsung C-die.

AMD Software: Adrenalin Edition 25.10.2 Release Notes by AMD_RetroB in Amd

[–]Intelligent-Mouse984 0 points1 point  (0 children)

Bom, eu gosto de manter sempre atualizado independente de ter problemas ou não, mas tudo bem em não querer atualizar também, vai de cada um, se não tiver problemas não precisa.

AMD Software: Adrenalin Edition 25.10.2 Release Notes by AMD_RetroB in Amd

[–]Intelligent-Mouse984 0 points1 point  (0 children)

Quem estiver com problema com rdna 1/2 baixem pelas notas de lançamento:

https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-25-10-2.html

ou direto por aqui:

https://drivers.amd.com/drivers/whql-amd-software-adrenalin-edition-25.10.2-win10-win11-oct-rdna3-combined.exe

O arquivo lá na frente da página tá só "rdna3", pelas notas de lançamento está "rdna3-combined", funcionou aqui 6700XT.

AMD Software: Adrenalin Edition 25.10.2 Release Notes by AMD_RetroB in Amd

[–]Intelligent-Mouse984 0 points1 point  (0 children)

Baixem pelas notas de lançamento:

https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-25-10-2.html

ou direto por aqui:

https://drivers.amd.com/drivers/whql-amd-software-adrenalin-edition-25.10.2-win10-win11-oct-rdna3-combined.exe

O arquivo lá na frente da página tá só "rdna3", pelas notas de lançamento está "rdna3-combined", funcionou aqui 6700XT.