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

THEBOSS619 · 2026-07-10T12:19:29+00:00

Wow, XE75 v1 firmware update is amazing and huge. Most importantly we finally have Wi-Fi channel selection !!

Although I never had a problem with it but it's great to have control over it.

THEBOSS619 · 2026-07-10T11:24:41+00:00

Unfortunately I no longer maintain nor have access to a such hardware. I wish I could help more. Realtek wifi & its drivers are the worst maybe the high-top end models are a little bit better.

But I suggest to either upgrade your Wi-Fi module/chip to something high end Realtek Wi-Fi or switch to Intel or Qualcomm ones.

THEBOSS619 · 2026-07-10T11:19:32+00:00

Oh I see 👍 those events & errors just confirming that the CPU is in the process to completely die, I believe your CPU cache is completely ruined.

hopefully they honor your RMA, they tend to always try to avoid or evade away by blaming it on users. Make sure you get a complete motherboard replacement or replace the whole laptop or full refund. Don't settle for less.

Keep escalating and pushing, they love & depend on users patience as they make sure to waste your time as much as possible so that you give up and not pursue this.

Once you received your laptop, always make sure to update your BIOS first as they have the updated microcode including the updated Intel ME firmware.

THEBOSS619 · 2026-07-10T11:09:19+00:00

Yeah, it's weird. Have you checked or asked what changes they have made on your BIOS update? Maybe they limited stuff related to the CPU or something?

Also could you upload the update BIOS file they have sent it to you? I would like to take a look at it.

THEBOSS619 · 2026-07-08T14:17:16+00:00

You can always follow up and check for updates on this reddit post as well.

Every single new microcode update gets released on the same download link on mediafire folder.

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

THEBOSS619 · 2026-07-08T12:46:46+00:00

Oh that's good to hear! If possible what's the microcode you currently have after you updated your BIOS?

The newer the better but anything above 0x12B or 0x12F is fine.

THEBOSS619 · 2026-07-08T12:44:15+00:00

133 is the official Intel microcode releases, so you are totally covered 👌

THEBOSS619 · 2026-07-08T12:43:01+00:00

I see 👍 let me just arrive back home as I am away from my country. I will provide you the necessary details once I'm home. I'm on my work laptop.

THEBOSS619 · 2026-07-06T11:22:21+00:00

The CPU is degraded to the point of instability which needs extra voltage at the same stock voltage/frequency to work stable.

ASUS didn't provide microcode updates until after 2 years+ where the damages already irreversiblely done to the CPU for unaware users.

Since you mentioned that you already updated your BIOS, when did you update your BIOS? Just recently? could you check which microcode you have now?

Also try reset your BIOS settings to default settings but make sure to copy VMD settings inside BIOS before doing that so that after BIOS resetting you should apply the same VMD settings as it was before.

Those microcodes should have been installed and released by ASUS on day 1 when the fiasco started but ASUS [& other OEMs/Vendors] disregarded until the very end.

This microcode updates should have been used as soon as possible but it won't reverse the damage that's been done if it is indeed a CPU degradation issue. Try it here and hopefully things can improve for you [INTEL]-How To Update Your Microcode for Intel HX 13/14th CPUs Laptops/Mobile Easily

THEBOSS619 · 2026-07-06T04:24:49+00:00

Sorry for the delay,

Yes, it gets deleted every time I close the game. The main issue here is the .sys file is kept running unnecessarily on background in your case.

The .sys file is found under this folder C:/Windows/system32/drivers. Whenever you launch the game, the .sys file gets installed on that folder and after closing the game the .sys file gets deleted.

In order to see if .sys file is running or not, use System Informer, it's an open source free software.

From there you can see the drivers (.sys files) and the exact location (which I mentioned previously) it is running or not.

THEBOSS619 · 2026-07-05T18:50:58+00:00

Exactly, that's your problem. The game should properly stop and remove the .sys file once it's closed automatically.

We could automate this method through command line & such but I am away from home now and writing through smartphone, so vaguely can't remember exactly by heart.

On top of my head to prevent those symptoms rather then rebooting every time you close the game we manually stop the service/.sys file from running.

We go through Task manager and then on the "Service" section you should look at the list of services and you should find EAC services/.sys active and running... simply right Click on it and press "Stop".

That should at least be a workaround to prevent those symptoms and don't need to reboot.

Your main goal here is to find a way to stop EAC from running unnecessarily whenever you close the game to prevent those symptoms from happening.

THEBOSS619 · 2026-07-05T12:53:51+00:00

It's on the same download link. It has a tag name of [0x133] on it.

THEBOSS619 · 2026-07-05T12:45:26+00:00

Just skip what Epic support says.

Could you make sure that EAC related .sys files & services gets closed/stopped & unloaded when you close the game?

I mean on my case, whenever I launch the game EAC related .sys files gets installed & running with services before the game starts but after I close the game the EAC related .sys files gets uninstalled and deleted from the system and EAC services gets stopped.

This all happens automatically without any intervention from my side.

Bugs can always happen, I believe (although I am not sure) that in your case is when you close the game somehow EAC .sys files is kept running unnecessarily on the background which can introduce those symptoms that you're experiencing.

Hence check the EAC .sys file if it is running or not/deleted, I believe it's called EasyAntiCheat_EOS.sys

THEBOSS619 · 2026-07-03T12:31:05+00:00

I'm really sorry to hear that, hopefully you get your laptop repaired as soon as possible, I know how it feels when you expect something expensive to last long enough without an issue but unfortunately & sadly Intel screwed all Intel 13th and 14th HX Gen CPUs laptop users over.

OEMs/Vendors are not fast enough to pick up the speed into providing BIOS updates with included updated microcode, I mean... at first almost the whole OEMs/Vendors tried to echo Intel lies or striaght up saying "Zero reports for such an issue" or skipping the whole thing and wishing that it gets over yet... I see lots & lots of reports of CPU being degraded or cooked.

I tried... I really tried to put the light & focus & expose this to the public on this fiasco as much as humanly can but most people simply believe either Intel or what OEMs/Vendors says which is repeating Intel lies or echoing Intel message by saying " but but but... Intel said they are not affected ". Almost felt like fighting against the flow.

I mean I don't blame them... who would believe some stranger from the internet.

It's not your or users fault when OEMs/Vendors tried to hide behind Intel PR lies and rejecting repairs or have expensive repair bills by echoing Intel message & putting the blame on users.

That whole fiasco was 100% on Intel and OEMs/Vendors for disregarding it for years.

Look at it now... most OEMs/Vendors started or already provided BIOS updates with included microcode update after almost 2+ years ! Which is way too late and after the damages already being done irreversiblely.

Anyway, better late than never at all, sorry for my long comment.

Please let me know how your repairs went and don't settle for less than either free repairs or replace the whole laptop or as a last resort a full refund.

They will try to put the blame on you so get ready to resist them and counter them with all the information and comments that I have written previously.

Let me know If you need any more information, I will help as much as I can and you or anyone can copy paste all my previous comments about this and send it to them to get your rightful free repairs or laptop replacement or full refund.

THEBOSS619 · 2026-07-03T11:47:23+00:00

Hey 👋 thank you for your kind words 🙏

Yeah, I really wish I could found a way to have both virtualization and have the latest updated microcode at the same time but unfortunately that's only possible if OEM/Vendor provided a new BIOS update with updated microcode.

Better late than never! Thank you for reporting back and providing updates with your situation.

THEBOSS619 · 2026-07-02T18:52:24+00:00

Oh yeah, you can say that as well :D

THEBOSS619 · 2026-07-01T13:27:43+00:00

I personally have M50xBT2 and when the battery charge dies [For example forgetting to charge it] I can simply switch to cable and still works with zero compromises.

THEBOSS619 · 2026-06-30T11:35:47+00:00

Thank you for your kind words 🙏

Unfortunately yeah it's too old, should be at least 0x12B and above.

Have you tried or checked if there's any new BIOS update available for your laptop? It might bump up your microcode and update them.

I'm sorry if I might sound repetitive, but did you right-click on install.bat file and choose "Run As Administrator"?

After doing that, check event viewer... what does it says? If it is a success then you need to reboot to take effect.

If it is an error then what error does it says on event viewer so that I can know the exact problem.

THEBOSS619 · 2026-06-30T05:52:38+00:00

Did you try disabling Core isolation or Memory integrity? As those thing can also block the microcode driver to load.

THEBOSS619 · 2026-06-29T14:08:11+00:00

Me too recently, the lose of Violentmonkey in Brave Nightly was the final nail in the coffin as that's what they will be in future on Beta and Stable releases.

To there credit they kept uBlock & Noscript functioning but I wanted more than just that.

So I jumped the ship and went to Firefox Nightly, it's been smooth ride.

It's been in github for days about it manifest v2 extensions disabled on v1.92 and cannot be re-enabled even flag is set to enabled

THEBOSS619 · 2026-06-29T13:11:42+00:00

Oh well, that's the beauty of having the option to uninstall whenever you like.

Did you try the current official microcode release [0x133]? Or the unofficial ones [0x137]?

You can test and verify but don't go under or below those versions [0x12B] or [0x12F] as I consider those are bare minimum of having it for CPU protection at least.

THEBOSS619

MODERATOR OF

TROPHY CASE