Page 19 of 70 FirstFirst ... 9 17 18 19 20 21 29 69 ... LastLast
Results 181 to 190 of 693
  1. #181
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    5

    Quote Originally Posted by firefox2026 View Post
    Then I found this python tool to convert the binary to .dat file. https://github.com/bgw/bdw-ucode-upd...pts/bin2dat.py

    Then I re-installed the Vmdriver with that dat file.. Now I see that the CPU microcode updates and I have the hardware support showing up now. However windows isn't enabling it because of the microcode is not updated before the boot up. That is why in order for the driver way to work we need some way to get windows to enable the fix support on the fly or some manual way of enabling it. If not then this way is pretty much a dead horse. Which is a shame cause this would at least let people with older systems keep running without a BIOS fix.
    At first, thank you for the URL to the binary2ascii microcode converter!

    Two questions:

    1) Did you try to restart computer? MIcrocode could survive during this process.
    2) Do you have registry keys (https://support.microsoft.com/en-ca/...tive-execution), which explicitly enable MS update?
    3) Could you please show the output of Get-SpeculativeControlSettings?

  2. #182
    ROG Guru: White Belt Array Margus PC Specs
    Margus PC Specs
    MotherboardAsus Maximus hero VII
    Processor4790K
    Memory (part number)CMD16GXM2A2400C10
    Graphics Card #1MSI GTX 970 Gaming 4g
    Sound CardSB Recon 3D
    MonitorBENQ 2411Z
    Storage #1samsung 850 evo
    CPU CoolerLIQMAX 2 240
    Power SupplySeasonic X Platinum 1050w
    OS Windows 10 HOME

    Join Date
    Sep 2014
    Reputation
    10
    Posts
    86

    I not expect any update and did it myself. I havE z97 maximus hero VII i paid lot but asus told its 5 years old and no updates planned anymore witch is bad thinking for sutch issue.

    Click image for larger version. 

Name:	unknown.png 
Views:	9 
Size:	67.4 KB 
ID:	70375

    Here is bios for M7H i made its highly optmized for my needs so your own risks but if it work for me whay not to othes use flashback from usb stick while pc is off. Tested only devils rest cpus idk. Might its haswell devils canyon only for broadw i not updated microcode.

    https://drive.google.com/open?id=1d6...wkk02QYnqe3O9e
    Last edited by Margus; 01-10-2018 at 02:51 PM.

  3. #183
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    6

    Why are the BIOS updates for ROG STRIX X299-E GAMING late? I heard that ASUS were releasing BIOS updates for X299 boards yesterday, but the ASUS support/download page for ROG STRIX X299-E GAMING boards has not been updated with BIOS 1102 yet as advertised here https://www.asus.com/News/V5urzYAT6myCC1o2

    So, where can I obtain BIOS version 1102?

  4. #184
    ROG Guru: White Belt Array ELIESEH PC Specs
    ELIESEH PC Specs
    MotherboardASUS ROG STRIX X99 GAMING
    ProcessorIntel® Core™ i7-6900K
    Memory (part number)CMK32GX4M4A2400C14
    Graphics Card #1ROG-STRIX-GTX1080TI-O11G
    MonitorACER XB271HU
    Storage #1Samsung SSD 960 EVO 256 GB
    Storage #2Samsung SSD 850 EVO 500 GB
    CPU CoolerHydro Series™ H115i
    CaseNZXT Phantom 820
    Power SupplyCooler Master V1000
    Keyboard Razer BlackWidow Chroma V2
    Mouse Razer DeathAdder Elite
    Headset ASUS Cerberus
    Mouse Pad QcK
    OS Windows 10 Pro
    Network RouterASUS RT-N66U

    Join Date
    Jun 2017
    Reputation
    42
    Posts
    107

    Scottish CAMINO

    Quote Originally Posted by donavanbadboy View Post
    Why are the BIOS updates for ROG STRIX X299-E GAMING late? I heard that ASUS were releasing BIOS updates for X299 boards yesterday, but the ASUS support/download page for ROG STRIX X299-E GAMING boards has not been updated with BIOS 1102 yet as advertised here https://www.asus.com/News/V5urzYAT6myCC1o2

    So, where can I obtain BIOS version 1102?
    SAME HERE for the X99 STRIX, Still BIOS 1801 on the driver Asus download page, where is the bios 1901 ?!!

  5. #185
    ROG Enthusiast Array SumTingWong PC Specs
    SumTingWong PC Specs
    MotherboardASUS Maximus Vii Hero Z97
    Processori7 4790k @ 4.5Ghz
    Memory (part number)Corsair Red Vengeance Red 32GB DDR3
    Graphics Card #1ASUS Strix GTX 970
    Sound CardN/A
    MonitorASUS 27' 1080P
    Storage #1Samsung 256GB 850 EVO SSD
    Storage #2Seagate 1TB HDD + WD 2TB HDD
    CPU CoolerNoctua NH D15S
    CaseCorsair 750D
    Power SupplyEVGA G2 850W
    Keyboard Razer 2015
    Mouse Razer 2015
    Headset Walmart headset
    Mouse Pad N/A
    Headset/Speakers LogicTech $30 speaker from Walmart
    OS Windows 10 64 bit

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    57

    tourist000

    Quote Originally Posted by ELIESEH View Post
    SAME HERE for the X99 STRIX, Still BIOS 1801 on the driver Asus download page, where is the bios 1901 ?!!
    Intel vows to stop Meltdown and Spectre by end of January, so let's see if they keep their vows to us consumers. http://www.techradar.com/news/intel-...end-of-january

    In the article news, Intel CEO said " The company's CEO Brian Krzanich used the opening moments of the keynote to promise that the company would patch 90% of affected processors made in the past five years by the end of this week. From there, the following 10% of vulnerable processors will see fixes by the end of the month."

    So I suggest everyone to wait and be patient ( at least I am patient right now) for the official BIOS push out from the motherboard vendor. As Intel said, in order to exploit Meltdown and Spectre, you need to visit a malicious site then download, install, and run the malicious application. Usually, your antivirus will stop it in the first place.
    Last edited by SumTingWong; 01-10-2018 at 05:05 PM.

  6. #186
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    12

    Quote Originally Posted by AndyU View Post
    At first, thank you for the URL to the binary2ascii microcode converter!

    Two questions:

    1) Did you try to restart computer? MIcrocode could survive during this process.
    2) Do you have registry keys (https://support.microsoft.com/en-ca/...tive-execution), which explicitly enable MS update?
    3) Could you please show the output of Get-SpeculativeControlSettings?
    I also used the new latest linux module that intel came out with and the microcode was a newer version than what I got out of the debian build.

    1)So far when I restart the computer the driver updates the CPU microcode and I check it with the SIW tool.

    2) I tried to update the registry keys and that didn't seem to help.

    3)

    PS C:\script\SpeculationControl> Get-SpeculationControlSettings
    Speculation control settings for CVE-2017-5715 [branch target injection]

    Hardware support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is enabled: False
    Windows OS support for branch target injection mitigation is disabled by system policy: False
    Windows OS support for branch target injection mitigation is disabled by absence of hardware support: False

    Speculation control settings for CVE-2017-5754 [rogue data cache load]

    Hardware requires kernel VA shadowing: True
    Windows OS support for kernel VA shadow is present: True
    Windows OS support for kernel VA shadow is enabled: True
    Windows OS support for PCID performance optimization is enabled: True [not required for security]

    Suggested actions

    * Follow the guidance for enabling Windows Client support for speculation control mitigations described in https://support.microsoft.com/help/4073119


    BTIHardwarePresent : True
    BTIWindowsSupportPresent : True
    BTIWindowsSupportEnabled : False
    BTIDisabledBySystemPolicy : False
    BTIDisabledByNoHardwareSupport : False
    KVAShadowRequired : True
    KVAShadowWindowsSupportPresent : True
    KVAShadowWindowsSupportEnabled : True
    KVAShadowPcidEnabled : True

  7. #187
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    6

    Quote Originally Posted by SumTingWong View Post
    So I suggest everyone to wait and be patient
    But ASUS have already announced some BIOS updates as per https://www.asus.com/News/V5urzYAT6myCC1o2 which should have been released yesterday.

  8. #188
    ROG Enthusiast Array SumTingWong PC Specs
    SumTingWong PC Specs
    MotherboardASUS Maximus Vii Hero Z97
    Processori7 4790k @ 4.5Ghz
    Memory (part number)Corsair Red Vengeance Red 32GB DDR3
    Graphics Card #1ASUS Strix GTX 970
    Sound CardN/A
    MonitorASUS 27' 1080P
    Storage #1Samsung 256GB 850 EVO SSD
    Storage #2Seagate 1TB HDD + WD 2TB HDD
    CPU CoolerNoctua NH D15S
    CaseCorsair 750D
    Power SupplyEVGA G2 850W
    Keyboard Razer 2015
    Mouse Razer 2015
    Headset Walmart headset
    Mouse Pad N/A
    Headset/Speakers LogicTech $30 speaker from Walmart
    OS Windows 10 64 bit

    Join Date
    Jan 2018
    Reputation
    10
    Posts
    57

    Quote Originally Posted by donavanbadboy View Post
    But ASUS have already announced some BIOS updates as per https://www.asus.com/News/V5urzYAT6myCC1o2 which should have been released yesterday.
    ASUS probably testing it again to make sure everything is fine before push it out?

  9. #189
    New ROGer Array
    Join Date
    Jan 2018
    Reputation
    10
    Posts
    6

    Quote Originally Posted by SumTingWong View Post
    ASUS probably testing it again to make sure everything is fine before push it out?
    You are correct, I am being impatient, but as someone who knows enough about Spectre and Meltdown to write PoC "working" exploits in a test environment I realise the true seriousness of the problem.

    Making sure your AV is up to date and being generally cautious about which web sites you visit is not good enough.

    I hope ASUS push out microcode updates from Intel in short order for every applicable product they have ever made, and ASUS should (if possible) sue Intel for the costs.

  10. #190
    Administrator Array Silent Scone@ASUS's Avatar
    Join Date
    Mar 2016
    Reputation
    124
    Posts
    1,798

    Quote Originally Posted by firefox2026 View Post
    I also used the new latest linux module that intel came out with and the microcode was a newer version than what I got out of the debian build.

    1)So far when I restart the computer the driver updates the CPU microcode and I check it with the SIW tool.

    2) I tried to update the registry keys and that didn't seem to help.

    3)

    PS C:\script\SpeculationControl> Get-SpeculationControlSettings
    Speculation control settings for CVE-2017-5715 [branch target injection]

    Hardware support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is present: True
    Windows OS support for branch target injection mitigation is enabled: False
    Windows OS support for branch target injection mitigation is disabled by system policy: False
    Windows OS support for branch target injection mitigation is disabled by absence of hardware support: False

    Speculation control settings for CVE-2017-5754 [rogue data cache load]

    Hardware requires kernel VA shadowing: True
    Windows OS support for kernel VA shadow is present: True
    Windows OS support for kernel VA shadow is enabled: True
    Windows OS support for PCID performance optimization is enabled: True [not required for security]

    Suggested actions

    * Follow the guidance for enabling Windows Client support for speculation control mitigations described in https://support.microsoft.com/help/4073119


    BTIHardwarePresent : True
    BTIWindowsSupportPresent : True
    BTIWindowsSupportEnabled : False
    BTIDisabledBySystemPolicy : False
    BTIDisabledByNoHardwareSupport : False
    KVAShadowRequired : True
    KVAShadowWindowsSupportPresent : True
    KVAShadowWindowsSupportEnabled : True
    KVAShadowPcidEnabled : True
    This is due to the driver not being present at boot, thus before hand-off, the older microcode is still present whilst the OS is loading. Best thing to do is to wait for the UEFI update.

Page 19 of 70 FirstFirst ... 9 17 18 19 20 21 29 69 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •