@Robson Dias:
Welcome at Win-RAID Forum!

Zitat von Robson Dias im Beitrag #1926

---

The file Intel ME System Tools v11.0 r15 is corrupted! Please upload the file again, tks!

---

@ all:

Red is the color that the eye is most keen on seeing first. I already had a note at the beginning of the thread about WinRar v5.x being a requirement. I added today two more red, bold and underlined notes that repeat that same sentence. Hopefully that will do it, even Dieter must be tired of saying the same thing over and over, I know I am.

@ MonarchX:

a) MEA is not part of UBU but a separate tool called by UBU in case it's needed. SoniX cannot do anything if MEA has an issue or may not know the answer for a MEA specific question.
b) As Fernando said, MEA scans the SPI image you drag & drop to it and not what's inside the SPI chip. Use MEA.exe -info command for the latter or better, MEInfo.
c) The ME Region is usually locked when it comes to read/writing. So if you flash a SPI image which has an older ME firmware, your newer ME firmware inside the SPI chip won't be replaced. FWUpdate does not mind if the ME Region is read/write protected, it can update the firmware. But any other flasher has to respect that protection.

@ propergol:

Not possible with FWUpdate, the VCN of 1202 is 11 whereas 1180 is 7. You cannot downgrade to a lower Version Control Number with FWUpdate. Only with FPT by using the ME Region extracted from your OEM SPI Image and only if your Flash Descriptor is unlocked. Look at the previous pages for instructions given to other users and adjust to your own needs. The ME does control some system clocks but your issue seems more like a BIOS or hardware one in case of module incompatibility and so on.

Your question makes no sense. MEI stands for Management Engine Interface, it's the driver for any given operating system. The Management Engine (ME) is a co-processor which acts as a supervisor of the main CPU and can act independently. Some of its firmware can be found at the SPI chip and that's what this thread is all about. The MEI driver is certainly not the one causing issues, maybe firmware although I highly doubt it as I said earlier. Slow performance could be the result of mixing non-identical memories or setting wrong BIOS settings. I won't go into detail on what could be causing such behavior, there are other subforums for that, but if you want to try downgrading the ME firmware then, as I said, read the previous pages to see how to do that with FPT.

Zitat von rivage im Beitrag #1933

---

Do I need to reformat windows or I can just install the iNF MEi without reformatting?

---

Zitat von rivage im Beitrag #1933

---

because I've read many times that MEi should always be installed as the very first driver of a reformatting process and you should never try to mess up with it again.

---

From Flash Programming Tool, try command fptw -greset and see if that fixes the issue you are having. If not, I assume based on the fact that you uploaded a full dump that your flash descriptor is unlocked or have a programmer. Correct? In that case, we can fix the ME region easily.

If you used fptw -d command and produced that file you uploaded then yes, your descriptor is unlocked. I don't think you did something wrong, you were probably unlucky and something got messed up by itself during the update. The attached ME Region is the one from the latest ASUS Z97-K 2801 SPI Image. Flash via Flash Programming Tool using the command fptw -rewrite -me -f ME.bin followed by the command fptw -greset. Check MEInfo and MEManuf. Afterwards, you can try updating to the latest 1.5MB firmware again if you wish. After restart, check MEInfo and MEManuf once again.

That's ok because:

a) It doesn't matter for 9.1 to 9.1 updating
b) SPI Image 2701 has the exact same ME Region inside

Note: If you update the BIOS (SPI Image) after the ME and the latter is updated, it might get downgraded automatically due to the older version of 2801. So, it would be better to update the BIOS first.

So go for it. I think that previously it was stuck at FWUpdate mode for some reason. The -greset command should have fixed that but anyway, you can repair the whole ME Region so why bother figuring out that went wrong. However, next time you want to update, make sure to disable all background programs, especially motherboard overclocking utilities and such. Prefer EFI/DOS if the latter is difficult. Maybe something was interfering.