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

[Freeze87]

Side note: You can also just delete the mcupdate_GenuineIntel.dll from System 32. It doesn't need to be there. The system will run just fine with the BIOS microcode. Albeit without Spectre protections(if the microcode in the BIOS hasn't been updated with said protections).

Deleted it. Can confirm: overclocking works again.

System:
x99 gaming
i7 6800k @ 4.0ghz again (undervolted)

Thank you very much

 

[rkt]

Overclocked my i7 6850k to 4.4 ghz by changing bclk - it seems stable.
Calmed down for a moment...

 

[Gasaraki]

KB4100347

Summary


Recent Changes:

• Intel Microcode Updates around the following products (CPUs) have been revised. We recommend to take this latest update to stay current:
  • Broadwell Server E, EP, EP4S
  • Broadwell Server EX
  • Skylake Server SP (H0, M0, U0)
  • Skylake D (Bakerville)
  • Skylake X (Basin Falls)

https://support.microsoft.com/en-us...or-windows-10-version-1803-and-windows-server

Well it seems to impact a lot of Intel CPUs. Be careful then.

Which doesn't affect overclocking which is done in the BIOS settings. Windows can't stop you overclocking in your BIOS.

 

[MrGenius]

Which doesn't affect overclocking which is done in the BIOS settings. Windows can't stop you overclocking in your BIOS.

You can hypothesize all you want. It doesn't make you right. Especially when real world evidence suggests otherwise.

Look. The scenario is this. The motherboard BIOS has a microcode for the CPU. Windows also has a microcode for the CPU in System 32. Windows will not use the microcode in the motherboard BIOS unless that's all there is for it to use. Windows does this because the microcode it has in System 32 is updated with Spectre protection(via the September KB4100437 update), or for whatever other reason it deems the microcode in System 32 to be superior to(or even just as good as) the microcode in the motherboard BIOS. Which is a "good" thing. Except when it breaks CPU overclocking and/or causes significant performance loss. Then it's not such a "good" thing.

None of this is even debatable. It just is what it is. And that's that.

 

[Darmok N Jalad]

did you watch any other videos on this as most of these were either proven to hard to implement (extensive knowledge of the hardware and alot of time for actual access to that hardware) or just down right BS claims by CTS labs (Who on their own web-page stated they were in it for monetary gain) in order to gain access to cheap AMD shares by dirtying their name in public

Hers my favorite page on the reputable CTS-labs website:
http://cts-labs.com/past-publications
Clearly, this security company is hard at work finding hardware/software flaws for our protection! Can’t wait for them to publish their findings on the AMD issues they went public with over 9 months ago.

 

[lexluthermiester]

Hers my favorite page on the reputable CTS-labs website:
http://cts-labs.com/past-publications
Clearly, this security company is hard at work finding hardware/software flaws for our protection! Can’t wait for them to publish their findings on the AMD issues they went public with over 9 months ago.

Not only is this completely off-topic, but it is needless as this has been discussed, at serious length, in other areas of the forum.

 

[kime01]

thank you all for everything you discussed here about this annoying problem.
I always have been just a reader of this thread, now I should intervene, registering me, only to add an info could be useful for many here.

AFTER updating yesterday to Windows 10 1903, changing (or deleting) mcupdate_genuineintel.dll won't work anymore (BSOD if the new file is not in system32 folder). Until 1809 that solution worked great.

SOLUTION: run Inspectre (as administrator) and click on "disable Spectre Protection": OCing returns to work perfectly (i also deleted the file but I think it could be useless). Tested on X99 6850K processor and ASUS X99 STRIX Gaming Mobo (4.3GHz OC'ed)

 

[MrGenius]

AFTER updating yesterday to Windows 10 1903, changing (or deleting) mcupdate_genuineintel.dll won't work anymore (BSOD if the new file is not in system32 folder). Until 1809 that solution worked great.

I just did a clean install of 1903 and deleted the mcupdate_GenuineIntel.dll. No issues here.

I haven't tried replacing it with the 1803 version yet. I'll post results when I do.

BTW...you're welcome.

 

[Fangio1951]

hi MrGenius,

Quick question - did you delete the file AFTER you did the 1903 install ??

regards

 

[Eskimonster]

Im so glad my system aint overclocked atm, this is just another thing that makes me wanna go AMD:

 

[Space Lynx]

some people have 0 issues overclocking with latest updates and microcodes. /shrug

 

[MrGenius]

hi MrGenius,

Quick question - did you delete the file AFTER you did the 1903 install ??

regards

R U serious?

Better question would be...how could I possibly have deleted it before actually installing it? I did mention "clean install". And, even if I updated/upgraded to it, it would still be replaced in the process(even if I deleted it prior).

 

[Eskimonster]

some people have 0 issues overclocking with latest updates and microcodes. /shrug

i use

	I-7 3770k

 

[kime01]

I just did a clean install of 1903 and deleted the mcupdate_GenuineIntel.dll. No issues here.

View attachment 123515

I haven't tried replacing it with the 1803 version yet. I'll post results when I do.

BTW...you're welcome.

In my personal case I tried both:
- replacing with old file (4/11/2018 version, page 2 of this thread) -> BSOD (fixable deleting the old and renaming the .bak but no OC working);
- deleting the new file -> Windows 10 boots but without OC (standards 3.8 frequencies).

The curious thing this is one of the few places on www where you can read news and info on this issue, I really love you guys!

 

[unclewebb]

Has anyone with a 6800K tried using Intel XTU or ThrottleStop to get their overclock back after they boot up? ThrottleStop does not fully support Turbo Boost 3.0 but it might be good enough to get your overclock back. Post some pics so I can have a look.

i use I-7 3770k

This is only a problem for CPUs running on the X99 chipset.

 

[Deleted member 50521]

Has anyone with a 6800K tried using Intel XTU or ThrottleStop to get their overclock back after they boot up? ThrottleStop does not fully support Turbo Boost 3.0 but it might be good enough to get your overclock back. Post some pics so I can have a look.


This is only a problem for CPUs running on the X99 chipset.

X99 is a cursed platform

 

[MrGenius]

- replacing with old file (4/11/2018 version, page 2 of this thread) -> BSOD (fixable deleting the old and renaming the .bak but no OC working);

I just tried the old file method and it didn't work for me either. I didn't get a BSOD. But it refused to boot into Windows with it. I had to use used startup repair to fix it. Which, for whatever reason, deleted it. So I'm still running without any mcupdate_GenuineIntel.dll. And I still haven't experienced any issues running with it like that.

EDIT: Turns out startup repair just did a system restore with my latest restore point. Which makes sense as to why the file vanished in the process. Didn't know that's something it could/would do. Learn something every day...

 

[R-T-B]

Better question would be...how could I possibly have deleted it before actually installing it? I did mention "clean install". And, even if I updated/upgraded to it, it would still be replaced in the process(even if I deleted it prior).

Imageprep, dism, or one of those MS service tools.

X99 is a cursed platform

You should call a priest with all the trouble you've had on that board. I believe it's got the devil inside.

 

[kime01]

Has anyone with a 6800K tried using Intel XTU or ThrottleStop to get their overclock back after they boot up? ThrottleStop does not fully support Turbo Boost 3.0 but it might be good enough to get your overclock back. Post some pics so I can have a look.


This is only a problem for CPUs running on the X99 chipset.

I've installed Intel ITU to test. It replaces the working ASUS ITU (my mobo is ASUS') but doesn't start (stuck in the main window for minutes).

However, ASUS ITU (before being replaced) said OC is working even without applying the solution discussed here (deleting/disableSpectre) but checking with other SW (e.g. CPUID HWmonitor) CPU freqs are blocked to non OCed ones.
So I'd say ITU doesn't fix.

 

[shamus21]

Well i am running an Asus x99 with a 5820k lastest Bios about 2 years, old not the beta Bios and still have my 4.5 overclock running with out issues and this is with the update method not the Usb clean install which i had to do with last years update after it locked up the system.

 

[Candor]

It's been mentioned several times that haswell-e is not affected, only broadwell-e

 

[HUSKIE]

As above mentioned...

 

[SoNic67]

I have Ivy Bridge-EP generation CPUs (two of E5-2630 V2 on one board) and I didn't get the update. Last OS update was yesterday an I am still at version 1809, build 17763.529

 

[HUSKIE]

I have Ivy Bridge-EP generation CPUs (two of E5-2630 V2 on one board) and I didn't get the update. Last OS update was yesterday an I am still at version 1809, build 17763.529

You are not affected anyway.

 

[John Naylor]

If users don't like being on the bleeding edge .,,. would suggest not being the 1st one on your block to install new updates. Ask Woody has probably the biggest collection of "warnings" ... . When discussing preview rollups, I always respond "What advantage is there to installing this today ? Whether the chance is 10, 25, 50, 100% of having a problem why take the chance ? Wait 30 days and see if you are affected, by what and if it's been fixed when the next month rolls around."