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 06:13 AM
That is interesting. I have strix g16 in 13980hx and RTX4080 and mine reports 012B with the 330 BIOS 🤔
11-16-2024 05:21 AM - edited 11-16-2024 05:26 AM
Updated scar 16 2023 g634jy bios to 330 and still the same microcode, Asus? Seriously? Only 2024 Asus rog strix/scar models have the pleasure of updating the microcode?
This laptop is the last asus laptop I will buy, next time I will buy a laptop from a gaming brand that cares about all their users.
11-16-2024 06:19 AM
Indeed, after updating the BIOS to version 330 there were no changes in the reported microcode version. Does this mean that the microcode itself remained unchanged and this was another update that contained everything except the microcode itself?
G834JY
11-16-2024 06:26 AM
You have an older version of HWinfo64. Try updating it, and check again. Maybe that is the problem 🤷
11-16-2024 06:29 AM
As I wrote before. It would be nice of Asus to include a change log with BIOS updates. Not only "optional" or "critical".
11-16-2024 06:56 AM
There must be a bug. Opened HWInfo again, and it states 115 again, not 12B. That, or I am starting to hallucinate. Note to my self. Less coffee. Sorry for the previous misleading comments.
11-16-2024 06:59 AM
Nice work Asus, I will never forget it. Such a ***** gaming brand
11-16-2024 07:21 AM
I have an ASUS ROG Strix G614JZ_G614JZ (i7-13650HX) and just found out about this issue. I updated the bios but microcode is still 115. I've never experienced problems with the CPU. @Da-BOSS what would you suggest to do?
11-16-2024 07:45 AM
Intel states, that there is no issue with the mobile HX processors, and me personally, I never encountered a BSOD for the past year, or game crashes with my 13980HX (I use it every day at work, and at home so it runs 16 hours a day). Even my two year old 13600KF, on which my son plays every day is rock stable. So there are only two option. 1. Intel says the truth and DA-BOSS is on a hysterical crusade against windmills... or 2. DA-BOSS is right (and you can update your microcode with his tool at your own risk) and Intel is just making a fool of itself just to have more problems than it already has (which in my humble opinion would make no sense when the problem is already identified and the solution is the 0x12B microcode or later). My only problem is the eTVB, which has a problem identified and corrected in the 0x125 microcode, and we are still at 115. But the question is, is the eTVB behavior the same with the desktop and mobile processors? Because the mobile versions are never pushed that hard and high in comparison to the desktop versions with liquid cooling (which gamers nexus stated is the majority of dead and dying 13900/14900 CPUs, not the air cooled ones)... I think, only a Intel tech could seriously answer these questions. A lot of questions, few real answers.
11-16-2024 08:00 AM
How strange that the Asus technicians do not include the microcode, if they did it in the G16 2024, the new V330 bios in G16 2023 says optional, it does not say critical, it means that it is a revision without any change in microcode, but if the processors HX 14th generation are the same as the 13th generation only with different frequencies, it is to say the least, very strange...