BLACK LIST 2. Adjustable voltage control/turbo ratio limits locked out - Affected 10th gen notebooks

This thread is for 10th gen notebooks...

The history... From my other thread...
BLACK LIST. Adjustable voltage control/turbo ratio limits are locked out due latest Win Update/Bios"
http://forum.notebookreview.com/threads/the-throttlestop-guide.531329/page-1082#post-10977989


Please post your notebook/desktop model, if your PC come with no ability for voltage adjustment (undervolt) in bios/3rd party software as ThrottleStop or XTU... I will add it into this 1th post. Thanks

The basis for creating this thread.
Protecting your Intel CPU from Plundervolt attacks can ruin your overclock/undervolt

Spoiler: THE BLACK LIST - 10th gen Notebook models with adjustable voltage control removed by the ODM/OEM

1) Dell XPS 15 9500 and XPS 17 9700 http://forum.notebookreview.com/thr...cted-10th-gen-notebooks.833280/#post-11024268

2) HP Pavilion 16.1 http://forum.notebookreview.com/thr...0th-gen-notebooks.833280/page-2#post-11042342

Preview from the spoiler...

1) Dell XPS 15 9500 and XPS 17 9700
2) HP Pavilion 16.1

 

Saved for later use

 

XPS 15 and 17 confirmed:
at 8:00

I also haven't been able to find a 10th Gen Lenovo that is able to undervolt, but most people aren't talking about it.

 

Thanks. +reps Dell XPS 15 9500 and XPS 17 9700 added into the list of shame!

Is it confirmed it can't be undervolted with Throttlestop or XTU?

 

Lenovo E14 (and presumable E15 as they have exactly the same internals) is still able to undervolt, even on the latest BIOS ver 1.11 date 21/04/2020. Am fully updated on Windows, and apparantly I still have SGX enabled (I thought I disabled, it, but apparantly the BIOS update reset some settings)

 

On my XPS 9570 with i7-8570H, BIOS version 1.16.2 addressed SA-00289 and locked the CPU. ThrottleStop 9.0 will show "locked" in FIVR, I can edit the voltage offset but they're not applied to the CPU, turbo boost adjustment is disabled.

I was able to downgrade the BIOS to older versions, chose to stay at 1.15. It'll say "Intel ME update failed" during the process, but after restoring Factory Settings (which is absolutely needed), the CPU will be unlocked again. Be sure to disable "UEFI capsule firmware update" in BIOS, or Windows Updates will automatically bring it back up again.

Weird thing is, my Inspiron 2-in-1 7391 also has SA-00289 listed in 1.4 update (Jan 2020), but the i5-10210U is not locked, I was able to apply -80mV as well as TurboBoost adjustments. The latest BIOS 1.5 doesn't mention anything related.

 

Add the 2020 Razer Blade Pro 17 and 15-inch Base to the list. BIOS 1.03 appears to lock out undervolting for these models. There is no "update" as yet for the 2020 15-inch Advanced, though I expect one will be coming in fairly short order. Good news is that, at least for now, Razer doesn't force BIOS updates through Windows Update. Bad news is that once current inventory runs out, new production runs will have the locked out version installed by default, and unlike with Asus or Dell, there's no easy way to revert back to older revisions.

Link

 

Will be a few days before I update threads. On vacation with a phone and awful internet. I will follow up everything later. Thanks +reps

 

Related information about Clevo and TongFang, intitially posted here.

Don't rejoice too soon yet. Here are the latest updates that are supposed to be rolled out this month.

P9xxED/EF/EN and P9xRD/RF/RN
BIOS 1.07.15
Microcode Update to 0xC6

NB70TH
BIOS 1.07.09
Microcode Update to 0xCA

P7xxTMx-(G)
BIOS 1.07.29
Microcode Update to 0xCA

I don't know if those updates have anything to do Undervolting; I don't have more detailed changelogs.
It will take a few weeks before we start testing these update on P9xx and P7xx series (We don't carry NB70TH).


Info about Microcode Update via Windows Update

The main reason why you have been relatively safe from getting automatic Microcode updates via Windows Update might be a lack on WU CHID management in this ODM/LOEM Whitelabel eco-system.
Microsoft can only target drivers and firmware updates on your system if it has permission from the system vendor. Your system can only be identified if certain SMBIOS DMI strings are known.

CHID = Computer Hardware ID

Example:
{22c8188f-30b7-559b-afd2-b77ca7b21d1c} <- Manufacturer + Baseboard Manufacturer + Baseboard Product

The "Manufacturer" string is the one that is read as "System Manufacturer" in HWiNFO64.
Microsoft's CHID management does not allow any CHID idendities that does not include this string.

Consequently, if you have a custom Manufacturer string on your system (from your seller) and if this string has *not* been submitted to the ODM or to Microsoft for WU CHID management, Microsoft won't be able to target your system with platform-dependent drivers and firmware through Windows Update.

At least, this is according to my only moderately well-informed understanding. Exceptions might apply.

By the way, those strings can be easily overwritten by end-users with recent Clevo system with Insyde BIOS if you have access to the EFI Tool called "H2OSDE-Sx64.efi". Typical parameters are:
-SM = System Manufacturer
-SP = System Product
-BM = Baseboard Manufacturer
-SS = System Serial Number
-CA = Chassis Asset Tag

Code Example:
H2OSDE-Sx64.efi -SM "Example Company" -SP "Example Product" -SS 123456789

Tools for other BIOS platforms exist with different names but similar structure.
But beware, some of the strings can be overwritten again by future BIOS updates, depending on system vendor and model. In such cases, you would need to run the DMI Edit Tool again after the BIOS update to customize your strings.


Undervolting Overview across 2019 and 2020 models

For more information on our Undervolting efforts, check out this thread in our sub-reddit:
https://www.reddit.com/r/XMG_gg/comments/h0wuoh/cpu_undervolting_in_bios_setup_for_xmg_and/

We also opened another thread with a Benchmark comparison of -50mV Undervolting on 10th Gen Comet Lake i7-10875H - check it out:
https://www.reddit.com/r/XMG_gg/comments/hivmj7/insights_undervolting_on_comet_lake_10th_gen/

The end of the each thread includes a link to a survey ( Undervolting Community Feedback on Google Forms) where we would like to gain some additional market insights. Feel free to fill out, even on the off chance that you don't have any idea about Undervolting.

Cheers,
Tom

 

What about the PC50 series?

 

We have enabled BIOS Undervolting in the PC50 series (KEY 15 in our brand, see KEY 15 launch thread on Reddit) as a customization. I don't see future microcode updates for PC50Dx on any roadmap yet, but who knows what's gonna happen in the future. We don't want to put too much pressure on our contacts, but we will monitor the situation and test each new future BIOS and Microcode update to make sure it still supports our Undervolting implementation before we release it.

The 3 updates from my earlier post were all for Coffee Lake and might be unrelated to Undervolting.

Cheers,
Tom

 

These microcodes address intel security mitigation issues. Unfortunately, anything "C6" and newer have a performance hit even if you have all security migitation settings disabled in the registry/inspectre etc and even on old versions of windows that are not mitigation aware.. ( https://support.microsoft.com/en-us...ive-execution-side-channel-vulnerabilities-in )

As far as I know, blocking undervolting has nothing to do with microcode anything but with disabling an XTU setting in hidden menus in the BIOS (which is why it can be re-enabled on MSI laptops).

 

Looks like the HP Pavilion 16.1 is a no go for undervolting (at 3:20):

 

Thanks.

Bump.

 

I don't know about the HP 15.1 anymore, but you can enable undervolting on the XPS 9500 and 9700.

 

I was redirected here from the previous thread.
My laptop is a Mi Notebook 14(alt. Redmibook 14 in other markets) and there is no way to adjust the voltage levels of the chip in the BIOS or via apps like XTU/ThrottleShop.

My model runs on the Core i3 10110U, but the same model is also available with a Core i5 10210U which should be locked aswell.

@Papusan