Skylake / Kaby Lake Hyper-threading bug

Discussion in 'Hardware Components and Aftermarket Upgrades' started by Assembler, Jun 26, 2017.

  1. hacktrix2006

    hacktrix2006 Notebook Evangelist

    Reputations:
    216
    Messages:
    623
    Likes Received:
    384
    Trophy Points:
    76
    I have always been respectful when I have stepped out of line I have apologised. When I have placed in support tickets I have been polite. In fact I let them know of the issue as soon as I found out and even pointed them the right way to the information. Unless they have said something to you very differently. Yes things have been heated at times but what was meant to be expected after a promise which was the main reason to purchase there product after years of saving up and nearly a year of research.

    At the same time they can't really leave a system in a flawed state either where data loss can occur.

    I can't sell the system as no one will buy it due the resale value being smashed with the MXM issue(s). So either way for me it seems it's a loose loose.

    Sent from my pa_osprey using Tapatalk
     
    Vasudev and hmscott like this.
  2. Papusan

    Papusan JOKEBOOKS = That sucks! Dont wast your $ on FILTHY

    Reputations:
    15,521
    Messages:
    19,893
    Likes Received:
    31,187
    Trophy Points:
    931
    They all would probably fix it, if the problem was similar as Superfish Vulnerability:rolleyes: Loss of data ain't importent enough!! @hmscott @Phoenix :rolleyes:
     
    Vasudev, Ultra Male and Robbo99999 like this.
  3. hacktrix2006

    hacktrix2006 Notebook Evangelist

    Reputations:
    216
    Messages:
    623
    Likes Received:
    384
    Trophy Points:
    76
    @Papusan If it was something like SuperFish it would solely depend if the OEM in question was caught out, in case of Lenovo they was caught out so they had no choice but to patch it out due to the up roar. It also not Lenovo first time either being caught out either with something fishy. Just look at their Whitelisting of Wifi cards and charging a premium for the same card as a standard OEM but with a Lenovo ID in the firmware instead that caused a stink and still does to this day.
     
    Vasudev, hmscott and Papusan like this.
  4. plee82

    plee82 Notebook Evangelist

    Reputations:
    92
    Messages:
    502
    Likes Received:
    356
    Trophy Points:
    76
    Another microcode patch for gt62vr. Now it is BE.
     
    Vasudev and hmscott like this.
  5. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    4,141
    Messages:
    7,260
    Likes Received:
    4,860
    Trophy Points:
    431
    It should be BA since it fixes HT bug completely. BE microcode is temporary fix for HT bug on 6700hq.
     
  6. plee82

    plee82 Notebook Evangelist

    Reputations:
    92
    Messages:
    502
    Likes Received:
    356
    Trophy Points:
    76
    It actually updated from BA to BE.
     
  7. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    4,141
    Messages:
    7,260
    Likes Received:
    4,860
    Trophy Points:
    431
    Which is your CPU, 6700HQ or 6820HK? On 6700HQ, BA is latest microcode revision for 6700HQ whilst BE is a superseded by BA. You can use UBU or similar to check the latest microcode.
     
  8. plee82

    plee82 Notebook Evangelist

    Reputations:
    92
    Messages:
    502
    Likes Received:
    356
    Trophy Points:
    76
    6700HQ. Well, that is what the BIOS update did.
     
    Vasudev likes this.
  9. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    4,141
    Messages:
    7,260
    Likes Received:
    4,860
    Trophy Points:
    431
    hmscott likes this.
  10. plee82

    plee82 Notebook Evangelist

    Reputations:
    92
    Messages:
    502
    Likes Received:
    356
    Trophy Points:
    76
    hmscott likes this.
Loading...

Share This Page