• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Ryzen DRAM Calculator by 1usmus

Hi guys,

thanks for the quick replies.
I added the system specs to my profile.
TSME was already turned off, that was the first thing I did, simply forgot to mention it.
I reduced VSOC to 1,25V, lower was not possible to boot into Windows, it crashed like 2s after login. 1,25V appears to be working correctly so far.
VDIMM is reduced to 1,38V, have to test if it will work with less.

xmpdefault.png

These are the old values with 3800Mhz and TSME on.


xmp4133.png


This is a current run with 1,38V and TSME off.

ZenTimings_Screenshot.png
 
I use XMP , about the same as fast preset .
 

Attachments

  • Captureimport xmp.PNG
    Captureimport xmp.PNG
    78.1 KB · Views: 315
4750G is a desktop CPU. Although yes it's restricted to OEM's it can still be bought in DIY market. And yes it needs to have the security features disabled to achieve optimal performance. Tho it is slower in (CPU limited) games than Zen 2 (direct comparisons are 3700X and 3800X). But it can run higher IF and memory clocks and lower latency once properly configured.
I know becvause i had one for testing. I managed to achieve 60,6ns latency with Hynix J-Die. With either Micron or Samsung B-die i would have gotten under 60ns (thats generally Zen 3 territory).

The calculator itselt needs a major update to support new chips. But im guessing 1usmus is busy wiith CTR program instead.
I suggest watching Buildzoid's videos instead. He's been messing around with Micron B-Die a lot recently.
Thanks for the notice... I wanted to say an APU not a mobile CPU.
 
Hi guys,

thanks for the quick replies.
I added the system specs to my profile.
TSME was already turned off, that was the first thing I did, simply forgot to mention it.
I reduced VSOC to 1,25V, lower was not possible to boot into Windows, it crashed like 2s after login. 1,25V appears to be working correctly so far.
VDIMM is reduced to 1,38V, have to test if it will work with less.

View attachment 185406
These are the old values with 3800Mhz and TSME on.


View attachment 185407

This is a current run with 1,38V and TSME off.

View attachment 185408
Find the timings used with Micron rev E DR fast at 3800, that might work as the new rev B seems to be a bit better than rev E at timings. Try safe if it doesn't work, that is very likely to work.
 
I have a question and some feedback. I want to OC 128GB RAM on a Threadripper platform from 3200 to 3600MHz. The main problem is that I'm running Linux and DRAM Calc is Windows only.
So here is my first question for @1usmus - how feasible is Linux port of DRAM Calc? Linux community might be small, but I think it can help with porting if there is will to do it.
Sorry for pinging you here, I don't have Twitter acc.

After couple attempts I was able to make it run through Wine, but I'm not familiar with memory OC and I cannot verify if it's giving correct results.
Second problem that I found was that there is no option for 8 DIMM modules. I don't know if this is the default or it's a Wine/Linux thing. If there is an option for sTRX platform there should be 8 DIMM option.
Third problem that I found was a lot unhandled exceptions, very similar to what is reporting @theGryphon here: https://www.techpowerup.com/forums/...for-ryzen-v1-7-2-released.266904/post-4262438

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

************** Exception Text **************
System.Management.ManagementException: Error code: 0x80041002
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.PropertyData.RefreshPropertyInfo()
   at System.Management.PropertyDataCollection.get_Item(String propertyName)
   at Ryzen_DRAM_Calculator_1._5._0.MainForm.MEMORY_STATUS()
   at Ryzen_DRAM_Calculator_1._5._0.MainForm.Form1_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at MetroFramework.Forms.MetroForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at MetroFramework.Forms.MetroForm.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.7.3
    Assembly Version: 1.7.3.0
    Win32 Version: 1.7.3.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/Ryzen_DRAM_Calculator_1.7.3.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MetroFramework
    Assembly Version: 1.2.0.3
    Win32 Version: 1.2.0.3
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/MetroFramework.DLL
----------------------------------------
HCIMemTestController
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929
    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
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.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.

Code:
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.ParseManualSetting()
   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 MetroFramework.Controls.MetroTile.OnMouseUp(MouseEventArgs e)
   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.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.7.3
    Assembly Version: 1.7.3.0
    Win32 Version: 1.7.3.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/Ryzen_DRAM_Calculator_1.7.3.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MetroFramework
    Assembly Version: 1.2.0.3
    Win32 Version: 1.2.0.3
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/MetroFramework.DLL
----------------------------------------
HCIMemTestController
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929
    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
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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.
 
I have a question and some feedback. I want to OC 128GB RAM on a Threadripper platform from 3200 to 3600MHz. The main problem is that I'm running Linux and DRAM Calc is Windows only.
So here is my first question for @1usmus - how feasible is Linux port of DRAM Calc? Linux community might be small, but I think it can help with porting if there is will to do it.
Sorry for pinging you here, I don't have Twitter acc.

After couple attempts I was able to make it run through Wine, but I'm not familiar with memory OC and I cannot verify if it's giving correct results.
Second problem that I found was that there is no option for 8 DIMM modules. I don't know if this is the default or it's a Wine/Linux thing. If there is an option for sTRX platform there should be 8 DIMM option.
Third problem that I found was a lot unhandled exceptions, very similar to what is reporting @theGryphon here: https://www.techpowerup.com/forums/...for-ryzen-v1-7-2-released.266904/post-4262438

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

************** Exception Text **************
System.Management.ManagementException: Error code: 0x80041002
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.PropertyData.RefreshPropertyInfo()
   at System.Management.PropertyDataCollection.get_Item(String propertyName)
   at Ryzen_DRAM_Calculator_1._5._0.MainForm.MEMORY_STATUS()
   at Ryzen_DRAM_Calculator_1._5._0.MainForm.Form1_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at MetroFramework.Forms.MetroForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at MetroFramework.Forms.MetroForm.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.7.3
    Assembly Version: 1.7.3.0
    Win32 Version: 1.7.3.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/Ryzen_DRAM_Calculator_1.7.3.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MetroFramework
    Assembly Version: 1.2.0.3
    Win32 Version: 1.2.0.3
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/MetroFramework.DLL
----------------------------------------
HCIMemTestController
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929
    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
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.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.

Code:
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.ParseManualSetting()
   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 MetroFramework.Controls.MetroTile.OnMouseUp(MouseEventArgs e)
   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.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Ryzen DRAM Calculator 1.7.3
    Assembly Version: 1.7.3.0
    Win32 Version: 1.7.3.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/Ryzen_DRAM_Calculator_1.7.3.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
MetroFramework
    Assembly Version: 1.2.0.3
    Win32 Version: 1.2.0.3
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/MetroFramework.DLL
----------------------------------------
HCIMemTestController
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///Z:/home/dn/DRAM-Calculator-for-Ryzen-1.7.3/HCIMemTestController.DLL
----------------------------------------
System.Windows.Forms.DataVisualization
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929
    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
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
    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.0.30319.17929 built by: FX45RTMREL
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.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.

Serious question?

Why are you trying to overclock 128GB of ram on a workstation build?

Isn't stability a priority on that machine?
 
Hey guys, first time builder here.
Specs -
Ryxn 5600X
Arctic Freezer Duo 34 (Single tower dual fan air cooler)
MSI X570 Tomahawk WiFi
4 x 8GB Crucial Ballistix 3600mhz CL 16
ROG Strix Rx 5700 XT OC
I have done hours of research into parts and compatabiolity, overclocking both cpu and gpu (would ahve loved a 30 series NVIDIA what whatever), and gotten to RAM. I have basically the XMP enabled and want to know if its worth any performance gains in any titles both old and new, and if it would impact day to day performance for responsiveness to tune the RAM further.
 
hello guys so i recently purchased this kit on bestbuy.

https://www.bestbuy.com/site/corsai...ptimized-memory-black/6434211.p?skuId=6434211



CMW16GX4M2Z4000C18



I got a great deal plus rgb and i went ahead and purchased them. Now whats the best way i could run them. I have Asus Tuf Gaming x570

AMD 3900x

rtx 3080

The kit is rated at 18-22-22-42 4000mhz

For some reason i am unable to post pictures so is gonna be a little more complicated for me to explain as my English is bad.

Anyways i went ahead and downloaded Taiphoon and Dram Calculator for Ryzen.

I exported the ram info from taiphoon and imported them to dram as doing it manually was giving me errors, now i know this kit is not bdie. it was what i could get at the moment. so after all the settings tru bios i was able to have them at 3200mhz 1-1 1600, Cas 14-17-17-34

Should i run them like that or what!? i tried 3600mhz but i couldnt boot up. Could be because of the dram voltage with those settings, it was asking me to do 1.400, at the moment mine is running at the rated voltage 1.35
 

Attachments

  • settings.JPG
    settings.JPG
    145.8 KB · Views: 205
  • 14.JPG
    14.JPG
    34.5 KB · Views: 202
  • ram.JPG
    ram.JPG
    143.2 KB · Views: 185
  • 3600.JPG
    3600.JPG
    145.3 KB · Views: 186
@Antrax360
Run ZenTimings and screenshot here...

1613951104046.png



Also, something like this would help...

1613951282946.png

I wouldn't recommend to run them CL14-17-17...
Something like 16-18-18-18-38 or 16-19-19-19-38 at 3200~3600MHz (1:1:1) would be more feasible. And voltage should be ok for your sticks to go up to 1.38~1.4V, only if necessary.

Did you run any memory benchmark like AIDA64?
 
Last edited:
@Antrax360
Run ZenTimings and screenshot here...

View attachment 189390


Also, something like this would help...

View attachment 189391

I wouldn't recommend to run them CL14-17-17...
Something like 16-18-18-18-38 or 16-19-19-19-38 at 3200~3600MHz (1:1:1) would be more feasible. And voltage should be ok for your sticks to go up to 1.38~1.4V, only if necessary.

Did you run any memory benchmark like AIDA64?
I dont have aida64, i downloaded a free trial dont know if that helps. Here are the results. With the numbers i showed before, i havent messed with that anymore, i did some light gaming and no crashes.
 

Attachments

  • zen.JPG
    zen.JPG
    51.2 KB · Views: 350
  • aida.JPG
    aida.JPG
    60.2 KB · Views: 219
Yes it helps.
The good news is that your Corsair kit is fully compatible with Ryzen, as its a "Z" series (see Z4000 in part number).
The bad news is that your memory latency is pretty bad at 76+ns.

Dont try to tight timings and stay at 3200MHz. You need expensive bdies to achieve anything at that speed. You should increase speed to 3533~3600MHz with loosen timings like the ones I wrote on #309. Ryzens need a balance between speed and timings to achieve better memory performance. I've seen CJR/DJR sticks to achieve 3800MHz CL16-19-19-19-38 with 1.38V. Yours are Micron E/H die? Dont know what are capable of, but worth trying higher speeds. If you manage to decrease memory latency to around or even under 70ns it would be great. High speed (3733~3800MHz) and tight timings B-dies are in the middle/low 60s (62~65ns).
 
Yes it helps.
The good news is that your Corsair kit is fully compatible with Ryzen, as its a "Z" series (see Z4000 in part number).
The bad news is that your memory latency is pretty bad at 76+ns.

Dont try to tight timings and stay at 3200MHz. You need expensive bdies to achieve anything at that speed. You should increase speed to 3533~3600MHz with loosen timings like the ones I wrote on #309. Ryzens need a balance between speed and timings to achieve better memory performance. I've seen CJR/DJR sticks to achieve 3800MHz CL16-19-19-19-38 with 1.38V. Yours are Micron E/H die? Dont know what are capable of, but worth trying higher speeds. If you manage to decrease memory latency to around or even under 70ns it would be great. High speed (3733~3800MHz) and tight timings B-dies are in the middle/low 60s (62~65ns).
Beautiful I will go back and re test. I'll use regular xmp profile which I used for about 2 weeks. At rated speeds. Then post results at the other speeds.
 
Yes it helps.
The good news is that your Corsair kit is fully compatible with Ryzen, as its a "Z" series (see Z4000 in part number).
The bad news is that your memory latency is pretty bad at 76+ns.

Dont try to tight timings and stay at 3200MHz. You need expensive bdies to achieve anything at that speed. You should increase speed to 3533~3600MHz with loosen timings like the ones I wrote on #309. Ryzens need a balance between speed and timings to achieve better memory performance. I've seen CJR/DJR sticks to achieve 3800MHz CL16-19-19-19-38 with 1.38V. Yours are Micron E/H die? Dont know what are capable of, but worth trying higher speeds. If you manage to decrease memory latency to around or even under 70ns it would be great. High speed (3733~3800MHz) and tight timings B-dies are in the middle/low 60s (62~65ns).
High speed tight timing B die has less than 60ns. Standard B die is 60-65. I have 55.
 
High speed tight timing B die has less than 60ns. Standard B die is 60-65. I have 55.
Im talking about 3000 series and you about 5000 series. There's a difference...
 
Im talking about 3000 series and you about 5000 series. There's a difference...
I cant get it to post any higher than the speeds I posted previously at least not manual. Only xmp profile of 4000mhz at cl18. I tried all sort of combinations and nothing. So went back to 3200mhz at cl14
 
I cant get it to post any higher than the speeds I posted previously at least not manual. Only xmp profile of 4000mhz at cl18. I tried all sort of combinations and nothing. So went back to 3200mhz at cl14
Can you be more specific about what you tried exactly?
1. Speed, voltage, timings?
2. What DRAMcalculator suggests for 3600MHz?

Something that we didn't talk about is other memory subsystem's voltages like memory controller voltage (CLDO VDDP), Infinity Fabric voltage (CLDO VDDG IOD & VDDG CCD) and of course I/O die voltage (VSOC). Probably all these need tweeking and if you notice the Ryzen DRAM Calculator includes them too. I can see from your ZenTimings screenshot that those voltages are kinda low, bare minimum for stock settings only (up to 1600MHz).

ZenTimings_005.png
 
Can you be more specific about what you tried exactly?
1. Speed, voltage, timings?
2. What DRAMcalculator suggests for 3600MHz?

Something that we didn't talk about is other memory subsystem's voltages like memory controller voltage (CLDO VDDP), Infinity Fabric voltage (CLDO VDDG IOD & VDDG CCD) and of course I/O die voltage (VSOC). Probably all these need tweeking and if you notice the Ryzen DRAM Calculator includes them too. I can see from your ZenTimings screenshot that those voltages are kinda low, bare minimum for stock settings only (up to 1600MHz).

View attachment 189428
it recommended these settings. i tried your cl6 19 19 19 38 as well and nothing.
 

Attachments

  • 3600.JPG
    3600.JPG
    145.3 KB · Views: 145
I would use these

3600_b.png
 
Beautiful i will try those settings thank you soooo so much. Question when the computer doesnt boot because of those settings not working, that doesnt hut my hard drive or anything right? I mean i have to force shut down and reset. I got a blue screen once i needed to repair a file as well lol.
 
@Stinnerman
you can try tightening the timings, but with 4 sticks i wouldnt expect too much (but try).

@Antrax360
do you have the latest bios?
nothing prior made the 3600 kit in my friends rig work at full speed.
4000cl19 will not run on yours, only 5xxx series chip will really go past 1800 IF (without lots of tweaking stuff).

choose the xmp profile, but set the multi for the ram manually to 36x (rather than 40x on auto),
make sure to turn off gear down/power down, and set 2T manually.
not many boards run 1T out of the box, so unless you know its stable (TM5 or HCI),
use 2T first...
 
@Stinnerman
you can try tightening the timings, but with 4 sticks i wouldnt expect too much (but try).

@Antrax360
do you have the latest bios?
nothing prior made the 3600 kit in my friends rig work at full speed.
4000cl19 will not run on yours, only 5xxx series chip will really go past 1800 IF (without lots of tweaking stuff).

choose the xmp profile, but set the multi for the ram manually to 36x (rather than 40x on auto),
make sure to turn off gear down/power down, and set 2T manually.
not many boards run 1T out of the box, so unless you know its stable (TM5 or HCI),
use 2T first...
When I bought the ram I just went into bios. Enabled docp and it selected 4000mhz. Just booted up and used it like that. It was running fine no issues at cl19. Just wanted to try better timings.

Doesn't boot with those settings.
 
When I bought the ram I just went into bios. Enabled docp and it selected 4000mhz. Just booted up and used it like that. It was running fine no issues at cl19. Just wanted to try better timings.
Can you post a ZenTimings screenshot of the 4000 settings that worked? Maybe this would be your starting point and go from there instead of trying random settings.
DRAM oc can be pain and needs patience.
 
Can you post a ZenTimings screenshot of the 4000 settings that worked? Maybe this would be your starting point and go from there instead of trying random settings.
DRAM oc can be pain and needs patience.
those are xmp profiles for 4000mhz. I will also include the timings you recommended i was able too boot but only changing to 16-19-19-19-38 then the volts everything else is on auto. So there must be a setting that dram is giving me that i am getting no boot, i didnt know i could do it in parts and boot. Am sorry first time. So i will keep changing those numbers to see what works best

those are xmp profiles for 4000mhz. I will also include the timings you recommended i was able too boot but only changing to 16-19-19-19-38 then the volts everything else is on auto. So there must be a setting that dram is giving me that i am getting no boot, i didnt know i could do it in parts and boot. Am sorry first time. So i will keep changing those numbers to see what works best
i included what dram is suggesting which u already helped me with, i never included the advanced settings. is that any relevant, says my ram could achieve 4597 cl16
 

Attachments

  • docp.JPG
    docp.JPG
    49.8 KB · Views: 204
  • ur timings.JPG
    ur timings.JPG
    54.8 KB · Views: 225
  • 3600 timung.JPG
    3600 timung.JPG
    49.3 KB · Views: 230
  • dram suggestion.JPG
    dram suggestion.JPG
    144.1 KB · Views: 159
  • potential.JPG
    potential.JPG
    99.2 KB · Views: 196
it recommended these settings. i tried your cl6 19 19 19 38 as well and nothing.
It spit out those timings? That is some crazy crap. 14-19-19-19 are whacked timings, the gap from 14-19 is like canyon wide.
those are xmp profiles for 4000mhz. I will also include the timings you recommended i was able too boot but only changing to 16-19-19-19-38 then the volts everything else is on auto. So there must be a setting that dram is giving me that i am getting no boot, i didnt know i could do it in parts and boot. Am sorry first time. So i will keep changing those numbers to see what works best
The xmp 4000 is not really working or its very misleading as its running memory at a poor ratio ie. with fclk and uclk mismatched.
 
It spit out those timings? That is some crazy crap. 14-19-19-19 are whacked timings, the gap from 14-19 is like canyon wide.

The xmp 4000 is not really working or its very misleading as its running memory at a poor ratio ie. with fclk and uclk mismatched.
What should I do next then? What about the other numbers!? Leave them on auto!? Latency improved a lot. 69 with your numbers.
 
Back
Top