AMD is good at sandbagging. AMD makes themselves look bad once they don't sandbag like this thread keeps showing.
They better don't pull this BS again if/when 5GHz is finally attainable.
AMD is good at sandbagging. AMD makes themselves look bad once they don't sandbag like this thread keeps showing.
DrMrLordx got it to spec boost as did others here on this forum. WITHOUT LN2You know, if AMD just came out and said, "Those boost speeds are only for LN2 users", maybe that would be a solution.
I mean, we have the extreme high-end mobo category, with 12/16-phase wildly-overspecced VRMs, and BIOS settings for 1.5V-1.8V vcore, on CPUs that normally can only take 1.3V vcore on air. No-one here is claiming that they can't reach / use those vcore settings during nominal operation. (Because they are for LN2 benching.)
They better don't pull this BS again if/when 5GHz is finally attainable.
[Tom's Hardware reports on DerBauer's findings]
Yeah, my R5 3600 boosts to 4.2Ghz easily too... ONLY AT IDLE!DrMrLordx got it to spec boost as did others here on this forum. WITHOUT LN2
You know, if AMD just came out and said, "Those boost speeds are only for LN2 users", maybe that would be a solution.
I think by now it's pretty clear AMD was too optimistic regarding what frequencies are easily attainable with Zen 2 on TSMC's 7nm. For whatever reason they weren't able to backpedal in time so now them not having sandbagged in this instance is consequently hurting them (in the frequency PR fight that Intel will more an more focus on, having nothing else to show).Saw speculation out there that AMD cut the boost via agesa due to long term reliability issues. How long term are we talking about, no idea.
I mean AMD just got fined for the bulldozer core thing which was stupid really. this is much clearly and I see another double-digit millions fine coming in a couple years. Let's all admit it was a big blunder on AMDs part not putting 100mhz less on the box to avoid the whole debate and probably future class action lawsuit.
Yeah for performance it hardly matters still AMD just always manages to blunder somehow in a very avoidable way.
Yeah, my R5 3600 boosts to 4.2Ghz easily too... ONLY AT IDLE!
Yeah, that could well be true.I had no issues at all getting my 3600X to run (and hold) 4.5GHz+ on each core individually. That tells me that it isn't that the cores causing the issue, its the algorithms that are behind boost behaviour.
DrMrLordx got it to spec boost as did others here on this forum. WITHOUT LN2
Yeah, my R5 3600 boosts to 4.2Ghz easily too... ONLY AT IDLE!
Supposed to do **up to** 4.6 GHz.
Assuming that later BIOS revisions don't rectify something, I agree that they should have labelled it as 4.5 GHz - but "boost up to" does not equate to "will boost to".
https://www.tomshardware.com/news/amd-ryzen-3000-boost-frequency-bios-fix,40308.html
New article about incoming fix possibly.
Hopefully this works and gives the majority of users the 25Mhz (according to Der8auer's findings) they were shorted, so everyone can now be happy.For those of use who use all cores, this is a non-issue.I think gamers are the ones mostly affected.
Hopefully this works and gives the majority of users the 25Mhz (according to Der8auer's findings) they were shorted, so everyone can now be happy.
I agree. This whole deal about 25 mhz. Even as a computer nerd, I round numbers quite often, and to me its absurd to be upset about 25 mhz.Hopefully this works and gives the majority of users the 25Mhz (according to Der8auer's findings) they were shorted, so everyone can now be happy.
I don't own a Ryzen 3*** series CPU, but I would be one of the people who doesn't really care about this issue. I never look at boost rates of my Ryzen 2700X CPU, as all I care about is the CPU's actual performance. I'm not discounting those who pay attention or who are concerned about their clock rates, it's just something I personally not overally concerned about.