Monday, May 11th 2020

DRAM Calculator for Ryzen v1.7.2 Released

Yuri "1usmus" Bubliy over the weekend released the latest version of DRAM Calculator for Ryzen, the definitive tool for overclocking and optimizing memory on your AMD Ryzen-powered PC. The tool lets you calculate the best possible memory-related settings specific to your machine. Version 1.7.1 introduces several new changes. For starters, it now has updated presets for three of the most popular DDR4 DRAM die types obtained from hundreds of hours of re-testing various brands of memory modules on the latest version of AMD AGESA. These affect everything from procODT to VDDG settings, and the introduction of CL15t, which stabilizes problems encounted in finding timings with CL14t.

The R-XMP button (which attempts to translate your DIMM's XMP to AMD-compatible settings), and "Calculate EXTREME" buttons have been removed, and in their place, the "Calculate FAST" button has been optimized for the best possible stable settings; and "Calculate SAFE" for reasonably fast yet safe settings. DRAM Calculator for Ryzen now has DIMM PCB revision awareness. Several popular memory vendors have multiplie revisions of PCBs for the same DIMMs (and same DRAM chips, which can affect tuning headroom). This provides an additional layer of accuracy in calculating timings. In addition, there are several UI changes, such as a "compare timings" button with added functionality. Preliminary support is also added for future "Zen 3" based processors. Grab the tool from the link below.

DOWNLOAD: DRAM Calculator for Ryzen v1.7.2 by 1usmus
The change-log follows.

Update 09:07 UTC: The DRAM Calculator for Ryzen has just been updated to v1.7.2. Detailed below.

  • Reworking of all presets for Samsung b-die, Micron e-die and Hynix CJR (DJR). Improved support for configurations with 4 or 8 RAM modules.
  • R-XMP and Calculate EXTREME buttons removed.
  • Added new Help and my reviews section, which provides links to my materials in addition to reference information.
  • DRAM PCB Revision - select PCB RAM for more accurate calculation of timings. In most cases it is recommended to use "A0" for better compatibility.
  • The "Compare timings (ON/OFF)" button has received updated functionality. It can read not only the timings, but also show the state of the timings in color. Your personal assistant for creating individual presets.
  • Added "New version?" button, which allows you to visit the product homepage and read the materials regarding DRAM Calculator for Ryzen, check for updates or ask any question.
  • Error fixes and some graphical adjustments.
  • Timings read support for all Ryzen family processors (including future Zen 3 processors).
Version 1.7.2 change-log
  • Support OC assist for Micron E-die (A2) and CJR/DJR (A0 and A2)
  • Some correction for OC assist (Samsung B-die)
  • Additional presets for Hynix CJR / DJR (now A0 and A2)
  • Error fix: "Parse data"
  • Minor fix: voltage for Samsung B-die
  • Minor fix: some timings for Micron E-die
  • Minor fix: tWRRD for 4 DIMM configuration
  • Other bug fixes
Add your own comment

22 Comments on DRAM Calculator for Ryzen v1.7.2 Released

#1
karozy
So... will there be support for the weird Micron J mem chip found in Kingston's 2666 rams?
Posted on Reply
#3
ZoneDymo
King Mustard
Do Intel CPUs need a tool like this?
seeing as the 6700k did not need this when it came out in 2015 and Intel has just been rebranding it, nope they do not.
Posted on Reply
#4
Tomorrow
karozy
So... will there be support for the weird Micron J mem chip found in Kingston's 2666 rams?
Unlikely. Same as Hynix JJR that is used in many Kingston HyperX kits.
Posted on Reply
#5
stimpy88
King Mustard
Do Intel CPUs need a tool like this?
No, they don't "need" this tool. And neither does Ryzen.

But Intel users could "need" a tool like this if they also want to maximise their memory performance, as no XMP profile will tune a system like this tool can.
Posted on Reply
#6
XL-R8R
Condensing the releases/updates instead of putting out a new version every 4 days (unless a priority) is probably a kinder approach to take; I admit, the programme is tiny in size, but still.



Good stuff nonetheless.


Edit -> typo in the download link - 1.71 vs 1.72 - copy/paste error @btarunr.
Posted on Reply
#7
theGryphon
stimpy88
No, they don't "need" this tool. And neither does Ryzen.

But Intel users could "need" a tool like this if they also want to maximise their memory performance, as no XMP profile will tune a system like this tool can.
Bug report for 1usmus: After I import an XMP, it shows the loaded ns timings as before, but when I click on either of the calculate buttons, those ns timings just turn to zeros, which didn't happen before the 1.7.1 update.

Posted on Reply
#8
GoldenX
theGryphon
Bug report for 1usmus: After I import an XMP, it shows the loaded ns timings as before, but when I click on either of the calculate buttons, those ns timings just turn to zeros, which didn't happen before the 1.7.1 update.


Select Manual instead of A0.
Posted on Reply
#9
theGryphon
GoldenX
Select Manual instead of A0.
Hmm, Manual actually produced this error


and when I said continue, it gave me this kinda corrupt output:



The suggested timings above in Manual seem way too aggressive. Having worked on this DJR sticks for a while, C14 doesn't seem at all possible at 3800.
A2 profile produces suggestions that are very close to my experience with these sticks...

Another thing I noticed, when I use Manual, Compare Timings doesn't work...

PS1: I found a way to avoid the error with Manual. First select Samsung B or Micron E/H, run Calculate. Then change to Hynix CJR/DJR, run calculate. The problem I found here though is that if I select Micron E/H first, and then Hynix CJR/DJR, the DRAM voltage does not recalculate.

PS2: Here is the Details of the error report above:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.FormatException: Input string was not in a correct format.
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
at Ryzen_DRAM_Calculator_1._5._0.MainForm.v_drammin()
at Ryzen_DRAM_Calculator_1._5._0.MainForm.Calculate_SAFE_BTN(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.7.2
Assembly Version: 1.7.2.0
Win32 Version: 1.7.2.0
CodeBase: file:///D:/SetupFiles/NewPC/Tools/Monitoring/DRAM%20Calculator%20for%20Ryzen%201.7.2/DRAM%20Calculator%20for%20Ryzen%201.7.2.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MetroFramework
Assembly Version: 1.2.0.3
Win32 Version: 1.2.0.3
CodeBase: file:///D:/SetupFiles/NewPC/Tools/Monitoring/DRAM%20Calculator%20for%20Ryzen%201.7.2/MetroFramework.DLL
----------------------------------------
HCIMemTestController
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/SetupFiles/NewPC/Tools/Monitoring/DRAM%20Calculator%20for%20Ryzen%201.7.2/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3815.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.DataVisualization/v4.0_4.0.0.0__31bf3856ad364e35/System.Windows.Forms.DataVisualization.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Posted on Reply
#10
Punkenjoy
A good feature would be the tool to detect what motherboard you have and let you know what options are available to set by you and what are the proper name.

i tried this tools but i never managed to get a stable ram with the setting i was trying to put. So i just stay with my XMP settings. I had to figure out a bit what setting was what. At least the new feature to read current settings will help to make it easier to figure out what it what.

But overall, thx for making this incredible tool, i was not be able to make it run but at the same time, i am not sure if it's because i do it wrong, or if it's another case of my incredible luck with silicon lottery.
Posted on Reply
#11
AnarchoPrimitiv
Punkenjoy
A good feature would be the tool to detect what motherboard you have and let you know what options are available to set by you and what are the proper name.

i tried this tools but i never managed to get a stable ram with the setting i was trying to put. So i just stay with my XMP settings. I had to figure out a bit what setting was what. At least the new feature to read current settings will help to make it easier to figure out what it what.

But overall, thx for making this incredible tool, i was not be able to make it run but at the same time, i am not sure if it's because i do it wrong, or if it's another case of my incredible luck with silicon lottery.
I had the same problem and just ended up giving up as I figured it'd be such a minimal performance gain that it'd be impossible to notice anyway.

What would really be nice is if the program could just apply the settings for you and restart automatically
Posted on Reply
#12
Maxson
I'm trying the new version out and how do we work out what DRAM PCB Revision we have?

Posted on Reply
#13
Caring1
Maxson
I'm trying the new version out and how do we work out what DRAM PCB Revision we have?


In the O.P.
"In most cases it is recommended to use "A0" for better compatibility"

Or download Typhoon Burner to check the specifics of the Ram you have.
You can then Export those details to the Dram Calc.
Posted on Reply
#14
Maxson
Caring1
In the O.P.
"In most cases it is recommended to use "A0" for better compatibility"
Except for Micron E die A0 is not available. If I select A0 and click calculate fast or calculate safe it will say 'Please, check A2, bad bin or manual.'
Posted on Reply
#15
JapanMan
(Requist: From Japan)
The Offset voltage is changed to 0.1250V by BIOS of Ryzen. The cause of its bug and a mechanism were specified.

-Offset problem -
Basic : 0,0250V << Probably.
XFR: 0.0500V
TB: 0.0500V

Question) Why is Offset changed to 0.025+0.05+0,05 = 0.125V?
1) Vcore and 2) Base Offset 3) TB and 4) XFR

That's a principle of the program mistake added up:.
MOD which makes "P0 State" that.
But because the voltage is input double, 2.5V hangs.
There is a voltage limiter, so the voltage it doesn't take for that is corrected automatically.

⇒ That's the numerical value remains bug of the "power" in an equipped exchange "defense" (It's the bug work which occurs in SFC: GADYURIN.)
⇒ It's exchanged for Excalibur after an equipped exchange is removed once when it's original.
⇒ When exchanging it directly without removing a weapon, because you don't return it to the beginning, a parameter will be power 50 + weapon 166 + weapon 166 (Power increases in 380.)

In case of a TB boost program
(X) the way to change for that is impossible as a program.
(◎) It's a way right to increase after it's returned to the original numerical value.
Without returning the numerical value, TB and XFR change the numerical value just as it is, it's developed into the numerical value remains bug by the thing you (have added).

Offset is the mechanism added up.
One with an X does an X nothingness, and lay is also the trick to need the voltage wastefully 0.05 V (It's a presence of XFR.)
XFR and TB become effective at default. And it develops into Offset0.1250V problem ⇒ CPU is lack of the voltage and is a boot, and it isn't put on.
To refer to more biggest clocks of 1.40V or 1.50V for default, a fixation kill⇒ mother is dead (The voltage be reset for some reason, a bumpkin includes it, and.)

---
Offset increases 0.125 V by a defect of a TB boost. When a PC made an error, CMOS will be default automatically. But the voltage isn't reset. A TB boost will be "ON".
When it's Ryzen 3600, the SoC voltage should be set as more than 1.05 V.

Ryzen 1700 3.5Ghz 1.0750V + Offset 0.1250 = Vcore 1.2250V SoC AUTO (1.10V)
Ryzen 1600AF 3.8GHz 1.10V + Offset 0.1250 = Vcore 1.250V SoC AUTO (1.10V)
Ryzen 3600 0ffset -0.10V 4.0GHz ( 1.15V+Offset 0.1250V) = Vcore 1.2750V SoC 1.0750V
Ryzen 4600 Offset -0.10V 4.2Ghz ( 1.15V+Offset0.1250V) = Vcore 1.2750V SoC 1.125V
This bug is form March 2017 to 2020 Ryzen All BIOS
Posted on Reply
#17
GoldenX
Turns out my RAM is not Samsung B-die, it's C-die... I want to punch a puppy.
What should I use as reference in that case, Samsung OEM?
Posted on Reply
#18
lynx29
GoldenX
Turns out my RAM is not Samsung B-die, it's C-die... I want to punch a puppy.
What should I use as reference in that case, Samsung OEM?
please only hug puppies ; ;

just use dram calculator, it tells you what to make all your settings at... thats why i asked my question in post 17... im curious what peoples resuylts have been on dram calculator but not bdie related
Posted on Reply
#19
GoldenX
Yeah, but there is no preset for C-die.
Posted on Reply
#20
lynx29
GoldenX
Yeah, but there is no preset for C-die.
is there anyway to tell what die that ram i linked it? any database i can search? i want to make sure whatever i buy is compatible with the dram calculator
Posted on Reply
#21
Caring1
lynx29
is there anyway to tell what die that ram i linked it? any database i can search? i want to make sure whatever i buy is compatible with the dram calculator
buildapcsales/comments/ehuefd
Posted on Reply
#22
lynx29
Caring1
buildapcsales/comments/ehuefd
nice find, one of the comments on reddit says that is bdie, no way that is bdie... hmmm... i bet i could manage to get it to hit 3600 cas 16 though with a voltage bump and not changing anything else.
Posted on Reply
Add your own comment