Meltdown, Spectre Patch Is Making Some Old AMD PCs Unbootable

Some AMD system owners reported that the latest Windows patches, which include the fixes for the Meltdown and Spectre CPU flaws, have been bricking their computers. Following these reports, Microsoft decided to halt the updates until it tracks down the issues and makes the necessary changes.

Latest Videos FromTom's Hardware
Contributor

Lucian Armasu is a Contributing Writer for Tom's Hardware US. He covers software news and the issues surrounding privacy and security.

  • gdmaclew
    This is highly suspect.
    Microsoft is blaming AMD for not providing them with the proper documentation?
    Since most of the reports I have seen narrow the problem CPUs to older ones, I find it hard to believe that Microsoft didn't have detailed documentation of those CPU's years ago.
    And the flaw(s) were discovered months ago. They just didn't go public until a few days ago.
    Plus I also read reports that Microsoft is sending "fixes" for the Meltdown bug to users of AMD CPU's when AMD CPU's are NOT susceptable to that particular bug/flaw.
    Microsoft had a brain cramp and now is trying to weasel out of it.
    Wouldn't be the first time.
    Plus all this "knee-jerk" low-information response by some tech media outlets (and business ones too) are having an adverse effect on AMD stock prices.
    And Microsoft stock is UP? Why?
    It will be very interesting to see what happens down the road when this is settled out.
    Methinks I smell a rat.
    Reply
  • Kennyy Evony
    Intel, AMD, and microsaft need to be combined into one company and forced to work together to create a single product so none of them can sabotage their income.
    Reply
  • William_X89
    So you want less competition and higher prices Kennyy?
    Reply
  • chibiwings
    microsoft doesn't want to spend money patching i guess. on Old Systems and OS.
    Reply
  • jam.vanduyn
    https://answers.microsoft.com/en-us/windows/forum/windows_7-update/stop-0x000000c4-after-installing-kb4056894-2018-01/f09a8be3-5313-40bb-9cef-727fcdd4cd56 works for me !
    Reply