12-19-2024 03:46 AM - last edited Thursday
Hi everyone,
- Intel ME Consumer Firmware :
Check/Update Process :
Check current version : Right click on "Check.cmd" > Run as administrator
Install/Update : Right click on "Install.cmd" > Run as administrator > Automatic restart when install is done
OS requirements : Windows 10 64 bit or more recent.
Hardware requirements : Motherboards with Intel H810/B860/Z890 chipset.
12-30-2024 12:00 PM
Hi,
You are in the wrong thread for your motherboard.
1) Update your Intel MEI Drivers to the last from the first post of this thread : [DRIVERS] Intel Chipset/MEI/SATA/VROC (X299).
2) Update your Intel ME Firmware to the last from the first post of this thread : [FIRMWARE] Intel ME (X299).
3) Update your BIOS to the last from your motherboard support page (https://rog.asus.com/motherboards/rog-rampage/rog-rampage-vi-extreme-encore-model/helpdesk_bios/).
12-30-2024 02:05 PM - edited 12-30-2024 02:08 PM
Sorry, but I couldn't find anything on it with my board.
Thank You for taking the Time and providing those threads!
You Rule!
a month ago
Hi everyone,
- Intel ME Consumer Firmware :
Thread updated.
4 weeks ago - last edited 4 weeks ago
ignore message saw the version numbers
a week ago
No issues on my Z890 Extreme using the latest version (19.0.0.1895).
a week ago - last edited a week ago
I thought I seemed to have fixed things on my end… not the case
it corrupted some of my windows files. Choral /r/f
and sfx /scannow fixed most of the issues.
i think i was a dumb ass tuning the firmware update while overclocked. Can this cause issues?
Rebuilding my index also has helped. Was one of the weirdest things I’ve seen happen..
best way to describe what was going on is everything slowed down to a haunt and was getting several bsods something I have not had since making this build.
thank you for posting your response that you were good to go
a week ago - last edited a week ago
Ncoke0,
. . . I think posting that you had your PC Over-Clocked could be a very helpful insight for others to consider.
I honestly cannot say if leaving your PC in an overclocked state would or could interfere or not.
It goes beyond my own knowledge base to make a definitive statement to it.
I prefer to Post what I know and not speculate unless I have made it clear that I am speculating.
I can only say that it could be a likely cause given the BIOS setting changes made to setup over-clocking could likely conflict with any BIOS or ME Firmware updates. Probably would be a good preventative step to return your PC to its DEFAUT BIOS States before doing Updates.
{With that said, I know for many getting an over-clocked PC setup, tweaked and working isn't exactly a walk in the park. And so, undoing one might not be something most would want to do. On the upside of undoing an Over-Clocked PC is you might learn a better way of doing it the next time around.}
What I Know:
The thing about updates of any kind, be it Windows, BIOS & Firmware updates or other devices is that there is always a risk of something going wrong.
First, I would suggest to anyone doing any kind of update to first do a manual Restore point.
Some updates will do this automatically before installing and for good reason.
Second, is that it is recommended that you TURN-OFF your BitLocker before doing any updates other than a Windows update if you are running any OS that has that encryption for Drives.
Third, would be to TURN-OFF all Anit-Virus & Malware programs before updating. They can cause issues.
Sorry, I forgot another obvious but often overlooked step. Close all Apps & Programs before updating.
Hope these steps help.
a week ago - last edited a week ago
So further testing this me update has caused stability issues with my cu-dimm ram. Was working perfectly fine prior to updating the me
when I said I was overclocked it was specifically my ram, as I had ran dimm fit for 5 to 6 hours to make it potentially more stable. CPU was on stock settings. Ram was xmp2 8800mhz for this 48gb cu-dimm kit
when ever I enable xmp now after this,me update I get the spinning wheel of doom for windows.
is their a method to revert back to the prior me version? To rule out this scenario.
would be willing to do it at stock, and then redo the new me firmware at stock to see if these issues go away.
thank you for the assistance @MoKiChU
a week ago
SUGGESTIONS:
1. Try getting Windows into Safe Mode to do a System Restore to get everything back to before you did the ME Firmware update.
2. Another trouble shooting idea is if you can get Windows working in safe mode to see if you can remove/ uninstall DIMM FIT because it could be a software conflict issue that caused the problem from whatever the ME Firmware update changed.
NOTE: ME FIRMWARE Version Updates come with details about what the latest version will do, as in what device software communications it improves or fixes. Read what that ME Firmware version update was specifically to get a better idea of what the ME Firmware changed.
(a) There is a reason they say to do a System Restore before doing BIOS & ME Firmware updates.
(b) There is also a reason for closing all Apps & Programs before doing a BIOS & ME Firmware update, as well as TURNING-OFF all Anti-Virus & Malware.
And depending on the OS if you need to TURN-OFF BitLocker
Sometimes doing BIOS & ME Firmware updates is about the sequence of things done.
The DIMM FIT Kit was likely running in the background when you did the ME Firmware update and it created the conflict issue you are having.
3. Basically once you get Windows system restored and running again.. try uninstalling the DIMM FIT Kit, to redo the ME update and then reinstall it afterwards.
Unlikely, but still I should put it out there that some BIOS & ME Firmware updates are generally run together.
Usually the BIOS is updated and then the ME Firmware follows as a general rule.
However, there are ME Firmware instructions that have you install the ME Firmware first and then the BIOS Version Update.
Not knowing what version of Windows you are running, if it has BitLocker, then you should have seen the warning to turn off BitLocker before running the ME Firmware update.
A Guess at the cause of the ME Firmware update issue is that DIMM FIT was still running in the background when you did the ME Firmware Update.