[INTEL]-How To Update Your Microcode for Intel HX 13/14th CPUs Laptops/Mobile Easily.

[Da-BOSS]

Let me start with a small background info...

Since we know all Intel's fiasco about what is happening with Raptor Lake/Raptor Lake Refresh which is Intel's codename for the 13th and 14th generations of Intel Core processors, Most OEM/Vendors doesn't want to provide BIOS update that includes microcode update along with required updated Intel ME FW in order to work more effectively.

Since most laptops got outdated Intel ME FW & outdated microcode... this has become a serious problem since the CPUID of Intel HX 13/14th CPUs share the same code with Desktop variants and hence it should be considered Intel HX 13/14th CPUs as a Desktop CPU in a laptop case.

So it means they share the same impact as Desktop variants even if it doesn't boost enough to be of a concern, it does have relevancy and you now have the option to use this very simple driver that I am sharing it to you here on any Intel HX 13/14th CPUs Laptops/Mobile as long as it has CPUID of B0671.

Either way the requirement of updated Intel ME FW are just only mandatory when used in conjunction with any new microcode (If it's needed) in the BIOS but outside BIOS like... while running Windows or Linux this requirement of having an updated Intel ME FW is just optional.

Thanks to this VMware CPU Microcode Update Driver I can use it on any windows without needing to mess with the BIOS. Safest thing to update microcode.

Now... How to check if you got the latest microcode update or not? By simply check through HWINO64 or AIDA64 or even if you are using ThrottleStop tool will tell you which microcode you are using.

Here's some examples how it is shown which microcode are you using through various tools...

HWINFO64

AIDA64

ThrottleStop

Now fortunately I already packed it for you & ready to use without any further work required. Saving you the time to do it.

For the next part... You need to download this .zip file and extract it. Simply run the "Install.bat" file as an administrator.

The .zip file attached on this post look at the end of this post.

It shouldn't even take long and only few seconds and you will see this window... which is success.

You can even check the event viewer which confirms the success operation and applying the new microcode update.

Notice:- If doesn't update your microcode and it shows failing to apply microcode on event viewers... you need to disable virtualization either through Windows or simply go inside your BIOS and disable Intel virtualization and VT-d in the BIOS. This would allow the driver work!

September Microcode Update aka [0x12B]

New microcode update got released! This is the September microcode update which now they call it 0x12B .Please if you are using the 0x129 microcode previously then simply download the latest .zip pack from the attachment of this main post. Simply run uninstall.bat as admin [by right clicking on the file and choose "Run as Administrator"  and then run install.bat as an admin. 

No need to reboot, You just updated your microcode! Yes... it's that simple!

If you ever wanted to uninstall your updated microcode for whatever reasons... simply run "uninstall.bat" file as an administrator & reboot your laptop.

[Alpine_Alex]

Huh? So they're the same but not the same? Surely if it has a much lower TDP it's not the same? Also isn't PL1 and PL2 the same as the TDP? lol 😂

How does the car analogy even work? That sounds like you've set yourself up for a fall there 😂. Surely if we're talking about the engine we'd be talking about horse power as this is what directly correlates to the tolerances. If we're restricting the horse power, we're increasing the guardband for issues or failures.

In other words...if there's less current passing through the die it's possible we're in within sufficient guardband levels.

Which is what is being seen here in the data provided...

https://www.xmg.gg/en/news-update-intel-core-cpus-laptops-stability/

https://www.reddit.com/r/intel/comments/1e9mf04/intel_core_13th14th_gen_desktop_processors/

To close: Whilst I don't disagree it might make sense for Intel to assertively express that mobile vendors offer these updates, all these uneducated assumptions regarding how mobile chips are impacted seem a little desperate given there's no real evidence to suggest that they are, other than "They're the same" 😂

[myth55au]

https://www.techspot.com/news/103876-intel-laptop-cpus-crashing-company-remains-silent.html

[hexaae]

The problem with you is simple: you follow only "evidence" based on what Intel authority says and not by logic and investigation TOO (uh, Intel didn't say anything before people started commenting strange cases on social medias...). Feel free to follow that path only, you live in the best of possible worlds don't worry... 🤗  but stop trolling others please. I won't feed the trolls.

[Alpine_Alex]

---

@hexaae wrote:

The problem with you is simple: you follow only "evidence"

---

lol, glad we cleared that up.

The links posted aren't from Intel, so I'm not sure what you are referencing specifically. The data comes from a vendor who sell these in large quantities, but apparently they're not to be trusted either?

Once again, I wouldn't want to get in the way of people requesting the microcode, I just think it's unethical for someone to post up threads on the forum claiming they're CPU is going to die if they don't update, based on nothing other than what seems to be nothing more than guess work? Who made one person the authority on something with such wide spreading implications but with no evidence?

[AkramOM606]

Are you somehow paid by Intel? I don't know why you are defending them even, do you even have a mobile 13/14 gen Intel CPU? If not please stop posting your replies here!  

[hexaae]

He's just a troller with 0 messages before in ASUS forums, probably came here only with that mission. Ignore him. He doesn't even say anything everybody already know and can read online anyway from usual sources (and yes, he probably doesn't even have a 2-3000$ laptop with HX CPU, so...)

[Alpine_Alex]

Can you explain how it's trolling? I signed up as I wanted to know why suddenly the OP was so sure the issue impacted mobile chips.

 So far all we've got from the original poster is "it's the same CPU", and we need to take him at his word that our CPUs are going to fail? You say "I don't say anything that you can't read online", but that's exactly what @Da-BOSS has done by having the basic capacity to workout that it shares the same CPUID, incredible powers of deduction.

Sounds like certain individuals don't like it when they get called out for unsubstantiated nonsense? If that makes me a troll then so be it.

As I've said, I'm not saying people shouldn't update the firmware, it's their prerogative - my issue is with someone trying to talk from a position of authority who doesn't seem to want to back-up what they are saying. I'm sure it's frustrating for him as it's obvious he can't substantiate what they're saying.

I'm not advocating for people not updating, I'm asking for some substantiated evidence that would suggest there's reason for immediate concern. I have a 13900HX - I just want to know what makes him so certain (other than "it's the same CPU, which it clearly isn't other than it uses the same die).

[AkramOM606]

Your CPU will fail just like every other one, I already know 2 other cases of mobile CPU failure! I am also experiencing the same failure patterns (Memory corruption etc...)
https://community.intel.com/t5/Processors/i9-13980HX-Access-memory-issue-0xc0000005/m-p/1595756

[Alpine_Alex]

You know every failure doesn't have to be related to the same root cause? Zen has a failure rate too lol. Puget Systems said they have more Ryzen failures than Intel. Sorry you're having issues though.

Anyway you guys have fun with this, all I was hoping for some reasoning but been met with hostility.

Peace!

[hexaae]

---

@AkramOM606  ha scritto:

I already know 2 other cases of mobile CPU failure! I am also experiencing the same failure patterns (Memory corruption etc...)
https://community.intel.com/t5/Processors/i9-13980HX-Access-memory-issue-0xc0000005/m-p/1595756

---

Good. Let's collect here these reports too...