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

[MarkusSVK]

We all doo read your comments. Bot your problem is, that you work with your own assumptions. That it all what your comments are.

[Skylezprox]

I won't buy any other Asus laptop, I can't change my limit voltage to 1.4 or update the BIOS to prevent the degradation issue... this situation is so sad and frustrating for Asus customers.

If Dell has updating their laptops with the microcode, does It means that the microcode posted here works on HX processors?

[Da-BOSS]

---

@Skylezprox wrote:

If Dell has updating their laptops with the microcode, does It means that the microcode posted here works on HX processors?

---

Yes, absolutely it works and I always have been saying it since the release of microcode 0x125 when Lenovo did it 1st & now 0x129 too. It's just ASUS doesn't want to do it. 

MSI, DELL, Lenovo= released 0x129 & will release 0x129.

Others (Including ASUS)= Staying silent about it... the silence is deafening...

[MaxusLDragold]

@Da-BOSS is it actually worth to update the cpu to 0x129 microcode, 'cause doesn't it just limits the max voltage to 1.55V, which will still harm the cpu eventually?

[Da-BOSS]

The voltage limitation is from BIOS settings. It is ASUS job to do it like they did it to there motherboards. I already mentioned that before. I have realized that when motherboard manufacturers released BIOS updates.

What microcode doing is it lowers the undetected voltage transient spikes when boosting up. So that means it will spend less time boosting the voltage over 1.4v but it will still cross over it sometimes

So yes... it is still worth it as voltage transient spikes is one of the factors of CPU degradations. Intel provided partial fix of the problem... it's on OEMs part to do there job and apply voltage limitations.

Maybe Intel will provide another one or maybe not.. no body knows..  but the tech scene currently isn't still satisfied about this completely because some OEM skipped applying the voltage limitation as a default settings... so it requires from the users to do it manually through the BIOS.

[Silent_Scone]

---

@Da-BOSS wrote:

The voltage limitation is from BIOS settings. It is ASUS job to do it like they did it to there motherboards. I already mentioned that before. I have realized that when motherboard manufacturers released BIOS updates.

What microcode doing is it lowers the undetected voltage transient spikes when boosting up. So that means it will spend less time boosting the voltage over 1.4v but it will still cross over it sometimes

---

For clarification, that isn't what the microcode update does at all. What it does is limit the CPU VID request below 1.55v. That's the extent of what anyone outside of Intel knows. Anyone claiming otherwise is incorrect. 

[Da-BOSS]

For clarification, It's exactly what I am saying to do. You are totally wrong... It's a BIOS setting... it's not the microcode that is limiting the VID table... it's a BIOS setting that does that...

All it does the microcode is changes the boosting characteristics... It changes the boosting algorithm to try not boost at 1.4v+ states far too long which previously it would stay at 1.4v+ far too long causing the accelerating CPU degradation. With 0x129 Microcode it will still sometimes go 1.4v+ but way conservatively.

Even Buildzoid saying the same thing & tested it too...

https://youtu.be/TOvJAHhQKZg?t=526 

Even the title video says it all...

So... "Intel default settings" is a BIOS option... BIOS setting vs Microcode are two sperate thing. When Both enabled... they work effectively but if you only use the  microcode.. then that's only the half way fix.. BIOS setting is still missing.. which brings back to ASUS for not providing the proper BIOS settings to be available to laptop users who got Intel HX CPU + the missing microcode that other OEM already started rolling it out + the required Intel ME FW to all work correctly & properly.

[Silent_Scone]

1. What you’re describing Intel Defaults is various UEFI settings from Intel RC code that board vendors set to stay within power limits. It is a predefined profile made available for desktop SKUs on motherboards. This is what the timestamp in the video is alluding to, and has nothing to do with the subsequent microcode fix directly.

2.Your explanation of what the microcode does in the post I replied to is completely inaccurate. Nobody knows how Intel is limiting the VID, but your own understanding that it aims to result in “less time above 1.4v” is entirely untrue. The VID request is limited to 1.55v when ETVB is used. Only Intel know how this is being achieved.

Continue the discussion by all means, but keep things informative.

[Da-BOSS]

1. It's Predefined BIOS settings so it's a BIOS settings and it's absolutely needed with the microcode + the updated Intel ME FW.

2. Wrong... "No body knows"... ? I doubt it.. you can know through testing like I did... why should I wait from Intel dictating what should I know what shouldn't know... through testing we can know everything.. there some are made by a couple of YouTubers tested it (including me confirmed it) how the microcode boosting behavior differ from one another microcode on boosting characteristics (they boost conservatively on 0x129) and my own test proves the microcode doesn't limit VID voltage table without the Predefined BIOS settings that's missing & needed to be implemented for laptop with Intel HX CPUs.

Buildzoid confirmed it himself... the VID table crossing above 1.55v even while using the 0x129 microcode 

Buildzoid himself tested it already... without the Predefined BIOS settings (with 0x129 microcode) there's no VID voltage limitations... where's the microcode effect of VID voltage table limit?

I guess let me share the Buildzoid video again but this time... from the start...

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

Sooner or later we will know what kind of changes are done when they select Predefined BIOS setting they use so that we (as a laptop users) can replicate it and can do it... (or at least I can do it if ASUS didn't provide the option to do it to the users)

[Silent_Scone]

---

@Da-BOSS wrote:

1. It's Predefined BIOS settings so it's a BIOS settings and it's absolutely needed with the microcode + the updated Intel ME FW.

2. Wrong... "No body knows"... ? I doubt it.. you can know through testing like I did... why should I wait from Intel dictating what should I know what shouldn't know... through testing we can know everything.. there some are made by a couple of YouTubers tested it (including me confirmed it) how the microcode boosting behavior differ from one another microcode on boosting characteristics (they boost conservatively on 0x129) and my own test proves the microcode doesn't limit VID voltage table without the Predefined BIOS settings that's missing & needed to be implemented for laptop with Intel HX CPUs.

Buildzoid confirmed it himself... the VID table crossing above 1.55v even while using the 0x129 microcode 

Buildzoid himself tested it already... without the Predefined BIOS settings (with 0x129 microcode) there's no VID voltage limitations... where's the microcode effect of VID voltage table limit?

---

Can you show the timestamp in the video where he shows ETVB is enabled?  If you haven't thought to ask this, you probably shouldn't keep trying to be an authority on this topic. 

Again, keep the discussion healthy. If the arguing persists between you and other members it serves no purpose. 👍