Windows 10 October 2018 Update (Windows 10 ver. 1809) KILLS BW-E Overclock!!!!!!!!!

[JuSiZ1]

PLEASE ASUS....INTEL...MICROSOFT FIX your software. This is very annoying i never install KB4100347 update because this problem but now when win update install this october 18 update my overclocks is broken!! @Raja@asus @Chino @somebody to know how to fix this!?!?

[armin_maleki]

armin_maleki wrote:
i tired with ezflash on bios.tonight i will try with USB BIOS Flashback button and update my post.thank you for your answer

This is work,thank you chaosminionX and HiviZMan... 🙂
kamtec1 -----> just copy chaosminionX's Cap file in Fat32 flash and rename to R5E10...put it in USB BIOS Flashback behind of your case and hold flashbackbutton when your pc turn off with power on power supply for 3 second...the button blinking ...wait the blinking will end then turn on your computer...

[HiVizMan]

armin_maleki wrote:
This is work,thank you chaosminionX and HiviZMan... 🙂
kamtec1 -----> just copy chaosminionX's Cap file in Fat32 flash and rename to R5E10...put it in USB BIOS Flashback behind of your case and hold flashbackbutton when your pc turn off with power on power supply for 3 second...the button blinking ...wait the blinking will end then turn on your computer...

All good my friend I am pleased you have your PC sorted. Thank you for posting the good news.

[kamtec1]

HiVizMan wrote:
Please rename to M10H.CAP and use a USB2 drive to flash back.

USB drive should be FAT formatted.

Not worked for me 😞 "THIS IS NOT A PROPER BIOS"

[HiVizMan]

kamtec1 wrote:
Not worked for me 😞 "THIS IS NOT A PROPER BIOS"

The quick fix would be to simply revert the microcode dll that changed.

tobacco wrote:
You can change mcupdate_GenuineIntel.dll with a previous version. Which you can find in "C:\Windows\System32". To change that file you need to take the ownership of the file from security settings. This will revert kb4100347 update and its side effect.

[Hopper64]

How does one “change the ownership” of the .dll file to fix this problem? I see the security tab for the file, but how do you change the owner? Thanks.

[JustinThyme]

Im late to the party here but just noted Im in the same boat. Was wondering why some things slowed a bit then saw this sure as snot while my bclk is 100 and multi of 48 im not even syncing all 10 cores at 4.3. Some at 34, a few at 4100. Gonna have to read back and see if I can piece this thread together and wrap my head around it.

I was doing good and still hadnt even done FCU from last year yet until the 365 day delay was up and I couldn't extend anymore.

UPDATE
Tried the swap out and it doesnt work. Weirdest thing.......
All cores go to the full 4800
launch AIDA64 stress test and they all drop to 4300//////scratches head. Putting file back the way it was.

[HiVizMan]

Board depending the fix is the bios update with the microcode injected. Tested and working.

[Korth]

Intel released microcode which fixes Spectre and breaks overclocks. They've corrected the vulnerability and provided the promised/expected level of security on their "old" products. So they won't lose any money replacing parts or honouring warranty or getting bad press or confronting liability accusations.

But why would they be interested in correcting overclock issues or extending longevity on their "old" products? It costs them time and money and effort to roll out new code for old stuff, they'd rather work on new code which sells new stuff. The old parts still perform at Intel spec, Intel doesn't need to keep any promises (they never made) about overclocked performance above Intel spec - important since the vast majority of the affected parts are installed in Big Money enterprise platforms which require the security and always run strictly within Intel spec. The obvious win for Intel (and they know they're gonna win) is to basically force those enthusiasts who want overclocks to discard old Intel parts and rush out to buy overclockable new Intel parts.

The only backfire against Intel's recurring strongarmed lack of ethics/loyalty is some customers abandoning them "forever" for AMD ... it's all happened before, it's all happening again, but a small horde of disgruntled enthusiasts swearing new fealty to Team Red are just not enough to have much impact where Intel really makes its big revenues ... Intel loses a little money (some new Intel-haters join the crowd, meh), while Intel also gains a lot of money (selling piles of new CPUs!) ... they really have no motivation at all to change a methodology which has been lucrative for them so many times in the past.

[zombii]

I Have a motherboard Asus A II , with a I7 6800K

for now I use the DLL to overclock my CPU (at 4.1 at 1.4V )
Do you think I can flash my motherboard with the R5E10.CAP ?
or is not compatible ???

[Korth]

zombii wrote:
I Have a motherboard Asus A II , with a I7 6800K
Do you think I can flash my motherboard with the R5E10.CAP ?
or is not compatible ???

You can only flash BIOS/firmware which is specifically meant for your specific motherboard model. Nothing else will work.
Your board might reject an incompatible BIOS ... more likely an incompatible BIOS would just brick it ... in extreme cases an incompatible BIOS might even cause electrical/hardware damage to the board and anything else (CPU, RAM, PCIe, etc) plugged into it.

Only use BIOS/firmware downloaded from your motherboard page. ASUS X99 A-II BIOS is here. ASUS X99 R5E/R5E10 BIOS will not work.