Thank you
I tried BIOS [MEB x QSTV 2. bin] immediately. But the result is still the same as before.

BIOS settings default settings, memory is SLOT 1 only, or SLOT 2 only. As a precaution, I also replaced it with a spare memory.
However, the ME subsystem does not seem to start up properly and inevitably can not control the control + P.

Supplement:
When loading the BIOS with AMIBCP 4.55, the setting of MESubsystem appears to be present in the debug menu, but its menu is not displayed on the machine.
Advanced menu Only Initial MEB Enabled / Disabled is displayed.
As explained in # 14, BIOS setting seems to load the default value whenever you reset all. (Initial MEB switches to Enabled)

You're welcome! Sounds like you shorted something when you fried the original BIOS then. I would always manually load setup defaults and save and reboot as mentioned, fail safe is the norm for startup and many things are disabled this way.

ME settings (outside of debug) are in the chipset section of AMIBCP. There you will see ME is disabled by default until you set "Load Setup Defaults" Your BIOS does show you "Chipset" menu option section correct? If you do not have "Chipset" section of BIOS let me know and I can enable
Debug section is not used, and the ME setting (unconfigure ME) in there is in AMT which your board does not support.

I think BIOS is fine, something on the board fried or shorted out etc. Or you have not yet loaded setup defaults and rebooted back to BIOS.

There is no "chipset" in the BIOS setting item. Only "info", "system", "advanced", "main", "power", "security" exist.

Binary [MEB x QSTV 2. bin] has not yet been experimented with FMV-D 5380 (Machine 2). Please let me know as necessary.

Anxious points
Here is the only example that succeeded in successfully activating the ME subsystem with FMV - D 5380 (Machine 1). In case
That is the case when ME Region [5.0.3.1126_DO_PRD_EXTR.bin] is included in FITC as the first dump [F1 _ FMV - D 5380 - 1. bin].
[F 07 _ FMV - D 5380 - 1. Bin] in the attachment I uploaded corresponds. It is also possible to start the ME subsystem setting by operating CTRT + P.
The message "ME Error: No Channel 0 Memory; disabling HECI messaging" is not displayed

However, only intel Qst malfunctions. After POST, "CPU FAN ERROR" and Japanese message "CPU fan not found". Is displayed.
Fan is running at full speed. If you start windows 7 in this state and start SpeedFan, it seems that intel Qst is working but it can not detect everything except CPU.

When [5.0.3.1126_DO_PRD_EXTR.bin] is installed, exactly the same phenomenon can be confirmed in FMV-D 5380 (Machine 2) and FMV-D 5370 (Machine 3).
The binary is [F08 _ FMV - D 5380 - 2. Bin] and [F 09 _ FMV - D 5370. Bin].

From now on it can be expected that something of intel QST's parameters will not fit in [5.0.3.1126_DO_PRD_EXTR.bin] for FMV-D 5380 (Machines 1 and 2) and FMV-D 5370 (Machine 3).
It seems possible to load any binary file from "intelR Qst Config File" item in Flash image tab, ME Region item of Fitc.exe.
But I can not imagine what kind of binary file it is. In case
Download link for Intel ME 5 Firmware Repository Pack [5.0.3.1126_DO_PRD_EXTR.bin is included]
[ https://mega.nz/#!zRc2DCoa!7odtFfP6x1YLv...wDPQ8tOueMTa4t0 ]

Sorry, I should have asked before, can you please show me an image that shows each item, so I can see them in order.
That way I know exactly what is disabled and what is shown in what order, so I can enable chipset menu for you, thanks!

Can you boot this system to windows? If yes, please do that, and install Intel ME drivers, and then run MEinfoWin and send me image of output, thanks!

All BIOS I sent use that exact same ME version, however, I did not ever set any to exact same settings as F1 _ FMV - D 5380 - 1.bin because you said system 2 was exact same, so I used it's settings instead.
Now that I am convinced it is not 100% exact same, I will make you new BIOS with same ME as always, but with F1 _ FMV - D 5380 - 1.bin ME settings
This will be just to test if there is something wrong in the settings or BIOS itself of F1 _ FMV - D 5380 - 1, if it acts the same w/ same symptoms as F1 _ FMV - D 5380 - 1 you mentioned today, then I'm sure it's like I said some hardware item shorted out or partially fried (Fan controller, Sensor, resistor capacitor etc)
Damage like that is not always visible, often the bad part looks brand new still, bad for us to diagnose.

I already have all ME repositories, and used clean new ME when I started making all these BIOS. I did consider updating the ME to latest version, but wanted to try and get you going on same as F1 _ FMV - D 5380 - 02 BIOS ME version and settings since you initially said they are the same.
And they may very well be 100% exact same, but failure with 01 system is some bad part due to when you shorted the BIOS

When I make new BIOS with chipset menu enabled, I will update ME to latest version for that series. I do doubt this will help though, I think something is bad on the board

BIOS setting menu Send all the items of the image.
The download link is https://drive.google.com/file/d/1ZpM3Gdp...iew?usp=sharing
You can start Windows on this system.
The Intel ME driver is already installed, but it is not available.
Loading MEinfoWin will result in error 9250 and no status will be output.

Thanks for the BIOS images, I will check and see/try to enable chipset menu for you, then once we get that working (hopefully), you can see what settings are there relating to QST

Do you get same error from MEinfo in DOS?

What BIOS are you using, when you load windows and mention above Meinfo error, is it MEB x QSTV 2. bin? While I work on chipset menu access, you said "Now" F1 _ FMV - D 5380 - 1.bin BIOS is working?
If yes, please try this BIOS, with ME from F1 _ FMV - D 5380 - 1.bin directly extracted and inserted to MEB x QSTV 2. bin
https://www.sendspace.com/file/yns62k

Next I will work on "Chipset" menu access for you, and then when we get I will update ME version and see if that helps

Hello
I think that the binary I used for the last test was probably [MEB x QSTV 2. bin], but the memory is not known. Therefore,
We loaded a new BIOS [MESwap 01 - ToQSTV 2. rm] and tested it.
The output message is as follows.

Meinfo(DOS) MS-DOS7.1
Copyright(C) 2005-08 Intel(R) Corporation. All Rights Reserved.
Intel(R) MEInfo Version: 5.0.0.1167
Error 9250 HECI Connection to the Intel(R) AMT PTHI client failed..
Reading Fw Status Register....

Meinfo(Win) Windows7 32bit
Copyright(C) 2005-08 Intel(R) Corporation. All Rights Reserved.
Intel(R) MEInfo Version: 5.0.0.1167
Error 9250 HECI Connection to the Intel(R) AMT PTHI client failed..
Reading Fw Status Register....
FW Status Register: 0X10E41421

Both of them display the message "ME Error: No Channel 0 Memory; disabling HECI messaging", and the ME subsystem does not seem to be running.

FW Status Register: 0XFFFFFFFF

I am very wondering
Including ME Region [5.0.3.1126_DO_PRD_EXTR.bin] in the BIOS will solve the ME subsystem problem.
intel QST also seems to start working (Intel QST will return within the sensor field of Evelest Ultimate Edition ver 5.50)
However, a message "CPU fan is not connected" is displayed after POST. MCH, ICH, boad The temperature can not be detected.

This problem has been confirmed to occur on two other machines that do not have physical problems in the hardware.
Because the other two machines are normal from the beginning, we intentionally made experiments to include ME Region [5.0.3.1126_DO_PRD_EXTR.bin] in BIOS.

Thanks for dropping that knowledge on us @plutomaniac. I really dislike that FIT v5 (5.0.0.1167), sometimes seems to not keep settings on a save or build and reopen, even sometimes shows different settings when opening the same file. It's too bad new/updated version can't work on old files

@kanta - I already planned to update your ME to another version for testing, but I will use latest RGN, not an extracted version. I will use 5.2.0.1009_DO_PRD_RGN - I was waiting for your testing results above and then on the chipset menu BIOS posted below.
I doubt however that a new updated ME version will help, when the same original one the machine always used previously that worked, now no longer works properly even when a new clean reset version is introduced. But maybe, since you say other machines have similar issue too sometimes?

Here is that chipset menu BIOS for testing, please test this and tell me if any new BIOS menu appear (Maybe too many now! - Or maybe no new or maybe brick BIOS )
https://www.sendspace.com/file/90zpgc

@ all - Due to this memory issue, and the only two slots on the board populated, as mentioned before I do think you have some shorted or fried component IC or resistor etc from when you had the initial BIOS shorting incident.
I've thought this all along due to some of your testing comments, and now what plutomaniac said about the memory, QST and such above seems to confirm this. But it's hard to know, since you mentioned shorting, and all these issues, but now say other systems have similar problem which you didn't say previously.
In windows, can you verify all memory is there, in task manager performance tab (Total physical memory). Don't check with CPU-z or other apps, those will often only detect what is installed not what is working fully/properly.

Hello. Today I got a free time and I made a new experiment.

The attachment link is https://drive.google.com/file/d/1_mem7_9...iew?usp=sharing

First of all, it is a test with binary, [MESwap 01 - ToQSTV 2 - BCPM.rom] + machine 1 FMV - D 5380 NO.
There is no change on the status of the ME subsystem and intel QST problem.
Debug, Chipset, Boot, and the second "Exit" are newly added to the BIOS menu.
The ME sub-system in the Chipset menu was set to Enable from the beginning.
All items in "Intel QST Hardware Health Monitor" are "N / A", and there were no items that could be changed.
(The picture is P04 - P15 in the ZIP.)
There is no problem regarding the detection status of the memory. (The pictures are P16 and P15.)

Next we tested on machine 2 FMV-D 5380 NO.2.
Binary, [MESwap 01 - ToQSTV 2 - BCPM.rom] + Machine 2 The result of the test with FMV - D 5380 NO. 2 did not change with the result in Machine 1 FMV - D 5380 NO.
So, I modified the binary in order to know what kind of message is displayed in the "Debug, Chipset" of the BIOS item when the ME subsystem and intel QST operate without problems
For this binary [1D5380_02.BIN], the range from 0h to 25FFFFh is the same as[F02_FMV-D5380-2. bin]. However, 260000h - 3FFFFFh is the same as [MESwap01 - ToQSTV2 - BCPM.rom].
[1D5380_02.BIN] + Machine 2 FMV-D 5380 I tested with NO.2, the ME subsystem and intel QST worked normally (The pictures are P17 to P24.)

Supplement:
On JIQ 45Y motherboards of machines FMV - D 5380 and FMV - D 5370, we found that circuits (PWM and TACHI) for cooling fan control are directly connected to ICH 10 DO.
I also found a circuit to go to the Super IO chip (SCH 5147), but this circuit has been disconnected from the beginning. This probably will be used in machine FMV-CE / C50.
I think the BIOS item "Hardware Health Monitor" (picture is P10) is probably displayed on the machine FMV-CE / C50.
Besides, because the circuit for controlling the cooling fan passes over the PCI riser board (picture is P03.JPG), it is impossible to control irrespective of whether the BIOS is good or not when the riser board is not installed is.
If there is a damaged part due to a short circuit of the SPI - ROM, it is a situation where anything other than ICH 10 DO can not be considered.
Unfortunately I do not have a machine FMV-CE / C50. The manufacturer's stock BIOS download link is http://www.fmworld.net/download/E1009245/E1009245.exe.

What kind of modification did you make to add the item "BIOS item menu" Debug, Chipset, Boot "and the second item" Exit "?
Even though I loaded the BIOS binary with AMIBCP 4.53 and changed the access right to USER, no menu was displayed.

Thanks for report back about menus! If you add some images of the BIOS, just one or two is fine, so I can see all current menus now, I can correct it so only certain needed ones show up.
That BIOS I only made for this menu test, there were no other changes in it. So you did include images of the BIOS, sounds like it. I will download later when I have more time and check it all out.

I will explain more about the BIOS mod too later when I have more time, sorry I only popped in for a second and have to run right now, but I will let you know once I have time to write it all down

Please fix the above download link, thanks! It's same as initial download link you gave, with 12 BIOS examples and images 1-9 again.
I don't want to download those again, please remove all those BIOS and images of first download from any downloads you provide in the future, it's big waste of bandwidth, thanks
Please make new download package, that shows current list of all BIOS menu's at the top and what's in each of the new sections, so I can compare with your previous BIOS menu images.
That way I can make better guided example to show you how to make those changes

Hello. Sorry for the late reply.
Fixed the download link.
[FMVD 5380 _ P2. Zip]
https://drive.google.com/file/d/1_mem7_9...iew?usp=sharing

All memory is there, shown by task manager, but this is non-matching memory, maybe that is what causes the memory error/issue? Can you test with matching memory and see if you still have same memory issue.
Thank you for the images, I will look at these more tonight, and let you know about editing the menu's and fix so there is not duplicates too

We currently use spare memory (1 GB + 2 GB) because this system (machine 1) is excluded from the main.
However, the symptom of the problem had already occurred in the original memory (2 GB x 2). This is currently used in the system (Machine 2).
Symptoms of the problem also occur with other combination (1GB × 2).
In any of these combinations, the system (Machine 1) displays the message "ME Error: No Channel 0 Memory; disabling HECI messaging", and the ME subsystem
Tem is abnormal. In the same model (Machine 2), the problem of memory false recognition of such ME subsystem does not occur.
It is considered that there is no abnormality in these memory modules themselves.

Other
If you combine 4GB x 2 [PC 3 - 10600, 2 R x 16, x 2], or 4 GB x 1 [PC 3 - 10600, 2 R x 16], a beep will be heard and POST will not be performed.
This confirmed the problem in AMIBIOS 's "Memory Detect" module in a different experiment from this time.
Only this symptom occurs in all systems (machines 1, 2, 3). The manufacturer has not announced the fix of this problem of the BIOS, so this is also the next task