Throttlestop не работает андервольтинг

ThrottleStop undervolting isn’t changing anything

LunaticEyes

Processor	Core i7-9750H
Motherboard	Dell 01RGT1
Memory	2x4GB DDR4 2666 MHz
Video Card(s)	Intel(R) UHD Graphics 630 + GTX 1660 ti Max-Q
Storage	PC SN520 NVMe WDC 128GB + WDC WD10SPZX-75Z10T3 1TB

I’ve bought a Dell G3-3590-A30P and I’m suffering from thermal throttle (as everyone else, it seems). I tried to undervolt my processor using ThrottleStop and Intel XTU, but none of them worked.

ThrottleStop let me change the values, but the offset shown in the table doesn’t change, alongside the temperature hitting 100°C (212°F). When trying to use XTU, the voltage offset is greyed out:

CPU: Core i7-9750H
RAM: 8GB DDR4 2666 MHz
Motherboard: Dell 01RGT1 (laptop)
GPU (onboard): Intel(R) UHD Graphics 630
Driver: 25.20.100.6617
GPU (dedicated): GTX 1660 ti Max-Q
Driver: 26.21.14.4219
Laptop Model: Dell G3-3590-A30P
System BIOS: 1.9.2
OS Build/Version (dual boot): Windows 10 Home Single Language Version 10.0.18363 + Ubuntu 18.04.4 LTS (I hardly ever use it though)

Any ideas of what I should do?

unclewebb

ThrottleStop & RealTemp Author

BIOS updates are being released, likely by all manufacturers, that will block under volting. Do a Google search for Plundervolt if you want to find out more about this issue. Here is the reason why Intel has decided to do this.

INTEL-SA-00289

This fix has also disabled the adjustable Turbo Ratio Limits. You used to be able to lower those to control heat but not any more.

If you can go back to a previous BIOS version, you might be able to get under volting and adjustable turbo ratios back.

There are going to be a lot of unhappy laptop owners in the near future.

LunaticEyes

Processor	Core i7-9750H
Motherboard	Dell 01RGT1
Memory	2x4GB DDR4 2666 MHz
Video Card(s)	Intel(R) UHD Graphics 630 + GTX 1660 ti Max-Q
Storage	PC SN520 NVMe WDC 128GB + WDC WD10SPZX-75Z10T3 1TB

BIOS updates are being released, likely by all manufacturers, that will block under volting. Do a Google search for Plundervolt if you want to find out more about this issue. Here is the reason why Intel has decided to do this.

INTEL-SA-00289

This fix has also disabled the adjustable Turbo Ratio Limits. You used to be able to lower those to control heat but not any more.

If you can go back to a previous BIOS version, you might be able to get under volting and adjustable turbo ratios back.

There are going to be a lot of unhappy laptop owners in the near future.

BikeHelmet

New Member

I don’t understand why they don’t just add an auto-tuner? Click a button and let it find the limits, then they note that level and enforce staying comfortably back from it. You could probably still let most people shave off 40-80mv safely.

As is, factory tuning is now super important. Dell usually has way too many volts in their slim and light models, so they’re going to be more overheat-prone going forward.

basco

System Name	ibuytheusedstuff
Processor	5960x
Motherboard	x99 sabertooth
Cooling	old socket775 cooler
Memory	32 Viper
Video Card(s)	1080ti on morpheus 1
Storage	raptors+ssd
Display(s)	acer 120hz
Case	open bench
Audio Device(s)	onb
Power Supply	antec 1200 moar power
Mouse	mx 518
Keyboard	roccat arvo

unclewebb

ThrottleStop & RealTemp Author

@basco — Desktop computers allow voltage control in the BIOS. Most laptops do not have this option. Laptops only have voltage control by using software like Intel XTU or ThrottleStop.

It is software voltage control that is coming to an end. Either a BIOS update or a Windows Update only needs to set a single bit within the CPU to block voltage control. HP and Dell have already started releasing BIOS updates with this fix.

basco

System Name	ibuytheusedstuff
Processor	5960x
Motherboard	x99 sabertooth
Cooling	old socket775 cooler
Memory	32 Viper
Video Card(s)	1080ti on morpheus 1
Storage	raptors+ssd
Display(s)	acer 120hz
Case	open bench
Audio Device(s)	onb
Power Supply	antec 1200 moar power
Mouse	mx 518
Keyboard	roccat arvo

Thank you very much Mr. unclewebb for explaining this to me!

and a big thanks for your time + effort on throttlestop !

if ya need new hardware for testing shoot me a pm- i mean it

Tadas

New Member

It’s just waiting for a new update win ?
there is no solution ?

DELL G3 3590 i5 9300h

unclewebb

ThrottleStop & RealTemp Author

It was an Intel microcode update that has blocked under volting. The feature that allowed a person to change the CPU voltage while in Windows is not coming back.

If you have lost the ability to under volt your CPU, the only possible solution is to install the previous BIOS version, look in the BIOS for the option to reset the BIOS to default settings and then boot up and block any future BIOS updates.

Do a Google search for Dell G3 3590 and voltage and you will probably find a forum where users have either had success doing this on your laptop model or users that have not been able to go back. For some laptops, there has been no going back.

Tai Le

New Member

BIOS updates are being released, likely by all manufacturers, that will block under volting. Do a Google search for Plundervolt if you want to find out more about this issue. Here is the reason why Intel has decided to do this.

INTEL-SA-00289

This fix has also disabled the adjustable Turbo Ratio Limits. You used to be able to lower those to control heat but not any more.

If you can go back to a previous BIOS version, you might be able to get under volting and adjustable turbo ratios back.

There are going to be a lot of unhappy laptop owners in the near future.

Источник

Cannot undervolt with either ThrottleStop or Intel XTU

marc_oc

New Member

Hi, I had been using ThrottleStop for some time to undervolt my laptop’s CPU to reduce its temperature, but some time ago I noticed that ThrottleStop had a strange behaviour it did not have before.
— When going to the FIVR menu the Turbo ratio limits are greyed out and can’t be changed
— Changing the offset voltage for the CPU or the cache seems to have no effect
— The set multiplier option doesn’t show the turbo frequencies
— As soon as ThrottleStop launches, my CPU doesn’t go over 2.2 GHz (Base clock), even after closing ThrottleStop
— If I open ThrottleStop again, it shows that the current frequency is 0.00 MHz

Thinking that a windows update might have stopped ThrottleStop from working I tried to download Intel XTU. But when I launch XTU I get the following error:
«Unable to start Intel XTU. If there is another performance tuning application running, you must close it before trying to start this application».

I saw that some people had issues with a microcode update disabling undervolting capabilities, but my laptop shouldn’t be affected as it uses a Broadwell CPU. Since I am running the insider preview of Windows 10 I tried to create a Windows To Go USB drive with an older version of Windows, and ThrottleStop seems to be working properly on the older version. This makes me think that there might be a bug with the preview build of windows, but I looked around and I didn’t see anyone report any issues recently, so I am not sure if that is the problem.

Has anyone had an issue similar to this and have you been able to fix it if that is the case? If it’s of any help I can provide the logs that intel XTU generates when I try to launch it.

My laptop is a Lenovo Thinkpad X250 with a Core i5-5200u running the 19619 Insider Preview build of Windows 10.

unclewebb

ThrottleStop & RealTemp Author

ThrottleStop does not work correctly on many of the Windows 10 Insider Preview builds. Microsoft would like to block it from running. When an official version of Windows 10 is released, they count up the complaints, change their mind at the last minute and allow ThrottleStop to run after all.

ThrottleStop runs on the latest official Windows 10 1909 Build 18363. Will have to wait and see if it continues to work on the next official version 2004 Build 19041.

marc_oc

New Member

Yeah, thats what I figured, I guess we will have to wait until the official release of the update.

Thanks for answering!

unclewebb

ThrottleStop & RealTemp Author

Another user had this same problem recently while running the latest Windows 10 Insider Preview version. He found that the new Windows Subsystem for Linux (WSL) feature was the problem. This uses a VM which prevents ThrottleStop and Intel XTU from accessing your CPU registers. XTU does not start up and ThrottleStop does not work correctly. He was not even using this feature but it was still active. Disabling WSL solved his problem.

marc_oc

New Member

Max(IT)

Processor	Ryzen 7 5900X
Motherboard	Asus ROG Strix B550-F Gaming
Cooling	Arctic Freezer II 360
Memory	32 Gb G.Skill TridentZ RGB 3600CL16
Video Card(s)	EVGA RTX 3080 FTW3 Ultra
Storage	1 Tb Samsung 970 EVO NVMe + 1 Tb SSD WD Blue
Display(s)	Asus TUF Gaming VG27AQL1A + Samsung C24RG50
Case	Corsair 5000D Airflow
Power Supply	EVGA G3 750W
Mouse	Razer Basilisk
Keyboard	Razer Huntsman Elite
Benchmark Scores	3dMark TimeSpy — 17050 Cinebench R20 — 638/8955

unclewebb

ThrottleStop & RealTemp Author

Not sure if WSL 2 and ThrottleStop will ever be compatible. ThrottleStop and Intel XTU need direct access to the CPU’s registers. That is why ThrottleStop does not work in a VM.

Max(IT)

Processor	Ryzen 7 5900X
Motherboard	Asus ROG Strix B550-F Gaming
Cooling	Arctic Freezer II 360
Memory	32 Gb G.Skill TridentZ RGB 3600CL16
Video Card(s)	EVGA RTX 3080 FTW3 Ultra
Storage	1 Tb Samsung 970 EVO NVMe + 1 Tb SSD WD Blue
Display(s)	Asus TUF Gaming VG27AQL1A + Samsung C24RG50
Case	Corsair 5000D Airflow
Power Supply	EVGA G3 750W
Mouse	Razer Basilisk
Keyboard	Razer Huntsman Elite
Benchmark Scores	3dMark TimeSpy — 17050 Cinebench R20 — 638/8955

unclewebb

ThrottleStop & RealTemp Author

I use Sledgehammer to manage Windows Update. It gives users a chance to look at an update so they can decide if they want to install it or not.

bodayw

New Member

Hi, just registered in order to post here.

I would like to add that ThrottleStop is still not working on the «stable» release of Windows 10 2004 build 19041.264. Basically the issues are the same with OP: turbo ratio limits cannot be changed, undervolting has no effect etc.

I’m on a Surface Pro 7 with a i5-1035G4. When I was testing ThrottleStop on Windows 1903 yesterday it worked just fine.

Strangely, none of these are enabled in Windows Features on my machine: Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux.

unclewebb

ThrottleStop & RealTemp Author

Windows 10 2004 includes firmware (BIOS) updates for some computers. After the update, CPU voltage control and turbo ratio adjustments will be locked.

ThrottleStop is not the problem. It is your BIOS that has locked your CPU. Going back to 1903 will not help. You can try going back to the previous BIOS version but Microsoft usually locks going back.

bodayw

New Member

Windows 10 2004 includes firmware (BIOS) updates for some computers. After the update, CPU voltage control and turbo ratio adjustments will be locked.

ThrottleStop is not the problem. It is your BIOS that has locked your CPU. Going back to 1903 will not help. You can try going back to the previous BIOS version but Microsoft usually locks going back.

Right. I’m aware that there are some BIOS updates recently locking down CPU voltage control from a few brands, but didn’t think that could be the case for me.

Feels like undervolting has become too popular such that they started to take actions against us now?

Anyway thanks for the quick reply. Have been always appreciate your work.

unclewebb

ThrottleStop & RealTemp Author

Intel released a microcode update last December which blocks CPU voltage and turbo ratio adjustments. It is not about the popularity of under volting. Intel is trying to prevent Plundervolt security hacks.

INTEL-SA-00289

bodayw

New Member

Max(IT)

Processor	Ryzen 7 5900X
Motherboard	Asus ROG Strix B550-F Gaming
Cooling	Arctic Freezer II 360
Memory	32 Gb G.Skill TridentZ RGB 3600CL16
Video Card(s)	EVGA RTX 3080 FTW3 Ultra
Storage	1 Tb Samsung 970 EVO NVMe + 1 Tb SSD WD Blue
Display(s)	Asus TUF Gaming VG27AQL1A + Samsung C24RG50
Case	Corsair 5000D Airflow
Power Supply	EVGA G3 750W
Mouse	Razer Basilisk
Keyboard	Razer Huntsman Elite
Benchmark Scores	3dMark TimeSpy — 17050 Cinebench R20 — 638/8955

I use Sledgehammer to manage Windows Update. It gives users a chance to look at an update so they can decide if they want to install it or not.

garyliu

New Member

Hi, just registered in order to post here.

I would like to add that ThrottleStop is still not working on the «stable» release of Windows 10 2004 build 19041.264. Basically the issues are the same with OP: turbo ratio limits cannot be changed, undervolting has no effect etc.

I’m on a Surface Pro 7 with a i5-1035G4. When I was testing ThrottleStop on Windows 1903 yesterday it worked just fine.

Strangely, none of these are enabled in Windows Features on my machine: Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux.

Assimilator

Intel released a microcode update last December which blocks CPU voltage and turbo ratio adjustments. It is not about the popularity of under volting. Intel is trying to prevent Plundervolt security hacks.

INTEL-SA-00289

Does this mean that Throttlestop is basically dead on systems with Thunderbolt?

edit: disregard my nonsense

Max(IT)

Processor	Ryzen 7 5900X
Motherboard	Asus ROG Strix B550-F Gaming
Cooling	Arctic Freezer II 360
Memory	32 Gb G.Skill TridentZ RGB 3600CL16
Video Card(s)	EVGA RTX 3080 FTW3 Ultra
Storage	1 Tb Samsung 970 EVO NVMe + 1 Tb SSD WD Blue
Display(s)	Asus TUF Gaming VG27AQL1A + Samsung C24RG50
Case	Corsair 5000D Airflow
Power Supply	EVGA G3 750W
Mouse	Razer Basilisk
Keyboard	Razer Huntsman Elite
Benchmark Scores	3dMark TimeSpy — 17050 Cinebench R20 — 638/8955

Assimilator

You’re 100% right, thanks for the correction. So many bloody vulnerabilities with people trying to give them cool-sounding names that it all gets very confusing.

I guess my question is to @unclewebb — where to from here for ThrottleStop? If undervolting is going to be locked down for more and more people due to BIOS updates and Hyper-V and WSL and and and. are you still going to continue to support and develop this software? Particularly when most of that support is likely to be answering repeated «why doesn’t ThrottleStop work on my machine» questions like this one?

Max(IT)

Processor	Ryzen 7 5900X
Motherboard	Asus ROG Strix B550-F Gaming
Cooling	Arctic Freezer II 360
Memory	32 Gb G.Skill TridentZ RGB 3600CL16
Video Card(s)	EVGA RTX 3080 FTW3 Ultra
Storage	1 Tb Samsung 970 EVO NVMe + 1 Tb SSD WD Blue
Display(s)	Asus TUF Gaming VG27AQL1A + Samsung C24RG50
Case	Corsair 5000D Airflow
Power Supply	EVGA G3 750W
Mouse	Razer Basilisk
Keyboard	Razer Huntsman Elite
Benchmark Scores	3dMark TimeSpy — 17050 Cinebench R20 — 638/8955

You’re 100% right, thanks for the correction. So many bloody vulnerabilities with people trying to give them cool-sounding names that it all gets very confusing.

I guess my question is to @unclewebb — where to from here for ThrottleStop? If undervolting is going to be locked down for more and more people due to BIOS updates and Hyper-V and WSL and and and. are you still going to continue to support and develop this software? Particularly when most of that support is likely to be answering repeated «why doesn’t ThrottleStop work on my machine» questions like this one?

unclewebb

ThrottleStop & RealTemp Author

What recent update? What version of Windows are you using? Other users are running ThrottleStop in Windows 10 2004. The only known issue at the moment is the Disable and Lock Turbo Power Limits feature might not work in Windows 10 2004.

Did you unzip the ThrottleStop folder? Did you try right clicking on ThrottleStop.exe and selecting the Run as administrator menu option?

SnakeX

New Member

I face an issue with ThrottleStop after Windows update, version 2004, that cause BSOD with error PAGE_FAULT_IN_NONPAGED_AREA. This blog refers that this is because «Disable and Lock Turbo Power Limits» (RwDrv.sys) is checked, as unclewebb mentioned, which really seems to be the reason in my case. Strangely, this happens randomly to me whenever I run ThrottleStop with RwDrv.sys enabled. I mean at a first-run of throttlestop I will get the BSOD and then after two BSOD restarts, it will work just fine even with RwDrv.sys enabled. However, I will always get BSOD whenever I make ThrottleStop scheduled to run at windows start, thus, I had to run it manually now.

I have checked the undervolting and the other settings on those random cases where ThrottleStop works without BSOD, it works fine and everything was set according to HWiNFO64.

Following some suggestions, I have set virtual-ram/automatic-paging to no paging at all, so far, it works but not sure if it is really effective.

I have Dell XPS 9550 with i7-6700HQ, 16GB RAM

TheNetAvenger

New Member

Windows 10 2004 includes firmware (BIOS) updates for some computers. After the update, CPU voltage control and turbo ratio adjustments will be locked.

ThrottleStop is not the problem. It is your BIOS that has locked your CPU. Going back to 1903 will not help. You can try going back to the previous BIOS version but Microsoft usually locks going back.

Neither of these statements are entirely accurate.

BIOS updates are from the OEM, not Microsoft, and they must conform to the UEFI BIOS updating mechanisms. Even in this tightly integrated update method, rolling back a previous BIOS is a ‘requirement’ by Microsoft, and can often be down through rolling back the System Firmware Bios version Device Manager. Microsoft is fun to blame for crap, but this is one thing they get right, and try to enforce properly. (Locking and UEFI locks are something Microsoft doesn’t like — so much that it is easier to unlock a Microsoft Surface Laptop/Tablet and install Linux than it is to ‘unlock’ most Chromebooks.

OEMs can lock BIOS regression, but this is a pre-UEFI BIOS lock. However, even tightly locked BIOS (notebooks) often have a BIOS option allowing for BIOS downgrades. (Due to enterprise sales and customer requirements.)

-Windows 2004 works just fine with Throttlestop and XTU.

The last thing to mention here, is that many times users THINK a BIOS or OS update has locked their system from using XTU or ThrottleStop. 99% of the time these are not locked, and instead the BIOS needs to be retrained to identify the microcode and control firmware changes properly. Thus, these features will remain locked for stability reasons. This is often fixed with a simple: (‘Load System Defaults’) in the BIOS (NOT BIOS Defaults)

For example there is a Dell G7 brand of notebook, and the ‘rumor’ is that all later BIOS updates lock ThrottleStop and XTU from undervolting. However, the functionality NEVER changed. This isn’t true, as the latest June 2020 1.13 BIOS works just fine with XTU and ThrottleStop.

The reason changing to an older BIOS ‘seems’ to work, is that users rollback will do a ‘Load System Defaults’ when rolling back — or the rollback process of the BIOS itself runs the retrain boot feature. This also requires the current Windows EFI boot be selected as the retrain/boot information is added to that boot loader’s EFI. (So if you have Dual Windows Installs for testing, ‘Load System Defaults’ when booting (after the Windows Boot Manager Selection Screen)

The option is usually ‘Load System Defaults’ -as BIOS defaults just loads settings but does not force any hardware retraining. If the BIOS doesn’t seem to retrain, there is often a Power Button combination (Hold Power Button 45 Seconds) that will force the retraining — see OEM manuals. Ultimately, the user can also pull the CMOS and/or system battery for 30 seconds, this will force a full RAM and CPU/Microcode/Boot/Firmware/UEFI retraining.

I didn’t want to dig this thread back up, but if I can add even one bit of information that helps someone, I think it is worth it.

Источник