Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Intel's Skylake and Kaby Lake CPUs have nasty microcode bug

  • Please log in to reply
3 replies to this topic

#1 JohnC_21


  • Members
  • 22,103 posts
  • Gender:Male
  • Local time:12:58 PM

Posted 26 June 2017 - 06:46 AM

During April and May, Intel started updating processor documentation with a new errata note, and over the weekend we learned why: Skylake and Kaby Lake silicon has a microcode bug.

The erratum is described in detail on the Debian mailing list, and affects Skylake and Kaby Lake Intel Core processors (in desktop, high-end desktop, embedded and mobile platforms), Xeon v5 and v6 server processors, and some Pentium models.

The Debian advisory says affected users need to disable hyper-threading “immediately” in their BIOS or UEFI settings, because the processors can “dangerously misbehave when hyper-threading is enabled.”

Symptoms can include “application and system misbehaviour, data corruption, and data loss”.

Henrique de Moraes Holschuh, who authored the Debian post, notes that all operating systems, not only Linux, are subject to the bug.



BC AdBot (Login to Remove)



#2 Drillingmachine


  • Members
  • 2,287 posts
  • Gender:Male
  • Local time:06:58 PM

Posted 26 June 2017 - 07:45 AM

Not microcode bug but bug in processor itself that probably can be fixed with microcode update.

#3 hamluis



  • Moderator
  • 55,020 posts
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:58 AM

Posted 26 June 2017 - 08:37 AM




Edited by hamluis, 26 June 2017 - 08:42 AM.

#4 britechguy


    Been there, done that, got the T-shirt

  • Moderator
  • 6,531 posts
  • Gender:Male
  • Location:Staunton, VA
  • Local time:12:58 PM

Posted 26 June 2017 - 09:13 AM

And this is yet another example of why I routinely install UEFI/BIOS updates and encourage others to do so as well.


Fixes for problems such as this one, that can be ticking time bombs and that many will have no idea even exist, get included in those updates.  It's a situation where "if it ain't broke, don't fix it" isn't necessarily applicable.

Brian  AKA  Bri the Tech Guy (my website address is in my profile) Windows 10 Home, 64-bit, Version 1709, Build 16299


    Here is a test to find out whether your mission in life is complete.  If you’re alive, it isn’t.
             ~ Lauren Bacall


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users