Ryzen DRAM calculator updated

Alan1969 · 3 Feb 2020 at 13:01

to version 1.7.0

https://www.techpowerup.com/263451/dram-calculator-for-ryzen-by-1usmus-v1-7-0-released

https://www.gamersnexus.net/news-pc...nerability-amd-rdna2-gn-china-trip-in-the-air

Added functionality to read current memory timings for Zen 2 (AM4).
Added a memory bandwidth test (Read and Write).
Added an Inter-Core Latency test (AM4).
Improved the accuracy of Random and Custom latency test.
Some changes in the suggested CAD_BUS settings. This could offer a significant improvement in stability for configurations with two or more RAM modules.
VDDG setting is now divided into two independent settings: VDDG IOD and VDDG CCD voltage (as in AGESA 1004B bioses).
"Compare timings" now works for Zen 2 (AM4).
Added support for 3000 series Threadripper CPUs (Castle Peak).
Minor user experience GUI changes.
Added support for Hynix DJR (a new CJR revision that has backward compatibility with classic CJR).
Minor bugfixes

keenan · 3 Feb 2020 at 13:03

Thanks for the headsup!

Alan1969 · 3 Feb 2020 at 13:04

it has threadripper 3000 support
https://www.tomshardware.com/uk/news/1usmus-overclocking-dram-calculator-amd-threadripper-3000

GregI · 3 Feb 2020 at 13:15

It's an interesting update.

Here is my previous config it told me:
Current: https://i.imgur.com/Z62VTh1.png
Previous: https://i.imgur.com/WJ3M1bM.png

Timings stayed the same but Soc voltage has taken a drastic decrease in favor of bumping up the VDDG voltages. Don't know if I agree with that. CADBusClkDrv in bottom right also went from 24 to 30

Not sure if these changes eek more stability than previous version but since the 1.0.04, it was greatly needed.

opethdisciple · 3 Feb 2020 at 13:34

Yes, VDDG is very important for FCLK stabilisation.

That was the missing ingredent for me to get my CPU to stop crashing at 1800 FCLK.

I set VDDG to 1.0v and it's been happy for hundreds of hours since. (I did 165hrs in Odyssey alone at these settings)

Blackbadger · 3 Feb 2020 at 13:35

It maybe false positve due it being new, however the archive contains a memspeed.exe which is picked up as a trojan/backdoor by various scanners.
The previous version 1.6 scan's cleanly.

Not seen anyone else mention this..

For example..

Alibaba

Backdoor:Win32/Generic.bdced989

Cylance

Unsafe

Microsoft

PUA:Win32/Presenoker

Qihoo-360

Win32/Backdoor.762

opethdisciple · 3 Feb 2020 at 14:05

Either false positive or it has been compromised.

Best avoid it just in case for now.

GregI · 3 Feb 2020 at 16:25

opethdisciple said:
Yes, VDDG is very important for FCLK stabilisation.

That was the missing ingredent for me to get my CPU to stop crashing at 1800 FCLK.

I set VDDG to 1.0v and it's been happy for hundreds of hours since. (I did 165hrs in Odyssey alone at these settings)

Can you go into more detail about how you did stability tests for FCLK? I had mines at 1866 and although it worked I had a brief freeze in a game so I went back to 1800.

Also I scanned memtest with windows defender and malwarebytes, no threats here.

opethdisciple · 3 Feb 2020 at 16:30

Mine was easy. Anything over 1800MHz I would get audio corruption in windows. Only disappeared when I lowered it to 1800MHz

Alan1969 · 4 Feb 2020 at 14:19

I have used this for a few months now but I seem to remember that in the calculator the extreme settings hadn't been finished. Does anyone know when these will appear?

(and don't say when he has finished them!)

Overlag · 9 Feb 2020 at 16:28

I can never get these to work, on my Corsair 3200 or my Ballistix Elite 3600 memory these settings either dont post or throw up loads of memtest errors.

opethdisciple · 9 Feb 2020 at 23:36

I've not had any luck with it either. It's not magically gonna overcome hardware limitations.

GregI · 13 Feb 2020 at 15:09

Overlag said:
I can never get these to work, on my Corsair 3200 or my Ballistix Elite 3600 memory these settings either dont post or throw up loads of memtest errors.

People forget DRAM also has an advanced tab you can look at to configure further but yes, they rarely work. I've found copying every setting but setting geardown mode to enabled will always pass. I know this is now 1.5T Command rate but it still beats XMP almost always.

Also I don't want to insult anyone's intelligence but make sure you very clearly read the names of your settings and match them up to your motherboard. Most times it is in order but sometimes it's not, particularly on Asus boards.

For example: https://i.imgur.com/IGRdQaV.png
Does not match Asus order: https://i.imgur.com/09qVNZR.png

Write delay and read delay are swapped. Pay no attention to the numbers inputted in Asus screenshot, just quickly grabbed it from a random YouTube video.

Twinz · 15 Feb 2020 at 21:24

I have an issue with the new version where it won't import the XMP profile. I would normally assume operator error, but I have no problem importing XMP into the old version.

Nghtmare · 18 Feb 2020 at 18:08

I personally spend many days and hrs testing when Ryzen 3000 was released in July. If you already have your settings working fine, I don't think its worth messing with the values again.

Twinz · 18 Feb 2020 at 21:14

Twinz said:
I have an issue with the new version where it won't import the XMP profile. I would normally assume operator error, but I have no problem importing XMP into the old version.

I have the same issue.

ANDARIAL · 20 Feb 2020 at 09:04

I just wish bios creators and istmus would ALL use the same abreviations
Its like a quiz show for me trying to find the `correct`one to use