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

[dorsetknob]

Storm hits system shuts down maybe a 30 minute UPS was not long enough and POOF systems screwed and NO one to take blame for it.

that's it You should only update on a full moon and Clear skys
This Micro code update is Really Screwing people over.
Since Sandy Intel seem to hate overclockers and this seems to be the latest Action ( and it retrospectivle effects earlier CPU's ).

 

[TheoneandonlyMrK]

that's it You should only update on a full moon and Clear skys
This Micro code update is Really Screwing people over.
Since Sandy Intel seem to hate overclockers and this seems to be the latest Action ( and it retrospectivle effects earlier CPU's ).

Playing fair , over locking is niche ,but i don't think they did this knowingly and willingly to mess with over clocker's , just an unfortunate aside partially blameable on the mother board makers Not releasing bios updates beyond a year, looking in asus direction here especially.

Good luck with this though genuinely @xkm1948

 

[jsfitz54]

Case in point: Nearly every LGA1366 system is BIOS code based, but they are getting mc updates including this one today. Did someone miss this fact?

See post # 25

 

[GLD]

That is some BS hosiery you Intel guys got with the forced update.

 

[cadaveca]

That is some BS hosiery you Intel guys got with the forced update.

AMD's is coming, unfortunately. Too many people only think about Ryzen/TR/EPYC when it comes to AMD, but there are plenty of systems with early AMD designs that are having ALL SORTS of problems. Board makers have to work on BIOSes on all platforms or this is going to get even worse over the coming months as newer systems start to see problems as well. I mentioned some time ago that what people were complaining about for Spectre/Meltdown was far from over, and this is yet another impact for users with older stuff. AMD and Intel have no choice but to force these updates on users because they aren't updating their systems against these vulnerabilities on their own, for whatever reason. We've got at least another 5 years before this all melts into the background.

My systems do not have this problem, but they are as up-to-date as can be.

 

[dorsetknob]

We've got at least another 5 years before this all melts into the background.

Spotted that sly sense of humour

 

[AsRock]

that's it You should only update on a full moon and Clear skys
This Micro code update is Really Screwing people over.
Since Sandy Intel seem to hate overclockers and this seems to be the latest Action ( and it retrospectivle effects earlier CPU's ).

Well you live in the UK so yeah storms and power outages are like a blue moon happening. a lot of parts of America i can tell you power outages are much more common more so in summer.

In the UK i think over the 30 years of living their only remember 1 power outage but here in the US i am talking several a year, a UPS should be a requirement in the US. The other reason i run every thing on UPS's is were we live as it's classed as a industrial area so when all the businesses are closed our mains jumps from a average of 119v to127v which can course all kinds of issue's.

 

[R-T-B]

But they did not do this shit before

Well, mc updates have been done via Windows in the past if that's what you mean. Just less frequently, and less... destructively. You probably did not even notice them.

My point is uefi has nothing to do with it.

 

[AsRock]

No just were able to disable it, and enable when it was best for me. With the home version od Win10 disabling updates has not been possible.

 

[unclewebb]

With the home version od Win10 disabling updates has not been possible.

Have you tried using this script?

WUMT Wrapper Script 2.5.2
https://www.majorgeeks.com/files/details/wumt_wrapper_script.html

There is that nasty KB4100347. Thanks but no thanks.

Bye Bye KB4100347.

 

[phill]

Still waiting for the update at the moment... I've done a base line and nothing has changed so far....

 

[R-T-B]

No just were able to disable it, and enable when it was best for me. With the home version od Win10 disabling updates has not been possible.

ah, gotcha.

 

[NdMk2o1o]

This is downloading on my updates right now, any issues with Ryzen systems that anyone has heard of?

 

[AsRock]

Have you tried using this script?

WUMT Wrapper Script 2.5.2
https://www.majorgeeks.com/files/details/wumt_wrapper_script.html

There is that nasty KB4100347. Thanks but no thanks.

Bye Bye KB4100347.

Tried W1zzard's script from his thread and O&O program and still updates. Will try that too and see what happens.

EDIT: it's already disabled, and i am trying to just update when I want to not when MS wants to do it.

Normally ened up finding the system wanting to update though shutdown menu so will it disable it that late on ?.

 

[biffzinker]

This is downloading on my updates right now, any issues with Ryzen systems that anyone has heard of?

Nothing happened for me. If you moved your boot drive to an Intel build then you might run into the issue.

 

[unclewebb]

@AsRock - Run the script when you want to check Windows Update.
Windows Update will be disabled after you close WUMT until the next time you run the script.

You get to pick and choose what you want to install. Not Microsoft.

This tool also has an uninstall feature so you can uninstall bad updates once you become aware how bad they really are.

Edit- Not sure if uninstalling a microcode update will revert you back to the previous microcode version.

 

[NdMk2o1o]

If you moved your boot drive to an Intel build then you might run into the issue.

Blasphemer!

Afaik from some googling as it's an intel mc update only then on Ryzen systems even though the update is downloaded and "applied" I'm assuming it will look for an Intel CPU once downloaded and install, in the case of Ryzen it would see the AMD CPU and just ignore even though it does download.

 

[biffzinker]

It's on the drive waiting for any Intel CPU

 

[Zyll Goliat]

X58: No issues so far on my i7 970.

Same here no problem with my Asus P6X58D Premium&6-Core E5645......

 

[mkdr]

Did someone else notice an issue with the last Windows 10 updates with Optimus laptops? I have an issue right now that my Nvidia GPU doesnt clock up anymore, and I have not changed anything but Windows 10 updates of the past days.

 

[Space Lynx]

I installed KB4100347 just now on my gtx 1070 laptop. and I have 0 changes or issues in any game.

lulz. the hype is real

 

[AsRock]

I installed KB4100347 just now on my gtx 1070 laptop. and I have 0 changes or issues in any game.

lulz. the hype is real

Hype ?, so because it's been ok for you it's ok for everyone ?. Wow were not talking consoles here.

 

[notb]

Well f*uck me. Forced uninstalled that update in safe mode and now system is stuck in BSOD loop and can’t even get into recovery mode!

You've tried to uninstall a microcode update. This is the expected result.
This is basic stuff guys.

Thanks a bunch Microsoft for mess up my work computer with your “Intel validated” microcode update.

And also just another argument in the "overclocking work PCs" discussion...

My systems do not have this problem, but they are as up-to-date as can be.

Because this is the only proper approach, obviously. At least people are learning from whom to take advice...

Hype ?, so because it's been ok for you it's ok for everyone ?. Wow were not talking consoles here.

No. Because the only problem that anyone had in this thread is @xkm1948 and that was because he uninstalled the update, not installed it.

 

[hat]

You've tried to uninstall a microcode update. This is the expected result.
This is basic stuff guys.

Because such updates, or any software for that matter, should be carved into the eternal, never to be removed again...

And also just another argument in the "overclocking work PCs" discussion...

Work PC or not... I'd be uber pissed if I had a 6950x, whose MSRP is north of $1700, and suddenly not only be unable to overclock it but also have diminished performance (even if it were left at stock) thanks to a crappy update. And hey... maybe he needs those additional clock cycles for his work?

Because this is the only proper approach, obviously. At least people are learning from whom to take advice...

In a perfect world, yes. In the actual, not so perfect world we all live in... updates can and do wreck havoc from time to time, hence thread. Evidently cadaveca was one of the luckier ones who selected hardware that actually got proper support from the manufacturer. From what I gather, this microcode update can really fuck shit up without a proper BIOS update backing it.

No. Because the only problem that anyone had in this thread is @xkm1948 and that was because he uninstalled the update, not installed it.

wat

No... just... no. xkm1948 is not the only user in this thread complaining about the update. Secondly, he uninstalled the update not because he went about deleting things all willy nilly, he did so because the update caused problems in the first place.

 

[R-T-B]

You've tried to uninstall a microcode update. This is the expected result.
This is basic stuff guys.

Uh, no. There is no reason microcode updates should not be able to be uninstalled. I mean, they don't even persist across reboots, depending on a driver to load them everytime. They are about as "persistent" as RAM.

You may want to brush up on them "basics."