KB4465065 Intel Microcode Updates for Windows 10 v1809 - Sept. 26 Win Update

Page 9 of 12 FirstFirst ... 7891011 ... LastLast
  1. no1yak70's Avatar
    Posts : 30
    win 10 pro
       #80

    Guitarmageddon said:
    Where are you reading your microcode from? So as I've learned after watching this thread a bit is that there are two ways to update microcode. One way is to get via bios update which writes the microcode to the board itself. The other is via the manual Windows update which places it in a dll file. If at startup, windows sees more current code in the system files vs the bios, it uses that microcode. So you could update the bios but always be seeing the windows update provided code, and also the opposite.
    Thanks for the reply, code read in Intel's XTU software, CPU-Z and Aida64, reads 96 for bios 0602 and 9A for bios 0805.
      My Computer

  2. ddelo's Avatar
    Posts : 2,229
    Windows 10 Pro x64
       #81

    Guitarmageddon said:
    Where are you reading your microcode from? So as I've learned after watching this thread a bit is that there are two ways to update microcode. One way is to get via bios update which writes the microcode to the board itself. The other is via the manual Windows update which places it in a dll file. If at startup, windows sees more current code in the system files vs the bios, it uses that microcode. So you could update the bios but always be seeing the windows update provided code, and also the opposite.
    Absolutely correct statement with a slight change... the opposite is usually not true (i.e. the BIOS/UEFI microcode to be later than the MS provided one), and the reason is that if the BIOS/UEFI microcode is up to date, then there is no reason to even bother installing the Microsoft update (KB4465065, these days).

    The key to this whole process is to keep an eye on the latest intel® Microcode Revision Guidance bulletin.
    If the recommended microcode from Intel is the one currently running in the system, then you may rest assured that nothing needs to be updated.
    If intel has implemented a newer microcode, then first check the manufacturer's support page for an update to the BIOS/UEFI and if there is no update there, check the latest Microsoft microcode update, download and install it.

    For more detailed info, check here
      My Computer

  3. Guitarmageddon's Avatar
    Posts : 87
    Windows 10 home
       #82

    ddelo said:
    Absolutely correct statement with a slight change... the opposite is usually not true (i.e. the BIOS/UEFI microcode to be later than the MS provided one), and the reason is that if the BIOS/UEFI microcode is up to date, then there is no reason to even bother installing the Microsoft update (KB4465065, these days).

    The key to this whole process is to keep an eye on the latest intel® Microcode Revision Guidance bulletin.
    If the recommended microcode from Intel is the one currently running in the system, then you may rest assured that nothing needs to be updated.
    If intel has implemented a newer microcode, then first check the manufacturer's support page for an update to the BIOS/UEFI and if there is no update there, check the latest Microsoft microcode update, download and install it.

    For more detailed info, check here
    Ok good to note. But i still remain confused because I attempted to redownload the update and just apply to be safe (even though I think 8700k microcode was unchanged) and it said the update was already installed. But if it was a situation my code DID in fact change, am i only left to delete the update and redownload it with the newer date? Someone said they did an "in place updrage" but I don't have an interest in doing that , seems like a lot for a little return.
      My Computer

  4. Cliff S's Avatar
    Posts : 25,561
    Win10 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #83

    Guitarmageddon said:
    Ok good to note. But i still remain confused because I attempted to redownload the update and just apply to be safe (even though I think 8700k microcode was unchanged) and it said the update was already installed. But if it was a situation my code DID in fact change, am i only left to delete the update and redownload it with the newer date? Someone said they did an "in place updrage" but I don't have an interest in doing that , seems like a lot for a little return.
    The maximus X boards got an BIOS update(to 1901) a few days ago, no need for you to worry about the Microsoft one:
    ROG MAXIMUS X CODE BIOS 1901
    "Updated uCode for the latest Intel processor.
    Manufacture Order No "
      My Computers

  5. Guitarmageddon's Avatar
    Posts : 87
    Windows 10 home
       #84

    Cliff S said:
    The maximus X boards got an BIOS update(to 1901) a few days ago, no need for you to worry about the Microsoft one:
    Well I realllllly dont want to upgrade the bios until I really have to. I get the ME firmware updates, the microcode via windows, etc, so I didnt see a big need. Dotn want to risk making my former OC unstable.

    But on the ROG forum, a user found this. It looks like the microcode in the bios is unchanged anyway. And adds code for a yet to be released processor? comet lake?
    [BIOS] ROG Maximus X - Page 10
      My Computer

  6. Cliff S's Avatar
    Posts : 25,561
    Win10 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #85

    MicroCode Extractor, AIDA64, HWInfo64, and CPU-Z all show I have A2 for a microcode, which is for both the BIOS(1901) and the one through Microsoft update, so they are the same, for the 9900K at least.

    But I do understand about the BIOS update messing with an OC; or at the very least the possibility of going higher for benchmarking
    I got my 5.656GHz on BIOS 1704, 1801 didn't even let be boot into Windows 5.450, and now with 1901, I can barely get upto 5.5GHz(and only using BCLK 101.5000 at 54 multiplier
      My Computers

  7. Guitarmageddon's Avatar
    Posts : 87
    Windows 10 home
       #86

    Cliff S said:
    MicroCode Extractor, AIDA64, HWInfo64, and CPU-Z all show I have A2 for a microcode, which is for both the BIOS(1901) and the one through Microsoft update, so they are the same, for the 9900K at least.

    But I do understand about the BIOS update messing with an OC; or at the very least the possibility of going higher for benchmarking
    I got my 5.656GHz on BIOS 1704, 1801 didn't even let be boot into Windows 5.450, and now with 1901, I can barely get upto 5.5GHz(and only using BCLK 101.5000 at 54 multiplier
    Yes 1704 has been the go to for me

    Also, here I am complaining about preserving my 5.1 overclock on an 8700k and here you are with 5.6 on a 9900k haha.
      My Computer

  8. Cliff S's Avatar
    Posts : 25,561
    Win10 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #87

    Guitarmageddon said:
    Yes 1704 has been the go to for me

    Also, here I am complaining about preserving my 5.1 overclock on an 8700k and here you are with 5.6 on a 9900k haha.
    That was only for a CPU-Z validation, although I was able to use the UWP apps in Windows.
    But opening a regular system32 program was a sudden BSOD

    I had to turn off al virtualization in BIOS and make sure AURA was either turned on in Windows, or in BIOS, plus I used the eXtreme validation in CPU-Z that doesn't detect everything, like SPD for example, otherwise it would crash windows on opening.

    I couldn't even bench int using CPU-Z, just the validation ,which is a very short burst.

    But hey, 5.656 with just an AIO, I'm pleased.
      My Computers

  9. Guitarmageddon's Avatar
    Posts : 87
    Windows 10 home
       #88

    Cliff S said:
    That was only for a CPU-Z validation, although I was able to use the UWP apps in Windows.
    But opening a regular system32 program was a sudden BSOD

    I had to turn off al virtualization in BIOS and make sure AURA was either turned on in Windows, or in BIOS, plus I used the eXtreme validation in CPU-Z that doesn't detect everything, like SPD for example, otherwise it would crash windows on opening.

    I couldn't even bench int using CPU-Z, just the validation ,which is a very short burst.

    But hey, 5.656 with just an AIO, I'm pleased.
    Ohhhhhhh......well then haha. I did bench through all my stress tests at 5.2 but I'm still having to avx offset down to 4.9, for heat reasons. Although I would love to get avx to 5.0 and non at 5.2, I don't think the juice is worth the squeeze as they say. And I am on h150i, 360mm AIO
      My Computer


  10. Posts : 111
    Windows 10 Pro 1903
       #89

    Release microcode-20190514 . intel/Intel-Linux-Processor-Microcode-Data-Files . GitHub

    There is a new release 14/5/2019, wonder why Microsoft didn't make it for the 1809 yet?
      My Computer


 
Page 9 of 12 FirstFirst ... 7891011 ... LastLast

  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 20:55.
Find Us




Windows 10 Forums