Windows Client Guidance against speculative execution vulnerabilities

Page 42 of 75 FirstFirst ... 32404142434452 ... LastLast

  1. Posts : 3,453
       #410

    Here's mine... what am I looking for? Just wondering as apparently Skylake is more difficult to patch

    Windows Client Guidance against speculative execution vulnerabilities-capture.png
      My Computer


  2. Posts : 2,832
    Windows 10 Pro X64
       #411

    Hi,
    @Superfly : Apparently your CPU is using microcode that Intel recommends not to use.
    See Microcode Update guidance from Intel.
    OTOH, if you do not experience unexpected reboots then I'd leave well enough alone.

    Cheers,
      My Computers


  3. Posts : 2,832
    Windows 10 Pro X64
       #412

    Hi,

    (in order of ascending age).
    I don't know the capabilities of the first one; it might support BIOS recovery. The other two do not. I think the only option for recovery of a failed BIOS upgrade would be replacement of the BIOS chip with a working one.
    Not even a jumper setting on the MB that allows factory restore of the BIOS then ? Those machines aren't even that old really.

    Cheers,
      My Computers


  4. Posts : 3,453
       #413

    fdegrove said:
    Hi,
    @Superfly : Apparently your CPU is using microcode that Intel recommends not to use.
    See Microcode Update guidance from Intel.
    OTOH, if you do not experience unexpected reboots then I'd leave well enough alone.

    Cheers,
    Hmmm... nothing untoward thus far, but thanx for the heads-up!
      My Computer


  5. Posts : 2,324
    Win10
       #414

    pokeefe0001 said:
    The motherboards of my 3 computers are
    1. Notebook W65_67SZ BIOS AMI Version 1.03.05 Date 2/26/2014
    2. ASUST Z87-A Rev 1 BIOS AMI Version 1504 Date 10/3/2013
    3. Gigabyte X58A-UD3R BIOS Award Software Version Fh3 Date 8/4/2011

    (in order of ascending age).
    I don't know the capabilities of the first one; it might support BIOS recovery. The other two do not. I think the only option for recovery of a failed BIOS upgrade would be replacement of the BIOS chip with a working one.

    I could be wrong but I doubt I'm the only one in the world with BIOS that is not worth its salt.
    @pokeefe0001

    I have no#3 too, Revision 2 of it , running an Old modded Bios from TweakTown.... mod 2_fh .... so am in the same boat Currently but the MB has Gigabyte's Dual Bios ( only see on page 8 of the Manual) , there is no way to access the 2nd bios though it will have whatever the Board originally came with in it , I also have an older EP45_UD3P and it has saved me there twice in the past , the issue with that MB is the newer Bios require a 2mb Bios which can only be done in Windows via @VGA the 1st time (subsequent bios can be done normally) which is a bit nerve wracking.... it is supposed to all happen automatically but there are a couple of ways to try and force it if needed.

    --GIGABYTE--DUAL BIOS WEB

    Recover from GIGABYTE Backup BIOS (Only for motherboards with Dual BIOS technology)
    Method #1:

    1. Shut off the powersupply by pressing the button on the ”PSU” or by removing the power cable.
    2. Press the powerbutton 3-4 times to empty the stored energy in the power supply.
    3. Turn on the powersupply
    4. Press and hold the powerbutton, the system will start the bootup procedure but will shut down after a few second. Release the powerbutton after the system have shut down completely.
    5. Press the powerbutton to start the system.
    6. If this technique was successful the system will boot and you will see the following image.

    Method #2:

    1. Shut your PC down.
    2. Hold the power AND the reset button for about 10 sec, than release.
    3. Backup BIOS should kick in anytime soon now.

    Method #3:

    1. Short out pins 1 and 6 on the main BIOS chip (pin #1 should be marked with a red dot or whatever)
    2. Tell a friend (or a relative) of yours to press the power on button
    3. Remove the ghetto-like jumper you’re holding between pins 1 and 6 as soon as you hear a beep.
    4. Backup BIOS should kick in again and everything will (hopefully) be fine.


    If you still cannot get the system to boot please try with another graphics card (internal graphics should also be tested if available), test another CPU/APU and different memory modules. If the system is still not booting up, then please request RMA for the motherboard.
    Last edited by Kbird; 14 Aug 2018 at 23:32.
      My Computers


  6. Posts : 720
    Win10 x64 Pro - 2 desktops, 2 laptops
       #415

    fdegrove said:
    Not even a jumper setting on the MB that allows factory restore of the BIOS then ? Those machines aren't even that old really.
    Hmm. I'll look into that. I was just looking at the capabilities of the BIOS upgrade procedure and saw there was no support for a backout to a previous version - no multiple version support.
      My Computer


  7. Posts : 2,324
    Win10
       #416

    Superfly said:
    Here's mine... what am I looking for? Just wondering as apparently Skylake is more difficult to patch
    It maybe worth checking the CPUID against the PDF I posted , I was surprised I had a Haswell-EP 5820K not a "Extreme Processor" 5820K as I thought.

    Coretemp and Speecy will show the CPUID ............CPUz doesn't show the Code only the Name...

    KB
    Attached Thumbnails Attached Thumbnails Windows Client Guidance against speculative execution vulnerabilities-14.jpg  
      My Computers


  8. Posts : 2,666
    Windows 11 21H2 (22000.593)
       #417

    Kbird said:
    You can Check what version MicroCode Windows 10 is Using , and it may not be the one in the Bios , the CPU will use whichever one it Deems Newer automatically apparently ...... eg the OS's version maybe different...
    .
    .

    I found this Info ...surprisingly in a Post at FireFox as version 57 has some issues on Mobile Broadwell Chips..

    I am on 3A not the Bios version which is 38 and 3A is the currently recommend one from Intel. ( see PDF below )

    Thought I'd add this How Too here for Others use too :
    -----------------------------------------------------------------------------------------------------------------------------

    To see the processor micro architecture and which microcode revision is in use by Windows ,

    from an admin command prompt run this command :

    reg query HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0

    --The line labeled "VendorIdentifier" shows the CPU vendor (GenuineIntel for Intel or AuthenticAMD for AMD).

    --The line labeled "Identifier" gives the microarchitecture as three numbers: "Family", "Model" and "Stepping".
    -----These are relevant in identifying if a particular CPU bug may be relevant to the CPU in your computer.---

    --The line labeled "Update Revision" shows the current microcode revision (for the particular microarchitecture) with zeros on both sides.
    ------ For example, Update Revision REG_BINARY 000000001E000000 means that the revision is 1E (hexadecimal).

    --The line labeled "Previous Update Revision" shows the microcode revision loaded from BIOS.

    See Sample Image below.........

    ***You can also Open RegEdit and goto the specified Reg. Key above and look without using the Command Prompt.


    -----------------------------------------------------------------------------------------------------------------------------
    Would you mind posting the link to the original post where you found this info?

    Windows Client Guidance against speculative execution vulnerabilities-microcode-revision.png

    Windows Client Guidance against speculative execution vulnerabilities-microcode-revision-1.png

    As you can see, I don't have any leading zeroes. Furthermore, the PDF you supplied (direct link from Intel would be fantastic, in case they make changes to it that this copy will not have) only goes back to Sandy Bridge CPUs - mine is older, a Bloomfield (Core i7 965 EE) and thus I (would normally) suspect that they have not released an update.

    However, if you go to download the Linux* Processor Microcode Data File from Download Linux* Processor Microcode Data File you can see in the list where my CPU is listed as being a valid CPU for the update.

    Furthermore, if you visit this support page for my CPU, Downloads for Intel® Pentium® Processor Extreme Edition 965 (4M Cache, 3.73 GHz, 1066 MHz FSB) - you can see the Linux* Processor Microcode Data File listed multiple times. So, microcode updates for my CPU are available, so that PDF is either incomplete, or there is more information that users of older, legacy equipment need to know as well.

    Finally, that PDF was released after the newest microcode from 18 Jan was posted - but that microcode has been removed from download - I suspect because of the issues that it led to. I happen to have a copy of it on my machine (and it is different from the one released in Nov 2017).

    Since I have both files, (and the ability to download others from Intel) I can actually compare the different microcode files (94 in the Nov 2017 release, if I am reading the .ZIP file structure correctly) and actually verify if anything has been changed - as soon as I figure out which one is for my CPU.

    pokeefe0001 said:
    The motherboards of my 3 computers are
    1. Notebook W65_67SZ BIOS AMI Version 1.03.05 Date 2/26/2014
    2. ASUST Z87-A Rev 1 BIOS AMI Version 1504 Date 10/3/2013
    3. Gigabyte X58A-UD3R BIOS Award Software Version Fh3 Date 8/4/2011

    (in order of ascending age).
    I don't know the capabilities of the first one; it might support BIOS recovery. The other two do not. I think the only option for recovery of a failed BIOS upgrade would be replacement of the BIOS chip with a working one.

    I could be wrong but I doubt I'm the only one in the world with BIOS that is not worth its salt.
    Actually, after older 486 boards the OEMs started offering flash utilities to reprogram the EEPROMs that stored the BIOS info. But almost every BIOS I've ever worked with (and on legacy machines, from 496 through Core i7 1st generation machines) had the BIOS reset to default values in the BIOS itself. However, depending upon what choices your BIOS offers, a value change (particularly like one that changes your SATA drive drive loading from AHCI to 'standard' / IDE) may (and most likely will, if you're running Windows) render your machine unable to boot at all.

    fdegrove said:
    Hi,



    Not even a jumper setting on the MB that allows factory restore of the BIOS then ? Those machines aren't even that old really.

    Cheers,
    ^^^^ This. Most machines offered this as well, and some not so old (like mine) had button on the motherboard to power on and off the board and reset the CMOS (and also used a jumper to do the same, just in case). But I can also reset to default values from within the BIOS itself.
      My Computers


  9. Posts : 2,666
    Windows 11 21H2 (22000.593)
       #418

    Everything you never wanted to know about the BIOS:

    BIOS - Wikipedia

    Yeah, you can say what you want about WikiPaedia - but the links at the end are real links....and that is where the information comes from.
      My Computers


  10. Posts : 3,352
    Windows 10 Pro x64
       #419

    This is the Kaby Lake CPU in one of my PCs:

    Windows Client Guidance against speculative execution vulnerabilities-cpu-security.jpg

    Anybody know exactly which lines(s) refer to MCU? Intel Microcode Revision Guidance says 80 shouldn't be used, but 0x70 should. This PC should be OK since I just got a new BIOS update about a week ago that supposedly addresses Meltdown and Spectre. But I have a couple of others I need to check.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:30.
Find Us




Windows 10 Forums