What causes this ryzen oc bug?

Scougar · 19 Oct 2017 at 23:43

So... What causes the bug where you can either clock memory or the CPU, but not together? (Exception seems to be if you use xmp on memory then you can).

Driving me nuts.

Undesirable · 26 Oct 2017 at 02:52

There shouldn't be a bug, unless it's a known issue with an older BIOS version on your motherboard, and you haven't bothered to update it. Even then, I doubt there would be a bug whereby you can't overclock them both together. It's probably a memory compatibility issue, as Ryzen's very fussy about the RAM type. Hopefully A.G.E.S.A. v1.0.0.7 will fix it. Motherboard manufacturers don't have access to the A.G.E.S.A. source code, only AMD, yet it is one of the most important factors in stability and memory compatability. Keep that BIOS on the latest beta version.

Scougar · 26 Oct 2017 at 18:04

Undesirable said:
There shouldn't be a bug, unless it's a known issue with an older BIOS version on your motherboard, and you haven't bothered to update it. Even then, I doubt there would be a bug whereby you can't overclock them both together. It's probably a memory compatibility issue, as Ryzen's very fussy about the RAM type. Hopefully A.G.E.S.A. v1.0.0.7 will fix it. Motherboard manufacturers don't have access to the A.G.E.S.A. source code, only AMD, yet it is one of the most important factors in stability and memory compatability. Keep that BIOS on the latest beta version.

I have previously overclocked both together without issue. My RAM is also Ryzen specific branded, and Samsung B-die.

Undesirable · 26 Oct 2017 at 20:05

Scougar said:
I have previously overclocked both together without issue. My RAM is also Ryzen specific branded, and Samsung B-die.

So there's no bug then?

Scougar · 26 Oct 2017 at 20:30

Undesirable said:
So there's no bug then?

lol. Yes. Just because you haven't encountered it, doesn't mean it doesn't exist. That is like saying, I haven't had the 1500mhz bug happen yet, but now it does....

Thinking about it... I don't remember trying to OC the memory before, only the Core.. I struggled last time to get the XMP to work correctly and not using XMP played havoc with the system. So.. I was incorrect about it.

Trying to manually set memory (even to the same settings as XMP) and OC the core does not work. The core will downclock to default settings

Undesirable · 27 Oct 2017 at 04:25

It simply isn't a bug if it straight up doesn't allow you to overclock high quality memory certified for use with Ryzen. It would be widely talked about on forums and hotfixes issued by MSI. If they don't have a stable or BETA BIOS that fixes your issue, then wait for A.G.E.S.A. v1.0.0.7. If still nothing after that, then I would suggest there's something wrong with your board. Have you increased the memory voltage when you overclock it? I need details on what BIOS settings you've changed to emulate the XMP and overclock the CPU.

jaffveyda · 27 Oct 2017 at 09:13

Scougar said:
So... What causes the bug where you can either clock memory or the CPU, but not together? (Exception seems to be if you use xmp on memory then you can).

Driving me nuts.

I had problem with stability when either ram or cpu voltage was too low, cranked them up.

Scougar · 27 Oct 2017 at 16:23

Undesirable said:
It simply isn't a bug if it straight up doesn't allow you to overclock high quality memory certified for use with Ryzen. It would be widely talked about on forums and hotfixes issued by MSI. If they don't have a stable or BETA BIOS that fixes your issue, then wait for A.G.E.S.A. v1.0.0.7. If still nothing after that, then I would suggest there's something wrong with your board. Have you increased the memory voltage when you overclock it? I need details on what BIOS settings you've changed to emulate the XMP and overclock the CPU.

jaffveyda said:
I had problem with stability when either ram or cpu voltage was too low, cranked them up.

My SOC is plenty high enough at 1.2V (which tbh is too high), My memory is at 1.43v and my chip I have run at 1.3v and 1.256v with no difference.

Let me be clear. IT IS WORKING with XMP at 3.7Ghz and 3200 at C14/16/16/16/36/55. WITH XMP turned on.

When I try to do it manually (note using XMP), it completely drops the OC from the CPU and goes back to stock. I can even OC it using the MSI software in windows after this if I want an it works. But doing it manually on different bios's without using XMP it just plain drops the CPU OC.

This is not a stability issue.

Undesirable · 27 Oct 2017 at 20:01

And you're not on an old BIOS?

AndreiD · 30 Oct 2017 at 06:44

@Scougar Keep SoC at 1.1v with no LLC (Auto) at most for 24/7, 1.2V is too high.
B-die should run at at 3200 with those timings without needing so much voltage.

Issue on some boards seems to be they don't have DRAM boot voltage settings, I get cold boot bugs because of it which makes my RAM settings unstable.

Scougar · 30 Oct 2017 at 11:17

Undesirable said:
And you're not on an old BIOS?

Nope.

I am now just trying out the latest V1A1 beta bios as well. Soon as I get 3200mhz on the ram to work again I will try it out.

Ste · 6 Nov 2017 at 02:13

Either a bug with your hardware combination that isn’t particularly replicated elsewhere or that SOC voltage is screwing you. I had major issues with it that high personally. Drop it to 1.1.