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

[R-T-B]

Awesome! Thanks Froggie! I will dig around Win-RAID forum and see if I am conformable with modding.


@MrGenius I am definitely saving that file for the upcoming Fall Windows 10 update.

Look for UBU, the universal bios updater. After a few scary Ruski links it's actually a pretty easy to use tool. You will also probably need a copy of mmtool.exe which I can help with if need be, since that is... controlled or whatever. Not sure it's story, honestly.

I still say the best answer is just to replace the mcupdate_GenuineIntel.dll after the update(with the file dated 4/11/18). That way the system still thinks the update(the September 13 KB4100347, not the May 17 KB4100347, there's 2 with the same name) is installed. And it won't try to reinstall it(I've tested this theory and it's true). Then you don't need to uninstall the update or do whatever to prevent it from (re)installing. Or do any BIOS modding. You're done with it. And you keep a copy of both the pre and post update mcupdate_GenuineIntel.dll files so you can manually control the microcode that the OS uses(if you decide you aren't done with it). I realize it's not the best answer in every circumstance. But it's pretty close if not.

It would drive me nuts not being able to depend on sfc /scannow.

 

[lexluthermiester]

It would drive me nuts not being able to depend on sfc /scannow.

That can be solved by also replacing or deleting the offending dll file(s) in the system repository which will prevent it from being restored but will not jack with anything else.

 

[R-T-B]

That can be solved by also replacing or deleting the offending dll file(s) in the system repository which will prevent it from being restored but will not jack with anything else.

It'll make sfc /scannow give a clean positive?

My OCD requires this.

*pets computer while mumbling in golem voice*

"Fast computer, clean computer, really really quick..."

 

[lexluthermiester]

It'll make sfc /scannow give a clean positive?

My OCD requires this.

*pets computer while mumbling in golem voice*

"Fast computer, clean computer, really really quick..."

LOL! That's a good question. Likely not. I only run it once in a while and specifically with the " /verifyonly " switch which only reports what files it finds problematic. The reason I do this is that I fully remove[physically delete] Windows Defender, Internet Explorer, Windows Media Player and a few other things and customize a few system files. I don't want them automatically restored. Thus when it generates a list of files I know what I'm looking for and will see anything out of sorts.

 

[cadaveca]

Yeah, I can't call it a fix, if it breaks other things, either.

 

[MrGenius]

It doesn't break anything. You just need to keep it in mind, and be prepared to do it over again if/when necessary. Like after you run sfc /scannow, or when Windows 10 updates itself to a new version. I guess I'm used to it because I've been doing it with the imageres.dll(s) for quite a while now.

EDIT: An in-place upgrade will also reset the installed updates list. So it will attempt to reinstall it. I found that out yesterday when I did one. Well, not so much found out as expected it to happen, and verified it. I also found out that dism /online /cleanup-image /restorehealth will leave it as is.

 

[Athlonite]

Well atleast you have an Intel CPU installed in your machine I don't but was forced to install it anyways like an Intel Micro Code update is going to do a damn thing for my AMD CPU based system

 

[lexluthermiester]

like an Intel Micro Code update is going to do a damn thing for my AMD CPU based system

True. The patch for Intel CPU's will not be loaded or accessed in an AMD based system.

 

[freeagent]

All of my overclocks went to hell, I noticed a few days ago. I thought it was ram, played with it, tried different sets, went back to 7, nothing helped. I turned off hyperthreading, and am running at 4600 1.275v. It passes that new linpack extreme.. If I turn ht back on it fails. I thought I had 4400 nailed down with ht on, until it blue screened. My x5690 seems to be ok still, for now. I will probably turn ht off on that too. Bummer dude. It was fun while it lasted.

 

[mkdr]

@xkm1948 Windows cant nor wont flash/update your bios/UEFI with a MC update.

0. CPU contains hard coded MC
1. UEFI contains MC patch => loades it into CPU.
2. Windows/Linux/OS contains MC patch => loades it into CPU (overwrites the UEFI one)

=> removing/deinstalling the Windows MC file leads to just 1. The MC patch is loaded every time into the CPU the UEFI and OS boots. The loaded MC in the CPU is lost everytime the PC reboots.

You can hide the update with http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab after removing it.

 

[Assimilator]

Well atleast you have an Intel CPU installed in your machine I don't but was forced to install it anyways like an Intel Micro Code update is going to do a damn thing for my AMD CPU based system

Assuming Microsoft only pushed Intel microcode updates to Intel systems: what would happen if you switch out your AMD CPU and motherboard for an Intel pair, but keep the current OS? Boom, your OS is fubbernucked unless you're able to flash a BIOS with most up-to-date microcode, which for people with X99 systems isn't an option since their mobo vendors no longer issue BIOS updates.

Before you say "holy hell why would you even do that": I had an old AMD S939 system running Windows 7, and the board died and I wasn't able to source a replacement, so I substituted in a spare Intel LGA775 system because I couldn't be a**ed to reinstall all the software. Everything worked fine afterwards (apart from having to install new drivers and reactivate the OS). It's not technically a supported scenario, but it definitely works, and microcode updates help make it work.

 

[rkt]

X99 Extreme4 I7 6850k - after update I cannot overclock cpu through bios, it always at default values, but it possible through software... Before it was overclocked at 4,4 ghz. Bios update not helped.
Do not know what to do.

 

[Papahyooie]

Well I don't know if this is related, but I got home yesterday, and my wife's Asus 970 pro gaming/aura with AMD FX 8370's windows install is pretty much bricked after having taken the update over the weekend. Can't boot, can't repair, even the usual CMD fixes won't work because bootrec doesn't even see that there's a windows installed.

Like I said, no idea if this is related, as you guys are all talking about Broadwell, and this is an older AMD. But... How are they still in business??? Seriously considering going to linux full time.

 

[Assimilator]

@W1zzard Not sure what connections you have in the industry, but I'm certain an Intel rep would be interested to hear about this SNAFU.

 

[mkdr]

Assuming Microsoft only pushed Intel microcode updates to Intel systems: what would happen if you switch out your AMD CPU and motherboard for an Intel pair, but keep the current OS? Boom, your OS is fubbernucked unless you're able to flash a BIOS with most up-to-date microcode, which for people with X99 systems isn't an option since their mobo vendors no longer issue BIOS updates.

No.... that's not how it works... Every CPU is identified as Intel, AMD whatever by the Kernel at Windows boot and therefor only Intel CPUs get Intel MC and only AMD get AMD MC loaded into it at boot time...

 

[HeavyHemi]

6850K on an EVGA X99 FTW K is affected as well.

 

[Candor]

X99 Extreme4 I7 6850k - after update I cannot overclock cpu through bios, it always at default values, but it possible through software... Before it was overclocked at 4,4 ghz. Bios update not helped.
Do not know what to do.

This thread is only 6 pages long at this point and there are at least three solutions already stated here.

Have you read it?

 

[HeavyHemi]

This thread is only 6 pages long at this point and there are at least three solutions already stated here.

Have you read it?

Fortunately while this update did some weird shizz when it updated on the first restart to a bluescreen then a lock...I just did a power off, then rebooted. That seems to have saved me from anything getting corrupted. Uninstalled the update using Windows Add/Remove then hide and disabled the update service with WUMTminiTool. I'll have to pester EVGA to see if they will fix us up.

 

[xkm1948]

Fortunately while this update did some weird shizz when it updated on the first restart to a bluescreen then a lock...I just did a power off, then rebooted. That seems to have saved me from anything getting corrupted. Uninstalled the update using Windows Add/Remove then hide and disabled the update service with WUMTminiTool. I'll have to pester EVGA to see if they will fix us up.

Another BSOD victim. Good to know. BTW you are not another alias of me I assume? I was told this is just my particular problem lol @cadaveca


More than likely they won't. X99 is EOL for support, at least for ASUS.

 

[cadaveca]

More than likely they won't. X99 is EOL for support, at least for ASUS.

SO can we confirm that the microcode update killed your OC inh windows?

The OS not booting was because of the update removal?


OR did the update bork the OS too?

 

[xkm1948]

SO can we confirm that the microcode update killed your OC inh windows?

The OS not booting was because of the update removal?


OR did the update bork the OS too?

No idea. Sounds like the update messed up something in Windows that caused loss of overclocking. Removal of it in safe mode (uninstall updates from Windows options) caused BSOD upon restart. So yeah, no idea.

 

[HeavyHemi]

SO can we confirm that the microcode update killed your OC inh windows?

The OS not booting was because of the update removal?


OR did the update bork the OS too?

Hard to say what we can confirm. Now that I think about it, I think I had two blue screens trying to reboot, until I went into the BIOS on boot, didn't change anything, continued the boot and it completed.
Maybe I didn't have the other issue because I removed the update normally. Safe mode uninstalls are usually a last resort. Kinda digging the purple H avatar...it's Heavy man.

 

[freeagent]

ASUS has this recurring problem where the BIOS shits the bed if your OC isn't quite stable, so its possible. I've had users report a stable OC not working, when pushing memory, reflash somehow fixes it. What other use is USB BIOS Flashback? Its like they know and then that's the fix...

I was pushing my ram, and didn't get the results I was looking for.. normally, if there is a problem I lose the multi, and memory speed control. None of that happened this time, none of my overclocks would stabilize even with added vcore. So I read this thread and your comment stuck out. I just reflashed about 20 minutes ago and booted at 4600 with ht no problem. Ran some quick tests and thought I would report back.

 

[cadaveca]

I was pushing my ram, and didn't get the results I was looking for.. normally, if there is a problem I lose the multi, and memory speed control. None of that happened this time, none of my overclocks would stabilize even with added vcore. So I read this thread and your comment stuck out. I just reflashed about 20 minutes ago and booted at 4600 with ht no problem. Ran some quick tests and thought I would report back.

Losing OC on ASUS boards when pushing the limits IS normal and has been a thing for many generations now. Not that big of a deal, if you know how to deal with it.

 

[hat]

Losing OC on ASUS boards when pushing the limits IS normal and has been a thing for many generations now. Not that big of a deal, if you know how to deal with it.

Sounds like something pulling the cmos battery/shorting clr cmos pins might solve... but it also seems like a weird design flaw (choice)?