08-08-2024 01:54 PM - edited 09-26-2024 09:12 AM
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.
Solved! Go to Solution.
11-16-2024 08:25 AM
I don´t think that it is only a frequency difference. There must be other minor architectural changes to the 14th. gen. But we would need a statistical failure comparison to be sure. The 14th gen. is probably pushed to the limit of the Raptor Lake architecture, which should lead to a higher failure rate in comparison to the 13th gen. Both my 13980HX and a two year old 13600KF are rock stable, the HX running 16 hours a day at work and at home, with the desktop as my sons gaming rig. I concur that it is strange, but here must be a reason for the current situation with the microcode.
11-16-2024 09:27 AM
I want to think that yes, there must be something different, because otherwise I don't understand it, it's a shame that this new bios does not include the microcode, it would calm me down, my computer was always equipped with undervolt, since new it had maximum temperatures of 102° degrees squeezing the processor at 100%, now it does not go above 78° and taking it to the limit, yes, I have it limited to 4.4 Ghz, in games it works great for me, which is the main use.
11-16-2024 08:11 AM
The truth is that now I have my doubts, because if they updated the microcode in the G16 2024 model with HX processors, it means that the problem is also present in the HX series of laptops, at least for now detected in the 2024 version.
Now the question is this, can we really be calm using our equipment, knowing that it has been detected in the G16 2024 versions that share the same line of processors?
11-16-2024 08:33 AM
There will always be doubts with the 13/14th gen. Intels reputation went down the toilet.
11-16-2024 08:53 AM
In this case I will say something to this thread.
I want to say thanks to the user called Da-Boss, for help us bringing the microcode updates while Asus did nothing about that issue. I hope that the installed microcode and the -115mv undervolt is enough to stop the Intel degradation issue.
And the next laptop I buy I will be sure to choose any other gaming brand but this one, like the rest of my coworkers, who I have convinced to do the same with their next laptops.
Thanks for nothing Asus.
11-16-2024 09:09 AM
Does anyone know if it's safe / possible to install drivers for the newer models? For example, I could use bios for g16 (2024) on my g16 (2023).
11-16-2024 09:16 AM
No, you can damage your equipment, each BIOS is specific to the selected model, do not try it.
11-16-2024 10:11 AM
People say that 13th/14th gen degrades over time. Is it true? If so, my cpu must've been degrading for ~7 months. Is there a way to check how bad the current state is?
11-16-2024 11:15 AM
To everyone who got ASUS ROG Strix 2023 model, continue using the microcode driver update. ASUS right now won't care for 2023 users. ASUS didn't add 0x12B microcode for 2023 models and they simply skipped it and never cared for 2023 users, right now only 2024 models have 0x12B microcode update while 2023 versions are thrown under the bus. Don't use 2024 BIOS files on 2023 laptops, you will brick it.
Keep using the microcode driver update [0x12B].
I'm enraged and sad and angry at ASUS and how they decided to provide protection & prevention from CPU getting cooked to only 2024 models. Can any ASUS representers or who works for ASUS explain here why this disaster choices? why did you only provide the microcode for 2024 models and not for 2023?
The microcode 0x12B is MADE for 13th gen and 14th gen... BOTH NOT EITHER OF THEM...BUT BOTH... AGAIN THEY ARE MADE FOR BOTH... I'm utterly mad and how you are forcing users to just throw 2023 models in the trash bin when the CPU gets degraded or else pay for expensive repairs for mobo replacements.
as @o0Kingmaster0o said... "the processors HX 14th generation are the same as the 13th generation only with different frequencies" that is exactly the 100% fact!! there is no difference ZERO difference 13th gen = 14th gen = Desktop CPU. THEY ARE ALL AFFECTED.. again ALL.
All OEMs are providing BIOS updates with microcode for both 13th/14th gen, why only you ASUS does it for 14th gen? WHY?!? what is this choices?
Here's a screenshot looking inside BIOS file 330 ... they didn't add 0x12B microcode!! why ASUS? just WHY? there's nothing else explains this behavior except you want users to buy 2024 models.
no microcode 0x12B
11-16-2024 12:16 PM
Yeah, this is really sad to see honestly! Can any Mods try to talk to their managers and explain this situation? We are fans of ASUS products but this behaviour from them is totally unacceptable and that's not how you loyalize customers or treat your customers! If they don't hook up 2023 models with the new microcode I will never buy an ASUS product again! I've been using ASUS products since 2014.