Soldato
Its not his fault on messages then fair enough. He still needs to brush up on the methods when reviewing, he fudged this one up and take it on the chin.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
However this is a clear case of Jay not having a clue and instead of going to MSI and saying look I'm seeing something odd with this (like most people would with a faulty product), he made a video lambasting AMD and MSI making himself look like a total tit.
None of this little storm in a teacup would have occurred if he had done some basic due diligence on the products he was using. Such as how to OC the CPU and finding out why his whizzbang mobo wasn't whizzing and was banging too much.
The icing on the cake was just attacking everyone on Twitter and Reddit who for the most part were civil and pointing out his errors. There were a few being dicks but he's gonna attract that with the amount of subs he has.
Thats not very nice humbug, to be honest, you dont know how it works yourself, I didnt say it before as I was been polite.
The idle 1.5v is absolutely nothing to do with the boost algorithm by the way.
I never said JayZ got it completely right, but I agree with him that cpu's shouldnt be idling at 1.5v. If I remember right you was claiming there was nothing wrong with the old broken amd scheduler right even when amd themselves issued a fix? One way to identify a shill is when he still defends something that even the company acknowledges as broken.
As a reminder the basis of my comment is when I left my 2600x idling overnight on remote desktop and all that time it was at 1.4+ volts. I also explained that it had an operational effect, higher temps and power draw, when I moved the system to the microsoft scheduler. It worked properly.
However where jayz got it wrong is looking at the voltage in the bios, in every modern bios I have used they idle at load voltages. So seeing 1.5v in the bios in that regard is not broken as bios's dont utilise power saving modes, no cstates or pstates.
He also got it completely wrong by diagnosing the bios as been broken without doing any kind of cpu or board swapout first.
My 2600x will use XFR voltage in bios if thats enabled, but interestingly it uses the all core voltage not single core, which is different to what jayz was seeing, perhaps that is what threw him off. I assume either msi or AMD have made a change on ryzen 3000 series so the load on the chips is different in the bios.
Now AMD specs say volts up to 1.5v are within normal parameters. However they also said the following on reddit.
1.5v is within specification, the chips are designed to burst up to this voltage as and when load demands require it.
Thats a bit different to having a chip sit at 1.5v 24/7.
It is a bit like a car that is rated up to a certain amount of revs but its not designed to run at those revs 24/7.
My opinion is no one's chips are going to blow up, they will all probably easily last out warranty periods. But at the same time I think the 1.5v idling is perhaps a bug, also the AGESA update's issued are unusual practice for a released cpu product. Which was the basis of my beta comment (alongside the scheduler patch).
He's shown many times that he hasn't the foggiest when it comes to Ryzen and even trying to OC Vega which is a challenge at the best of times. He's gotten into overclocking just using simple tools like Afterburner and hasn't really learn't the more complicated stuff. I'd have expected his LN2 overclocking to have helped but it doesn't seem to have done so. As for the Pre-prod board he was adamant it was retail until MSI confirmed otherwise...doubt it. as the poster above says really. it's the no publicity is bad publicity mentality.
i can't for 1 minute believe he doesn't know the operational characteristics of the R3K chips. maybe, just maybe, he forgot he was using a pre-production board but i imagine it was just a 'shout loud' video to attract attention, clicks and views. but then again i have a low opinion of most of these self appointed tech experts.
jesus, that's even more 'frightening' - he should maybe stick to what he knows best, weight loss videosHe's shown many times that he hasn't the foggiest when it comes to Ryzen and even trying to OC Vega which is a challenge at the best of times. He's gotten into overclocking just using simple tools like Afterburner and hasn't really learn't the more complicated stuff. I'd have expected his LN2 overclocking to have helped but it doesn't seem to have done so
wtf can you even say to that. that level of ineptness is forgivable if it was some dude doing the review in his bedroom, just about.As for the Pre-prod board he was adamant it was retail until MSI confirmed otherwise...
did he have the first ever released Vega's or was it after the world and their dog(at least in enthusiast circles) knew that oc'ing Vega was a bit more nuanced? please say it was the former and not the latter......but i can guess which it probably wasWhen he did the Vega56 OC, he did the classic whack power to max and then stick Core to Max and Mem to Max in Afterburner. While AB still didn't have support for Vega properly...
There's a reason using OverdriveNTool was better for Vega. I miss that, Navi is just a bitch to OC as there's no granular control of the voltage and perf targets
Oh it was well after there was enough info out to do it right. Zero tech tuber's I've seen got it right though. Even GN didn't, he still thinks pretty much zero gain with mem OC on Vega, cos his 56 didn't OC on mem at all. My 1150MHz on mem was a crap load of perfdid he have the first ever released Vega's or was it after the world and their dog(at least in enthusiast circles) knew that oc'ing Vega was a bit more nuanced? please say it was the former and not the latter......but i can guess which it probably was
did he have the first ever released Vega's or was it after the world and their dog(at least in enthusiast circles) knew that oc'ing Vega was a bit more nuanced? please say it was the former and not the latter......but i can guess which it probably was
When he did the Vega56 OC, he did the classic whack power to max and then stick Core to Max and Mem to Max in Afterburner. While AB still didn't have support for Vega properly...
There's a reason using OverdriveNTool was better for Vega. I miss that, Navi is just a bitch to OC as there's no granular control of the voltage and perf targets
OK back to subject.
Today apparently the launch, in some regions, of the Ryzen 3500X & 3500 6 core 6 thread CPUs.
Have we pricing on these out of interest?
I must look into the rest of the line, as bar the big names I haven't looked properly at this or the integrated GFX chips.
Still cant get 3600MHz stable on my ram. I've typed in everything form the dram calc this time including the power supply stuff and after about 10 days of stability, yesterday it froze and today I had a reboot.
So I've gone back to DOCP 3200MHz at CL14. Which to be honest is probably a good thing as it is a smidgen faster than 3600MHz CL16 anyway according to a ram latency calculator.
Anyone running x570 aorus elite? Is the latest f5b bios now fault free? I know f5a had a boot order issue.
I've used both F5a and now F5b without any problems on my Elite.