Overclock.net › Forums › AMD › AMD CPUs › [Official] AMD Ryzen DDR4 24/7 Memory Stability Thread
New Posts  All Forums:Forum Nav:

[Official] AMD Ryzen DDR4 24/7 Memory Stability Thread - Page 87

post #861 of 1150
Thread Starter 
Quote:
Originally Posted by Worldwin View Post

One thing i notice while using GSAT is that my AMD display driver keeps crashing, even when just using XMP. I am guessing i am running out of memory as i have it set to 14500 leaving pretty much no room for background tasks.

You want to be assigning 85-90% of what is available, then ideally not use the machine till the test has completed.
post #862 of 1150
Hey, I am reporting in with a 2933CL14 @ 1.4 V stable G.Skill Aegis 3000CL16 2x8GB kit (F4-3000C16-8GISB) on a MSI X370 Gaming Plus with a Ryzen 5 1600 (3.8 GHz @ 1.34 V). I am wondering whether I picked the right balance of timings and speed, and if not, how I should try increasing it. I tried TheStilt's 3200CL16 Hynix AFR and MFR settings already but sadly couldn't get it to POST. Can I somehow see which dies I got?

Below are my current fully stable setings.



Thanks in advance for any input!
Edited by patthehat - 10/7/17 at 9:57am
post #863 of 1150
thigobr--7000@3.9---3200MHz-C14-14-14-28-1T---1.350v---SOC 0.950v---BIOS 0902---HCI---1000%---F4-3200C14-8GTZ



@patthehat Thaiphoon Burner can sometimes extract information about the ICs used on the module:

http://www.softnology.biz/files.html
post #864 of 1150
Quote:
Originally Posted by Silent Scone View Post

You want to be assigning 85-90% of what is available, then ideally not use the machine till the test has completed.

Yea when i set it to 14500 only 300mb avail vs 14300 where ~500mb avail.

Anyhow my ST drawcall for DX11 went from 1.68m @ XMP to 1.76m tightening timings @ 3200. Since im not done im hoping to hit 1.8m.
post #865 of 1150
So a little thing I found with my particular setup.

Tcwl and Trdwr subtimings are influenced by the other. If I set my Trdwr timing to 6, I cannot set Tcwl any lower than the default timing of 14. On the other side of the fence, if I set Tcwl to 10 (Can't set to 9, it self-corrects to 10 for me), the lowest I can set Trdwr to is 9.

The latter increases copy speeds marginally compared to the former.

RAM used is in my sig. Samsung B-die. I don't think the geardown mode is correctly managed on my MSI board; If I set GDM to disabled, I should be able to set command rate to 1, but it auto-configures to 2 on it's own. Probably losing some performance there, otherwise I could likely get CAS to 13. Feel free to steal timings. I have not yet found the lowest Trfc can go, and Tras and Trc violates some rules still so I won't go lower than that. Anyways, heres the timings I managed on 3200. I'll work on 3333 next but it's hard to get stable; The RAM itself is rock solid, but random BSOD's when not putting a load on the PC plague this build.

edit: tRFC got misconfigured, correcting it now. also temporarily on stock CPU speeds to see if I can fish out some BSOD's

KQIWClA.png
KQEpPbI.png
Edited by ssateneth - 10/7/17 at 2:56pm
post #866 of 1150
Twcl should be equal to or 1 less than CL. Ryzen appears not to like odd twcl.

Of course you can break this rule but stability means nothing if performance is lost.

Tfaw rule is trrds multiplied by 4+0-8.
Your at 12 when minimum should be 16.

Many seem to focus solely on stability and speed but seldom focus on how it impacts performance.

Aida means very little realworld wise tbh.

My system does not BSOD FYI. I can't imagine why wink.gif


Edited by chew* - 10/7/17 at 3:13pm
post #867 of 1150
Quote:
Originally Posted by ssateneth View Post

I don't think the geardown mode is correctly managed on my MSI board; If I set GDM to disabled, I should be able to set command rate to 1, but it auto-configures to 2 on it's own.

Quirky BIOS, set CMD to Auto, reboot, then set it to 1 and it will take. same with the tcwl, set another figure reboot the set what you want and it will take.

Great bandwidth numbers on 3200, I'm not close with 3333, 3333 is fine for me perhaps as I am not so aggressive my Aida numbers are R:94 w:98 c:93 l:62, I have to run 3466 to get close to you, both are stable HCI memtest into the 1000s, prime for a day, 3466 struggles with cold boot. ~ 30% success rate can't seem to tune it out.

I notice you are on 1.62, what does it bring SSD Raid there yet, I'm still on official 1.5?
Edited by sandysuk - 10/7/17 at 3:38pm
post #868 of 1150
Quote:
Originally Posted by sandysuk View Post

Quirky BIOS, set CMD to Auto, reboot, then set it to 1 and it will take. same with the tcwl, set another figure reboot the set what you want and it will take.

Great bandwidth numbers on 3200, I'm not close with 3333, 3333 is fine for me perhaps as I am not so aggressive my Aida numbers are R:94 w:98 c:93 l:62, I have to run 3466 to get close to you, both are stable HCI memtest into the 1000s, prime for a day, 3466 struggles with cold boot. ~ 30% success rate can't seem to tune it out.

I notice you are on 1.62, what does it bring SSD Raid there yet, I'm still on official 1.5?

Thanks for pointing out how to set a stuck setting. I got GDM disabled, 1T command rate, and CAS latency down to 13. AIDA memory latency is down to 61.1ns, but i'll likely switch back to UA (some of the stuff I do benefits more from UMA than NUMA). I'll run HCI maybe overnight.

I haven't touched RAID in a long time (last array was a 6 drive RAID10 on mechanical drives). Reasons being I don't want to risk data loss on a RAID0 due to 1 drive failing. Don't want to spend a lot on extra drives either, and lastly prevents just pulling out the drive and plopping it in a different system and having access to the data (usually need the same motherboard type to use RAID created by BIOS). I've been trying newer revisions anyways to try to aid in memory stuff obviously. 1.63 is available but recommend not using it since it has a bug where any ram speed other than 2133 causes about 30 seconds of POST beeping until it continues the POST process and successfully booting. Makes it very hard to tweak settings in a timely manner.

Just wanted to reiterate 2933 is rock solid. Still working the bugs out of 3200. 3333 is really hard (even at stock timings and CPU), 3466 I can only sometimes get to POST.
post #869 of 1150
You happen to have multiple vgas installed in that system?

If so stick only 1 in then start from scratch dealing with your bsods if they even exist after.

If only 1 vga you have other issues.
Edited by chew* - 10/7/17 at 8:24pm
post #870 of 1150
Quote:
Originally Posted by chew* View Post

You happen to have multiple vgas installed in that system?

If so stick only 1 in then start from scratch dealing with your bsods if they even exist after.

If only 1 vga you have other issues.

Only 1 VGA.

BTW, some more behaviors I noted. When doing a memory intensive activity and you dont have enough SoC voltage, no BSOD. Instead it instantly restarts. I'm ok with 0.9v SOC on 3200. 3333 requires more than 0.9. Quick and dirty 1v fixes that issue.

Also might be some signaling thing going on for 3333 and higher. If I have Auto volts, I am almost guaranteed to BSOD on OS load (Wont even get to desktop). If I set to 1.45v, its much more reliable. If I set to 1.4375, it has similar behavior to Auto volts (this is stock CPU speed. Temperatures are fine, just dumping different voltages to see what happens).

Some people mention VDDP but this board does not have a slider for VDDP. There is something like CLDO_VDDP but that is something else. That setting does not seem to have any significant effect (Tried a 1v to 0.8v at steps of 0.01 with no discernible change)
Edited by ssateneth - 10/7/17 at 8:30pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › [Official] AMD Ryzen DDR4 24/7 Memory Stability Thread