[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!

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]

Hey bro,

Appreciate the guide but you should probably fact check before you go off half cocked.You're saying vendors "don't want to", but XGM in Germany have stated here publicly that they have no knowledge that they should be using the microcode on mobile CPUs. Also more importantly they have not noticed any uplift in RMA or returns due to this problem. 

You're basically just going off the CPUID alone - Intel haven't mentioned mobile chips being fed this update, so you're telling people to update to a microcode that's currently not officially supported for that SKU which might not be recommended. See exert below.

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

They have also conducted some analysis here which they observe vastly different sustained boost behavior to the desktop counterparts. With far less peak current, it probably goes someway to explain why no vendor is reporting failures on these chips.

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

Intel haven't said that they plan to update mobile SKUs, either. Surely they would stipulate this to laptop vendors if they thought it was necessary.

Bottom line, be wary of telling people to update when Intel themselves haven't told laptop vendors to use this microcode.

[Da-BOSS]

Yes, OEM/Vendors doesn't want to do it.... because they are just basing it with RMA/Repairs data cases... which is absurd. It is a slow death unseen degradation. Intel themselves never said "Intel HX CPU are not affected" they only said "Mobile"... Saying "Mobile" are very vague term.. we all know how Intel playing games & fooling everyone. You got many series of Intel series and I am pretty sure 100% they are talking about the U & H but never about the HX series.

That's the problem... and as long as Intel won't admit it... then OEM/Vendors won't do anything except basing on RMA/Repairs data cases rather than taking preemptive/preventive measurements.

Lenovo themselves acknowledged the problem & already provided 0x125 microcode updates to there laptops users who are sharing the same CPUID as the desktop variants...

and they will provide this current new ones which is 0x129 microcode in the near future. So any other OEMs they will keep down playing it and saying "There's no reports" or "There's no cases" rather than taking preemptive/preventive measurements.

[Alpine_Alex]

The HX is a mobile SKU, though, it has completely different clocks and TDP. You seem to be being awfully dismissive of the findings above.

I think you''re making too many assumptions here. Is the Legion Pro 0x125 microcode available from the Levono product page?

Why would vendors not want to give their customers a safety net? The exert I've shown you clearly says they aren't sure the update is supported - are you saying they're lying?

Maybe best to wait for confirmation rather than encourage people to update to a microcode that the manufacturers aren't currently pushing out.

[Da-BOSS]

Yes, Vendors won't provide a safety net for the customers bec. Intel won't confirm this issue specifically for Intel HX... they just said the most vague term "Mobile" and all vendors simply followed it as if they see Intel HX as a mobile CPU but it's actually not... they are Desktop CPU into a laptop case -HX and -S CPUs (desktop CPUs) have the same CPUID they're both equivalent in this context.

I don't need confirmation... it is already confirmed it's so obvious, it's a fact since the days of AlderLake HX CPU got released and by recent Lenovo move... that confirmed it even more than ever 

As long as Intel won't do anything for laptops that have Intel HX CPU 13th/14th series... OEM/Vendors won't move an inch about it. They will actually be waiting until customers requesting repairs and charging them with high repair prices with motherboard replacement. Since it's a slow death degradation problem. It's win-win situation for OEM/Vendors.

Legion Pro 0x125 microcode are available from the Levono product page. They even provided Intel Management Engine 16.1 Firmware update to 16.1.32.2418 in order to work with 0x125 microcode release.

They are available for those models... Legion Pro 7 16IRX8H, Legion Pro 7 16IRX8 and Legion Pro 5 16IRX8. The BIOS version is kwcn46ww. Check it by yourself in Lenovo support page and everyone is reporting it that they got 0x125 microcode with slight decrease on voltage reporting too.

I have seen inside the BIOS file by using Phoenix Tool & grabbed BIOS from there support page by myself and I confirmed it too... they got the 0x125 microcode.

Why would Lenovo do it if HX is a mobile SKU? because they know Intel HX CPU isn't a "mobile" sku... 

[AkramOM606]

I am having the same stability issues as this guy right here in the Intel Forum! So clearly laptop CPUs are also affected since they are literally using the same die as their desktop counterparts!
https://community.intel.com/t5/Processors/i9-13980HX-Access-memory-issue-0xc0000005/m-p/1595756

[randomoswot]

well intel goes by 13th and 14th gen with 65w or more rules now. if u download intel identification utility it will display your processor in my case 13980hx and latest microcode which shows 0129 therefore is clear u should update as per spec determined by the vondor utility your lattest microcode should be 129.  i did it few days ago and i post the finding above in OP post

[Ladds]

I think that you should refrain yourself for advicing people to apply this update. 

#1. Only some parts of processors has been affected.

#2. Everywhere, on each website you can read that they are mobile processors.

#3. People suddenly started to report 10 degree higher temperatures after applying this update so something is definitely wrong and this is not fixing any problems.

According to available informations, if you are CPU has been manufactured in 2023 you are ******ed, but if in 2024 you can skip this updates.

[hexaae]

HX mobile CPUs are just the same as desktop, what seems to reassure Intel about mobiles is just they don't have the same clock and TDP or PL1/2... Well, to me it's basically like saying: «Well, your car's motor is defective and can melt with time... BUT since with your model you don't usually reach such high speed you're "safe"».

I DO NOT FEEL SAFE and nothing ensures our HX CPUs with a bit more time (2-3 years) will exhibit the same behavior of desktops CPUs that were just deteriorating FASTER, hence more reports ATM. It seems a logical thinking.

[Da-BOSS]

That's an amazing & cool example you have shared ! 👌 I will even use your example whenever I face someone who doesn't want to accept this fact.