• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Intel bug incoming? Meltdown and Spectre exploits

It's not seeing the CVE-2017-5715 compatible microcode update.

Should look like this :
Meltdown.png


That's from a ThinkPad with i7-6500u and updated EFI.
 
...
Spectre can only be completely fixed in hardware.
I imagine AMD are running around like headless chickens trying to figure out if they can do anything to mitigate Spectre in Pinnacle Ridge before its release, but I bet it's too late for that. Unless of course they've already fixed it (since Intel and AMD are both supposed to have known about this stuff for months) and are keeping tight-lipped, but I don't see why they wouldn't shout it from the rooftops?
 
The response I got from MSI when asking for a new BIOS...

Regarding your concern, thanks for contacting us. In this case, the issue will not affect Z77 MB, thus please don't worry about it. Thanks!
 
The response I got from MSI when asking for a new BIOS...

Oh rly MSI.

I have a Z77 mobo (Gigabyte) and a 3570k. Are they basically saying I am immune to these vulnerabilities....

I think what they are saying is "the board is too old, we aren't going to patch it".

Last BIOS for my board was 2014 and then before that 2012. Not expecting any new BIOS.
 
The response I got from MSI when asking for a new BIOS...
Regarding your concern, thanks for contacting us. In this case, the issue will not affect Z77 MB, thus please don't worry about it. Thanks!
Well that's a lie. Not very good from MSI. Although to be fair, I don't think the other vendors will do anything about systems of this age either. There is even a question mark over my X99 board and others which came out 2-3 years ago.
 
Last edited:
Well that's a lie. Not very good from MSI. Although to be fair, I don't think the other vendors will do anything about systems of this age either. There is even a question mark over my X99 board and others which came out 2-3 years ago.

MSI's attitude as always is to deny or sweep under the carpet anything that might damage the sales of their product rather than providing decent support.

You only have to look at the level of fail in the following MSI forum thread regarding this security vulnerability to see how several forum mods try to silence users who ask awkward to answer questions, to the extent they are reminded of the forum rules in a way to try and silence people from anything that might be construed as complaining or stating that the thread has been essentially moved to a junk category where it won't get seen. The lack of basic IT understanding by some of the mods is astounding. Even when you ask tech support directly by opening a ticket, different people get very different answers from them, eg one was told their Z77A-G45 would be patched and someone else with a Z87 chipset board was told it was too old.

https://forum-en.msi.com/index.php?topic=297707.0

Something else I took away from that thread is the previous suggestion in our thread here was a solution using a VMware microcode update driver to inject the newest microcode into the Windows OS. It seems this occurs to late for the OS to recognise it and appears you have to have this in the BIOS so that it gets picked up at system boot up.

There are tools available to modify a BIOS file to do the update and as I suspected some capable end users I think will step up and share as someone in the above MSI thread has for the Z87-GD65 but really I think MSI should be doing this. Intel need to work closer with motherboard manufacturers to ensure they do.

I think the response from different motherboard manufacturers and device manufacturers such as laptops and pre-built PC's will vary and I for one will be taking note of it when buying my next hardware.
 
MSI's attitude as always is to deny or sweep under the carpet anything that might damage the sales of their product rather than providing decent support.

You only have to look at the level of fail in the following MSI forum thread regarding this security vulnerability to see how several forum mods try to silence users who ask awkward to answer questions, to the extent they are reminded of the forum rules in a way to try and silence people from anything that might be construed as complaining or stating that the thread has been essentially moved to a junk category where it won't get seen. The lack of basic IT understanding by some of the mods is astounding. Even when you ask tech support directly by opening a ticket, different people get very different answers from them, eg one was told their Z77A-G45 would be patched and someone else with a Z87 chipset board was told it was too old.

https://forum-en.msi.com/index.php?topic=297707.0

Something else I took away from that thread is the previous suggestion in our thread here was a solution using a VMware microcode update driver to inject the newest microcode into the Windows OS. It seems this occurs to late for the OS to recognise it and appears you have to have this in the BIOS so that it gets picked up at system boot up.

There are tools available to modify a BIOS file to do the update and as I suspected some capable end users I think will step up and share as someone in the above MSI thread has for the Z87-GD65 but really I think MSI should be doing this. Intel need to work closer with motherboard manufacturers to ensure they do.

I think the response from different motherboard manufacturers and device manufacturers such as laptops and pre-built PC's will vary and I for one will be taking note of it when buying my next hardware.

Linux has the ability to load microcode without updating the BIOS. In fact I am able to toggle the microcode on and off in real time in the Ubuntu proprietary drivers section. I don't know why Windows cannot do similar.
 
Is it a bad idea to get an 8700k then in the light of this bug?

I think anyone looking to upgrade right now should wait, #A because reviewers are still getting to grips with the performance impact of Coffeelake so we still don't know the full extent of it and #B because Ryzen 2 will be here soon and it looks like it will close the gap to Intel's Mhz difference.
 
I am not patching take the passwords i have fraud insurance and authenticators. No sir all the yummy 2fps more for me hopefully but i like to live on the edge. And i been hacked before and i got right back up. Because that is what makes back to back 95 96 two time champs.

And in my world 2fps can be the difference between being number one, Or being number no-one...
 
I am not patching take the passwords i have fraud insurance and authenticators. No sir all the yummy 2fps more for me hopefully but i like to live on the edge. And i been hacked before and i got right back up. Because that is what makes back to back 95 96 two time champs.

And in my world 2fps can be the difference between being number one, Or being number no-one...

Huh?
 
Back
Top Bottom