What? Completely ridiculous answer. Can't find the driver, ha-ha. Lol. Tell them that you use it in that case. Unfortunately or not, the ME is responsible for other system components like system clocks, overclocking, thermal monitoring, silicon workaround (solve cpu silicon issues which normally require a new stepping), fan control and more. So the engineer should not have it disabled. No need to explain it to them, just tell them that you use it and you'd appreciate a BIOS version which works with it. Long stretch but if you can get them to also update it to the latest 8.1.70.1590 version (so that we can grab it for other people, we are stuck at 8.1.65) then that would be super great. They seem to cooperate so who knows, we might get lucky. But yes, the first priority for your system it to at least have a BIOS that works with it.

That's due to something you did recently. You flashed some SPI or ME region which has completely different settings. The previous files you provided (dump, backup, my cleanup fix) as well as the last ones (full = dump, x7909_PCI_0929_bios = backup) have the exact same settings. The me.bin dump is completely different so it's something you flashed recently. Restore back to the previous ME regions we were working with.

That makes no sense, not possible. The full SPI image dump and the ME region dump taken from the same system without any reflashes in between should have the same ME region as far as settings are concerned. You must have confused some file with another.

No need to tag me with @username, I follow replies regardless.

To compare settings properly, you should use the "Save" xml option in FITC as exlained at step 11 of the cleanup guide. If you typed those two commands consecutively, then there is no way to see such drastic differences. The "me.bin" file has completely different ME DATA configuration from all the other files. Restart the system and try again with "fptw -d spi.bin" and "fptw -d me.bin -me" and you should see the same values at the two xml files created by FITC.

Well this is utterly strange and first time seeing it. The system has only one SPI chip, right? First, try a "fptw -greset" and check if you see the same weirdness after the ME reset. If you do get the same strange result, dump the full SPI and then flash it back with "fptw -f full.bin" followed by a "fptw -greset". After the reset, check again.

Check physically if it has two chips, although I doubt it. Even if it did, such behavior is not justified either. A manual greset can be performed by removing all power from the board for 1 minute or so. I don't understand why that happens. It makes no sense to me.

From hash checks, the ME region from the FITC folder is identical to the one I extracted manually from the original SPI image, which of course makes sense. So, the problem (if any) lies with FITC. The me region you dump with "FPT -d me.bin -me" is definitely the same as the full.bin image. Just that, for some reason, FITC interprets the "full SPI image" vs "me region only" settings in a wrong way. Might be a bug. I'll need to do a similar test on my own Z77 system tomorrow and let you know if I see the same behavior and if yes, I'll check if this is reproducible at older FITC. It might be C600 PCH FITC settings related only or something. Mmm, more tests are needed to pinpoint. But I believe it's FITC. That would make sense compared to different data being dumped.