Leoplate25 wrote:
Hi, i did what Da-BOSS posted and RWEverything and HWINFO64 show "BA" microcode, so i updated it, i think, because my BIOS keeps showing "9E". I have an i7-6700k (Intel64 Family 6 Model 94 Stepping 3) on an ASUS Z170 Sabertooth S. Can someone tell me if it's ok? Thanks!!!
i used this
http://www.win-raid.com/t154f16-Tool-Guide-News-quot-UEFI-BIOS-Updater-quot-UBU.html
I did it!!! I put the usb stick in the usb 3.0 port and it flashed the BIOS. Sooo scared because it takes too long and 3 restarts. Thanks to everybody who gave me a hand with this!!!
Korth wrote:
@eldata,
No, not quite yet, lol.
For SKL desktop SKUs yes, since Apr2017 (as we already know from the OP links in this thread).
For KBL desktop SKUs no, not yet. Intel is still dragging their feet. ASUS will get their chance to drag their feet once Intel passes the ball to them.
And CFL is, of course, an 8th gen refinement of 7th gen KBL which is itself a refinement of 6th gen SKL, they run off very much the same microarchitecture and microcode steppings (at least we know SKL and KBL do, CFL is not yet available for examination).
The latest info *from Intel* that I could find:
https://communities.intel.com/thread/115745
https://communities.intel.com/message/483358
Legolas (28Jun2017): "Does this issue effect Desktop Skylake processors and Kabylake processors? I hope Intel is looking into it."
Intel Corporation (28Jun2017): "Hi Legolas, This also affects the desktop processors; however, Intel is currently working on a solution, once available, it will be published. Best Regards, Juan V."
Intel Corporation (29Jun2017): "Hi Legolas, The likelihood of running into this issue is low. A [Skylake] fix for this issue is available and started rollout out to system manufacturers in April 2017. Intel recommends checking to make sure your BIOS is up to date. Best Regards, Juan V."
Do you have links to anything *from Intel* which state otherwise? Better yet, a link *from Intel* to a fix for my Kaby Lake CPUs?
It's worth noting that Intel discourages code complexes which create the specific conditions that cause this bug to manifest. NVIDIA is already working out other bugs in their drivers (which create high interrupt latencies when Hyperthreading) and might choose to also avert Intel's HT bug by simply compiling their binaries with different (or differently ordered) instructions, commands, and registers - so in this example, if NVIDIA chooses to implement this fix, the Intel HT bug wouldn't be invoked by running NVIDIA code (or by running game engines built onto it). I've installed patches for Autodesk, Solidworks, and SIMUL8 which also circumvent this Intel HT bug in those apps. Although the proper fix for Windows users is an Intel firmware update because no one really knows exactly how WinOS components really behave at the system hardware level, lol, otherwise there's still always a small chance for a stray unfixed app to "seriously compromise" the entire system.
