HP Compaq Elite 8300 MT FW Status Recovery Error

BIOS/UEFI Modding BIOS Modding Guides and Problems
1

This error has been displayed on the BIOS boot screen for almost a year now. The system works fine until recently when I decided to fix the error since it’s really annoying.

First, I inserted a jumper to short the FDO pins on my motherboard so that it will unlock the Flash Descriptor region and allow me to read and write the Flash Descriptor region. After I did that, the system keeps turning on and off within a second and it repeats this process indefinitely until it decides to boot. When it does boot, the computer will almost certainly hang within a few minutes after it boots into Windows after which I will power off the computer and it will repeat the on off cycle again. It has been like this ever since.

This are the steps that I’ve tried:

  • Updating the BIOS to the latest version (No effect)
  • Updating Intel ME (Complains about a valid HECI device not being found)

MEInfo Output:
MEInfo.zip (952 Bytes)

I’ve managed to dump the whole BIOS using Intel FPT on this very unstable system. The chip marking on the BIOS is “Winbond 25Q128BVFG”
This is the full BIOS dump:
FULLBIOS.zip (5.1 MB)

Here are the screenshot with errors:

vlcsnap-2022-06-13-17h32m00s255
vlcsnap-2022-06-13-17h32m00s2551920×1080 39.2 KB

vlcsnap-2022-06-13-17h32m30s624
vlcsnap-2022-06-13-17h32m30s6241920×1080 41.1 KB

vlcsnap-2022-06-13-17h32m47s892
vlcsnap-2022-06-13-17h32m47s8921920×1080 39.8 KB

2
  • Updating Intel ME (Complains about a valid HECI device not being found)

In Windows the driver must be installed for MEI/HECI communications, otherwise ME tools will fail as you saw.

2 HP Elite 8300 MT Update files to ME Corporate, performed on OS environment, being on latest bios 3.08 (8.1.31.1351):

Before this, restore FDO jumper, do an FPT -greset or discharge the system AC for a t least 15m.

3

Alright thanks for the reply. I’ll try this and report back ASAP.

4

Now what did you precisely do?

  • Did you flash the FD? If so- which file? Which command?
  • Did you flash other parts of the firmware? If so- which file? Which command?

Are the FDO pins still jumpered?

The MEInfo output is taken with jumper set, that’s not valid.

5

No, I have not flash FD or any parts of the firmware.

The FDO pins are still currently jumped. Even if I remove the jumper, the computer still has the same symptom, turning on and off in a second and boots whenever it likes to.

It usually takes hours and from what I observed from this few days, it only boots 4-5 time in a 24 hour period and the constant monitoring to wait until it boots is really wearing down my patience to only have it freeze at anytime (usually in a few minutes) and I have to start the process of turning it off and on again until it decides to boot again.

I’ll try to get the MEInfo output without the jumper set any chance I get.

I have also tried leaving the system discharged for a day (without the pins jumped) and powering it on and the symptom still persists.

6

I did some additional research and found out that my ME firmware might be corrupted. To quote plutomaniac,

I can see the problem. The ME firmware is corrupted (probably happened during an older FWUpdate) because HP has messed up while building the SPI image for that system. All their released SPI/BIOS updates (2008-2015) have semi-broken Flash Descriptor region starting Offset & Sizes. Some overlap due to wrong sizes.

Before/Wrong:

0x0 - 0x1000 (FD)
0x1000 - 0x3000 (GbE)
0x3000 - 0xD000 (PDR) → overlaps with ME as 0xD000 > 0xB000
0xB000 - 0x26A000 (ME) → overlaps with BIOS as 0x26A000 > 0x260000
0x260000 - 0x65F000 (BIOS) → out of SPI bounds as 0x65F000 > 0x400000 (4MB)

After/Correct:

0x0 - 0x1000 (FD)
0x1000 - 0x3000 (GbE)
0x3000 - 0xB000 (PDR)
0xB000 - 0x260000 (ME)
0x260000 - 0x65F000 (BIOS) → left intact due to Flash Image Tool v5 being stupid

I followed the Engine CleanUp Guide on the Engine/ME region only (to avoid any more FIT v5 stupidity) and manually fixed the FD where needed. At the attached archive you’ll find the full fixed SPI image, the fixed ME region as well as the fixed Flash Descriptor region (which should not cause ME corruption during FWUpdate anymore). Run Flash Programming Tool with commands:

fpt -desc -f 7G1_0127_fix_desc.bin
fpt -me -f 7G1_0127_fix_me.bin
fpt -greset

Quoted from: 2233-HECI error during MEBx execution - #6 by plutomaniac

I have also updated Intel ME to version 8.1.72.3002 as @MeatWar recommended but I’m still having the same errors in the first post (screenshots). I can’t seem to update from DOS, EFI or in Windows so I jumped the FDO pins and updated Intel ME manually by flashing Intel ME using FPT using the guide [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization.

I can confirm that Intel ME drivers are installed and I downloaded the drivers from HP website again and installed it.

I have removed the FDO jumper and the BIOS does indeed reflect the latest Intel ME version which is 8.1.72.3002. I did a FPT -greset and the system is now back to turning on and off.

Here is the MEInfo dump without the FDO jumper set:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\windows\system32> cd "D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64"
PS D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64> ls


    Directory: D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        10/06/2022   2:05 PM             78 error.log
-a----        21/03/2020   9:43 PM          61952 Idrvdll32e.dll
-a----        21/03/2020   9:43 PM        1190872 MEInfoWin64.exe
-a----        21/03/2020   9:43 PM         114176 Pmxdll32e.dll


PS D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64> .\MEInfoWin64.exe

Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.

Intel(R) ME code versions:

BIOS Version:                           K01 v03.08
MEBx Version:                           8.0.0.0063
Gbe Version:                            1.3
VendorID:                               8086
PCH Version:                            4
FW Version:                             8.1.72.3002
UNS Version:                            Not Available
LMS Version:                            Not Available
MEI Driver Version:                     11.0.0.1157
Wireless Hardware Version:              Not Available
Wireless Driver Version:                Not Available

FW Capabilities:                        0x0DFE5C47

    Intel(R) Active Management Technology - PRESENT/ENABLED
    Intel(R) Capability Licensing Service - PRESENT/ENABLED
    Protect Audio Video Path - PRESENT/ENABLED
    Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Intel(R) AMT State:                     Enabled
CPU Upgrade State:                      Not Upgradable
Cryptography Support:                   Enabled
Last ME reset reason:                   Global system reset
Local FWUpdate:                         Enabled
BIOS Config Lock:                       Enabled
GbE Config Lock:                        Enabled
Host Read Access to ME:                 Disabled
Host Write Access to ME:                Disabled
SPI Flash ID #1:                        EF4018
SPI Flash ID VSCC #1:                   20052005
SPI Flash BIOS VSCC:                    20052005
BIOS boot State:                        Pre Boot
OEM Id:                                 00000000-0000-0000-0000-000000000000

Error 8199: Communication error between application and Intel(R) ME (Get Intel(R) AMT State)

Error 8199: Communication error between application and Intel(R) ME (Get System UUID)

Error 8199: Communication error between application and Intel(R) ME (Get Ipv4 Info)

Error 8199: Communication error between application and Intel(R) ME (Get Ipv4 Info)

Error 8199: Communication error between application and Intel(R) ME (Get Ipv6 Info)

Error 8199: Communication error between application and Intel(R) ME (Get Ipv6 Info)

Error 8199: Communication error between application and Intel(R) ME (Get Provisioning State)

Error 8199: Communication error between application and Intel(R) ME (Get Provisioning Mode)
Capability Licensing Service:           Enabled
Capability Licensing Service Status:    Permit info not available
OEM Tag:                                0x00000001
Wireless Micro-code Mismatch:           No
Wireless Micro-code ID in Firmware:     0x0000
Wireless LAN in Firmware:               Unknown
Wireless Hardware ID:                   No Intel WLAN card installed
Wireless LAN Hardware:                  No Intel WLAN card installed
Localized Language:                     Unknown
Independent Firmware Recovery:          Disabled
PS D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64> .\MEInfoWin64.exe -verbose

Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.


FW Status Register1: 0x1E000642
FW Status Register2: 0x6900010C

  CurrentState:                         Recovery
  ManufacturingMode:                    Disabled
  FlashPartition:                       Valid
  OperationalState:                     M0 with UMA
  InitComplete:                         Complete
  BUPLoadState:                         Failure
  ErrorCode:                            No Error
  ModeOfOperation:                      Normal
  ICC:                                  Valid OEM data, ICC not programmed

  Windows OS Version : 6.2.9200 ""
  OS BIOS Support    : UEFI

    Table Type   0 ( 0x 00 ) found, size of  24 (0x 18 ) bytes

  Windows OS Version : 6.2.9200 ""
  OS BIOS Support    : UEFI

    Table Type   0 ( 0x 00 ) found, size of  24 (0x 18 ) bytes
    Table Type   1 ( 0x 01 ) found, size of  27 (0x 1B ) bytes
    Table Type   2 ( 0x 02 ) found, size of  15 (0x 0F ) bytes
    Table Type   3 ( 0x 03 ) found, size of  22 (0x 16 ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type  16 ( 0x 10 ) found, size of  23 (0x 17 ) bytes
    Table Type  11 ( 0x 0B ) found, size of   5 (0x 05 ) bytes
    Table Type  24 ( 0x 18 ) found, size of   5 (0x 05 ) bytes
    Table Type  32 ( 0x 20 ) found, size of  20 (0x 14 ) bytes
    Table Type  41 ( 0x 29 ) found, size of  11 (0x 0B ) bytes
    Table Type  41 ( 0x 29 ) found, size of  11 (0x 0B ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  20 ( 0x 14 ) found, size of  35 (0x 23 ) bytes
    Table Type   4 ( 0x 04 ) found, size of  42 (0x 2A ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  20 ( 0x 14 ) found, size of  35 (0x 23 ) bytes
    Table Type  19 ( 0x 13 ) found, size of  31 (0x 1F ) bytes
    Table Type  13 ( 0x 0D ) found, size of  22 (0x 16 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   9 ( 0x 09 ) found, size of  17 (0x 11 ) bytes
    Table Type   9 ( 0x 09 ) found, size of  17 (0x 11 ) bytes
    Table Type   9 ( 0x 09 ) found, size of  17 (0x 11 ) bytes
    Table Type   9 ( 0x 09 ) found, size of  17 (0x 11 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type   8 ( 0x 08 ) found, size of   9 (0x 09 ) bytes
    Table Type 129 ( 0x 81 ) found, size of   8 (0x 08 ) bytes
    Table Type 130 ( 0x 82 ) found, size of  20 (0x 14 ) bytes
    Table Type 131 ( 0x 83 ) found, size of  64 (0x 40 ) bytes
        MEBx Version found is 8.0.0.0063

Get ME FWU info command...done

Get ME FWU version command...done

Get ME FWU feature state command...done

Get ME FWU platform type command...done

Get ME FWU feature capability command...done

Get ME FWU OEM Id command...done
FW Capabilities value is 0xDFE5C47
Feature enablement is 0xDFE5C47
Platform type is 0x42421412
Intel(R) ME code versions:

BIOS Version:                           K01 v03.08
MEBx Version:                           8.0.0.0063
Gbe Version:                            1.3
VendorID:                               8086
PCH Version:                            4
FW Version:                             8.1.72.3002
UNS Version:                            Not Available
LMS Version:                            Not Available
MEI Driver Version:                     11.0.0.1157
Wireless Hardware Version:              Not Available
Wireless Driver Version:                Not Available

FW Capabilities:                        0x0DFE5C47

    Intel(R) Active Management Technology - PRESENT/ENABLED
    Intel(R) Standard Manageability - NOT PRESENT
    Intel(R) Anti-Theft Technology - NOT PRESENT
    Intel(R) Capability Licensing Service - PRESENT/ENABLED
    Protect Audio Video Path - PRESENT/ENABLED
    Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Intel(R) AMT State:                     Enabled

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS CPU allowed feature information command...done
CPU Upgrade State:                      Not Upgradable
Cryptography Support:                   Enabled
Last ME reset reason:                   Global system reset
Local FWUpdate:                         Enabled

Get BIOS flash lockdown status...done
BIOS Config Lock:                       Enabled

Get GbE flash lockdown status...done
GbE Config Lock:                        Enabled

Get flash master region access status...done
Host Read Access to ME:                 Disabled
Host Write Access to ME:                Disabled
SPI Flash ID #1:                        EF4018
SPI Flash ID VSCC #1:                   20052005
SPI Flash BIOS VSCC:                    20052005
Protected Range Register Base #0 0x0
Protected Range Register Limit #0 0x0
Protected Range Register Base #1 0xFF0
Protected Range Register Limit #1 0xFFF
Protected Range Register Base #2 0x0
Protected Range Register Limit #2 0x0
Protected Range Register Base #3 0x0
Protected Range Register Limit #3 0x0
Protected Range Register Base #4 0x0
Protected Range Register Limit #4 0x0
BIOS boot State:                        Pre Boot
OEM Id:                                 00000000-0000-0000-0000-000000000000

Get Intel(R) AMT state command...error

Error 8199: Communication error between application and Intel(R) ME (Get Intel(R) AMT State)

Get system UUID command...error

Error 8199: Communication error between application and Intel(R) ME (Get System UUID)

Get LanInterfaceSettings command for wired interface...error

Error 8199: Communication error between application and Intel(R) ME (Get Ipv4 Info)

Get LanInterfaceSettings command for wireless interface...error

Error 8199: Communication error between application and Intel(R) ME (Get Ipv4 Info)

Get IPv6InterfaceStatus command for wired interface...error

Error 8199: Communication error between application and Intel(R) ME (Get Ipv6 Info)

Get IPv6InterfaceStatus command for wireless interface...error

Error 8199: Communication error between application and Intel(R) ME (Get Ipv6 Info)

Get provisioning state command...error

Error 8199: Communication error between application and Intel(R) ME (Get Provisioning State)

Get Provisioning Tls Mode command...error

Error 8199: Communication error between application and Intel(R) ME (Get Provisioning Mode)
Capability Licensing Service:           Enabled

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS permit information command...done
Command response status indicates permit not found

Get iCLS CPU allowed feature information command...done

Get iCLS PCH allowed feature information command...done

Get iCLS PCH allowed feature information command...done
Capability Licensing Service Status:    Permit info not available

Get ME FWU OEM Tag command...done
OEM Tag:                                0x00000001

Get ME FWU Platform Attribute (WLAN ucode) command...done
Wireless Micro-code Mismatch:           No
Wireless Micro-code ID in Firmware:     0x0000
Wireless LAN in Firmware:               Unknown
Wireless Hardware ID:                   No Intel WLAN card installed
Wireless LAN Hardware:                  No Intel WLAN card installed

Get ME FWU Platform Attribute (WLAN ucode) command...done
Localized Language:                     Unknown

Get ME FWU Info command...done
Independent Firmware Recovery:          Disabled
PS D:\Users\user\Downloads\Intel ME System Tools v8 r3\MEInfo\Windows64>
7

Forgot to tell you but no harm done anyway, just to your information, any corrupted ME FW image cant be fixed even with an updated ME FW.
I do suggest cleaning the ME according the guide you already know by Plutomaniac
You can wait for @lfb6 opinion.

EDIT: The guide has nothing to do with SOIC form and the fparts.txt is a vendor IC needed to the tool as part of Intel ME tools package.

8

I’m willing to take the risk of somehow corrupting the BIOS since I technically have a BIOS programmer on hand. I’m currently waiting for my SOIC16 clip to arrive if it will be used anyway. I have a CH341A and a SOIC8 clip but since this BIOS has 16 pins, I can’t do anything with it.

The guide by plutomaniac involves modifying fparts.txt from what I’m guessing is from Intel FPT. plutomaniac seems to be working on a 8MB BIOS chip with 8 pins but mine is a 16MB chip so I guess it wouldn’t work.

I’ll try to do more research in the meantime and wait for the computer to boot again

9

Quoted from: 2233-HECI error during MEBx execution - #6 by plutomaniac

This is a much older system with an ME 5, your FD seems to be OK, check boundaries in UEFIToolNE, they’re correct:

fd
fd944×476 61.9 KB

I have also updated Intel ME to version 8.1.72.3002 as @MeatWar recommended but I’m still having the same errors in the first post (screenshots). I can’t seem to update from DOS, EFI or in Windows so I jumped the FDO pins and updated Intel ME manually by flashing Intel ME using FPT using the guide [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization.[/quote]I’m sorry, but it’s unclear what you did here: “updated Intel ME manually by flashing Intel ME using FPT using the guide”

Which ME firmware did you use for the “update”? Cleaning procedure is normally done with same version stock ME firmware?
Can you post /attach the firmware or ME region you used for flashing?

I have removed the FDO jumper and the BIOS does indeed reflect the latest Intel ME version which is 8.1.72.3002. I did a FPT -greset and the system is now back to turning on and off.
Here is the MEInfo dump without the FDO jumper set.

Well, the output is still indicating that the ME firmware is corrupted like for example
CurrentState: Recovery
BUPLoadState: Failure
ICC: Valid OEM data, ICC not programmed

This is your dump from first post:

fw
fw1073×631 157 KB

The flash descriptor is except for the read/write settings and a mentioning of the version identical to latest stock, GbE doesn’t matter here, ME is possibly corrupt, bios region is except for a signature as shown a 100% identical to latest stock bios up to the green line. First padding in bios seems to contain settings (NVRAM?) in an unusual way, might be corruption there, too.
First steps now would be to get the ME in an uncorrupted state.

As written: Can you post /attach the firmware or ME region you used for flashing?

10

extracted-ne-FULLBIOS-UPDATED-CLEANED-INTEL_ME.zip (2.5 MB)

This is the Intel ME firmware I used to flash using the command fptw64.exe -ME -F extracted-ne-FULLBIOS-UPDATED-CLEANED-INTEL_ME.BIN

All other regions of the BIOS are unaffected except for ME and FD which I flipped the Read / Write to all “YES” using HxD and flashed the FD region. Specifically, BIOS/CPU, Engine and GbE bits using this guide [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing with this specific section from the guide:

image
image1366×456 35.8 KB

image
image1011×518 28.8 KB

Modified FD region:
extracted-ne-FULLBIOS-UPDATED-CLEANED-FD.zip (455 Bytes)

I used this specific Intel ME as the base, “8.1.72.3002_5MB_PRD_RGN.bin” obtained from “ME 8 Repository r20.rar” of [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization just to be specific.

image

And finally this is the full BIOS dump with the FD and ME changes:
FULLBIOS-UPDATED-CLEANED-INTEL_ME-UNLOCKED_ALL.zip (5.1 MB)

11

OK, I understand. Unfortunately I get a 100% identical result if I combine cleaning of the firmware image posted in #1 with updating to ME 8.1.72. That’d mean that the ME should be ‘clean’ and ready to use. No incidence of en error made and nothing to hope from a second run of cleaning.

There might be a source for errors in using Windows for running MEInfo.

  • Can you create a bootable DOS USB stick and use the DOS versions of MEInfo and MEMAnuf?

Otherwise- how’s the board behaving now?

12

Ok so I created a bootable USB with FreeDOS installed. Currently, I only have MEInfo output on hand. I’ll try to get MEMAnuf output as well when the computer boots.

MEInfo.EXE -VERBOSE:

vlcsnap-2022-06-15-07h21m48s644
vlcsnap-2022-06-15-07h21m48s6441920×1080 137 KB

vlcsnap-2022-06-15-07h21m57s069
vlcsnap-2022-06-15-07h21m57s0691920×1080 116 KB

vlcsnap-2022-06-15-07h22m03s280
vlcsnap-2022-06-15-07h22m03s2801920×1080 137 KB

vlcsnap-2022-06-15-07h22m08s995
vlcsnap-2022-06-15-07h22m08s9951920×1080 136 KB

vlcsnap-2022-06-15-07h22m19s267
vlcsnap-2022-06-15-07h22m19s2671920×1080 122 KB

vlcsnap-2022-06-15-07h22m31s226
vlcsnap-2022-06-15-07h22m31s2261920×1080 152 KB

vlcsnap-2022-06-15-07h22m38s603
vlcsnap-2022-06-15-07h22m38s6031920×1080 159 KB

vlcsnap-2022-06-15-07h22m45s839
vlcsnap-2022-06-15-07h22m45s8391920×1080 171 KB

vlcsnap-2022-06-15-07h22m52s869
vlcsnap-2022-06-15-07h22m52s8691920×1080 188 KB

vlcsnap-2022-06-15-07h23m00s016
vlcsnap-2022-06-15-07h23m00s0161920×1080 168 KB

vlcsnap-2022-06-15-07h23m07s512
vlcsnap-2022-06-15-07h23m07s5121920×1080 167 KB

MEInfo.exe -FWSTS:

vlcsnap-2022-06-15-07h21m48s644
vlcsnap-2022-06-15-07h21m48s6441920×1080 137 KB

I had let the computer fully discharge overnight (don’t know if that actually helps) and is currently waiting for it to boot again. In the meantime, the symptoms still persist, board turning on and off every second until it decides to boot.

Update:

This is the MEManuf output that I managed to get in FreeDOS before it shutting down unexpectedly

vlcsnap-2022-06-15-19h09m18s788
vlcsnap-2022-06-15-19h09m18s7881920×1080 127 KB

vlcsnap-2022-06-15-19h24m59s968
vlcsnap-2022-06-15-19h24m59s9681920×1080 165 KB

vlcsnap-2022-06-15-19h10m08s843
vlcsnap-2022-06-15-19h10m08s8431920×1080 166 KB

Update:
I ran MEManuf.exe -VERBOSE a second time in FreeDOS and its tests are causing the board to shutdown unexpenctedly specifically when it’s requesting the “Request Intel (R) ME Full BIST test command…done” part.

13

Thanks. I’m afraid that sounds pretty much hardware. Seems that the ME fails to load /initialize the hardware in an early state (BUPLoadState Failure)

You might try to flash the latest stock HP firmware, sp95971 does contain a complete firmware image, but I doubt that this will help you- Sorry.

14

Alright sure. Thanks for the help anyways!