• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Undervolt not applying

J

Jace

New Member
Joined
Mar 29, 2020
Messages
5 (0.00/day)
Ever since I got my laptop (a Dell G5) i've been using throttlestop to undervolt it, and it's been working like a charm. However, yesterday the undervolt just suddenly disappeared. I've tried resetting it, redownloading throttlestop, restarting the laptop, etc. None of that worked. Any help?
1585483884576.png
1585483844041.png
 
i think unclewebb said there are microcode updates from microsoft over win update that prevents any form of oc or uv.

www.techpowerup.com

ThrottleStop not working

I have an i7 7700HQ and ThrottleStop just won't work. Undervolt not applying, Turbo Power Limit option greyed out, CPU speed capped to 2.8GHz. I have the 2020 Beta version. Help.
www.techpowerup.com www.techpowerup.com
 
basco said:
i think unclewebb said there are microcode updates from microsoft over win update that prevents any form of oc or uv.

www.techpowerup.com

ThrottleStop not working

I have an i7 7700HQ and ThrottleStop just won't work. Undervolt not applying, Turbo Power Limit option greyed out, CPU speed capped to 2.8GHz. I have the 2020 Beta version. Help.
www.techpowerup.com www.techpowerup.com
Click to expand...
should i revert the update then? I do remember having to update yesterday morning
 
yes if its possible
there will be no way back to overclock with these updates
we are talking bout win10?

but you could talk to @unclewebb he is the good men behind throttlestop
 
i have been trying resolve this same issue with my dell which i had for 5 days.

The day it was delivered i installed throttlestop and undervolted verified everything working as it supposed to be.

Than yesterday my fans were going crazy i checked and the offsets were stuck on 0.000 i had no clue about the the microcode changes etc if i had i would of disabled the windows updates somehow.

I also learnt that windows update can update the bios too?

I was updated to microcode version 0xCA on bios version 1.3.0 ( dell update info states the intel patch of microcode security issue on this verion )

i managed to downgrade the bios to 1.2.1 which downgraded the microcode to version 0xC6 (checking the update logs it did not mention intel security issue hence it's from oct 2019)

i done factory reset of the bios settings etc.

Long story short It's still showing locked for fivr control.

I checked mcaupdate dll under system32 but i can't seem find any old backups of this prior the update.

I don't know if reinstalling windows this old version would work but i can't risk loosing my data.

So even downgrading the bios did not work for me. I gave up and just saw this thread sorry if i hijacked it but i will be following the progress
 
update: tried reverting the last update, did not fix it.

thats unfortunate geeuk, i guess we just wait for the future and see if future releases can help.
 
no, I havent messed with the bios at all, i'll give it a try right now.
 
Jace said:
no, I havent messed with the bios at all, i'll give it a try right now.
Click to expand...

If it allows you give it a try because sometimes it does not allow to downgrade however with my inspiron it did. After downgrading reset the bios settings to factory (you won't loose anything) and than try again.

If you do downgrade the bios to previous version let me which version of microcode it went down to mine went from CA to C6

Reason i ask that i didn't revert the update in windows. However i did use a bootable/live version of windows 10 that also had the fivr locked so i gave up.
 
Jace said:
downgrade did not fix it, and the microcode version went to AA
Click to expand...

I guess as you mentioned earlier we should leave to time.

Maybe someone can find a solution, i have searched on google and I can see many posts popping up specially on reddit with same issues as us.

Whatever update they have done it has been done in the last couple of days.
 
Last edited:
maybe its a dell specific update ?
 
I believe so because from my search everyone complaining were mainly dell users.
 
Nope, on Acer & with an insider build I've had the issue for at least 2-3 weeks. Not the first time Wintel have pulled this stunt, in the past they blocked non Z (boards) overclocking via this route multiple times heck I had bunch of machines BSOD because of that :nutkick:
 
Given that we have so much free time on our hands I might just take that as an option :laugh:
 
I believe the ME was updated and that it can't be reverted to an earlier version.
 
Caring1 said:
I believe the ME was updated and that it can't be reverted to an earlier version.
Click to expand...

100% correct i did see a warning when rewriting old bioses it kept showing a warning about me not changed.
 
After going back to the previous BIOS, did you go into the BIOS and select the Reset to defaults option? That has restored under volting for some users.
 
unclewebb said:
After going back to the previous BIOS, did you go into the BIOS and select the Reset to defaults option? That has restored under volting for some users.
Click to expand...

Yes I reset it to defaults after going back to version C6. I tried reinstalling windows 10 after the reset of the bios but still had the FIVR locked.
 
geeuk said:
but still had the FIVR locked.
Click to expand...
You might be out of luck. The only other thing I can think of is deleting the Windows microcode update file. It would be best to set a Windows restore point and save a back up copy of this file before you delete it.

C:\Windows\System32\mcupdate_GenuineIntel.dll

Caring1 said:
I believe the ME was updated and that it can't be reverted to an earlier version.
Click to expand...
This is going to be a bigger problem for users than I originally thought. Anyone that wants to avoid this problem should be using a tool like Sledgehammer so they can be in charge of what Windows Updates get installed on their computer.

www.ghacks.net

Control Windows Updates with Sledgehammer (formerly WUMT Wrapper Script) - gHacks Tech News

Windows Update Mini Tool Wrapper Script restored control over the update behavior. The tool's successor, Sledgehammer, is now available.
www.ghacks.net www.ghacks.net
 
unclewebb said:
The only other thing I can think of is deleting the Windows microcode update file.
Click to expand...

I did this after downgrading the bios with microcode C6 still did not work :(

I didn't delete it just renamed it..

I than downloadeded an older version of windows 10 (from nov 2019) disabled updates and run it via usb live boot just to test if that windows version would allow undervolting but it didn't also work.

Caring1 said:
I believe the ME was updated and that it can't be reverted to an earlier version.
Click to expand...

I think despite downgrading the bios the ME part of it is not actually being downgraded so that's why it's still staying locked?

Because when I downgraded i do recall seeing an error about ME failing.

Before posting i did hours worth of searching all your posts @unclewebb thanks for your advice and help.
 
Hey for people still having the undervoltiong locked for me i just got in the bios and reset to "factory settings" and it was back maybe it will help someone.
 
You must log in or register to reply here.
Back
Top