XTU Version required for overclocking Z420 on Win 10?

[uberck2020]

Brian thank you so much for chipping in. Yes this seems to be a compatibility problem between XTU and the version of Windows it's running on, not a hardware issue.

Brian, can you please boot a copy of Win 10 Pro v2004 on your system and try to get XTU running stable?

Balthxzar, v2004 is already out, just MS is taking it's time to push to our systems. You can still get to 2004 if it's not showing up in windows updates by manually installing through the free media creation tool on Microsoft's website. Can you please update to 2004, and let us know if XTU is working and what version please?

Edit: here's the direct link to the tool:

Windows 10 2004 Media Creation Tool 

Also, I went back and checked my earlier posts, I tested v 5.2.0.14 on Win 10 1909, that was a no go. If someone gets it working on a fresh copy of 2004 64bit, then it might have something to do with my current configuration, and it'll help me narrow down the issue:

[Balthxzar]

I'll try spinning up 2004 over the weekend, my z420 is my work computer and I can't afford it down over the week,

I'll let you know if I get XTU working 

[DGroves]

due to the number of msg's between both you, you might want to consider using a "PM"  (personal email) email exchange

[Balthxzar]

Hi, I'd rather go through this on here, that way, in future others can follow the steps and solutions covered,

Thanks

[Diamantius]

I can confirm that after updating to W10 2004, no OC is applied to the CPU, even though the clock table has been updated by XTU and even CPU-Z sees it.
For instance, here's my 1650v2, previously happily running @ 4,2GHz on all cores with default vcore, now limited at 3,6Ghz. 

[Balthxzar]

Hi Diamantius, thanks for joining the conversation, 

thanks for confirming that Windows 10 2004 breaks the overclocking in XTU, is this from a fresh install of XTU or just the existing version? have you tried any other software to get the higher multipliers to load? (back around 1809 I needed to use throttlestop to load the multipliers)

thanks,

Charles.

[Diamantius]

It simply stopped working post-update. I was also using Throttlestop along with XTU and it worked fine, but not anymore. Throttlestop can read the increased multipliers that XTU sets, but the CPU ignores them.  There are several reports for this issue online, some say that it is due to the microcode update in 2004, e.g.:https://linustechtips.com/main/topic/1218505-windows-10-2004-update-locking-cpu-clock-speed/

But I don't really see how we can get out of this at the moment.

P.S. Latest XTU doesn't work for me either, I get the same .NET error when trying to launch it. 

[Balthxzar]

It looks like that issue was eventually resolved, by re-doing the XTU settings, I'd recommend loading the default clock profile, uninstalling XTU, clearing the registry and then re-installing XTU and applying your OC profile again, I had this issue when switching from version to version.

thanks,

Charles 

[Diamantius]

Thanks for replying, Charles. After doing that more than 10 times in a row, I eventually gave up 😞

[uberck2020]

Hey Diamantius,

Thanks so much for chipping in, I figured this was a software compatibility issue related to Windows 10.

I tried posting on the Intel forums a few months back, but the response I got was that IvyBridgeE was never supported by XTU, which I knew was bogus, so I stopped bothering asking there as it was no help and I didn't want to waste my time.

I probably should have pushed the issue more there, but didn't want to repost all the stuff I posted here and explain everything again lol.

Pretty sure this will fall on the Intel developers if it ever gets looked at, just not sure if we'll ever see a fix, as the v2 series is like 5 generations old now, not to mention AMD is crushing Intel in the consumer segment right now . Its still listed in the latest XTU release doc, so I've got my fingers crossed.

Which version do you have at least running without the .NET error?

Thanks again.

-Christos

My device info: