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

[fArkzAr]

Hello my good sir, I'm just passing by to rectify the information I gave wrongly, I managed to access the hidden settings of the Asus (ROG G18) bios with SREP, from this I reached the 5.6GHz standards of my processor with a maximum VID of 1.28V (Limited to 1.3V in BIOS) which really makes sense considering that originally the processor requires 1.45V to reach this frequency but with 180mV of undervolt we have the voltage x frequency curve at 5.6Ghz with 1.27V with no more voltage spikes when the processor is at idle or with light processes that are the real problem. Thank you very much for helping us and distributing this information so that we do not become dependent on a manufacturer that has not done anything to date regarding these problems.

Hi sir, how did you do this through SREP? I downloaded it to a flash drive, booted up and only had 3 menus: boot menu, device menu. Could you share your srep_config file? I'm not very experienced with this.

 

[j0z3k87]

When I back to home I will provide some screen shots I had some issues with my scar but at the end I been able to lock at 1.4 also without Tvb with 52x on clock my laptop working like dream with additional 125 undervolt

 

[QyInvoLing]

I've tried this solution and successfully updated my 14600kf's microcode to 0x12b, but the bios remains at 0x125——after doing that, I found that I cannot boot after enabling xmp... Keep every params of the memory to jedec standard solves this problem. Any ideas about that?

 

[THEBOSS619]

I've tried this solution and successfully updated my 14600kf's microcode to 0x12b, but the bios remains at 0x125——after doing that, I found that I cannot boot after enabling xmp... Keep every params of the memory to jedec standard solves this problem. Any ideas about that?

Thank you for reporting

1st of all, it doesn't touch your BIOS so obviously it will still display 0x125 and 2nd of all again it doesn't touch your BIOS so I don't know how a microcode affects xmp. I can say it might affect undervolting but not RAM related stuff

When I back to home I will provide some screen shots I had some issues with my scar but at the end I been able to lock at 1.4 also without Tvb with 52x on clock my laptop working like dream with additional 125 undervolt

Glad you find a way to do that! Please let us know so that everybody can benefit from your screenshots thank you

Great news for ASUS users! sorry for the tag but you must see this @hexaae

ASUS just released a BIOS update with 0x12B ! but I think only to specific 2024 models... not all yet... but hopefully this gives us some hope that it will get released for all 2023/2024 models that uses Intel HX CPUs

Of course the usual generic changelog that ASUS put in.... "Optimize system performance" but look... it doesn't say Importance: "Optional" but it says "Critical" ... now they are very serious huh? as a user from ASUS forums said....

This means that the Asus technicians found something really related to the 13th and 14th Generation problem in the HX versions because the bios for G16 2024 says CRITICAL very clearly, it is definitely a good thing for all owners of the G16 models.

Reference:-

• https://rog-forum.asus.com/t5/rog-s...-14th-cpus/m-p/1055590/highlight/true#M207263
• https://rog.asus.com/laptops/rog-strix/rog-strix-g16-2024/helpdesk_bios/

 

[j0z3k87]

my model also get 12B so now it is not conspiracy theory like they tried to convince us?

 

[THEBOSS619]

my model also get 12B so now it is not conspiracy theory like they tried to convince us?

exactly, and the same exact people who keeps telling that it's not a affected are right now coping so hard. It just confirms all what I have been saying since day 1 ! I have been attacked / disregarded / dismissed for just simply saying facts & truth.

Gamers Nexus himself doesn't believe Intels crap statements and he received lots of emails about degraded Intel HX CPUs from his users/viewers.

It is funny... OEMs now just started to wake up? where they have been all those previous months ? why all this wait? why wait until the CPU gets cooked & it's too late to salvage it?, the only option is mobo replacement... good luck getting approval from OEMs for that & if they did approve mobo replacements... get ready to pay up for repairs. It is just a sad sad moment but... at least OEMs started to do something.

Better late than never, completely disappointed about how Intel & OEMs handled Intel HX CPUs users with 100% complete lies, pointing fingers, etc... no one is excluded from this mess... NO ONE... from the top to the bottom... from CEO to OEMs forum moderators. They are all to blame for echoing Intel lies without any kind of verifications They are all to blame for that & I wish Intel & OEMs gonna pay a price for it.

I have been on top of the issue when raptor lake blow up & been repetitively saying from the very first day that HX are Desktop CPU, what affects Desktop CPU affects HX too. Period.

I don't care who is right or wrong but I can't see when Intel lying publicly and OEM echoing them without any kind of caring to consumers, it is just unacceptable & I'm glad I exposed them. Actions speaks louder than words, I always live by those lines.

If no body talking about it... and pushing for answers... then who will? I could just be careless about others & sit back and let others figure it out.

 

[macinow21]

Hello, I am using a ROG STRIX G18 2023 (G814-JI) with i9-13980HX and RTX 4070.

First of all, I use this PC for 1 year and I wasnt experiencing or paying attention to heat issues. I recently noticed (4 months ago= high temperatures (exceeding 105 degrees with 4000-ish rpm fanspeed) resulting throttling up to 55%. I didnt think much about it because ambient temp was 30-35 in summer. But PC didnt throttle back then. In particular, I had problems after one BIOS V328 if I remember correctly. I saw Intel desktop CPU fiasco and when I searched about laptops, I did not find something bad about it back then. But yesterday I had enough of low performance and decided to search deeper.
Heres what I did about this issue:
1) Formatted Windows with clean 24H2 iso. This did not much about heat issues but system fludidy now better.
2) Tried reflashing BIOS V330 but it didnt make a difference.
3) Checked fans-cooling by eye and didnt see any dust.

Now I want to tell you what I noticed after searching all this:
ASUS probably never update drivers in their ROG Support website (https://rog.asus.com/laptops/rog-strix/rog-strix-g18-2023-series/helpdesk_download). Most of chipset and CPU related drivers from late 2022. Also I couldnt find any newer ones. When I checked the support page for ROG STRIX Z890-F GW there are drivers from November 2024. Why drivers for laptops didnt get update since then?

Also BIOS V330 dated 09/13/2024 but update released recently (like 6 days ago). After installing I noticed theres no update for microcode. My laptop's version is 115 (checked with HWiNFO).
Theres no update for Intel ME - firmware version 16.1.27.2176 driver version 2229.3.2.0 date 07/14/2022. CPU driver dated 04/21/2009 with version 10.0.26100.2161.

My question is how can I update these old drivers officially? Why ASUS wont release newer ones? I saw some people updated with other mobos drivers. I will try step by step but ASUS must provide supported and compatible drivers. After trying all these software updates, if heat not solved, I will try to clean the laptop by myself or go to the service center.

I am waiting your suggestions. Thank you in advance.

 

[Lalaquesle]

Hello, I am using a ROG STRIX G18 2023 (G814-JI) with i9-13980HX and RTX 4070.

First of all, I use this PC for 1 year and I wasnt experiencing or paying attention to heat issues. I recently noticed (4 months ago= high temperatures (exceeding 105 degrees with 4000-ish rpm fanspeed) resulting throttling up to 55%. I didnt think much about it because ambient temp was 30-35 in summer. But PC didnt throttle back then. In particular, I had problems after one BIOS V328 if I remember correctly. I saw Intel desktop CPU fiasco and when I searched about laptops, I did not find something bad about it back then. But yesterday I had enough of low performance and decided to search deeper.
Heres what I did about this issue:
1) Formatted Windows with clean 24H2 iso. This did not much about heat issues but system fludidy now better.
2) Tried reflashing BIOS V330 but it didnt make a difference.
3) Checked fans-cooling by eye and didnt see any dust.

Now I want to tell you what I noticed after searching all this:
ASUS probably never update drivers in their ROG Support website (https://rog.asus.com/laptops/rog-strix/rog-strix-g18-2023-series/helpdesk_download). Most of chipset and CPU related drivers from late 2022. Also I couldnt find any newer ones. When I checked the support page for ROG STRIX Z890-F GW there are drivers from November 2024. Why drivers for laptops didnt get update since then?

Also BIOS V330 dated 09/13/2024 but update released recently (like 6 days ago). After installing I noticed theres no update for microcode. My laptop's version is 115 (checked with HWiNFO).
Theres no update for Intel ME - firmware version 16.1.27.2176 driver version 2229.3.2.0 date 07/14/2022. CPU driver dated 04/21/2009 with version 10.0.26100.2161.

My question is how can I update these old drivers officially? Why ASUS wont release newer ones? I saw some people updated with other mobos drivers. I will try step by step but ASUS must provide supported and compatible drivers. After trying all these software updates, if heat not solved, I will try to clean the laptop by myself or go to the service center.

I am waiting your suggestions. Thank you in advance.

Hello,

The first thing would be to undervolt the CPU (Throttlestop) and GPU like those posted in this thread, . I also have a G18, the only difference to yours is the GPU, and one of the first things I did was reapply the liquid metal that Asus applies excessively and ends up leaking to the sides, leaving areas of the chips uncovered as shown in the images below. In my case, the last 4 E cores reached 100 degrees quickly while the others maintained temperatures around 20-30 degrees lower. And on the GPU the hotspot had a difference of more than 20 degrees. For GPU undervolting, there are several tutorials on YT. Just remember that reapplying liquid metal can kill your laptop if not done correctly. Additionally, you can limit it to 5Ghz to have a temperature without peaks since the two cores that reach 5.6Ghz will no longer do this and disabling Hyper Threading also helps without affecting gaming performance, in some cases even improving. I updated some drivers unofficially and there were no differences in performance or temperature. Try monitoring with HWInfo or HW Monitor and see if there are very large differences in maximum temperatures between the processor cores or between the GPU and the hotspot, if there are any, the problem is most likely the application of liquid metal

 

[j0z3k87]

had the same in mine SCAR 2024 model... Its your new laptop?

 

[macinow21]

Hello,

The first thing would be to undervolt the CPU (Throttlestop) and GPU like those posted in this thread, . I also have a G18, the only difference to yours is the GPU, and one of the first things I did was reapply the liquid metal that Asus applies excessively and ends up leaking to the sides, leaving areas of the chips uncovered as shown in the images below. In my case, the last 4 E cores reached 100 degrees quickly while the others maintained temperatures around 20-30 degrees lower. And on the GPU the hotspot had a difference of more than 20 degrees. For GPU undervolting, there are several tutorials on YT. Just remember that reapplying liquid metal can kill your laptop if not done correctly. Additionally, you can limit it to 5Ghz to have a temperature without peaks since the two cores that reach 5.6Ghz will no longer do this and disabling Hyper Threading also helps without affecting gaming performance, in some cases even improving. I updated some drivers unofficially and there were no differences in performance or temperature. Try monitoring with HWInfo or HW Monitor and see if there are very large differences in maximum temperatures between the processor cores or between the GPU and the hotspot, if there are any, the problem is most likely the application of liquid metal

View attachment 372295View attachment 372296

Thanks for reply, you can see my temperatures in the screenshot. GPU hotspot and GPU difference is nearly 12-13 degrees at max. I moved this PC with my backpack 20 times maximum, other than that always on desk and on power. Temperatures in my first message is in WoT game, 2K ultra settings with turbo mode off, I had to get 200 FPS avg before summer. Thats why I am suspicious about BIOS V328 "CRITICAL" update, also if its not V328, one BIOS update cut CPU fan speed by 1100 RPM.

Does undervolting drops performance? This is not my aim, I want to get full performance without exceeding temperature limits.

Cinebench R23 Test - Fan speed 4800 at 88 degrees (turbo mode factory default)
Current temperatures had difference of 2-4 degrees at max, like P cores run 90 degrees avg and E cores 84-85 degrees avg

 

[QyInvoLing]

Is there any solution for linux? I've tried to update intel-microcode using apt, only getting 0x129 microcode

According to this comment, updating microcode in operating system could fix some issues, but not this instability issue, as fixing it needs to restart the hardware, which is impossible in OS and only can be done in BIOS.

 

[:D:D]

Interesting

Hi folks, let me add some clarity. The microcode update (MCU) for the 13th and 14th Generation Intel desktop processors that was released last week (MCU Revision ID 129) is not effective for the Instability issue when loaded from the OS. To be effective, the MCU will need to be loaded from BIOS. This is the same for all operating systems; Windows, Linux, virtualization environments, or anything else where the MCU is loaded after BIOS done. This is also why the MCU was not posted to this repository last week since we did not want to confuse people into believing that systems were mitigated for this issue by loading the MCU from the OS or virtualization environment.

As they did supply 0x129 and later 0x12B which is already in Fedora 41 IIRC. There's also some vague comments about resets but haven't seen them described in detail. CPU / ME ? Let me see if I can find the post(s)

Edit: Think it was this one, same guy.

Yes, just to confirm, in this case, the microcode update must be loaded from BIOS to be effective for the instability issue.

Some issues can be resolved when the microcode update is loaded, but other issues, such as this one, require resetting hardware after loading the microcode update.

What HW needs resetting? Usually the microcode patch is set very early, well at least for BSP so most HW is already in a reset state and needs setting up.

 

[QyInvoLing]

Interesting

As they did supply 0x129 and later 0x12B which is already in Fedora 41 IIRC. There's also some vague comments about resets but haven't seen them described in detail. CPU / ME ? Let me see if I can find the post(s)

Edit: Think it was this one, same guy.

What HW needs resetting? Usually the microcode patch is set very early, well at least for BSP so most HW is already in a reset state and needs setting up.

I lacks necessary knowledge for judging these description about reset...Meanwhile there's nothing updated for Ubuntu, so I tried to modify the bios, replace 0x104 microcode with 0x12b, which turned my motherboard into a brick. I'll check it out later once the programmer I ordered arrive by using the platform only updated microcode in windows for a couple of months and check whether it downgraded.

 

[:D:D]

That sucks. Which BIOS bricked, would you post a manufacturer's link?

Sorry, I wasn't asking you specifically about reset just that I'm a little skeptical about having to do a reset if the microcode is applied early, PEI or before. Maybe someone could ask the guy to clarify.

 

[macinow21]

Is there any solution for linux? I've tried to update intel-microcode using apt, only getting 0x129 microcode

According to this comment, updating microcode in operating system could fix some issues, but not this instability issue, as fixing it needs to restart the hardware, which is impossible in OS and only can be done in BIOS.

Only real solution is probably BIOS update. OEM needs to fix this issue + update outdated drivers.

 

[QyInvoLing]

That sucks. Which BIOS bricked, would you post a manufacturer's link?

Sorry, I wasn't asking you specifically about reset just that I'm a little skeptical about having to do a reset if the microcode is applied early, PEI or before. Maybe someone could ask the guy to clarify.

I probably misreplaced the microcode so the motherboard bricked, I've prepared a correctly replaced bios and I'll check it later once the programmer I bought arrived. The motherboard is called "JGINYUE b760m star", which is slightly longer than an itx mb and offers 4x M.2& 3xHDMI+1xDP&2x2.5G RJ45.

I may ask the guy on github later about the "reset", as I didn't heard of that idea before too.

 

[THEBOSS619]

WIN & SUCCESS
Just wanted to share good news here regarding for ASUS users with Intel HX CPUs 13th/14th gen We did it! After I was grinding against ASUS mods & reps & emails with also the help of other people [while there is some people who's against BIOS/Microcode update ] ASUS finally made a move after a long months of fighting.

@hexaae you want to see this

 

[shishimaru]

MSI has also just released a new BIOS update for my HX laptop after one year, but I can't find any changelog Let's see if it addresses the microcode situation.

edit: nope, it doesn't. Shame.

 

[:D:D]

The motherboard is called "JGINYUE b760m star"

Cool. 0x104 is smaller than 0x12B. Maybe you could invalidate 0x104 and sacrifice one of the bigger ones for replacement?

I notice the 790M got 0x12B update so maybe it's in the works for your board. Have you tried contacting support?

FWIW they all seem to be using ME 16.1.25.1917 firmware, don't know if that has any affect or not. @THEBOSS619 ?

 

[tkolrmx]

I've been experiencing random unrecoverable system freeze usually when something is left on full screen mode for a long time (like a vlc on pause) and I was wondering if it's related to 13th/14th gen issue. I've checked the whea dmp log and it says intel?

 

[THEBOSS619]

I've been experiencing random unrecoverable system freeze usually when something is left on full screen mode for a long time (like a vlc on pause) and I was wondering if it's related to 13th/14th gen issue. I've checked the whea dmp log and it says intel?

Have a look at this compiled list that indicates CPU is degraded, try one of the methods and see if it crashes for you. This can guide you https://www.reddit.com/r/intel/comments/1ekiwku
UE5 & Linux USB method was most consistent ones that show signs of CPU degradation on Intel HX CPUs. Two of my work friends happened to them and I tested those two methods on there laptops and it was indeed having degraded CPU issues. 1st was Acer Helios with HX i9 13th gen and other one was Gigabyte HX i7 14th gen.

Both OEMs reported a generic answer indicates "CPU Problem" and both OEMs suggested solution was "Motherboard replacement". I bet most OEMs they don't diagnose the reason behind those problem immediately. I guess they straight up repair users laptop, replace mobo and then find out later the reason behind this

MSI has also just released a new BIOS update for my HX laptop after one year, but I can't find any changelog Let's see if it addresses the microcode situation.

edit: nope, it doesn't. Shame.

Check your Intel ME FW, they might have updated only the Intel ME FW. ASUS have done the same thing for 2023 laptop models and they promised to provide 0x12B microcode update soon on the next BIOS update release.

Cool. 0x104 is smaller than 0x12B. Maybe you could invalidate 0x104 and sacrifice one of the bigger ones for replacement?

I notice the 790M got 0x12B update so maybe it's in the works for your board. Have you tried contacting support?

FWIW they all seem to be using ME 16.1.25.1917 firmware, don't know if that has any affect or not. @THEBOSS619 ?

Intel ME FW It must be not lower than 16.1.30.2307. Anything with Intel ME FW version 16.1.30.2307 or above is good and you don't need further updates for it. You can do it easily for your motherboard. You just need to look the right chipset series model name that you have and download the related files to update your Intel ME FW.

Usually it is H770/HM770 that you need to look for it, both H770/HM770 are exactly the same thing. You can check this through HWINFO64... here's an example of mine.

Just for the sake of assurance, please double check everything

You can find them under "FIRMWARE" section
https://www.elevenforum.com/t/index-all-my-drivers-firmware-software-threads.11360/

I recommend doing the update process while in "Safe mode" due to how sensitive this update process are & to prevent any interruption from anything.

Any thing that interrupts the update process will result on bricked motherboard or flashing the wrong Intel ME FW will obviously brick your motherboard/Laptop/PC. Again Double Check Everything.

 

[:D:D]

Intel ME FW It must be not lower than 16.1.30.2307. Anything with Intel ME FW version 16.1.30.2307 or above is good and you don't need further updates for it.

Thanks. Do you have a link as to why a firmware from Sep 2023 is required? Intel only indicate BIOS firmware needs updating, they should also IMO indicate ME firmware requirement.

Intel Core 13th and 14th Gen Desktop Instability Root Cause Update

Following extensive investigation of the Intel® Core™ 13th and 14th Gen desktop processor Vmin Shift Instability issue, Intel can now confirm the root cause diagnosis for the issue. This post will cover Intel’s understanding of the root cause, as well as additional mitigations and next steps for...

community.intel.com

Tried searching but closest I came to was some Asus statements with BIOS updates for 125, 129 and 12b.

For 125

Before BIOS update, please download the Intel ME update tool from the ASUS support site and update the ME firmware to Version 16.1.30.2307 to ensure optimized system settings.

For 129

Updating this BIOS will simultaneously update the corresponding Intel ME to version 16.1.30.2307v4

For 12B

1.Updated with Intel microcode 0x12B to address elevated voltage requests during idle or light activity, further mitigating Vmin Shift instability issues.
2.The option to disable C1E in the BIOS has been removed to ensure it remains enabled, reducing processor stress and maintaining stability per Intel's recommendation.
Before BIOS update, please download the Intel ME update tool from the ASUS support site and update the ME firmware to Version 16.1.32.2473 to ensure optimized system settings.

Seems fairly generic statements and ME updates mostly describe reasons as "security vulnerabilities"


Regarding HX, from spec update

Presumably if HX 8+16 unaffected it would be "N/A" not "No Fix"

 

[THEBOSS619]

Thanks. Do you have a link as to why a firmware from Sep 2023 is required? Intel only indicate BIOS firmware needs updating, they should also IMO indicate ME firmware requirement

Exactly, Intel should indicate ME FW requirements but they didn't because they expect OEMs to follow Intel instructions on providing BIOS updates with microcode update + the needed Intel ME FW.

If you remember about 0x129 microcode update once being available to the public previously on desktop/PC world... almost all OEMs provided BIOS updates with microcode 0x129 + Intel ME FW In a single package. Some even tells you specifically to update Intel ME FW first & then update the BIOS which includes 0x129 & then 0x12B BIOS update.

Lenovo, Acer, etc.. have provided Intel ME FW update with there own BIOS update that includes 0x125/0x129/etc.. as well for Intel HX CPUs & Desktop ones as well without even mentioning about Intel ME firmware being updated on changelog.

Regarding Intel ME firmware requirement, Unfortunately no link to show this [I have seen it before on Intel forums but I no longer can find it through my browsing history]. I have known about this through a friend of mine. He is working at a hospital as an IT & he deals with Intel rep or through there channel of Intel communication.

The first thing Intel rep told him is to update Intel ME FW first before continuing to update BIOS as a crucial requirement step.

My only proof about Intel ME FW requirement is he told me about it when I asked about managing the servers since most of them running Linux OS based & most OEM provide tools for windows only regarding updating Intel ME FW so it was a nightmare for him

Intel ME firmware security list fixes that you see online are only true for Intel ME FW part but they aren't true about IUP. I have seen mentioning about IUP very rarely, I guess it's a one time thing they have mentioned about it for as long as I remember.

I am sure 99% that they aren't focusing on updating Intel ME FW or it isn't the goal about it... but they are updating IUP modules that comes with updated Intel ME FW. You can't just update IUP alone while keeping Intel ME FW severely outdated.

There's a minimum requirement must be met of Intel ME FW to be installed before updating IUP & I believe in order to get IUP update... you have to update Intel ME FW as well.

IUP modules consist of those on the list that comes with Intel ME FW:-

• Power Management Controller (PMC)
• Platform Controller Hub Configuration (PCHC)
• USB Type C Physical (PHY).

The first two IUP modules are the most important thing & they have a role & contribution about Intel RaptorLake fiasco as well. Hence why you see almost all OEMs are updating Intel ME FW along with BIOS update that includes (0x129 & 0x12B) microcode.

They aren't updating Intel ME FW just for security but it's for updating IUP modules which requires Intel ME firmware to be updated as well if it doesn't meet the minimum requirement of having a specific Intel ME FW.

Forgive me such a long comment, I tried to simplify it as much as I can without omitting any important info. hopefully I didn't miss anything & correct me if I'm wrong... we all do mistakes.. I'm human after all

Regarding HX, from spec update

Presumably if HX 8+16 unaffected it would be "N/A" not "No Fix"

You called it, correct and just to make everything clear for everyone... HX 8+16 means Raptor Lake CPU while HX 8+8 means Alder Lake CPU.

Gotta love how Intel naming confusing schemes are...

 

[P4ND3R550N]

Hi all. I have bought myself a Xidax XM10 gaming laptop. With i9 14900HX and RTX 4090 and other awesome specs. But i am looking to update micro update. Can someone please help me with this. Can someone send me a link step by step what i should do? I have disabled memory integrity in core isolation, disabled virtualization and still it does not update the micro code.

 

[THEBOSS619]

Hi all. I have bought myself a Xidax XM10 gaming laptop. With i9 14900HX and RTX 4090 and other awesome specs. But i am looking to update micro update. Can someone please help me with this. Can someone send me a link step by step what i should do? I have disabled memory integrity in core isolation, disabled virtualization and still it does not update the micro code.

Check event viewer, look for "cpumcupdate" event log, and see what does it says and post it here, so that we can help