@The Engineer The FD is locked, so the ME Region is R/W protected.

@Ferrous

so this makes me think that the firmware itself is not corrupted but it is an access problem or what?!!!!!!

Is W protection what makes the me fw n/a ?

If for example I tried that

AfuEfix64.efi E1762IMS.70X /p /b /n /k /r /me

and me failed,will this brick my computer or prevent it from booting?

@ plutomaniac:

Thank you. Using your EFI Shell, I ran "setvar 0x2D4 0x1" and received the following:

setvar: Invalid argument - '0x1'
setvar: Unable to set - 8BE4DF61-93CA-11D2-AA0D-00E098032B8C - 0x2D4

Please advise.

@ Plutomaniac:

Thank you so much. I was finally able to set both 0x561 and 0x2D4 to 0x1 from 0x0 using the GNU GRUB shell that you provided.

However, when I ran "fptw64 -d spi.bin", I got the same CPU error as before.

I also tried running "fptw64 -greset" again and received the same error as before there as well.

Should I try to flash the A10 BIOS again or am I out of options?

fine!

@ Plutomaniac:

I appreciate all of your help. To be honest, I had a brain cramp and failed to press the power button after entering "exit" at the shell prompt after changing the values to 0x1. I simply let it boot to the next EFI option, which was into the Win 10 DVD repair. I then restarted from the troubleshooting menu. After everything failed again, I shut it down completely.

After reading your last post, I booted it back up, went back into the shell, and checked both values. 0x1 had stuck for both. I tried "fptw64 -greset" and "fptw64 -d spi.bin" again. Both failed.

I re-flashed the A10 BIOS. This time, it paused for a moment at 0% Sending Intel Management Engine Firmware Update, then continued on to a new error, ME Firmware Update Failed: Image Loading. It progressed through that and continued with the flash, which resulted in BIOS Update Successful.

These things are now true:
1. There is no longer a MEBx option at the F12 boot menu.
2. Message FW Status Recovery Error no longer shows on boot.
3. The Device Manager no longer shows an error for the Intel Management Engine Interface. In fact, it doesn't show the Intel Management Engine Interface in the System devices section of Device Manager at all now.
4. When I tried to re-install the Intel Management Engine Interface driver, it gave me options to uninstall or repair it. I chose to repair it and the result was a "fatal" error dialog box with no apparent effect. I then ran the installer again and chose to uninstall. It performed that successfully. I rebooted and tried to install the driver again. It now gives me the error, This platform is not supported.
5. I ran MEInfo and MEManuf again and both are now saying Unknown or unsupported hardware platform.
6. The BIOS information (see image) shows all firmware versions are now up-to-date.


I am puzzled as to how the BIOS flash indicates that the ME firmware update failed, but the above image clearly shows it on the right version.

Just from the little bit of time that I've spent with the laptop since, it does seem to be running faster and behaving better from a power management standpoint.

I apologize for being such a pain. It still doesn't seem to be 100% correct. Have I royally screwed it up or is there something else that can be done to set it all right besides tear it apart?

@forceadmin
That's because you have disabled ME. Set those 2 option back to 0x0 and it will be back.

@ plutomaniac
Attached file is dumped from a Supermicro ICH9R board w/ X7SBE Phoenix cME FirstBios Pro 2.0a dated 14.09.2011. I could dump the chip after desoldering its GND pin ;)
Currently ME Analyzer states this bios contains no ME nor a SPS?

@ plutomaniac:

Thanks to you and @ Ferrous. I set both values back to 0x0 and attempted all flashes, resets, and tests that you have given me up to this point again. The same errors exist that were there before disabling ME. The only difference seems to be that when I run the BIOS .exe file from within Windows, the initial dialog box indicates that all firmware is now up-to-date (see previous screen capture).

Is there anything else to try from a software standpoint? If not, would it hurt to leave ME disabled? It really did seem to perform better when disabled.