Hacker News Reader

Comment by geerlingguy | Hacker News Reader

Just a note: GamersNexus has been digging into this issue quite a bit, and supposedly has a video nearly ready with their initial results [1].

I'd wait until there's more evidence about who's to blame and how large the problem is before putting much weight into the media reports.

[1] https://twitter.com/GamersNexus/status/1651308183745331202

View on HN

Almost always good to wait on GN. They tend to do a much more thorough and careful analysis of situations like these.

Are they always the first to get the news? No. But they almost always get it right which I appreciate a lot. IE: The 12-pin power debacle.

I like to wait for the inevitable five minute king Linus Tech Tips video where Linus calls the guy at Gamers Nexus “really smart” and just repeats the findings that are somewhere in the hour long GN video. Because I only sorta care a little about this stuff.

GN seems to think it is Asus's fault, possibly due to bad firmware/BIOS

There were few reports from non-asus ones IIRC, but it's hard to tell whether that was same "the EXPO profile loaded from memory fried it" or someone just going "MoRe VoLtS BeTtEr" and frying it.

Four motherboard makers have come forward and issued press releases about new firmware they are releasing that limits the SoC voltage, thus preventing this issue. What further evidence is needed?

The question is if they limit abnormal voltage, or just lock to "safe" ones. this might not be a solution, this could be just a workaround basically crippling oc

AFAIK none of them said anything about what is happening nor what their fix is doing

That can simply be a preemptive measure to prevent a further user meltdown.

Reply on news.ycombinator.com