Broadwell E users watch out for Windows 10 KB4100347 update

[Korth]

It is a big problem. Alas, overclocking means overspec, operating outside rated spec, no guarantees ... and no liability for Intel, they do demonstrate overclocks and tacitly support/encourage it, of course, but they never actually promise overclocks on any of their products. Not their problem, even if it is (quite arguably) their design flaw.

So Intel may come up with better fixes, if anything better is possible. But they don't have to, and I'm of the opinion (just an opinion) that they won't because the affected products are basically not a market segment where Intel makes most of its money, they're a business and will likely focus (quite properly) on investing their support into those products which bring them their revenue. I think we can only hope Intel decides to be charitable (or obsessive) enough to invent better firmware updates ... or come up with our own.

[Mr. Fox]

I do not allow Windows Update filth on my systems. The "security" is not important enough to put up with their endless supply of utter nonsense. I personally think all of the blabber about Meltdown and Spectre is overhyped drama.

[ThrashZone]

Hi,
What is obvious is the microcode is not tested very well on eol platforms
Best to report on the feedback hub
asus doesn't care either beta bios and all it took them 6 months to finally release it lol because of sudden shut downs "on some configurations" whatever the heck that really means

Either way for haswell-e I'll stay on 2101
Broardwell-e bios over shoot vccio cpu 1.05 voltages way too much 1.25v+ to keep that around where as 2101 and later all stay within 1.05+- so something was never right to begin with.

Yes indeed over hyped steaming pile has always been my position too but now 10 is installing it, it's a problem not so much for win-7 though

Also too darn bad RAGA@ASUS has selective support attention disorder

[madmarc69]

I used the "wushowhide.diagcab" to block the update.

[Nixon2992]

Users Broadwell-E try substitution microcodes from last update for W10 (ucode version :0xB00002C) to ucode version :0xB00002E via VMWare?
This ucode version will be stock on W10 RS5 build and on RS5 cannot disable Spectre/Meltdown protection.
https://www.win-raid.com/t3355f47-In...cussion-9.html

[Caipirinha]

this is SH1** i got this oc block attack for my 6850K - RAMPAGE V EDITION 10 exactlly on 31 AUGUST ( and yet have no clue how this update belongs to 14 sep when this attack happened to me on 31 aug)
heres what happned : 31 august 2018 3 AM my pc was on already and i was afk then after 3 hours i came back i saw my pc has been turned off by itself i pushed the power button nothing happened pushed pushed pushed nothing happened then i pushed the SAFE BOOT button on the board it turned on got into bios and checked for everything and my overclocks settings in bios and everything was on correct Numbers for voltages ferequencies and timings which im using now for 2 years full stable: (6850K @ 4.3 1.35v - @4.4 1.4v FULL STABLE and for my 4x8GB tridentz rams > 3400mhz CL 14-15-16 with some configurations on secondery and third timings) , so i closed the bios and then bam system turned off again then back again to bios rolled back everything to the default bios setting with No overclock and F10 saved and restart then back to windows called my super geniuse friend who is among top 10 RAM overclockers in the world , told him about the issue HE WAS SO SHOCKED then suddenly i remebered the SPECTRE MELTDOWN thing and i told him can it be because of that ? then he and i started to research about related issues with bios/windows updates or any sort of cpu microcode attack and motherboard firmware attack on the net after hours we figured out that its 99% an intel sabotage to my cpu microcode or bios frameware (not the bios for sure because i switched between 2 bioses and in all of them same problem and i did clear cmos flashed bios 100 times no goal) ,
and he said intel is doing this randomly or to almost every systems that are currently runing x99 platforms or some other platform or cpus to Force them buy the new Upcoming 9 series or extreme series so i was so MAD AT intel and whoever did this : """"""""suddenly NO overclock for ur thousandS dollars pc and throw it to your garbage u r f***ked now""""""" because i even myself had plans on buying the new 9 series myself from 3 months before and i was getting ready to sell my cpu/mb bundle and get the new ones and then the last minute i have to face """""""""how to sell it at a good price with no overclock option on it......""""""""

LONG TALK SHORT 2 days ago my friend showed me these news about this kb4100347 i couldnt believe what im hearing and all these folks who have faced my issue on their haswell-E and broadwel-E pcs i got so happy and shocked at the same time i cant believe what intel and microsoft have just did with this microcode update intel calm down and know that u cant threat ur users with these type of threats and this is not how cpu making companies business work in todays world many of us have been or still are your fans and enjoyed your products all these years and have had respects to you all the time This is not the way to appreciate them in response.

MY SYSTEM COULDNT EVEN BOOT ON ANYTHING MORE THAN 2133 mhz FOR DRAMS FEREQUENCIE NO XMP AND NO TIMINGS THAN AUTO AND FOR THE CPU I COULDNT EVEN SET TO >> sync all cores...I HAD TO SET EVERYTHING ON "AUTO" AND MY CPU WAS RUNING @ ITS DEFAULT 3.6 GHZ (and ofcourse on windows for my power plan i switched to>> performance mode to be able to run on 3.8 ghz last days of using it)

PS:i have to add that this update also Broked my first bios and left it Corrupted because i got the latest bios (1902 Beta) to test if it solves the issue or not at that moment but shockingly in the middle of the installation of the new bios process stopped and system off so seems that microcode update blocked the instalation process and i lost the first bios and now have just the second Bios available on my board:|

[Nixon2992]

this is SH1** i got this oc block attack for my 6850K - RAMPAGE V EDITION 10 exactlly on 31 AUGUST ( and yet have no clue how this update belongs to 14 sep when this attack happened to me on 31 aug)
heres what happned : 31 august 2018 3 AM my pc was on already and i was afk then after 3 hours i came back i saw my pc has been turned off by itself i pushed the power button nothing happened pushed pushed pushed nothing happened then i pushed the SAFE BOOT button on the board it turned on got into bios and checked for everything and my overclocks settings in bios and everything was on correct Numbers for voltages ferequencies and timings which im using now for 2 years full stable: (6850K @ 4.3 1.35v - @4.4 1.4v FULL STABLE and for my 4x8GB tridentz rams > 3400mhz CL 14-15-16 with some configurations on secondery and third timings) , so i closed the bios and then bam system turned off again then back again to bios rolled back everything to the default bios setting with No overclock and F10 saved and restart then back to windows called my super geniuse friend who is among top 10 RAM overclockers in the world , told him about the issue HE WAS SO SHOCKED then suddenly i remebered the SPECTRE MELTDOWN thing and i told him can it be because of that ? then he and i started to research about related issues with bios/windows updates or any sort of cpu microcode attack and motherboard firmware attack on the net after hours we figured out that its 99% an intel sabotage to my cpu microcode or bios frameware (not the bios for sure because i switched between 2 bioses and in all of them same problem and i did clear cmos flashed bios 100 times no goal) ,
and he said intel is doing this randomly or to almost every systems that are currently runing x99 platforms or some other platform or cpus to Force them buy the new Upcoming 9 series or extreme series so i was so MAD AT intel and whoever did this : """"""""suddenly NO overclock for ur thousandS dollars pc and throw it to your garbage u r f***ked now""""""" because i even myself had plans on buying the new 9 series myself from 3 months before and i was getting ready to sell my cpu/mb bundle and get the new ones and then the last minute i have to face """""""""how to sell it at a good price with no overclock option on it......""""""""

LONG TALK SHORT 2 days ago my friend showed me these news about this kb4100347 i couldnt believe what im hearing and all these folks who have faced my issue on their haswell-E and broadwel-E pcs i got so happy and shocked at the same time i cant believe what intel and microsoft have just did with this microcode update intel calm down and know that u cant threat ur users with these type of threats and this is not how cpu making companies business work in todays world many of us have been or still are your fans and enjoyed your products all these years and have had respects to you all the time This is not the way to appreciate them in response.

MY SYSTEM COULDNT EVEN BOOT ON ANYTHING MORE THAN 2133 mhz FOR DRAMS FEREQUENCIE NO XMP AND NO TIMINGS THAN AUTO AND FOR THE CPU I COULDNT EVEN SET TO >> sync all cores...I HAD TO SET EVERYTHING ON "AUTO" AND MY CPU WAS RUNING @ ITS DEFAULT 3.6 GHZ (and ofcourse on windows for my power plan i switched to>> performance mode to be able to run on 3.8 ghz last days of using it)

PS:i have to add that this update also Broked my first bios and left it Corrupted because i got the latest bios (1902 Beta) to test if it solves the issue or not at that moment but shockingly in the middle of the installation of the new bios process stopped and system off so seems that microcode update blocked the instalation process and i lost the first bios and now have just the second Bios available on my board:|

You try boot on any live Linux distribitions with old Kernels(for example Debian 7) and check overclocking frequncy via Bash:lscpu | grep MHz?

https://cdimage.debian.org/mirror/cd...me-desktop.iso

[Vaipan]

I had a huge issue with this update too and tried EVERYTHING. I didn't know if it was the update, but you guys confirmed it. Finally, I found something that worked.

For some reason, the CPU multiplier is limited to defaults. If you move it past the defaults, the OS will move it back to defaults. However, when you up the Bus / Strap, you can still overclock within that initial multiplier range.

So for example, on my 6900k, CPU won't overclock past 37x on 100mhz strap no matter my BIOS settings. But when I up my bus to 125, I can use 36 multiplier and get 4.5ghz. This seems to be the only limit. Checking all of my hardware monitors so far, and the multiplier seems to be the only limit. I am totally unfamiliar with overclocking on 125 bus, but everything is stable right now after stress testing and I was even able to increase my OC from 4.4 to 4.5 (not as a result of the update, just as a result of me messing with my OC for the first time in forever).

So if you want a work around, you'll have to up your strap to 125 or whatever you choose. My OC works fine for now, but holy ****, they should have sent us a ****ing warning. What a waste of time.

[SSJ3Weasel]

I had a huge issue with this update too and tried EVERYTHING. I didn't know if it was the update, but you guys confirmed it. Finally, I found something that worked.

For some reason, the CPU multiplier is limited to defaults. If you move it past the defaults, the OS will move it back to defaults. However, when you up the Bus / Strap, you can still overclock within that initial multiplier range.

So for example, on my 6900k, CPU won't overclock past 37x on 100mhz strap no matter my BIOS settings. But when I up my bus to 125, I can use 36 multiplier and get 4.5ghz. This seems to be the only limit. Checking all of my hardware monitors so far, and the multiplier seems to be the only limit. I am totally unfamiliar with overclocking on 125 bus, but everything is stable right now after stress testing and I was even able to increase my OC from 4.4 to 4.5 (not as a result of the update, just as a result of me messing with my OC for the first time in forever).

So if you want a work around, you'll have to up your strap to 125 or whatever you choose. My OC works fine for now, but holy ****, they should have sent us a ****ing warning. What a waste of time.

Most people dont like to OC using bus due to it messing with other hardware and can cause things not to run right, we shouldn't have to use bus OCing to fix something the updates shouldn't brake something, I let it slide with the KB4100347 but the 1809 update is also doing this and this is unsatisfactory, Asus and/or Windows needs to fix this issue I'm not going to spend this much money on something and not be able to use the features that I'm suppose to have.

[Mr. Fox]

A few days ago I made the mistake of leaving Windows Update enabled and that same effed up KB4100347 cancer code from Micro$lop really screwed up my 7960X performance. My BIOS setting for the core ratio was being ignored (not syncing all cores) and only Core #0 was overclocking to the 51x value I set. The other 15 cores would only run 42x. I could override it temporarily in Windows with XTU, TurboV Core or AI Suite. Sometimes I had to change and apply core ratio values 2 or 3 times before it would take. It really was driving me nuts. I finally just said screw it and diskparted the SSD and restored my Windows 10 Enterprise 2016 LTSB image with no updates allowed and it instantly restored proper functionality. Uninstalling that update did not help.

But, it's all back to normal now. I've never cared about the "security" update crap, and now I care even less. No way I am sacrificing functionality just because an extremely remote risk exists. Crossing the street is dangerous, and so is driving and flying in an airplane. Just not worth losing any sleep over. I'm more than happy to take my chances with the digital baba yaga rather than allowing my CPU performance to be impaired.