How turning off undervolting for just a moment?

[the_koal]

Hi, I have this question for a time and I haven't found nothing about it. So I would appreciate if someone could get me a little help.

Currently my FIVR control is with the voltage adjustment unlocked in order to have undervolt. Sometimes I want to brief turn off the offset changes, mainly to test if an application is not working as intend due to undervolting. I have tested and it seems if I just change profile, nothing happens. The offset is still applied even if the profile has the "Unlock Adjustable Voltage" unchecked with zero offset. If I'm not wrong the button "Turn On/Off" in the monitoring screen is legacy and do not actually turn off/on things, right?

What I usually do to get undervolt turned off is turning on Virtual Machine and Hypervision in Window's Features. I also use some android apps sometime, so turning on those features I know undervolt will not work.

Is there any another solution that I can just turn off/turn on undervolt in a easy way? ThrottleStop is set to start by Task Schedule when Windows initiates, so I'm considering just to disable the scheduled task and restart the system, but that is not too much practical.

 

[unclewebb]

The offset is still applied even if the profile has the "Unlock Adjustable Voltage" unchecked with zero offset.

Post a screenshot of the FIVR window that shows the problem. Are you looking at the FIVR monitoring table for voltage information? HWiNFO does not report any voltage changes in real time. After you make a voltage change with ThrottleStop, you have to exit HWiNFO and restart it so it updates the voltage information it displays.

 

[Bogus5]

I've also wondered about this once and maybe it would be enough to have two directories with the same version of TS in one with the ini file with changes, and in the other without changes and disable TS with changes and run unchanged (?).

 

[the_koal]

Post a screenshot of the FIVR window that shows the problem. Are you looking at the FIVR monitoring table for voltage information? HWiNFO does not report any voltage changes in real time. After you make a voltage change with ThrottleStop, you have to exit HWiNFO and restart it so it updates the voltage information it displays.

I'm not actually using HWiNFO to check the voltage, I see directly at the FIVR monitoring table.

Here is when the undervolt is applied and my daily profile in throttlestop.

Here is the another profile that tried to create to turn off undervolt.

If I let this screen with this profile selected, is the undervolt supposed to be turned off?

 

[unclewebb]

Use ThrottleStop 9.6

If you want to reset the voltages to zero, you have to check the Unlock Adjustable voltage box in every profile. It will only apply your zero voltages when the Unlock Adjustable Voltage box is checked.

When you switch to a profile and that box is not checked, ThrottleStop leaves the voltages as is and does not try to make any changes. That is not what you want.

 

[the_koal]

If you want to reset the voltages to zero, you have to check the Unlock Adjustable voltage box in every profile. It will only apply your zero voltages when the Unlock Adjustable Voltage box is checked.

Thank you for your help.

I let Unlock Adjustable voltage box in every profile checked, but there's one profile that the offset is set to 0. If I change to this one will be like undervolt is turned off?

Also, one last question. Is it possible to "stable" undervolt become "unstable" after some years? I had this offset voltage configured for more than two years and I things were stable. The only problem that I had were when I enable hybrid mode, which uses the iGPU. But usually I don't use hybrid mode and just use dGPU all the time. So I'm just using these values for a long time. But recently, I was playing Counter Strike 2 and I'm getting some freezes. I can't do nothing, only a forced shutdown to restart the system. I was thinking the culprit was the game itself, but I just got a freeze some minutes ago and I wasn't even gaming. Just basic tasks.

Bad undervolts can cause freezes? No BSODs, only total freezes.

 

[unclewebb]

Most 10750H are not 100% stable when the cache is set to -85 mV. Most similar CPUs start to lose stability at -70 mV. Not enough voltage can cause a BSOD or can cause a computer to freeze. Your voltage setting is not stable. Your CPU needs more voltage.

If I change to this one will be like undervolt is turned off?

Do some testing. Change profiles and watch the FIVR monitoring table to see if the voltage changes. If you checked Unlock Adjustable Voltage for every profile, this will work correctly.

 

[the_koal]

Do some testing. Change profiles and watch the FIVR monitoring table to see if the voltage changes. If you checked Unlock Adjustable Voltage for every profile, this will work correctly.

I think it worked. I changed the profile for "No Undervolt" and the offset in FIVR monitoring table stayed as 0.

Most 10750H are not 100% stable when the cache is set to -85 mV. Most similar CPUs start to lose stability at -70 mV. Not enough voltage can cause a BSOD or can cause a computer to freeze. Your voltage setting is not stable. Your CPU needs more voltage.

Thanks again for sharing your thoughts. Based on that knowledge, can I just increase cache in +5mv until gest stable or it's better to already aim to at least -70mv? As I told you, I haven't had problems with these voltages for around 2 years.

Also, increase voltage for only cache is enough or should do the same to core? Currently core is -85.9mv and cache -80.1mv

 

[unclewebb]

I think it worked.

What do you mean you think it worked?

the offset in FIVR monitoring table stayed as 0

You tested it and the FIVR monitoring table reported +0.0000 for offset voltage when switching to your No Undervolt profile. We can conclude that checking the Unlock Adjustable Voltage box for every profile 100%, absolutely, positively, definitely worked. Problem solved.

Most people think that if a computer does not crash that it is stable. That is not always true. When the voltage is slowly reduced, at some point, a CPU will start generating errors. Many errors are not serious enough to cause a computer to immediately crash. Over time, random Windows files or any file can become corrupted.

I prefer not to live on the edge of stability like this. I would use -70 mV for the cache like many other people are using. You can try using -75 mV. Run the TS Bench 960M test and see if it reports any errors. Even if your computer does not crash during this test, if any errors are reported, your CPU needs more voltage.

The cache offset is the important one. You can probably leave the core offset as is. Any errors or blue screens or freezes are signs that your CPU needs more voltage.

 

[the_koal]

What do you mean you think it worked?

I wasn't 100% sure but you just confirmed me now. The FIVR monitoring table shows what offset value is being used. I got it now.

I prefer not to live on the edge of stability like this. I would use -70 mV for the cache like many other people are using. You can try using -75 mV. Run the TS Bench 960M test and see if it reports any errors. Even if your computer does not crash during this test, if any errors are reported, your CPU needs more voltage.

Thanks a lot. I didn't know about that. These are valuable tips. I will do what you suggested to make sure I get real stability.

The cache offset is the important one. You can probably leave the core offset as is. Any errors or blue screens or freezes are signs that your CPU needs more voltage.

Thanks again!