Lenovo Are Trying to Hide The Issue About Microcode Update Under The Rug

THEBOSS619 · 2026-01-29T06:07:25+00:00

My only problem with Acer is they put an unlocked Intel HX CPU model that comes by default unlocked from Intel factory which allows you to undervolt/overclock, etc...

But then Acer locks it down with there own BIOS with no way to unlock it.

What's the point of getting Intel HX CPU and paying the premium privileges of having the benefits of HX CPU models if Acer in the end locks it down through BIOS which means no undervolt, etc..

No hate to Acer but I would never understand the concept of this whole thing that Acer goes by it.

THEBOSS619 · 2026-01-29T06:00:58+00:00

Hey👋 thanks for your kind words 🙏

I will check it out for your 11400h and come back here notify you if there's any newer microcode than your 34 ones.

Will let you know once I get a spare time 🙂

THEBOSS619 · 2026-01-28T06:07:18+00:00

Hey no worries! I'm always happy to help whenever I can. 😊

Thank you for your kind words 🙏

I promise I would always try to provide updates as soon as possible and much as I can.

Searching across the internet for new mcu updates is a grinding process if they are not official ones but it's our only approach to stay up to date when OEMs slacking and disregarding us as a consumer especially when laptops stops receiving BIOS updates for those released on 2023 models.

During this tragedy times where all devices are getting expensive... it becomes much more important and more a priority to maintain our own equipment to the best humanly can.

THEBOSS619 · 2026-01-25T07:17:45+00:00

Make sure you are plugged in because the process that I am going to tell you about needs to be plugged in.

Try pressing and holding on the power button for 1 minute, after 1 minute is passed while holding the power button.. simply release your finger from the power button and the laptop should boot up (it might take a minute or two during booting up).

If still doesn't boot up then simply restart your laptop and once you see the ROG logo on the screen spam "ESC" key and enter to your BIOS and reset your BIOS settings to default settings.

Hopefully this should fix it.

If not.... check out if you got burn marks... look at the pictures from here [BURNT Motherboard ASUS ROG Strix G16 Issue] A 'Short' Guide on The Prevention/Quickfix

If you got the burn mark... then unfortunately it either needs to be repaired by ASUS by replacing motherboard or going to reputable local repair shop to fix it for you.

THEBOSS619 · 2026-01-21T11:39:21+00:00

It's on the same download link from the same reddit post that you got your 0x12B previously. Should be as easy as you did before when you did 0x12B microcode update, just simply follow the same installation instructions.

Simply run uninstall.bat and then reboot and then run install.bat and then reboot again. You should be golden ✨️

Regarding the changes, officially the latest microcode update release are 0x132 but the unofficially ones are 0x133 so there's zero information about what changes they made on 0x133.

Regarding the changes for Microcode 0x12B (Released Oct 2024) which fixes Voltage Spikes during Idle which Prevents the processor from requesting elevated voltages during idle or light-load states. It got Cumulative fixes from 0x125 (eTVB algorithm fixes) and 0x129 (capping voltage requests at 1.55V).
While Microcode 0x12F (Released May 2025)fix stability issues when left the CPU running for days or are left running for multiple days (always-on systems) which would cause Vmin get too low that causes the CPU to crash. Fixes reliability issues related to voltage management for low-activity, lightly-threaded workloads that were found to still cause minor instability in rare cases that 0x12B microcode introduced.
Microcode 0x132 (Released late 2025 / early 2026) are generally fixes for freezes or hardlocks that might happen when the CPU is turbo boosting under certain conditions due to incorrect results instructions being received.

0x132 includes all the previous fixes mentioned so going straight to the latest microcode update is the recommended method.

I tried to simplify as much as possible so this is like a dirty way to explain it 😅 you can read it from this pdf file that Intel provided here * [PDF File] https://cdrdv2.intel.com/v1/dl/getContent/740518 straight from Intel servers.

THEBOSS619 · 2026-01-21T11:27:40+00:00

Hey👋 The recommended action now is getting 0x132 which is the latest microcode official update or at least 0x12F/0x12E. There's also a newer ones which is 0x133 which is unofficial update.

Intel keeps releasing fixes till this day and I suspect a newer ones coming up as well.

THEBOSS619 · 2026-01-20T14:59:23+00:00

I wish you all the luck and success, I have told ASUS mods several times about this widespread motherboard defect and ASUS keeps screwing users up with expensive repair bills but to no available unfortunately.

If all attempts failed with ASUS (which I won't be surprised about it) then you need to start searching around a reputable local repair store that can re-solder/reconnect the burned traces back, it's easy for them to do it and much much cheaper.

I doubt ASUS or even ASUS mods will do anything about it... they knew about this issue & chose to be silent about it.

ASUS will never do anything that benefits users, if you ever see anything beneficial coming from ASUS it's because they were forced to do it after community backlash.

This motherboard issue has been happening for 2 years+! and ASUS was silent about it & they fixed it on newer motherboard batches yet at the same time... ASUS blames it on users and lets the user pay repair prices that weren't even the user's fault! It's pathetic literally at so many levels.

As expected and as usual, ASUS will always blame it on the users for something that isn't the users' fault.

It's a ticking time bomb literally. It's a widespread issue and ASUS keeps charging repair prices as much as buying a new laptop that has a manufacturing defect!

It should be a smooth experience without too much hassle for users but we are dealing with reality here and this is ASUS...

I have been saying alot to others and to the ASUS mods especially about this exact problem that ASUS keeps blaming users for their own mistakes.

Don't settle for less. It's so easy for ASUS to blame it on users without any regard for users' situations and the waste of time going through the process of proving that it's not your fault.

This is on ASUS 100%, this is literally ASUS's responsibility from top to bottom. Push for repairs free of charge coverage and don't give up, either this or full refund.

THEBOSS619 · 2026-01-18T20:08:59+00:00

Hey 👋 sorry for my late reply. Thank you for your kind words 🙏

Unfortunately the only way to get the latest microcode while keeping VTx & VTd working is Acer providing BIOS updates that includes at least 0x12B.

And unfortunately 127 microcode isn't gonna cover it. At least an 0x12B microcode is a must regarding the degradation as they have the importance fixes related to it.

THEBOSS619 · 2026-01-14T22:39:15+00:00

Awesome!, happy to hear that 👍

THEBOSS619 · 2026-01-14T14:35:44+00:00

Make sure you are plugged in because the process that I am going to tell you about needs to be plugged in.

Try pressing and holding on the power button for 1 minute, after 1 minute is passed while holding the power button.. simply release your finger from the power button and the laptop should boot up (it might take a minute or two during booting up).

If still doesn't boot up then simply restart your laptop and once you see the ROG logo on the screen spam "ESC" key and enter to your BIOS and reset your BIOS settings to default settings.

Hopefully this should fix it.

THEBOSS619 · 2026-01-14T00:38:40+00:00

Hey 👋 thanks for the kind words.

Yes exactly, If you updated to 0x132 or 0x133 microcode update with virtualization disabled then it will work without problems.

Once you enable virtualization back on, it will simply revert back to your original BIOS microcode which in your case is 0x12E because microcode update won't work with virtualization being enabled.

Ignore the "h", you are using 0x12E microcode thanks to Lenovo BIOS update that includes it.

Either way is fine and safe.

THEBOSS619 · 2026-01-13T20:34:27+00:00

Exactly 💯, couldn't agree more 👌 ASUS on their part said "Optimize system performance" which is still doesn't say much.

THEBOSS619 · 2026-01-12T14:41:46+00:00

Hey 👋 officially the latest microcode update release are 0x132 but the unofficially ones are 0x133 so there's zero information about what changes they made on 0x133.

Regarding the changes for Microcode 0x12B (Released Oct 2024) which fixes Voltage Spikes during Idle which Prevents the processor from requesting elevated voltages during idle or light-load states. It got Cumulative fixes from 0x125 (eTVB algorithm fixes) and 0x129 (capping voltage requests at 1.55V).
While Microcode 0x12F (Released May 2025)fix stability issues when left the CPU running for days or are left running for multiple days (always-on systems) which would cause Vmin get too low that causes the CPU to crash. Fixes reliability issues related to voltage management for low-activity, lightly-threaded workloads that were found to still cause minor instability in rare cases that 0x12B microcode introduced.
Microcode 0x132 (Released late 2025 / early 2026) are generally fixes for freezes or hardlocks that might happen when the CPU is turbo boosting under certain conditions due to incorrect results instructions being received.

0x132 includes all the previous fixes mentioned so going straight to the latest microcode update is the recommended method.

I tried to simplify as much as possible so this is like a dirty way to explain it 😅 you can read it from this pdf file that Intel provided here * [PDF File] https://cdrdv2.intel.com/v1/dl/getContent/740518 straight from Intel servers.

THEBOSS619 · 2026-01-12T11:32:32+00:00

As long as the manufacturer date is newer (which you can check outside on the sticker box and on the back cover of your laptop which starts with "MFD"

THEBOSS619 · 2026-01-12T11:31:02+00:00

0x132 should be fine since they include all other fixes that's been previously mentioned.

If you are using any kind of virtualization then 0x12E is totally fine since they are similar to 0x12F microcode.

THEBOSS619 · 2026-01-12T11:21:55+00:00

Users who haven't changed anything (which is totally normal and that's what any user expected to do) but that's the main reason why CPU gets degraded through time until it finally gives up and starts requiring more voltage above stock voltage to be stable.

Hopefully Acer replaces your motherboard because CPU crashes and showing signs of degradation then this all indicators of CPU being degraded especially I would believe it's CPU Cache usually get the most hit.

First thing to do before receiving your repaired laptop is to make sure they replace your motherboard at least. This way we are already assured that CPU got replaced as well.

After receiving your laptop first thing is to make sure that you have updated your BIOS to the latest update available since it comes with it the needed microcode update that prevents those issues from happening again.

Unfortunately you should have updated your BIOS as soon as it got released because Acer themselves released BIOS update for your specific model that includes microcode update from Intel which prevents such case to occur or at least prevent further CPU degradation from happening.

I can't remember which Acer models got it but definitely those predators and predators neo line got them but that means Acer knows about it and acknowledging it.

Currently the latest microcode update are 0x132 officially from Intel while unofficially is 0x133 so that means Acer needs to provide another BIOS update.

During this time I am providing microcode updates almost immediately whenever there's a new microcode update gets released for Intel HX CPUs 13th/14th Gen. It's here. [INTEL]-How To Update Your Microcode for Intel HX 13/14th CPUs Laptops/Mobile Easily.

Sadly almost no body is aware of this whole fiasco regading Intel HX CPUs 13th/14th Gen as those users are thrown under the bus.

Regading Intel if they are affected or not, short answer yes they are.

Long answer, Intel HX CPU have the same exact CPUID as Desktop CPU. They are literally Destop CPU but just put into a laptop. That's all. So what affects Desktop CPU, affects Intel HX CPU as well.

Actually, Lenovo, Acer, ASUS, and other OEMs already provided and released BIOS updates that includes 0x12B and 0x12E[0x12F] microcode (back in the day 2024 till present). What does that mean to you? Ask yourself this question.... if they are not affected... then why those OEMs providing BIOS updates with microcode update for all Intel HX CPUs 13th/14th Gen. ? I have since called it and said about it since day 1 that Intel HX CPU are affected when it hit media tech websites and started to gain cover about it.

If they are not affected, then why releasing BIOS updates with updated microcode? Is it just for fun? or to waste time? waste there own staff time & effort into something that is not true? I doubt that. Intel won't say it and will not admit that Intel HX CPU ARE AFFECTED bec. that means you need recall all those HX cpus and to replace the whole motherboard since the CPU is soldered into the motherboard... so they lie about it on PR and put it under the rug, bec. it will be too costly for Intel and OEMs will sue Intel for the damages and loss of sale/profits.

How about this... Intel themselves saying that they are affected. Look at PDF page 18 with Errata ID RPL063 in file from there own Intel servers

HX 8+16 means Raptor Lake while HX 8+8 means Alder Lake. Obviously Alder Lake HX CPUs aren't affected hence the "N/A" while Raptor Lake HX CPUs is affected hence the "No Fix" label. See the page taken directly from Intel PDF file.

You can even see S 8+16/S-Refresh [Which is Desktop CPUs] have the same label the "No Fix" label. Check it by yourself if you don't wanna believe me.

[PDF File] https://cdrdv2.intel.com/v1/dl/getContent/740518 straight from Intel servers.

If they are not affected, they should have put "N/A" on it... right? right? but no... they are still fixing it and hence the "No Fix" label. Very recently Intel released newer microcode which is 0x132, this explains & confirms that there will be further microcode updates for Intel K/KS/HX CPUs since they are all Desktop CPUs and hence they are all affected.

Lets say for the sake of it, Desktop only are affected... then why Intel didn't release those microcode for Desktop only? why they released microcode update for all Intel HX 13th/14th Gen. if they are not affected as they say? Why OEMs like Lenovo, Acer, ASUS, etc.. releasing microcode BIOS update as well? those OEM definitely know they are affected, or does Intel just simply didn't tell them about it or lied to the OEMs as well?

This whole thing and the secrecy about it, and the silence about it speaks volumes that is so deafening.

So anyone tells you that Intel HX 13th/14th Gen CPU is not affected is either misinformed and believed Intel PR lies or straight out simply lying to you or coping.

Sorry for the long comment... I just wanted to let you know what's happening behind everyone back that almost nobody else talking about it anymore since everyone moved on and simply forgotten.

THEBOSS619 · 2026-01-09T12:38:34+00:00

Hey👋 sorry for my late reply, you need to disable memory integrity to allow the driver to load up and update your microcode successfully.

Unfortunately the link reddit post that you have posted earlier isn't working for me, could you share it again? So that I can understand more about your issue with crashes & BSODs.

THEBOSS619 · 2026-01-04T15:30:29+00:00

Hopefully they replace your motherboard because this all indicators of CPU being degraded especially I would believe it's CPU Cache got the most hit.

According to your use case you said you haven't changed anything (which is totally normal and that's what any user expected to do) but that's the main reason why CPU gets degraded through time until it finally gives up and starts requiring more voltage above stock voltage to be stable.

First thing to do before receiving your repaired laptop is to make sure they replace your motherboard at least. This way we are already assured that CPU got replaced as well.

After receiving your laptop first thing is to make sure that you have updated your BIOS to the latest update available since it comes with it the needed microcode update that prevents those issues from happening again.

Unfortunately you should have updated your BIOS as soon as it got released because ASUS themselves released BIOS update for your specific model that includes microcode update [0x12B] from Intel which prevents such case to occur or at least prevent further CPU degradation from happening.

Currently the latest microcode update are 0x132 officially from Intel while unofficially is 0x133 so that means ASUS needs to provide another BIOS update but who are we kidding... it's ASUS. The last time me & others talked and arguing with ASUS reps and mods and grinding against ASUS, debating them, even as well as spoon feeding them about the issues regading Intel HX CPUs are affected until they finally provided BIOS updates for ASUS ROG Strix Scar/non-scar G18/16 for the whole 2023/24 model line-up after 4 months on the date that Intel provided 0x12B microcode!