Intel XTU and ThrottleStop no longer working to undervolt Xeon E-2186m after firmware update

I was using ThrottleStop to undervolt the Xeon E-2186m on the ZBook 17 G5 to reduce temps, and everything was golden until applying the latest firmware. MB BIOS Q70 Ver. 01.09.01 and CPU microcode Revision BA are installed.

If anyone with an HP Probook, EliteBook, or, especially a ZBook that has the latest firmware could please check if you are able to still undervolt with TS or XTU, I would be interested to see if it's just my system.

 

That's to be expected. Google "Plundervolt". Intel is going to disable the ability to change VCore on ALL CPUs via Microcode Update for a very far fetched security risk....

 

So you need root privileges to even execute Plundervolt? If someone's gotten that far, an attack by VCore is the least of your worries.

 

HP seems to be the first manufacturer keeping the world safe from under volting.
Microcode 0xBA is the one to avoid. It disables under volting on the E-2186m.

http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1085#post-10979315

Once the lock bit is set, software under volting will be blocked. Intel XTU, ThrottleStop, Linux, does not matter.

 

Perhaps a more wide-spread NBR site wide alert to not update your Intel BIOS past a certain date or you might lose your undervolting ability might be in order?

Using the command-line in a "run as administrator" cmd or powershell, add /nodate to your winflash string to install the older BIOS version than is currently installed:

winflash /nodate

Hopefully this still works, I haven't had to do it myself for a few years.

There may be vendor specific options that you need, that one above is for Asus laptops. Look up your make / model command line BIOS flash instructions and add /nodate to try to regress the BIOS for your make / model.

There have been times in the past where regressing the BIOS to the previous version is not enough to get rid of all the changes the undesired BIOS install left behind.

Someone will have to try regressing their BIOS to the previous version and report back if it works or not on their make / model.

 

Yes, there were already reports of the cancer update with some HP Omen owners a couple of weeks ago, almost immediately after it was unleashed on unsuspecting victims. This is sad, as the average Joe will jump on BIOS updates just because "new is always better" in the flawed assumption of the masses. Those that know better know that newer has seldom been better for the past few years now. The bitter truth of the matter is the only truly safe computer (or tablet, or smartphone,) is the one that is turned off and disconnected from power. But, running with scissors is a far greater risk than Plundervolt.

 

Always do your due diligence if you absolutely has to jump on any new bios/firmware updates. Ask, ask and again ask the different guinea pig what is changed with latest and greatest. And don't trust answers from only one of them.

 

It's such a far fetched risk. I can't even..

 

Even if it were not far fetched, a 'fix' that results in the product being impaired directly and immediately is not acceptable. Better to leave it vulnerable. A case of the cure being worse than the disease. A cure for diabetes that causes cancer cannot be viewed as a legitimate option.

 

Indeed. I wonder if it's possible to flash the EEPROM externally without having to desolder.

 

I flashed my MECH-15 BIOS mod using an SPI programmer to get around the signature bull crap. It should be possible unless the system has BIOS Guard. Many newer Dell and Alienware laptops cannot be flashed with unsigned firmware even using an SPI programmer because of that filth. I know some of the other notebook manufacturers may be using that now, but I am not sure which of them are doing so. The only fix for that is replacement of the PCH chip with another one that does not have that payload of rubbish. But, it may be possible (not sure) if you are using the SPI programmer to flash signed firmware.

 

Hello guys, I can also confirm that the latest bios update for the Zbook 15 g6 disables undervolt. I have the i7 9850h and I tried undervolting with with both XTU and throttlestop and it would not apply any settings. I just reverted back to the previous bios version and undervolting works again.

 

Excellent!, thank you for trying out regressing the BIOS, glad to hear that works

 

It would be nice if people with new bios update that <disables undervolt> could test out if disabling the SGX features can regain undervolt functionality. Please, check it out properly before you roll-back to old working bios.

 

Didn't Intel say to disable SGX *until* the voltage adjustment disable firmware patch was available for your motherboard? I wouldn't expect disabling SGX would re-enable voltage adjustments.

It's worth a try I guess, @marckus would you like to give it a shot?

If your BIOS allows disabling SGX - you might check that first - then disable SGX and install the voltage tuning killing BIOS again... yikes... then see if your undervolt still works with SGX disabled?

Thank you!

 

Did not know about SGX before i rolled back to the old version, will give it a try and see if it works

 

It's up to the ODM/OEM manufacturer how they will implement the new security fixes.

Thanks. +rep

 

I tried the new bios update for the zbook 15 g6 and disabled SGX, but undervolting still would not work.

 

Thank you for checking that out @marckus, now at least we know for sure that the BIOS firmware patch will disable undervolting no matter what the SGX setting.

You were able to revert back to the previous BIOS again ok?

What method, tool, or command did you use on your laptop to regress to the previous BIOS?

 

I just downloaded the older bios installer from the hp site. It asks for you to input a code written on the screen if you want to revert, but if you follow what it says on the same screen it should be OK.

You may need to check if reverting to older bios versions is permitted in the bios options and un check it before you attempt to revert.

Everything works well after downgrading to the older bios.

 

It turns out my EliteBook 840 G6 won't undervolt. Maybe Windows Update nuked it as I did see a few Intel-branded updates installed over the last week.

Not sure if it's related, but using the InSpectre tool, I can't disable the Spectre protection. Clicking the button does nothing. So maybe that's locked out too. I never tried it until today so I don't know if this was always the case.

Charles

 

I can't remember the last time the InSpectre tool actually worked. It worked fine when it was first released but with the constant Windows updates it stopped doing anything and I reckon the developer has just given up on it.

 

You are probably going to try this already, but if not it would help to know if any of the recent updates can be uninstalled to restore undervolt.

Also if you can still undervolt in the BIOS before Windows loads - does that BIOS set undervolt persist through boot into Windows even with the new Intel firmware installed by Windows Update.

Hopefully one or both of those 2 workarounds can restore undervolt.

 

Have you checked the Intel Microcode version with Hwinfo/Throttlestop? I can't see what Intel branded update that could do this. Not even sure Microsoft have created a new Microcode.

Edit.
https://support.microsoft.com/en-us/help/4093836/summary-of-intel-microcode-updates

Not sure what you use to stop unwanted updates. If you're able to roll back to working state maybe give this tool a try. StopUpdates10 — New tool to stop Windows Updates +++. It will run in the background but maybe still worh a try.

Or the usual tweaks http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1087#post-10980641

Have always worked for me. Whatever OS version. Same for bro @Mr. Fox

I know you have had problems but say it don't work is wrong.

I'm on Win 10 Enterprise LTSC 2019 (1809) and with latest build. InSpectre works and I got my highest CBR-15 score with it http://forum.notebookreview.com/threads/clevo-overclockers-lounge.788975/page-1868#post-10982545

 

This is where I read that Intel is patching plundervolt via updates: https://www.bleepingcomputer.com/ne...volt-high-severity-issues-in-platform-update/

I got the latest version of ThrottleStop and it looks like this; FIVR is locked. According what unclewebb wrote in this post I don't know if there is anything that can be done.



Charles

 

For the Microsoft overlay of Rev. 0xBA that lock only holds true after Windows loads, right? So if your BIOS will allow a negative undervolt you could set it there before entering Windows and after entering Windows no changes could be made, but the BIOS undervolt would still be valid?

What about replacing the microcode store installed by the MS patch? Or finding the specific patch from Windows Update and uninstalling then blocking that?

Any other ideas on how to block or reverse this?

We've already verified it's possible to reverse the voltage locking BIOS update, and revert to the previous BIOS (winflash /nodate if needed) and that reverses the lock on voltage tuning from the BIOS side.

 

I'm so glad that the cancer micro-code has no effect on my desktop's X299 CPU. It's nice having no SGX support whatsoever at the hardware level. It's patched for Plundervolt nonsense, but it hasn't affected it at all.

 

Would you mind sharing a link? I only see the latest BIOS on the website now.

 

This is the link to the bios version 01.02.02 Rev.A for the HP Zbook 15 G6, released on Oct 9, 2019

https://ftp.hp.com/pub/softpaq/sp99501-100000/sp99616.exe

 

Got it! Undervolting is back, now -130mV and 1700pts on the 9880H n Cinebench R15.

 

Count me in the got-my-undervolt-back club too. It was the BIOS after all, not Windows updates. I downgraded my EliteBook 840 G6 to the R70 1.03.03 BIOS dated October 2019, available here. The BIOS starting with R70 01.03.04 stop undervolting.

I also disabled Intel SGX in the BIOS which is what was preventing the InSpectre tool from working, so all that stuff is disabled too.

My laptop is now so dangerous it's exciting.

Charles

 

Thats good.

Changes with the R70 VERSION: 01.03.04 REV: A PASS: 1

https://support.hp.com/soar-attachment/838/col91900-ob-242489-1-ob-242489-1_sp100135_releasedoc.html

Any of the fixes still there after rollback? ME, EC etc. Checked Microcode in TS?

 

The Intel ME version is the same, I looked at that last night. I'll have to check the CPU microcode later, I don't have my laptop with me. (Edit: Per TS, my CPU micro code is 0xC6.)

Undervolt -109.4 mV on CPU core/cache, Turbo Power short is 51W for 4 seconds, Turbo Power long is 28W (up from factory 18W). I also repasted the CPU with AS5.
CPU temps reach the upper 80s/lower 90s during Cinebench but not 99 C like stock. Best Cinebench R15 run with those settings is below. Stock I think I got 628 cb.

I ended up reducing Turbo Power Short to 40W for 2.5 seconds, I was occasionally hitting 99 degrees C. 51W is just too much for the heatsink. I also reduced Turbo Power Long to 23W and things are nice and cool, the CPU hasn't topped 90 degrees in days.



Charles

 

FFS, I should probably save some of these undervolt capable BIOSes, huh... At least rollback is possible. Last time I tried it on Elitebook/ZBook said I can't revert to older versions.

 

For quite a while the BIOS based flash and Windows based winflash wouldn't let you install an older BIOS than was currently running. You can add /nodate to the command line for winflash and that will allow flashing an older BIOS:
http://forum.notebookreview.com/thr...m-after-firmware-update.831546/#post-10980512

It looks like some BIOS will allow regressing the BIOS to an older version, YMMV.

 

Excellent method to obsolete laptops, new and old!

Glad this worked. I wonder if some of us will not have the option to roll back bios.

 

I just updated my HP KBL-G i7-8705G from 0xc6 to 0xca. According to Intel https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases, KBL-G 0xc6 and WHL-U 0xc6 microcode are released in the same batch 20191115. Throttlestop can still modify frequency and voltage without any issue. My guess is that HP may only block undervolt on business/enterprise models and leave it on for consumer ones.

 

How would SGX prevent "InSpectre to work". That is nonsense. InSpectre just sets two registry entries you can set yourself too if you want:

https://support.microsoft.com/en-us...ive-execution-side-channel-vulnerabilities-in

To disable all mitigations for Intel CPUs:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 3 /f

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f

The InSpectre tool has a bug. The toggle buttons show no toggle if you press it once, you have to toggle them a few times on/off/on/off to make it show correctly. Also you have to start it with administrator rights.

 

i got a dell g7 7790, w/ i7 9750h 2.6-4.5ghz...but after my update XTU doesn't let my golden -145 undervolt anymore...
--
i googled and ppl are flat out reverting from 1.12 to .9 or whatever regress bios...how?
--
also i can't get anything over 4.0 ghz...
--
also i noticed a setting (hopefully it's in my old bios i need to revert to) that say it'll keep me at highest cpu clock 40evas...i clicked it...and i'm always at 4.0ghz, but not 4.5 despite even XTU saying 4.5 is my highest
--
also now with that "stay at highest setting in cpu" actually unchecked whatever it was called to make it stay at highest (haha, verbage)...XTU says sugested settings is to: "Intel Turbo Boost Technology; Disable"
--
whaever i unchecked i'll write it down and come back and edit my post here...but i love it if it's actually keepingme at 100% all times...but ony at 4.0? wtf!

 

@Silverusaf99 you drunk?

 

Because 4.0Ghz is the all core clock that your CPU can run, stop using the high performance options that only put your cpu at high clocks making the laptop run hotter and drain the battery faster AND because all cores are being boosted you lose the higher turbo boost clocks that are allowed when less cores are being used..

Regarding the undervolt, rename the microcode update file in the System32 folder so that windows wont update your cpu microcode, thats due to a flaw in the SGX and a thing called Plundervolt.

 

what i could disable in bios was "intel speed step," it said it would keep my cpu at highest freq...but xtu is only showing 4.0

 

what's the name of this microcode file? do i not need to regress my BIOS?

 

mcupdate_GenuineIntel.dll located in C:\Windows\System32 rename it to something like mcupdate_GenuineIntel_backup.

Then reboot and check your undervolt.

If you didn't update your BIOS there is no need to downgrade anything.

 

itired to take ownership of mcupdate_GenuineIntel.dll and everything's greyed out in the objects subpanel...ie, users, admin, all the privs everything...

 

copy it to your desktop, change the name on desktop, delete the file that is on system32, replace with the already name changed one, dont think you can change the name of the file while its on the system32 folder.

 

can't delete the file that's in sys32...copied to dsktp and changed name, moved it into system32...but cannot delete...i tried figureing out the inheritance issue in RE: to the containers allowed as in "trustedblah" as in "disableinheritance" or tried to find the parent container that does indeed own the dir/files, but everything's greyed out...even searching for new containers, ie, usr,grps, etc...but i'm missing the mark here..i hope someone w/ more knowledge on elevated privs/active dir can helps me out...
--
i read that b/c im on win10 home this changes back to a troble for me next update. i am assume it his is nOT the case as the micro file is not found.

 

hello i cannot install 1.11bios from 1.12 via exe, what can I even do now?

 

i have bios reversion premitted in bios for my g7 7790, and have sgx settings off...

 

i removed that file...(ugh. finally), and am not able to undervolt anything...