ROG Scar 16-17-18 gaming laptops and Intel 13th and 14th gen stability issue

[hexaae]

So... what about this Intel scandal recently emerged?

Intel has finally tracked down the problem making 13th- and 14th-gen CPUs crash | Ars Technica

If you're using a 13th- or 14th-generation CPU and you're not noticing any problems, the microcode update should prevent your processor from degrading. But if you're already noticing stability problems, Tom's Hardware reports that "the bug causes irreversible degradation of the impacted processors" and that the fix will not be able to reverse the damage that has already happened.

Intel says that an analysis of defective processors "confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor." In other words, the CPU is receiving too much power, which is degrading stability over time.

Are ASUS+Intel planning BIOS updates to mitigate the issue?

[hexaae]

---

@dreamlexa  ha scritto:

i found a temporary solution for now which is quite stable - i disabled the degraded core in software

---

This is a strong clue it's actually a CPU problem, not a software issue of any kind (bad drivers etc.)... there's a very low chance is a bad factory CPU pasting with liquid metal but if temps are OK for that core, it's very unlikely.

[hexaae]

At this moment Alienware released the microcode update for their laptops: BIOS UPDATE WITH MICROCODE UPDATE 129 HAS BEEN RELEASED FOR M16 R1 AND M18 R1 : r/Alienware (reddit....

Also MSI seems will update the microcode for their laptops too: Any MSI laptop users suffering from intel gen 13/14 (mobile) issues connected to mainstream degradat...

Lenovo too from rumors and discord.

ASUS... ?

[Da-BOSS]

Till now nothing from ASUS or even a statement about any kind of BIOS update. I'm simply furious with those actions...

[Hipflask]

https://forum-en.msi.com/index.php?threads/msi-titan-hx-2024-14th-gen-intel-help.401738/

MSI latest BIOS still also doesn't have it. Because it wasn't rolled out for mobile chips, but you know better, right?

https://community.intel.com/t5/Processors/Intel-Core-13-14th-Gen-Instability-Update-Future-Products/...

It's listed here in black and white now.

[Da-BOSS]

Dell themselves provided BIOS updates for there own laptops who got Intel HX series with 0x129 microcode because it was rolled out for Intel HX chips but you know better, right? 🤣

https://www.reddit.com/r/Alienware/comments/1etp205/bios_update_with_microcode_update_129_has_been/ 

Stop spreading false information and stop calling it "Mobile chip" because it's not... it a DESKTOP CPU. It's listed here in black and white now. 😂

they suffer from other issues unfortunately...

https://community.intel.com/t5/Processors/Does-the-recent-problem-concerns-laptop-i9-14900HX-or-only...

"The symptoms being reported in 13th/14th Gen mobile systems – including system hangs and crashes – are common symptoms stemming from a broad range of potential software and hardware issues. Intel has not been able to correlate reports of Intel Core 13th/14th Gen HX or other mobile processors to the Vmin Shift Instability issue."

There's another reasons & Intel isn't saying the full story here... & they are keeping it up to OEM's and Microsoft to support that or not... which is crime.

When I asked what other issues that Intel HX CPUs they suffer from exactly... I got no response. You can see me on the forums on same link I have shared here.

Something is fishy here... Yea, I don't believe them ... if this new microcode September update covers Intel HX CPUs... then this confirms that they are 100% hiding something & they don't want to admit it to avoid consequences and OEMs doesn't want to move a finger about it.

Edit...

Lenovo will provide it on there next BIOS update...

https://www.reddit.com/r/Lenovo/comments/1eusavl/any_bios_updates_for_laptop_intel_1314th_gen/ 

[Hipflask]

1. The manufacturer of the CPU has a public statement telling people the HX CPU is unaffected. 

2. It's not a desktop CPU, no desktop CPU has the same specification as the HX range. They share the same die, that is it. Power specification is NOT the same.

3. 12th Gen desktop CPUs are also unaffected.

4. The Lenovo message would imply they don't know the cause of the instability on mobile products, and they're still in contact with Intel regarding it. 

Which begs the question, what are you doing here and why haven't you just bought from another vendor or gone to the Intel forum instead?

[Da-BOSS]

Why would I get other vendor if most of them are the same as ASUS?

Let me quote a user on reddit who said every dirty Intel moves @dingoDoobie

1- Intel tried to BS their way out of the desktop chip issues multiple times, they've found so many problems in different areas that you could compare it to incompetence and not be blamed. I won't believe a word they say, nor should others, until it's independently confirmed by multiple 3rd party experts.

2- That article contradicts itself, with indications that mobile chips are suffering from some yet to be described issue whilst saying further down that they are not affected: While Intel maintains that Vmin Shift Instability is not necessarily the root cause or only cause of the crashes — it’s still investigating — Intel spokesperson Thomas Hannaford now tells The Verge that laptop chips basically aren’t affected at all. “Confirming 13/14th gen mobile isn’t impacted by the instability issue broadly speaking,” he tells me by email.. This is not a definitive answer, it's corporate double speak for damage control. Here's an interesting Intel doc that actually alludes to the fact that the desktop issues are not necessarily fixed by the microcode update and doesn't explicitly rule out faulty mobile chips: https://www.intel.com/content/www/us/en/content-details/831172/intel-core-13th-and-14th-gen-instability-customer-passthrough-q-a.html

3- Another previous article indicates there are some instability issues, but Intel is doing the same thing it did with the desktop issues originally (blaming the user, it must be your software or hardware config without proffering proof). Suspicious to say the least. What do they call a small amount, 5%, 10%, 20%, what??? https://www.tomshardware.com/pc-components/cpus/intel-says-13th-and-14th-gen-mobile-cpus-are-crashing-but-not-due-to-the-same-bug-as-desktop-chips-chipmaker-blames-common-software-and-hardware-issues

If anything, I would say don't trust Intel's word, they won't give the statistics, their sample sizes are limited to what they test themselves internally, and they have lied already, or at the least didn't properly QA/QC the desktop chips, and misled consumers on a faulty premise. Personally, I think most mobile chips are likely ok/within normal range for failure and not affected by voltage issues at least (until something proves otherwise); the HX chips though, I am not convinced in the slightest. The HX chips are desktop grade and seemingly fabbed the same, just repackaged for a laptop. Something smells fishy still...

Please stop the non sensical statements and accept the facts.

[Hipflask]

All I've posted is facts. Which is a far cry from the drivel you've been posting for the last few weeks. Let's break this down so everyone can see how you've manipulated your angle as the situation has unfolded...

1. Initially you were claiming any voltage over >1.4v was detrimental to the CPU.

2. When it transpired that Intel were only capping the voltage to >1.55v, you then decided that it was actually transient voltages that were the issue, without really having a reasonable grasp on the topic - as if transients wouldn't be seen above 1.4v if Intel are only capping the VID to 1.55v. Truly preposterous nonsense that makes no sense, literally blinding people with nonsense in an effort to save some face.

3. You then claimed that, perhaps, this wasn't the mid August update - maybe because even a broken clock could potentially be right twice a day.

4. You then also made claims that MSI were planning on rolling out 0x129 to mobile products based on a random users post that he had spoken to support. That was several weeks ago. They've just released an update and it does not contain this microcode.

5. You've been praising Lenovo for releasing the microcode, however, they've been seen now on Reddit claiming to still be in communication with Intel regarding further updates. As there are no further updates planned for desktop, this means that Lenovo must be aware that 0x129 isn't the answer - and yet here you are advocating for ASUS to install it.

6. Intel now publicly disclose that HX CPUs are unaffected.

7. We're now being linked to random users posts on Reddit as if they're a credible source of information.

The only thing that's truly nonsensical about all of this is why you're here and not in that Intel thread.

[Da-BOSS]

So you are saying I should take credible source from you? Who are you? Why would I even need to reply to your non sensible comments?

And why would I need to listen to you if you didn't read a single comment I made since the Intel fiasco.

Please if you want to bla bla bla about it. There's a PM function on this forum and spare everyone time from your misinformation you're trying to spread.

Stop playing around & dodging... it doesn't work with me 😉 

[Hipflask]

The timeline in my post is really for other peoples benefit, not yours. Best of luck on your crusade.