Idk man, i feel you.. i think every reboot the system with ryzen have a mind on his own. To me it needs HCI stable, As if it dont pass HCI im not comfortable with it. GSAT proves stable but the system with fail stronger tests including whea errors. Same on intel. HCI stable no whea errors aka borderline "semi" stable i will call it.@zGunBLADEz
I take my hat off to you! :thumb: . Damn nice results for sure :thumb: .
I had an ~2 day fight on 3466MHz The Stilt preset using a R7 2700X and F4-3200C14D-16GTZ. In a way worth it, as allowed me to gain experience and tune setup before moving on.
I found upto 3400MHz I needed to adjust only SOC/VDIMM. There were 2 settings that created large gains in stability for me on 3466MHz.
3466MHz using HCI passed ~40min, failed Y-Cruncher in <30min. Setting VTTDDR to 0.687V made Y-Cruncher last for ~2.75hrs before fail. Then I used P95, as needed something that made profile fail quick to tune it. Even then it took a lot of attempts to discover ProcODT needed to be set to 48 Ohms. This surprised me, as the RAM I used, has been used with 5 differing Ryzen gen 1 and 1x TR, never did I use that ProcODT value. So as advised by several experienced members in C6H thread at launch, ProcODT definitely needs tuning based on combined HW in use. I also found with CPU stock I needed SOC: 0.956V but when combined with ACB OC of 4.075GHz SOC needed bump to 0.968V.
Anyhow here is some screenies.
ASUS ROG C7H UEFI 0601
R7 2700X UA 1805SUS (PState 0 4.075GHz VID: 1.287 SOC: 0.968V)
F4-3200C14D-16GTZ (3466MHz C15 1T VDIMM: 1.37V VTT: 0.687V)
thanks.Sry to just burst in and yell stuff around and btw hi @all, but did you check your DIMM Temperature while stressing with GSAT and HCI? Have a new Ryzen system too since last week with F4-3200C14D-32GTZR as a 2x16GB Kit and tried to oc them too slightly from 3200 to 3333 with optimized timings, funny was that with the same test as you did just only 1hr of GSAT everything was fine and stable but e.g. playing WoW or Destiny 2 gave me random crashes and read errors and i checked again GSAT alone 1hr no problem then i added Heaven in the background and as soon my Stick reached about 50-51 °C errors appeared everywhere, right now i was sitting at about 1.39v for the VDIMMS and about 1.05 SOC but can't test further now my power supply magic smoked yesterday while playing but that's different story.
And great job so far, keep it up :thumb:
oh okay thanks man !I'm running 3600C13\3533C14\3533C13 for 6 months at 1.5v, no problems at all. XMP's max is 1.5v, anything over is not known if safe. I believe that there's a bit more safety room over 1.5 volts
Im using HCI memtest pro, and automatically open 5 instances when i press start, automatically using 96% ram usage. do i still need to open 16 ?You should be opening 16 instances of HCI memtest, so that it can pass over your RAM faster.
I've posted few posts above with nearly the same issue, so far no solutions :Sanyone knows the stable timings for CMK16GX4M2B3200C16. this is samsung die. ryzen 5 2600 asrock ab350m pro4
xmp settings doens't boot/bsod.
Forget I thought you were running at 3200 I'm going blind, lol. I deleted my comments.Hi all.....
I'm a bit of a noob when it comes to OC'ing ram. I read through this thread a while back...and the search function isn't the greatest since the move.
I ran the HCI/Google Stress test at 3400mhz....passed both. Thought I would try 3466....the Google test says Thread 7 found 1 error, and Thread 10 found 1 error.
Here is a screen shot of one of the errors....I can't make head or tails out of it....thought I would post here and perhaps get some guidance from more experienced OC'ers.
View attachment 195065
I'm running the 2600x(stock clocks), fixed core voltage at 1.325v and the SoC is 1.150v. I'm using the GSkill Flare X Series F4-3200C14D-16GFX. I set the timings manually using the Ryzen DRAM Calculator. I believe I'm on the "Safe" settings profile that it generated. I'm on the Asus Strix X470 Gaming board.
Any info would be appreciated.
EDIT: I believe I have the DRAM at 1.45v
EDIT II: I was on the "Fast" profile, testing "Safe" now.