Ryzen 1600 keeps defaulting to 1500

[iamthenugget]

As above I have the 1600 with msi x370 pro gaming carbon

When.ever I try any sort or Overclocked at all the clocks sit at 1500mhz and never go above until I do a full reset on of the bios and load optimised defaults.


Any suggestions as to what I'm doing wrong.

TiA

 

[iamthenugget]

have the same as you what bios are you running?

hello

im running 1.70 bios. not sure what the problem is but i dont feel comfortable running auto volts.

also ive had this problem on bios 1.5, 1.6 and 1.7 making my cpu pretty much useless.

 

[iamthenugget]

Over at reddit, the guys are saying this happen when using auto volts.

thing is when i use auto volts I DONT have this problem only when i manually set voltage.

on a side note at least my ram runs at its full 3200 with no problems

 

[iamthenugget]

mmm strange as im on the beta bios so i will upgrade to 1.7
but i have put the cpu voltage to 1.4 x40 multi and upped soc to 1.1v
got my 3000mhz ram @2933... done some cinebench bit of encoding and played games and it's been fine, i'm even thinking of dropping the volts

any volts i manually imput over about 1.29 automatically downclocks all cores to 1500 x15

 

[iamthenugget]

have you tried to run the OC with your ram at 2133mhz just to see if that has an effect?
Or even 2400, 2666mhz?

yes tried every combo you can think of and literally everything is rock solid until i manually input volvts.

4.2 auto runs 3 or 4 runs of cinebench easy with 1.368 auto volts yet 3.2 @1.295v results in an instant 15x and 1.5 core speed

 

[iamthenugget]

So why not just settle on 4.0/4.1ghz on 1.368v? A lot of people would be very happy with that overclock.

The added benefit of being on auto volts is that the chip will clock down and undervolt when idle (just make sure you ahve selected Ryzen Balanced or Balanced power profile).

i can only run my ram at 2133 and i would really like to have control over volts etc as i have no idea what they upvolt to. hwmonitor shows a max og 1.45 which is way too high for my liking

 

[iamthenugget]

Same problem here on my X370 Carbon. Really disappointing bug but that's early adopting I guess.

I was specifically told I was not an early adopter to ryzen here about 6 or 7 weeks back as all teething problems had been solved.

Surely this late in the day is late comers should expect stability

 

[iamthenugget]

strange it has not happened to me

hmmmm i dont know. i really should take screenshots???

 

[iamthenugget]

here is a reply straight from MSI

Let's set some things straight.
The overclock IS working....
What isn't is the AGESA code from AMD.
The CPU is getting stuck in a lower power state and not clocking up to it's max. It's a pretty known issue with Ryzen right now, and users across ALL OEM's (so Asus, Gigabyte, MSI, ASRock, etc...) are all experiencing the same thing. So it's not because you got an MSI motherboard at all, but because of something AMD did with their BIOS code.
It also relates to the CPU to some degree as well. Some CPU's exhibit the issue while others do not. Users went so far as to buy a whole new motherboard, only to find out the issue remained on the new motherboard.

The best you an do is leave VCore at AUTO for now, and set the frequency multiplier to something like 38 or 39, maybe 40 and see if it works well like that.
Unfortunately, at this time, you can go back to using BIOS 1.1, and use that to get a better overclock with the voltage increased. But you may have issues with memory and overclocking your memory then.
I think using a VCore at AUTO on the latest BIOS is probably the best option. Especially if you want to overclock your memory.

so is it the AGESA code from AMD or not?? if it is the code then that would suggest that all manufacturers would be affected???

 

[iamthenugget]

MSI moderators (not actually MSI employees but people on power trips) have been blaming AMD for every problem since release. Ignore them.

They have been banning people that suggest it is MSI's responsibility and refuse to back down. They use one of their rules which says you can't post in a manner which might bash MSI.

Thry refuse to even acknowledge problems until there are too many users with problems to ignore.

i dont know about other board manufacturers but i can say 110% certain that gigabyte do not have this problem on the GAB350m board as my son has that board and it runs absolutely flawless.

so as far as im concerned then yes i agree this is MSIs problem and they appear to be blaming AMD rather than sort the problem/fault themselves