After a Windows 10 Update Today Overclocking is lost. WTF Microsoft and Intel???

[agent_x007]

High Performance plan can be set to "0" for minimum CPU clock.

Plan itself also doesn't "switch off" idle CPU states.
Even on it, my CPU Vcore can go lower than 1V (according to CPU-z).

Settings of plan can be changed in it's options, and switching between plans is a simple left click in Control Panel/Power Options (where you can create your own plan, if you want).

I'm really not 100% conviced this OC lock is only that... a power plan "snafu".

 

[Deleted member 50521]

Plus people would want their CPU to idle down in between work sessions for power saving. Why should I set it to high performance mode to keep CPU 100% when it works perfectly in power saving mode before?

 

[biffzinker]

You shouldn't need a high performance power plan to OC. If you do that you throw idle power saving features out the window. Most of us probably don't want our over clocked chips running north of 5GHz 24/7. Smells like a bug to me if that is indeed the case.

Intel's recent chips drop down to the supported C-states irrelevant to Windows power plan.

 

[cadaveca]

Plus people would want their CPU to idle down in between work sessions for power saving. Why should I set it to high performance mode to keep CPU 100% when it works perfectly in power saving mode before?

Read the post above your last one. Set "o" as the plan minimum and the clocks will drop, as well as voltage? Also, I thought that power-saving mode was only for laptops...? Power Saver mode specifically states that it reduces CPU performance to save power as much as possible...?

So if you've got the right windows options here.. then this is much ado about nothing?

If you ask me, sounds like the windows update actually fixed things to be the way they were supposed to be, and before, Windows was broken, but people got used to it. Makes for one hell of a hilarious story that went all over.

 

[MrGenius]

Well, that's ignoring the sub-topic of the thread. Which is the performance loss attributable to the forced microcode update. Which requires a bit more of a workaround to "fix" than the overclocking thing(evidently). So it might also be about how you define "broken". Your definition might not match mine.

 

[Deleted member 50521]

OK to clarify I reinstalled the freaking update. Then no matter what ever power options I set in UEFI the overclocking is not applied. So as far as this is concerned, the causation is crystal clear:

Microcode conflict between OS and UEFI WILL cause the loss of overclocking.

Now I am going to uninstall that freaking update and hopefully I am not going into a BSOD loop again. All for the sake of satisfying @cadaveca curiosity

 

[biffzinker]

@xkm1948 The update applied by the OS overwrites the EFI microcode update on the CPU. No conflict can occur.

 

[Deleted member 50521]

@xkm1948 The update applied by the OS overwrites the EFI microcode update on the CPU. No conflict can occur.

No. Check my post before. Even after the update my UEFL microcode remains the 2A version

 

[lexluthermiester]

Nehalem and chips on lga1366 seem hit the worst, which makes sense I suppose.

Can anyone confirm this?

 

[cadaveca]

No. Check my post before. Even after the update my UEFL microcode remains the 2A version

What he is saying is that the OS microcode supercedes the one from the BIOS when the OS is active. It shouldn't matter what's in the BIOS... yet seemingly in some situations it does? No idea. This is a very interesting situation.

 

[MrGenius]

Essentially, yes. However...

The update applied by the OS overwrites the EFI microcode update on the CPU.

No. It does not.

1. If the microcode in the BIOS/UEFI has been updated for the Spectre vulnerability the microcode update in the OS does not apply. The purpose of the OS microcode update is to widely distribute the mitigation for Spectre. As BIOS updates to deal with it are not being widely distributed. Too many CPUs, too many motherboards. That's the "problem" it's intended to solve. So you don't need a BIOS update now. You just need this Windows update(in theory anyway).

2. The OS, once booted, loads the microcode from the file in System32(if necessary for Spectre mitigation). Overriding(overwrite is bad terminology) the microcode loaded by the motherboard BIOS/UEFI. The microcode is not permanently stored/written on the CPU. It disappears when the CPU is powered off.

 

[kastriot]

You should publish book based on this thread..

 

[Candor]

So I heard that the microcode updates will be integrated within the Windows 10 October Update, creating another shitstorm for broadwell-e users.

This means there will be no KB update to remove or block.

So I suppose replacing the dll with an earlier version will be the only fix then?

 

[hat]

So I heard that the microcode updates will be integrated within the Windows 10 October Update, creating another shitstorm for broadwell-e users.

This means there will be no KB update to remove or block.

So I suppose replacing the dll with an earlier version will be the only fix then?

Sounds about right... unless it's "fixed" better in the October update.

 

[Deleted member 50521]

I am blocking all new Windows 10 updates now. Seriously considering going Linux main now

 

[Gripen90]

So I heard that the microcode updates will be integrated within the Windows 10 October Update, creating another shitstorm for broadwell-e users.

This means there will be no KB update to remove or block.

So I suppose replacing the dll with an earlier version will be the only fix then?

If that happens I'll get hold on a Core i7 5960X instead and sell my Core i7 6900K.

 

[Candor]

Some people have installed Windows 10 (1809) Build 17763.1 - considered to be RTM.

Microcode updates integrated within the Windows 10 October Update seems confirmed at this stage.

Using InSpectre tool to disable spectre and meltdown protections does not fix the issue.

Replacing "mcupdate_genuineintel.dll" with version prior to Sept 2018 does work.

 

[adamwzl]

Update to my post earlier, just uninstalling the KB update does not fix the crashing. Just lost over 400 SR in Overwatch troubleshooting this problem. Had to revert back to a August snapshot for my machine to get rid of all the problems. Microsoft is seriously getting lazy with it's testing.

 

[FreedomEclipse]

This update has also bugged out Microsoft Security Center -- It keeps telling me that my kaspersky firewall is disabled when it clearly is not.

 

[Sawyer86]

Hi everyone, with windows 1803 version i have solved this overlock issue by uninstalling the update kz100347 and hidding this one from windows update using Wrapper Script.
Today windows updated to 1809 october and the overclock issue is back.
I have i7 6900k 4.4ghz (100x44) asus x99 deluxe II. Now im back to 100x37@3700mhz...
In this case i cannot uninstall kz100347. So i don't know how i can return to my overclock.
Can you please help me? Tnx

 

[MrGenius]

Hi everyone, with windows 1803 version i have solved this overlock issue by uninstalling the update kz100347 and hidding this one from windows update using Wrapper Script.
Today windows updated to 1809 october and the overclock issue is back.
I have i7 6900k 4.4ghz (100x44) asus x99 deluxe II. Now im back to 100x37@3700mhz...
In this case i cannot uninstall kz100347. So i don't know how i can return to my overclock.
Can you please help me? Tnx

Read the thread. It's only 9 pages. The answer's in there. Hell...the answer's 3 posts above yours actually. The dll you need is towards the beginning. Page 2 or 3 IIRC...

Edit: Yep. Page 2. This post here.

 

[Deleted member 50521]

I am blocking Windows 10 updates so someone brave need to try the new 1809 update and report the results for all of us.

 

[hat]

Upon updating to 1809*

*Not to be taken seriously. I haven't even received 1809 yet.

 

[MrGenius]

My Windows 10 rig is down ATM. Mobo died(or rather got killed by me ) the day before I was going to upgrade to 1809. I should have it up and running again in about a week.

 

[Gripen90]

Read the thread. It's only 9 pages. The answer's in there. Hell...the answer's 3 posts above yours actually. The dll you need is towards the beginning. Page 2 or 3 IIRC...

Edit: Yep. Page 2. This post here.

The new 1809 update borks it
I tried it with the new build and replacing the dll just screws up the whole boot with no boot at all. I had to replace it with the original 1809 update again to get windows started again.