I came here after following this link (Z200 switches off after 30 minutes - unable to Ctrl-P or flash ME firmware (5)) from the HP forum. I also read this one ( Layman seeking help to fix Intel MEI firmware causing unexpected laptop shutdowns every 30 minutes).
My system is shutting off without warning after 30 minutes whether on the Bios screen or in Windows. This probelm started after I did a clean install of Windows 10, upgraded the RAM and installed a 64GB Msata SSD to take advantage of Rapid Storage Technology. The BIOS got corrupted somewhere in the process and I installed the latest and only version currently offered by HP for this machine by flashing from a USB. More details are provided below.
Error messages in the system log after restarting from one of these shutdowns indicate that the previous shut down was triggered by the Hardware Watchdog Timer.
This is my system
Computer: Hewlett-Packard Envy DV6-7250ca Notebook
OS Name Microsoft Windows 10 Home
Version 10.0.17763 Build 17763
Processor: Intel(R) Core™ i7-3630QM CPU @ 2.40GHz, 2401 Mhz, 4 Core(s), 8 Logical Processor(s)
Motherboard: Hewlett-Packard 181B (also Indicated on the board as Goya/Balen 1.0-DDR3 11254-3 48.4ST10.031)
Chipset: Intel 7 Series/C216
BIOS Version/Date: Insyde F.2E, 2016-09-07 (HP SP77453) (Previously installed version was F.28, 2013-07-25)
RAM: 16 GB – G.Skill F3-1600C11D-16GRSL DDRL-1600 8GBx2 (Replaces factory installed 2x4GB RAM)
HDD: 750 GB, 5400 rpm
Added a 64 GB Msata SSD to available slot.
I downloaded Intel ME System Tools v8 r3 and ran MEInfo and MEManuf from DOS using a bootable USB. Both gave error messages.
MSInfo Error 9458: Communication error between application and Intel(R) ME module (FW Update client)
MSInfo Error 9459:Internal error (could not determine FW features information)
MEManuf Error 9296: MEMANUF Test Failed
What do I do now?
Yes, that means that the ME firmware is corrupted. You basically need to follow steps 3 and 4 from the second link you referred to.
I was able to get my firmware repaired and the system seems to be operating as it should. It wasn’t all smooth sailing and I thought it might help others if I described what I went through.
The system is an HP consumer notebook PC, 2012 vintage with the Intel HM77 chipset. To unlock the read/write access to the firmware I had to hold down the Windows key plus the left and right arrow keys, press and hold the start button until I heard the fan start and then release the other keys when I first saw something appear on the screen. (I learned of this method reading some of the other posts on Win-Raid. It took a few tries to get it right and I couldn’t tell until I was able to dump one of the files). I was then able to dump the SPI file. I followed steps 1 through 11 in section D1 of the [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization and cleaned the SPI file.
When I tried to flash the cleaned SPI file, I found the that read/write access to the firmware was locked and had be unlocked again. It must relock when the machine is rebooted. The first attempt to flash the firmware failed with a message indicating that the BIOS was locked. I decided that I would proceed on the assumption that the BIOS was ok and replace only the Flash Descriptor and ME region firmware.
I then dumped the Flash Descriptor (desc) and ME bin files. I created a new ME region image which required a significant amount of 0xFF padding (see step 12 of D1) to match the size of the original bin file. Using the Hex editor, I extracted the replacement Flash Descriptor image from the cleaned SPI file that I created above.
I was able to compare both the ME region and Flash Descriptor BIN files to their originals using the Hex editor.
I decided to flash the firmware images using DOS. This required booting from a USB key loaded with DOS, the Flash Programming Tool and the replacement firmware image files. The firmware read/write access had to be unlocked again on start-up using the procedure described above with the addition of tapping the escape key to interrupt the boot in order to select the USB drive to boot from.
Using the Flash Programming Tool, I loaded the Flash Descriptor and then the ME region files using 2 separate DOS commands. Both files loaded successfully and were verified. A couple of messages appeared on the DOS screen after executing the command to load the ME region file. There may have been more, but these were the ones left on the screen: PDR Region does not exist, Could not communicate with HECI, GBE Region does not exist. I don’t know if these messages were to be expected or if they indicated a problem.
I restarted the system and let it boot into Windows. I checked in the Device Manager and saw that the Intel Management Engine Interface, which had previously been missing, was now listed under System Devices. (I learned from reading other posts on Win-Raid that this device was missing from the list for others who were having the same problem).
I then went back and ran the fpt -greset command described in step 12 of D1.
The system has been operating normally for 1 week now and is no longer shutting off on its own after 30 minutes. Thank you, Win-Raid, for helping me resolve this issue.
Thanks for posting back your success and method @MMBtu3413 - good tip you shared about the FD/ME read/write access, I’ll have to try and keep that in mind and see if it applies to many HP models or only certain ones.
Plutomaniac - can this little tip be added somehow as a possible method for HP users to the FD unlock guide, or do you think it may be limited in reach to only certain HP?
@MMBtu3413
Seriously, great work! You certainly managed successfully to gather all possible information before doing anything invasive by following the guides carefully and by reading past experiences from other people. Your thought process on how to move forward was also perfect when problems, such as the BIOS lock, were encountered. Such a thing is rare and much appreciated so thank you instead. 
To answer some questions: The yellow “region does not exist” messages are normal for systems which don’t use them. It’s true that the device does not appear at the OS when the firmware is corrupted or temporarily disabled for servicing. The temporary disablement is valid for one boot only and you’ll need to do it again each time, as you noticed. To avoid that until you can fix the issue, you could dump the FD, enable read/write access to the Engine region and then flash it back. At the end, once everything is fixed, you can run “fpt -closemnf” to restore back the read/write locks for better security.
They are indeed model or at least generation limited. At the other HP threads that MMBtu3413 must have read, I remember finding and recommending other special key combinations to unlock read/write access or that MPM or similar.