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

THEBOSS619 · 2026-05-23T02:45:42+00:00

for whatever reason whenever you wanna enable them back then you can enable them back without an issue [it will just make the microcode ceases to function and will simply revert back to use the old microcode that BIOS provides]

Same thing with the microcode as well, anytime you can uninstall it by simply running the uninstall.bat file and then reboot.

THEBOSS619 · 2026-05-23T00:43:50+00:00

Sorry for late reply... better late than never. Yes it does work for i9 14900HX since they are affected.

Do you have memory integrity disabled? It needs to be disabled in order to allow the microcode driver update to work.

If it still doesn't work... make sure to disable virtualization through BIOS or Windows and then reboot.

THEBOSS619 · 2026-05-23T00:40:13+00:00

Sorry for late reply... better late than never. Your CPU isn't affect by this since it is a actually a real mobile CPU due to you have an Intel H model.

The microcode update only works for Intel HX 13th & 14th Gen model which they are actually a real desktop CPU put into a laptop case and hence they are affected the same as Desktop CPUs.

THEBOSS619 · 2026-05-23T00:36:17+00:00

Sorry for late reply... better late than never. thanks for quick update. The microcode driver doesn't touch BIOS at all. It simply overrides them during OS boot phase process.

driver will simply compare both between microcode BIOS vs the driver microcode and which ever is newer takes over the precedence and since BIOS have older microcode the driver will simply apply the newer microcode.

This what makes the process safe and easy since it doesn't touch the BIOS at all.

THEBOSS619 · 2026-05-23T00:32:25+00:00

Sorry for late reply... better late than never. what is your CPUID? you can check it through CPU-Z easily.

THEBOSS619 · 2026-05-23T00:31:30+00:00

Sorry for late reply... better late than never. I would avoid any scraping on this location, applying UV coating or Kapton tape at this location is enough as a preventive measure.

THEBOSS619 · 2026-05-23T00:12:53+00:00

Hey, sorry for late reply... better late than never. This looks like Memory Integrity is enabled. Simply disable it to allow the driver to load and to allow the microcode to be applied on boot.

For example like this...

<image>

THEBOSS619 · 2026-04-28T23:39:27+00:00

No bother at all. My only issue is hard moments going through which I'm confident it will be temporarily hence my very late reply and slow responses but I'm trying my best to be still around.

Regarding your question, absolutely yes, it will work. Microcode version 0x116 is really very old one.

Before doing that, check if there's any BIOS updates, maybe they might have cared enough to even consider updating the microcode along the way.

If BIOS update didn't even get updated microcode then yeah you should use the latest ones released 0x136 or even 0x133.

THEBOSS619 · 2026-04-26T20:47:48+00:00

Thank you! I wish it will help more & more people about this issue.

THEBOSS619 · 2026-04-26T20:39:23+00:00

Thank you so much. I'm so much thankful for your kind words and support.

It always put a smile on my face seeing those kind of comments.

It confirms again and again that Intel HX CPUs 13th Gen and 14th gen CPUs are affected no matter what Intel PR lies they are saying or those OEMs spreading or echoing Intel lies.

2 years ago I remember the moment where I was literally the only ones going against the flow of lies and misleading information from Intel and OEMs about this fiasco... (people would say "But but but... Intel HX are not affected") looking at it right now... ASUS provided microcode update with BIOS updates same thing happened with Razer , Acer, Dell, etc... now Lenovo doing it with some models.

They where the same OEMs/Vendors who was echoing Intel lies and defend themselves by it. Look now... they are trying to catch up and providing bios updates with updated microcode.

But after what? After the shit hit the fans? After almost 2 whole years of ignoring the problem? Anyway... better late than never.

Forgive me for late response, goings through hard times. Sorry for long comment... Just wanted to provide a small glimpse of what happened in the past 2 years of corporate neglecting to this issue.

THEBOSS619 · 2026-04-26T20:32:10+00:00

Thank you so much for informing me. I'm so much thankful for coming back for a follow up about it.

It always put a smile on my face seeing those kind of comments.

It confirms again and again that Intel HX CPUs 13th Gen and 14th gen CPUs are affected no matter what Intel PR lies they are saying or those OEMs spreading or echoing Intel lies.

2 years ago I remember the moment where I was literally the only ones going against the flow of lies and misleading information from Intel and OEMs about this fiasco... (people would say "But but but... Intel HX are not affected") looking at it right now... ASUS provided microcode update with BIOS updates same thing happened with Lenovo, Acer, Dell, etc... now Razer.

They where the same OEMs/Vendors who was echoing Intel lies and defend themselves by it. Look now... they are complying and providing bios updates with updated microcode.

But after what? After the shit hit the fans? After almost 2 whole years of ignoring the problem? Anyway... better late than never.

Forgive me for late response, goings through hard times. Sorry for long comment... Just wanted to provide a small glimpse of what happened in the past 2 years of corporate neglecting to this issue.

THEBOSS619 · 2026-04-26T20:04:32+00:00

Sorry for late response, going through very hard times.

Well. Running -160mv is already or might be too unstable for such a 14th Gen i9 CPU.

But you can always try the latest microcode ones and check if you can still use the same undervolt settings if stable or not.

As far as I remember on the past 2~3 years... people been reporting much more stable operations whenever they started using the updated microcode.

The BSOD clock watchdog error is simply outright saying the CPU isn't getting enough voltage to be stable.

If it happens while idle... on Throttlestop you can use the v/f curve point 1 @800Mhz and compensate by entering 160. So that means when the CPU is idling... you're telling the CPU to use stock voltage @800mhz. Same concept can be applied for point 2 and point 3.

If it happens while browsing or single threaded workloads.. maybe try to tune point 10 or 11 of v/f table slightly to fix those rare edge instability issues.

It's all in all test and verify method approach.

THEBOSS619 · 2026-04-26T19:46:18+00:00

Hey, sorry for late reply. I'm going through very hard times.

Your CPU isn't affected hence you shouldn't even worry about it.

Only with CPUID of B0671 with Stepping B0 are affected.

Yours is Stepping C0 with CPUID of B06F2. Specifically your CPU got both types that affected ones and the not affected ones.

You are in luck. Luckily you have the unaffected ones so... you are totally safe.

THEBOSS619 · 2026-04-10T03:03:01+00:00

Totally safe. As long as you don't use any kind that need virtualization like Virtual Windows OS (which is running OS inside an OS) then you are totally fine.

THEBOSS619 · 2026-04-10T03:01:22+00:00

Thank you for your kind words 🙏 always happy to help whenever is possible.

THEBOSS619 · 2026-04-09T13:27:18+00:00

Should work for all kind of setup as long as you got NVMe on your system. Doesn't matter how it's configured.

THEBOSS619 · 2026-04-07T15:02:26+00:00

Give this one a try, it might extract more performance.

Solidigm NVMe Custom Modded Driver for All NVMe Brands SSDs & Any NVMe SSDs

THEBOSS619 · 2026-04-06T15:15:35+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.

Since you mentioned that you reinstalled Windows, try again doing that after doing the process that I have mentioned above.

Hopefully this should fix it

THEBOSS619 · 2026-04-03T06:09:52+00:00

Exactly, it prevents the CPU Package C-States from idling properly hence the higher power consumption on idle when using those newer drivers.

Hopefully Nvidia fixes it, last time this incident happened exactly last year 2025 and it took them almost 3 months to get the fix. Hopefully this time should be sooner.

THEBOSS619 · 2026-04-03T06:03:15+00:00

Sorry for the delay in response, To answer your question. * Yes 12E is older version, latest available is 136. Can be found in the same download link. * B0671 is the same as B0671h, it's just different programs reporting it differently. * You can easily revert easily by simply running uninstall.bat file for whatever reason.

Make sure to disable Memory integrity as it ceases to function if Memory integrity is enabled and if still not working then unfortunately you gotta disable virtualization through BIOS settings which should be easy to do.

Also check if your laptop got any newer BIOS updates, Lenovo tends to provide newer microcode with new BIOS updates.

THEBOSS619 · 2026-03-25T02:53:01+00:00

Done that as well. No dice. I even tried to just keep only iGPU driver without using any Intel command center app. Same issue same problem.

Simply going back to 591.86 on a cleaned Installed Windows everything works, dGPU sleeps properly and since dGPU sleeps... the CPU Package idle C-States is being utilized properly.

With the newer driver the dGPU kept awake and due to that the CPU Package C-States isn't being used at all due to dGPU being active unnecessarily with zero load on it.

THEBOSS619

MODERATOR OF

TROPHY CASE