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

post #1 of 193
Thread Starter 
AM4 Ryzen Memory Stability Thread


Please try to remember the following



Clarify what platform and CPU you are speaking about when asking a particular question or speaking about your experience.

Quote the user you are replying to when replying.

When posting stability results, be sure to include the CPU as described in the posting results instructions.

NOTE: SOC voltage should ideally not exceed 1.2v Anything above 1.25v has the potential to cause irreversible damage.

Recommended settings ca be found here in the guide provided by ASUS: http://www.mediafire.com/file/mciue95x0a2xfq7/C6H_XOC_Guide_v05.pdf



Happy posting! thumb.gif

Overview
This thread is dedicated to showing the various memory configurations of users with DDR4 on AMD Ryzen platforms.
There is no strict criteria here, all things AM4 memory overclocking welcome. However, to enter the stability chart certain criteria is to be met as this is generally speaking dedicated to showing what is obtainable on both platforms at an operational level.


If using ASUS you can also post here for help:



For stability results, using the recommendations from Raja@ASUS found below and in the overview seem the most requisite on recent platforms:

Quote:
Google stressapp test via W10 Bash Terminal(or another compatible Linux disti) is the best memory
stress test available. Google use this stress test to evaluate memory stability of their servers
– nothing more needs to be said about how valid that makes this as a stress test tool.


Windows 10 Installation
  • Install Bash Terminal: https://msdn.microsoft.com/en-gb/commandline/wsl/install_guide
  • Install the Google Stress App test by typing: sudo apt-get install stressapptest
  • Once installed open “Terminal” and type the following: stressapptest -W -s 3600
  • You can add argument "-M" and add the the amount of memory you wish to assign to the test (90% of available memory)
  • This will run the stressapp for one hour. The test will log any errors as it runs.


Mint Installation

Quote:
HCI Memtest for Windows

HCI Memtest can be run via DOS or Windows. http://hcidesign.com/memtest/

An instance needs to be opened for each individual thread, covering a total of 90-95% of memory giving the OS a little breathing room.

As an example Ryzen 7 1700 - 16GB RAM

16 instances with 850MB per instance.





NOTE: Version 5.0 notes state that it's 30% faster than previous versions. For testing densities beyond 16GB - it's recommended you use 5.0 Pro.

http://hcidesign.com/memtest/




Stability Results

Please submit results with the following format.

GSAT Results
For sake of simplicity submitted results will only record primary timing sets, but feel free to show subsequent secondary and terts within screenshot.
Linux Mint's Stressapp test needs to be run for a minimum of 1 hour by typing stressapptest -W -s 3600 in the Terminal.
To take a screenshot in Terminal type: gnome-screenshot

HCI
HCI consider 1000% to be the 'golden standard' however for larger densities this can be time consuming. A minimal coverage of two laps (200%) is required to be added to the table for HCI for density over 16GB. 16GB or less requires a minimum of 4 laps (400%)


Example:

Silent Scone--7000@3.7---3200Mhz-C14-13-13-36-2T---1.38v---SOC 1.2v---BIOS 0902---Stressapptest---1 Hour--F4-3200C14-8GTZ
Or
Silent Scone--7000@3.7---3200Mhz-C14-13-13-36-2T---1.38v---SOC 1.2v---BIOS 0902---HCI---400%---F4-3200C14-8GTZ


NOTE: This is not a leaderboard, as it is not a benchmark. This thread's main purpose is to both discuss information and various results and to gauge what is possible between different configurations, DIMM capabilities, and CPU samples. Results are welcome all the way up the frequency spectrum. If it's obtainable, it should be posted! smile.gif.

Should go without saying that general system and CPU stability should be gauged via the suggested means before attempting an outright memory stability test.






Have fun!

Edited by Silent Scone - 5/21/17 at 12:38am
post #2 of 193
Praz--1700X@3.9---3200MHz-C14-13-13-39-1T---1.35v---SOC 0.98125v---BIOS 0079---HCI---800%/GSAT 2 Hours






post #3 of 193
I'll do this in a bit but I wanted to ask a question

> SOC 1.3v

I have been running SOC 1.25v to get a stable 3.9Ghz w/ 3200Mhz @ 14-14-14-34-1T Timings. What is the safe upper bound on SOC? Gigabyte "claims" that it's safe to set SOC up to 1.35v with air/liquid but every other source claims that you're crazy to go above 1.2v.

My issue is that I am *really close* to getting 4GHz w/ 3600 16-16-16-36-1T but I don't know where I am going wrong. Previously I ran this a single time, but it was very unstable.

This is with the Gaming K7.
post #4 of 193
Thread Starter 
Quote:
Originally Posted by Secret Dragoon View Post

I'll do this in a bit but I wanted to ask a question

> SOC 1.3v

I have been running SOC 1.25v to get a stable 3.9Ghz w/ 3200Mhz @ 14-14-14-34-1T Timings. What is the safe upper bound on SOC? Gigabyte "claims" that it's safe to set SOC up to 1.35v with air/liquid but every other source claims that you're crazy to go above 1.2v.

My issue is that I am *really close* to getting 4GHz w/ 3600 16-16-16-36-1T but I don't know where I am going wrong. Previously I ran this a single time, but it was very unstable.

This is with the Gaming K7.

I've amended the post, as was going on older information. It's been brought to my attention that anything above 1.2v can be potentially lethal. So your sources are right. It's recommended you do not exceed this voltage.
post #5 of 193
If the crosshair is autoing 1.15v for the soc with 2933 and 3200 ratios shouldn't it be safe? i don't see a reason to modify it unless 1.15v's isn't enough. why run lower than the auto soc voltage?

also isn't the greater than 1.2v for the soc crosshair exclusive? since originally asus had a bug that caused soc voltages higher than 1.0v to fry the embed controller on the crosshair. they patched it in 0902. elmor did say in testing up to 1.25v's is fine. anything higher can bring back the motherboard bricking bug of frying the embed controller on the crosshair. he advised 1.2v limit to leave some headroom as 1.25v is the max. so gigabyte might be correct at least for their boards since they might not have the possibility of frying their embedded controllers. i can't recall if amd has released any info publicly about max soc voltages for ryzen.
Edited by orlfman - 4/24/17 at 1:21am
strix
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen R7 1800x Asus X370 Crosshair Vi Hero EVGA 1080 FTW G.skill Flare X 3200 2x8 16gb 
Hard DriveHard DriveHard DriveCooling
2x Western Digital Black 2TB 2x 512GB Samsung 850 Pro 1x 512GB Samsung 950 Pro Noctua NH-D15S + 2x Corsair ML120's 
OSMonitorKeyboardPower
Windows 10 Education Dell S2417DG Ducky One White & Grey - Cherry Reds Evga Supernova G3 750 
CaseMouse
Corsair Air 740 Steelseries Rival 700 
  hide details  
Reply
strix
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen R7 1800x Asus X370 Crosshair Vi Hero EVGA 1080 FTW G.skill Flare X 3200 2x8 16gb 
Hard DriveHard DriveHard DriveCooling
2x Western Digital Black 2TB 2x 512GB Samsung 850 Pro 1x 512GB Samsung 950 Pro Noctua NH-D15S + 2x Corsair ML120's 
OSMonitorKeyboardPower
Windows 10 Education Dell S2417DG Ducky One White & Grey - Cherry Reds Evga Supernova G3 750 
CaseMouse
Corsair Air 740 Steelseries Rival 700 
  hide details  
Reply
post #6 of 193
I believe an "Auto rule" in UEFI is bumping SOC on RAM strap change. Not that UEFI "looks up a table" within CPU/SMU and say "hey set x for me".

I had 2x R7 1700, all same hardware :-

i) if UEFI on default and I changed RAM strap to 2400MHz SOC = ~1.050V for both CPU.

ii) if UEFI on default, thus 2133MHz, SOC measured on ProbeIt point for 1st = ~0.838V 2nd = ~0.893V
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #7 of 193
Quote:
Originally Posted by gupsterg View Post

I believe an "Auto rule" in UEFI is bumping SOC on RAM strap change. Not that UEFI "looks up a table" within CPU/SMU and say "hey set x for me".

I had 2x R7 1700, all same hardware :-

i) if UEFI on default and I changed RAM strap to 2400MHz SOC = ~1.050V for both CPU.

ii) if UEFI on default, thus 2133MHz, SOC measured on ProbeIt point for 1st = ~0.838V 2nd = ~0.893V
yeah i've noticed this as well with my 1800x. 2133mhz = ~0.8 - 0.9v's. 2400 = 1.0v. 2933 & 3200 1.15v. 2666mhz i've seen 1.13 - 1.15v. i'm assuming those auto's are perfectly safe for both motherboard and cpu. i doubt asus wants bugs again that will cause more frying of parts after the embed controller fiasco.
Edited by orlfman - 4/24/17 at 12:53am
strix
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen R7 1800x Asus X370 Crosshair Vi Hero EVGA 1080 FTW G.skill Flare X 3200 2x8 16gb 
Hard DriveHard DriveHard DriveCooling
2x Western Digital Black 2TB 2x 512GB Samsung 850 Pro 1x 512GB Samsung 950 Pro Noctua NH-D15S + 2x Corsair ML120's 
OSMonitorKeyboardPower
Windows 10 Education Dell S2417DG Ducky One White & Grey - Cherry Reds Evga Supernova G3 750 
CaseMouse
Corsair Air 740 Steelseries Rival 700 
  hide details  
Reply
strix
(14 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen R7 1800x Asus X370 Crosshair Vi Hero EVGA 1080 FTW G.skill Flare X 3200 2x8 16gb 
Hard DriveHard DriveHard DriveCooling
2x Western Digital Black 2TB 2x 512GB Samsung 850 Pro 1x 512GB Samsung 950 Pro Noctua NH-D15S + 2x Corsair ML120's 
OSMonitorKeyboardPower
Windows 10 Education Dell S2417DG Ducky One White & Grey - Cherry Reds Evga Supernova G3 750 
CaseMouse
Corsair Air 740 Steelseries Rival 700 
  hide details  
Reply
post #8 of 193
No idea.

I measure default SOC. Set SOC manually as required, so on remeasure they match stock. Then I up RAM strap and increase SOC as required.

1st R7 1700 2933MHz 14-14-14-14-34-1T VBOOT/VDIMM 1.35V, SOC: ~0.900V needed, could not attain 3200MHz, even with ~1.050V SOC and VCORE increase with offset of +181mV.

2nd R7 1700 3200MHz 14-14-14-34-1T VBOOT/VDIMM 1.35V, SOC: ~0.975V needed.

This was UEFI 1002 or 0902, all same HW except CPU. 1st CPU disposed of, 2nd still not reaching any higher yet. Both could use BCLK of 134MHz with lower RAM strap, with pretty much 0 tweaks to 3.8GHz / BCLK 100MHz profile. Each again attained same 2933MHz/3200MHz.
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #9 of 193
Thread Starter 
Quote:
Originally Posted by orlfman View Post

If the crosshair is autoing 1.15v for the soc with 2933 and 3200 ratios shouldn't it be safe? i don't see a reason to modify it unless 1.15v's isn't enough. why run lower than the auto soc voltage?

also isn't the greater than 1.2v for the soc crosshair exclusive? since originally asus had a bug that caused soc voltages higher than 1.0v to fry the embed controller on the crosshair. they patched it in 0902. elmor did say in testing up to 1.25v's is fine. anything higher can bring back the motherboard bricking bug of frying the embed controller on the crosshair. he advised 1.2v limit to leave some headroom as 1.25v is the max. so gigabyte might be correct at least for their boards since they might not have the possibility of frying their embedded controllers. i can't recall if amd has released any info publicly about max soc voltages for ryzen.

I don't believe it is exclusive, more a safe limit for the platform if sympathetic and also due to known failures using excessive voltage. What other vendors are saying is up to them, but I'm leaving the recommendation in this thread that 1.2v should not be exceeded, 1.25v maximum.
Edited by Silent Scone - 4/24/17 at 2:27am
post #10 of 193
gupsterg--1700@3.8---3200Mhz-C14-14-14-34-1T---1.35v---SOC 0.975v---BIOS 0082---HCI---400%

W10C, CPU Batch: UA 1709PGT Country: Malaysia.




Above quick run, same settings TPU MemTest64 ~16.5hrs. (Click to show)


Prior to above W7, HCI MemTest ~6hrs/1000%, 7x 2048MB on 0079 but ProcODT as 53.3Ω so is same as 0082.

Warning: Spoiler! (Click to show)

Edited by gupsterg - 5/21/17 at 12:46am
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
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