An FDO jumper was used so the entire SPI was re-flashed with HP’s stock SPI image. The CSME is healthy, only DMI info from BIOS is missing which caused this new message to appear. For HP, I’m fairly certain you need to use their technician-only NbDmiFit tool to get the job done properly. I think the last version we’ve found will work on your system as it’s not that new. You’ll need to read the provided documentation yourself though but it shouldn’t be that difficult.
I thought so after reading back. Don’t you usually need a personalized SMC.bin from HP to use NbDmiFit? They send them out, if you provide proof of purchase and give them your serial, UUID etc.
It can be done without that I think, at least all the DMI info. Closing out the manufacturing though I am not sure about, that may need to be done with NbDmiFit he’ll have to see what options he has without a SMC.BIN
I have 2.05 version, if 2.13 proves to be too new or something.
Maybe you’re right about SMC but I’ve never used NbDmiFit so I don’t know. Something else you can try to avoid all is to re-flash the old BIOS region only but the problem may come back if it wasn’t just a corrupted CSME firmware. Maybe you can transfer the NVRAM only or something. You know these things best. 
Thanks for your reply, please download the info you asked from the link below, i wasnt able to upload it here because of file size , backup.bin is the image before flashing and the other bin file is the one which plutomaniac sent me
http://www.skidmail.com/intel/adnan.rar
I’ve never used NbDmiFit myself either, but here on forums when I’ve helped people try to use it or fix their BIOS etc, every time the user had to contact HP to get that SMC file.
It does sound like a ME Only issue, so you’re right, it may be best to first try direct swap back of his old BIOS region. If that fails and brings back error, then yes I can transfer out details to stock image, usually these are in padding files, sometimes NVRAM as you mentioned, or certain modules like SMBIOSStaticData
* Edit - here @AdnanMumtaz - first test this, write back with FD jumper on. This is your original BIOS region swapped back into stock image. If this fails, or brings back error, then I will pull the details out directly and swap them in.
http://s000.tinyupload.com/index.php?fil…139891800826420
Thanks a lot, Shall I use the same command FPTW64.exe -f filename.bin with this file ?
Yes, it’s a full SPI image so you need “fpt -f” as you said, like before.
plutomaniac - I was looking into the NdDMIFit package, and he may be able to use wndmifit only, which may not require a valid/proper SMC.BIN for all functions, I’m not sure… There is a FSMC.bin in there already, so maybe not a good sign. 
But, if ME FW was the only issue, then the above file should sort it out for him anyway. This is RSA Signed BIOS too, so we may run into some issues editing, signature is just above Last VTF
Thanks guys a billion! its done, no more errors and everything is working fine now. see the output below
Microsoft Windows [Version 10.0.18362.175]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd "\fw\Intel CSME System Tools v11 r25"
C:\FW\Intel CSME System Tools v11 r25>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70
Directory of C:\FW\Intel CSME System Tools v11 r25
14-Jun-19 04:15 PM <DIR> .
14-Jun-19 04:15 PM <DIR> …
14-Jun-19 04:15 PM <DIR> Clock Commander Tool
14-Jun-19 04:15 PM <DIR> Flash Image Tool
14-Jun-19 04:15 PM <DIR> Flash Programming Tool
14-Jun-19 04:15 PM <DIR> FWUpdate
14-Jun-19 04:15 PM <DIR> Manifest Extension Utility
14-Jun-19 04:15 PM <DIR> MEInfo
14-Jun-19 04:15 PM <DIR> MEManuf
14-Jun-19 05:18 AM 898 Tools Version Info.txt
1 File(s) 898 bytes
9 Dir(s) 240,414,494,720 bytes free
C:\FW\Intel CSME System Tools v11 r25>cd "Flash Programming Tool"
C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70
Directory of C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool
14-Jun-19 04:15 PM <DIR> .
14-Jun-19 04:15 PM <DIR> …
14-Jun-19 04:15 PM <DIR> DOS
14-Jun-19 04:15 PM <DIR> EFI64
14-Jun-19 04:15 PM <DIR> WIN32
23-Jun-19 02:22 AM <DIR> WIN64
0 File(s) 0 bytes
6 Dir(s) 240,414,298,112 bytes free
C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool>cd WIN64
C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>dir
Volume in drive C is Windows
Volume Serial Number is E24E-3F70
Directory of C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64
23-Jun-19 02:22 AM <DIR> .
23-Jun-19 02:22 AM <DIR> …
16-Jun-19 02:32 AM 6,291,456 bios.bin
16-Jun-19 08:50 PM 221 error.log
14-Jun-19 05:18 AM 15,153 fparts.txt
14-Jun-19 05:18 AM 3,261,416 FPTW64.exe
14-Jun-19 05:18 AM 72,848 Idrvdll32e.dll
14-Jun-19 05:18 AM 125,072 Pmxdll32e.dll
20-Jun-19 09:46 PM 8,388,608 RGNSwap.bin
15-Jun-19 05:51 AM 8,388,608 sp93316_081B7F47.bin
16-Jun-19 08:08 PM 8,388,608 sppi.bin
9 File(s) 34,931,990 bytes
2 Dir(s) 240,414,298,112 bytes free
C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>FPTW64.exe -f RGNSwap.bin
Intel (R) Flash Programming Tool. Version: 11.8.65.3590
Copyright (c) 2007 - 2018, Intel Corporation. All rights reserved.
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
W25Q64FV ID:0xEF4017 Size: 8192KB (65536Kb)
GbE Region does not exist.
- Reading Flash [0x0800000] 8192KB of 8192KB - 100 percent complete.
- Erasing Flash Block [0x002000] - 100 percent complete.
- Programming Flash [0x0002000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x0B1000] - 100 percent complete.
- Programming Flash [0x00B1000] 32KB of 32KB - 100 percent complete.
- Erasing Flash Block [0x0D4000] - 100 percent complete.
- Programming Flash [0x00D4000] 108KB of 108KB - 100 percent complete.
- Erasing Flash Block [0x0F0000] - 100 percent complete.
- Programming Flash [0x00F0000] 36KB of 36KB - 100 percent complete.
- Erasing Flash Block [0x10F000] - 100 percent complete.
- Programming Flash [0x010F000] 120KB of 120KB - 100 percent complete.
- Erasing Flash Block [0x1BE000] - 100 percent complete.
- Programming Flash [0x01BE000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x241000] - 100 percent complete.
- Programming Flash [0x0241000] 4KB of 4KB - 100 percent complete.
- Erasing Flash Block [0x261000] - 100 percent complete.
- Programming Flash [0x0261000] 124KB of 124KB - 100 percent complete.
- Erasing Flash Block [0x283000] - 100 percent complete.
- Programming Flash [0x0283000] 132KB of 132KB - 100 percent complete.
- Erasing Flash Block [0x7FF000] - 100 percent complete.
- Programming Flash [0x07FF000] 4KB of 4KB - 100 percent complete.
- Verifying Flash [0x0800000] 8192KB of 8192KB - 100 percent complete.
RESULT: The data is identical.
FPT Operation Successful.
C:\FW\Intel CSME System Tools v11 r25\Flash Programming Tool\WIN64>
What could be the reason of this issue, i would like to know so i can prevent it happening in the future
Just bad luck more often than not. At least you have an FDO jumper.
Glad I found this forum and you guys who have been extremely helpful and patient, otherwise I am sure the local HP service center would tell me they need to replace mother board LOL