Intel ME-Related POST Error With Sleep State Issue

[NDDan]

OK so ever since I got this board working a couple of weeks ago (on 1202 BIOS) I have always received the POST error:
"(A7) Me FW Downgrade - Request MeSpiLock Failed".

I didn't think much of it, but when I got Windows 10 loaded I noticed that I'm getting entries in the system log when the PC tries to "sleep" or enter a low-power state (specifically these, in order):
"Intel(R) Management Engine Interface driver has failed to perform handshake with the Firmware (FWSTS0: 0x90202242, FWSTS1: 0x84100006)."
"The Intel(R) Management Engine Interface is being disabled."

This is occasionally coupled with Windows reporting a dirty shutdown in the logs (may be a fluke, it's not with every shutdown). This morning the system was in some low-power "sleep" mode and the keyboard wouldn't come back until unplugged and re-plugged.

Anyway, this together with the POST error and started thinking ME FW or the MEI was to blame as those are the HW interface to low-power states. I'm currently using the ASUS-published MEI V11.0.0.1136. Adding to this in the BIOS, under the versions information it lists Intel ME FW Version as 0.0.0.0...which is strange.

Long story but when I finally got my Maximus VIII Hero working I had already flashed-back the BIOS to the then current 1202 BIOS revision from whatever the as-shipped state was (was troubleshooting what ended up being a memory issue)--I state this just to mention that I had no display to verify the pre-loaded BIOS ME FW version (or even the ASUS FW Version).

Troubleshooting: Updated MEI drivers = no impact (returned to ASUS-published MEI 1136)
Flashedback BIOS (cleared CMOS first) to 1001 = no impact, same POST and MEI errors, ME FW Ver in BIOS still report 0.0.0.0. Retuned to 1202. 1001 was listed as having an updated ME FW and was thinking maybe somehow, someway, the ME sector of the 1202 FW image didn't load as the rationale for the downgrade. Doesn't really make sense though, and I doubt the MEI driver would even load if the ME FW wasn't in place.

Background:
My initial problems with this build were memory (G.SKILL 3600 rated 8 x 2--listed compatible by G.SKILL but wouldn't post with QCode 53 as I recall). Replaced with G.SKILL 3200 16 x 2 on board QVL and POST's fine. As a troubleshooting step I flashbacked to 1202--no post with a QCode 53, so I don't know what the shipped ver was...

FWIW the relevant specs are: (and everything is still running at stock speeds and voltages until I get this sorted):
ASUS ROG MAXIMUS VIII HERO
Intel i7 6700k
G.SKILL Ripjaws V Series 32GB (2 x 16GB) (F4-3200C16D-32GVK)
EVGA GeForce 970 FTW+
Corsair HXi HX1000 PS
Corsair H100i GTX cooler
Windows 10 Pro x64
Storage: 512GB Samsung Pro 850 NVMe (boot), 512GB Samsung 850 EVO SSD, and a couple other SATA platter drives.

Hoping someone has experienced this or has a thought as to how to proceed; I'm considering going up to 1302 but I doubt that will change anything. I really want to stop the POST error and more importantly get the sleep modes to work correctly. Thoughts?

[AKBAAR]

try flashing your mobo to latest ME firmware from here
http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=select&id=105〈=fr

[NDDan]

AKBAAR wrote:
try flashing your mobo to latest ME firmware from here
http://www.station-drivers.com/index.php?option=com_remository&Itemid=352&func=select&id=105〈=fr

Does this require a special flashing tool? From some earlier reading I thought there were vendor-specific mods made to the stock intel ME FW's...is this something you've tried, if so can you report the ME FW version you are using?

[AKBAAR]

no tools needed just the falsher.exe that comes with it... under windows normal flashing
here is mine


flashing to new version fixes alot of stuff and add alot of options too

here is another detailed post easy to follow
http://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html

[Chino]

Clear your CMOS and update to the latest BIOS using an USB pendrive and the EZ Flash Utility in the BIOS.

[NDDan]

Chino wrote:
Clear your CMOS and update to the latest BIOS using an USB pendrive and the EZ Flash Utility in the BIOS.

Chino,

Appreciate it, I did do that, and then again after posting this message I thought I would have one more go-around, went up to 1302...no dice, same error. I use the following method, which maybe is flawed?:

--Powered Down, unplugged everything but monitor
CMOS Clear button on board
System goes through a couple of pre-os boot/re-boot cycles
System loads to screen asking to press F1 to enter CMOS
--Powered Down
Flashbacked with pendrive to 1302
--Powered Up
...

[AKBAAR]

also before and after u flash BIOS you need to load optimal defaults first before tweaking your bios