New
#80
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.
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
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![]()
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.![]()
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?