LLC (Load Line Calibration) not working... Bios fix required ASAP

[morph_]

Any eta on when there will be a bios patch/fix for LLC?

Vdrop is just too high at the moment it seems.

https://www.youtube.com/watch?v=hCAQpvFhiUs

[aznguyen316]

Raja@ASUS wrote:
The Prime, yes. Elmor would know about the Hero. Either way, all boards that require an UEFI update will get one.

Wow quick reply. I guess my fears in the previous post should hopefully be put to rest this week in regards to the Prime-A. Thanks for the acknowledgement.

[aznguyen316]

Tech Hog wrote:
Is this only affecting Strix boards btw? I've heard people saying that they think Prime-A and even M10H have the issue as well.

I really hope Asus R&D has recognized this does affect the Prime-A line as well and not only the Strix line.

I have already spoken with NewEgg and set up an RMA where they "made a one time exception" to allow for store credit refund. I have 14-days to return, but I am hoping I can just fix via BIOS update this week before I tear down the system. As long as the Prime-A has been recognized as also being affected, but I'm afraid it will be glossed over since many reports are just mentioning the Strix Z370 line.

[Korth]

Tech Hog wrote:
True. I think I'll order a new DMM just in case. You never know after all.

I prize my tried and true old DMMs. And I already have too many.

And yet I still find myself lusting at silly specs on the newest models.

[Tech_Hog]

Korth wrote:
I prize my tried and true old DMMs. And I already have too many.

And yet I still find myself lusting at silly specs on the newest models.

If I get one it'll be something cheap and basic lol

[morph_]

Been reported that some are getting as much as 0.9V vdroop though... is that inaccurate?

Just from apps such as CPUID / CPU-Z

[Raja]

morph. wrote:
Been reported that some are getting as much as 0.9V vdroop though... is that inaccurate?

Just from apps such as CPUID / CPU-Z

That's why you should measure properly before coming to a conclusion. Don't rely on software. Plus the IA AC/DC settings are likely involved, so calling this Vdroop may be inaccurate, too.

[morph_]

Sorry i'm not an electrical engineer, but don't these apps pull the data from the BIOS and if so the bios seems to be reporting incorrect power data how can 'enthusiasts' trust the read outs without multi-meters and what not to overclock?

[Raja]

morph. wrote:
Sorry i'm not an electrical engineer, but don't these apps pull the data from the BIOS and if so the bios seems to be reporting incorrect power data how can 'enthusiasts' trust the read outs without multi-meters and what not to overclock?

Power and voltage are not the same thing. They are related, but one shouldn't confuse where and when to use these terms. Software doesn't use bios to report voltages. Even if you were unsure of voltage, you can check cpu power consumption in software such as aida64. It's power that ultimately matters. Looking at voltage without checking current doesn't tell you much. P=VA. Remember that and you won't need to rely on reviewers for info.

As for the rest, like I said, I'll see if I can get a board to check, or ask one of the r&d guys to look into it. Oh, and yes, software often needs an update, too. That part would be up to the software developer to fix.

[Korth]

Raja@ASUS wrote:
Oh, and yes, software often needs an update, too. That part would be up to the software developer to fix.

Slightly off-topic, but I'm curious:

Benchmarking and hardware monitoring softwares (CPU-Z, HWMONITOR, HWiNFO, etc) need to be calibrated and updated for best accuracy on each new platform. Does ASUS provide sample boards or "confidential" technical data to these software devs before product launch?

[JustinThyme]

I am an electrical engineer and Im afraid Raja has this right. I have to say Im a bit disappointed in Tom to produce such rubbish with zero supporting documentation.
Are you personally experiencing measured Vdroop issues? If so the prudent thing to do is contact support and arrange for an RMA of your boards.

I have 3 software packages that pull whats supposed to be the same data from the smbus and no two read the same. This so called bug could be a result of these vendors not updating their software yet for the Z370 chipset. There's a million things here and nothing worse than troubleshooting conjecture.