Intel Extreme suddenly won't overclock

[Aashishkebab]

I have Dell XPS 9575 with the i7-8705g. Up until recently, I was easily able to overclock and undervolt inside Intel Extreme Tuning Utility.

However, I just reinstalled Windows. Now it says that "my platform doesn't support overclocking". I know this to be false because I was using the very same software to overclock and undervolt just a few weeks ago.

Anybody know what could cause this?

[AlHill]

XTU only supports X and K processors.  You have a G processor.  Your processor is not supported.

On the XTU download page, it tells you what processors are supported.  It also says " Intel XTU may or may not work on unsupported processors."

https://downloadcenter.intel.com/download/29183/Intel-Extreme-Tuning-Utility-Intel-XTU

Also, regarding undervolting"

https://securityboulevard.com/2019/12/plundervolt-a-new-intel-processor-undervolting-vulnerability/

Doc

[Aashishkebab]

I'm sorry but this is not true. The i7-8705g has a partially unlocked multiplier, and as I said in my post, I was previously able to overclock (up to 4.5 GHz) and was doing so for several years (I rarely went that high, but nonetheless it was an option).

[AlHill]

Do you see your processor in the list of supported processors?  The answer is no, therefore it is not supported.

Doc

[Aashishkebab]

Dude, as I said, *I have already overclocked it*. Or was I hallucinating for two years?

[AlHill]

And, Dude, as I have shown you in the documentation,  it says " Intel XTU may or may not work on unsupported processors.".

This is a case of NOT.  And, nothing is forever.

Good luck moving forward.

Doc

[n_scott_pearson]

My understanding is that, in response to Plundervolt, Intel has made changes to the microcode that alters or removes the capabilities for undervolting. You are not the only person who has lost a capability here, but Intel had no choice; vulnerabilities must be addressed.

Thus does Doc's "nothing is forever" get applied, unfortunately.

...S

[Aashishkebab]

So actually I got it to work. What I did was reset my BIOS to "Factory Settings", and somehow that fixed it, though I'm not sure why.