Hello, this is Kanta.
I have pointed out that Mr. plutomaniac can not understand the contents, so I will rewrite everything.
I am currently busy, so it will take time, so write it briefly below.
1. Machines that currently have problems
(Machine 1)
FUJITU JAPAN ESPRIMO FMV-D 5380 No. 1 (FMVDC4F0C1)
2. The symptom of the problem
BIOS - SPI The computer malfunctions due to a data defect in the flash ROM.
3. Attempted repair part 1
I tried repairing data by copying data from the same model machine. At least AMIBIOS is working normally, but ME firmware could not be recovered.
4. Attempted repair part 2
As we determined that ME firmware needs to be cleared, [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
We cleared the data according to, but it did not solve it at all. Moreover, CPU FAN TACH ERROR which was not in the past occurred.
5. Attached file
FMVESPRIMO.ZIP. (Download URL = https://drive.google.com/file/d/1ld-LSmz…7-gYduOuHC/view)
The first dump of problem (Machine 1) is [F01_FMV-D5380-1.bin]
First dump of another same type machine (Machine 2) [F02_FMV-D5380-2.bin]
First dump of machines that closely resemble (Machine 3) [F03_FMV-D5370.Bin]
ME trying to clear the firmware dump [F04_FMV-D5380-1.bin]
----------------------------------------------------------------------------------------------------------------------------------------------------
Hello everyone, nice to meet you. I am Kanta who lives in Japan.
Someone please help me. I currently have serious problems due to special Intel management engines.
I can not solve it with the clean ME Region, ribosstrophy setting method instructed at these sites below.
URL= [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization)
URL= Intel Engine: Firmware Repositories
URL= http://applemacbookfix.com/clear-region-fast-way/
URL= https://www.youtube.com/watch?time_continue=1&v=9Wli7_9v7CM
Please tell me how to create a clean ME region for a specific machine, a new repository.
It is thought that the intel QST of the built-in ME Region which is said to not exist so far is functioning the most special place.
Since the machine in which the problem occurred is probably not sold outside Japan, there is a possibility that existence is not known well,
Below, I will write in detail as much as possible.
All attached files exist in FMVESPRIMO.ZIP.（Download URL= https://drive.google.com/file/d/1ld-LSmz…7-gYduOuHC/view)
-------------------------------------------------------------
Machine owned by me
(Machine 1)
FUJITU JAPAN ESPRIMO FMV-D5380 NO.1 (FMVDC4F0C1) [INTEL ME VER 5.0.3.1126]
(Spec: URL= http://www.fmworld.net/biz/fmv/esprimo/0…ec.html)　
(Users Manual: URL= http://www.fmworld.net/biz/fmv/support/f…df/B6FJ1611.pdf)
(Machine 2)
FUJITU JAPAN ESPRIMO FMV-D5380 NO.2 (FMVDC4F0C1) [INTEL ME VER 5.0.3.1126]
(Spec: URL= http://www.fmworld.net/biz/fmv/esprimo/0904/d5380/spec.html)
(Users Manual: URL= http://www.fmworld.net/biz/fmv/support/f…df/B6FJ1611.pdf)
(Machine 3)
FUJITU JAPAN ESPRIMO FMV-D5370 (FMVDB4F041) [INTEL ME VER 5.0.1.1111]
(Spec: URL= http://www.fmworld.net/biz/fmv/esprimo/0810/d5370/spec.html)
(Users Manual: URL= http://www.fmworld.net/biz/fmv/support/f…df/B5FJ9271.pdf)
These are all computers manufactured by Fujitsu Electric in Japan.
The main specifications are as follows: [CPU = intel Core 2 duo E 8500 / intel Q 45 Express Chipset & ICH 10 DO / Mother Boad No. Wistron JIQ - 45 / Memory DDR 3 - 1066 2 GB x 2 TOTAL 4 GB)
The current operating system is Windows 7 32 bit main on all machines, and UBUNTU 16.04 LTS, windows XP, MS - DOS VERSION 7.1 are available in others.
The version of Intel management engine was investigated with ME analyzer v1.55.0 r122.
-------------------------------------------------------------
1. Background
I first destroyed BIOS SPI-ROM (MXIC MX25L3205) on FMV-D 5380 No. 1 (Machine 1) by mistake for pin assignment.
So we were able to dump miraculously the data from SPI-ROM (MXIC MX 25 L 3205) destroyed using ROM writer (TOP TOP 3000 & top WIN 6.36)
I prepared a new unused SPI-ROM (MXIC MX 25 L 3205), dumped it all the time and wrote all the data (4096 bytes) to the new SPI-ROM(MXIC MX 25 L 3205).
I attached it to FMV - D 5380 NO 1 (machine 1) and started it.
However, POST is very slow, or the screen is blacked out and an error has occurred, and the CPU fan and the power supply fan are rotating at full speed
"ME Error: No Channel 0 Memory; disabling HECI messaging" always appears in the error message, which is described as being a contact failure or installation error of the memory according to the user’s manual, but in fact Such a problem does not exist.
But sometimes POST takes a very long time but you can start Windows.
Since the data dumped from the SPI-ROM (MXIC MX 25 L 3205) of FMV-D 5380 NO 1 (Machine 1) was possibly broken,
I wrote the data dumped from the SPI-ROM (MXIC MX25L3205) of FMV-D5380 NO.2 (Machine 2), installed it and started it.
Then, what exactly the same problem occurred as before. There was also a doubt that somewhere on the motherboard was damaged at this point.
However, I thought that it was strange that Windows could start up from time to time.
So I did an experiment to move the data of SPI-ROM (MXIC MX 25 L 3205) as follows. For the experiment, CMOS clear (NVRAM RESET) is always performed every time.
FMV-D 5380 No. 1 (Machine 1) → FMV-D 5370 (Machine 3)
FMV-D 5380 No. 1 (machine 1) → FMV-D 5380 NO. 2 (machine 2)
FMV-D 5380 No. 2 (machine 2) → FMV-D 5380 No. 1 (machine 1)
FMV-D 5380 No. 2 (Machine 2) → FMV-D 5370 (Machine 3)
FMV-D 5370 (Machine 3) → FMV-D 5380 No. 1 (Machine 1)
FMV-D 5370 (Machine 3) → FMV-D 5380 No. 2 (Machine 2)
As a result of these experiments, what! Even in a combination without a doubt of the destruction of the motherboard, the same problem as before occurred.
-------------------------------------------------------------
attached files
The following files are files dumped from SPI FLASH ROM of (Machine 1) (Machine 2) (Machine 3)
[F01 _ FMV - D 5380 - 1. bin] FUJITU FMV - D 5380 NO. 1 (Machine 1) SPI FLASH ROM DUMP FILE
[F02 _ FMV - D 5380 - 2. bin] FUJITU FMV - D 5380 NO. 2 (Machine 2) SPI FLASH ROM DUMP FILE
[F03 _ FMV - D 5370. Bin] FUJITU FMV - D 5370 (Machine 3) SPI FLASH ROM DUMP FILE
Please be aware that the parts considered to be UUID and MAC address are intentionally replaced by 00 00 00 00 00. There is no problem with this part even if you input a free value.
Furthermore, since [F1 _ FMV - D 5380 - 1. bin] was able to dump miraculously from damaged SPI FLASH ROM, data seems to be partially broken.
I think that there is a failure in somewhere in MERegion, not total loss. However, specifically the defective part is unknown.
-------------------------------------------------------------
Part 2. Discussion
Considering from the results so far, I thought there was a problem other than breakage of hardware, motherboard and bios. Therefore we did a lot of experiments.
Specifically, it is a test to partially cut out, paste, and port the contents of the BIOS-ROM by using the binary editor (HEX EDITTER) and write it to the actual machine and start it up
As a result, it turned out that the above-mentioned problems occurred when the address 7FFF - D7FFFh of BIOSROM data was replaced with a machine different from the original machine.
Apparently I expected that there was a mechanism to lock the model to be mounted between 7FFF - D7FFFh.
On the other hand, FUJITU FMV - D 5380 No. 1 (Machine 1) for other parts 0 - 7 FFFh (MAC Adress etc) 260000 - 3 FFFFF (AMIBIOS etc)
FUJITU FMV-D 5380 No. 2 (Machine 2), FUJITU FMV-D 5370 (Machine 3), no problem occurred even if these were switched alternately
-------------------------------------------------------------
attached files
[F04 _ FMV - D 5380 - 1. Bin]
FUJITU FMV - D 5380 No. 1 (Machine 1) SPI FLASH ROM DUMP FILE [F1 _ FMV - D 5380 - 1. BIN]. Only addresses 7FFF - D7FFFh were exchanged for FUJITU FMV - D 5370 (machine 3) data [F3 _ FMV - D 5370. Bin].
This data has no problem in FUJITU FMV-D 5370 (Machine 3). However, there are problems in FUJITU FMV - D 5380 No. 1 (Machine 1) and FUJITU FMV - D 5380 NO. 2 (Machine 2).
[F05 _ FMV - D 5380 - 2. Bin]
FUJITU FMV - D 5380 NO. 2 (Machine 2) SPI FLASH ROM DUMP FILE [F2 _ FMV - D 5380 - 2. BIN] inside. Only addresses 7FFF - D7FFFh were exchanged for FUJITU FMV - D 5370 (Machine 2) data [F3 _ FMV - D 5370. Bin].
This data has no problem in FUJITU FMV-D 5370 (Machine 3). However, there are problems in FUJITU FMV - D 5380 No. 1 (Machine 1) and FUJITU FMV - D 5380 - 2 (Machine 2).
[F06_FMV-D 5370.bin]
FUJITU FMV - D 5370 (Machine 3) SPI FLASH ROM DUMP FILE [F3 _ FMV - D 5370. BIN] inside. Only the address 7FFF - D7FFFh was replaced with the data of FUJITU FMV - D 5380 NO. 2 (machine 2) [F2 _ FMV - D 5380 - 2. bin].
This data has no problem in FUJITU FMV-D 5380 NO. 2 (Machine 2). However, there is a problem in FUJITU FMV - D 5370 (Machine 1) and FUJITU FMV - D 5380 NO. 1 (Machine 1).
-------------------------------------------------------------
Part 3 Information gathering and experiment
When I was looking for information from the web, I discovered a lot of sites written about ME cleaners and clean ME regions and I came to this site (https://www.win-raid.com)
So referring to these sites below, I prepared Flash image tool Version 5.00.1167 and Intel ME 5 Firmware Repository Pack beforehand and attempted to incorporate a clean ME region and repository
(URL= [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization)
(URL= Intel Engine: Firmware Repositories)
(URL= http://applemacbookfix.com/clear-region-fast-way/)
(URL= https://www.youtube.com/watch?time_continue=1&v=9Wli7_9v7CM)
As I tried these things, it turned out that the range of BIOSROM data 7FFF - D7FFFh that I thought was problematic was almost equivalent to ME Region.
So I did the next experiment. For the experiment, CMOS clear (NVRAM RESET) is always performed every time.
FUJITU FMV-D 5380 NO.1 (Machine 1) Incorporate 5.0.3.1126_DO_PRD_EXTR.bin into SPI FLASH ROM DUMP FILE [F1 _ FMV - D 5380 - 1.bin]
Incorporate 5.0.3.1126_DO_PRD_EXTR.bin into FUJITU FMV-D 5380 No. 2 (machine 2) SPI FLASH ROM DUMP FILE [F2 _ FMV - D 5380 - 2. bin]
I created these files, burned them into SPI-ROM, and started up with (machine 1) and (machine 2).
When these experiments are done, POST got faster, CPU error occurred in the 1st and 2nd POST, but the error disappears from the 3rd POST.
ME Farmware itself seems to start function normally.
But what is that, despite the fact that FAN is connected, the CPU FAN Eerror that has never existed always occurs, and the CPU fan and the power supply fan are actually rotating with full power.
As a result, ME regions recovered by cleaning up but Intel QST did not recover function.
In addition to those, we experimented to intentionally incorporate different versions of [5.0.2.1121_DO_PRD_RGN.bin] and [5.2.0.1009_DO_PRD_RGN.bin], but the results were not different.
Windows 7 will work without problems. However, Intel QST still seems to have trouble, and it can not detect sensors other than CPU.
-------------------------------------------------------------
attached files
[F07 _ FMV - D 5380 - 1. Bin]
FUJITU FMV-D 5380 NO.1 (Machine 1) SPI FLASH ROM [5.0.3.1126_DO_PRD_EXTR.bin] is incorporated in DUMP FILE
[F08 _ FMV - D 5380 - 2. bin]
FUJITU FMV - D 5380 NO.2 (Machine 2) SPI FLASH ROM [5.0.3.1126_DO_PRD_EXTR.bin] is incorporated in DUMP FILE
[F09_FMV-D5370.bin]
FUJITU FMV-D5370 (Machine 2) SPI FLASH ROM [5.0.1.1111_DO_PRD_EXTR.bin] is incorporated in DUMP FILE
-------------------------------------------------------------
Part 4 I tried exploring the circuit on the board.
I followed the circuit of CPU fans and power supply fans. To what astonishingly it was directly connected to ICH 10 DO (82801 IDO).
It turned out not to be connected to Super IO chip or Embedded Controller.
These machines apparently seem to be very rare machines that use the Intel QST feature on top of the ME-RTOS that was previously thought not to exist.
As it is no longer possible to use the ME region and the ribostrozy file published on the site, there is no other way to create a clean ME region and ribonology dedicated to this machine
However, it is a very miserable situation. I think that the data inside the ME region seems to be fragmented to a large extent, I deleted it in a single place and started up it for about 100 times
There is no prospect of resolution in any way.
Below This incorporates 5.0.3.1126_DO_PRD_EXTR.bin into FUJITU FMV-D 5380 NO.2 (Machine 2) SPI FLASH ROM DUMP FILE [F5 _ FMV - D 5380 - 2. bin]
To the SPI flash and start fitting into FUJITU FMV - D 5380 No. 1 (Machine 1) and remove the SPI flash and dump it immediately after the CPU error etc does not come out.
Compared with [5.0.3.1126_DO_PRD_EXTR.bin], not only a lot of strange data is added but also it is divided into pieces.
--------------------------------------------------------------
attached files
[F10 _ FMV - D 5380 - 1. Bin]
FUJITU FMV-D 5380 NO.1 (Machine 1) SPI FLASH ROM [5.0.3.1126_DO_PRD_EXTR.bin] is incorporated in DUMP FILE.
After that, it is the data dumped from the SPI flash after letting POST three times in FUJITU FMV - D 5380 NO. 1 (Machine 1).
-------------------------------------------------------------
Part 5. Supplementary explanation
(A) Difference between FUJITU FMV-D 5380 and FUJITU FMV-D 5370
There is almost no difference between FUJITU FMV - D 5380 (machines 1 and 2) and FUJITU FMV - D 5370 (machine 3). Motherboards are all Wistoron JIQ 45Y
However, FUJITU FMV - D 5380 (machines 1 and 2) has the following difference which does not exist in FUJITU FMV - D 5370 (Machine 3).
(1) Control of the power supply fan in addition to the CPU fan
(2) There are parts for power supply fan control on the mother board (PWM to voltage conversion circuit power FET and chip parts)
(3) It seems that there is a program for power supply fan control inside intel QST
(4) I carried out an experiment to embed necessary parts for power supply fan control on the motherboard of FUJITU FMV-D 5370 (machine 3), but a program for power supply fan control
Because there is no control, we are always turning with full power. Intel QST If there is a program of the power supply fan control inside, it is expected to be available. But I do not know how to do that.
(B) About AMIBIOS
FUJITU FMV - D 5380 (Machines 1 and 2) and FUJITU FMV - D 5370 (Machine 3) and FMV - D 550 / B and FMV - D 751 / C. These are older machines, but Aptio BIOS is used. However, there is no UEFI mode.
AMIBCP version 4.55 and MMTool version 4.50 were necessary for remodeling this AMIBIOS. In case
(C) About Winstoron JIQ 45 Y motherboard
The Winstoron JIQ 45Y motherboard is incorporated in machines called FMV CE / E50 for machines other than FUJITU FMV - D 5380 and FUJITU FMV - D 5370.
However, MCH is said to be intel G45 Express Chipset. Unfortunately I do not have this machine.
(D) About Fujitsu FMV CE / E50
FUJITSU JAPAN DESKPOWER FMV-CE / E50 (FMVCEE 50) [Intel ME probably exists]
The main specifications are as follows: [CPU = intel Core 2 duo E 7500 / intel G45 Express Chipset & ICH 10 / Mother Boad No. Wistron JIQ 45 Y / Memory DDR 3 - 1066 2 GB x 2 TOTAL 4 GB)
(Spec: URL= http://www.fmworld.net/fmv/pcpm0812/deskpower/ce/method/)
(Users Manual: URL= https://www.fmworld.net/download/DD003729/DD003729.pdf)
(Users Manual: URL= http://www.fmworld.net/download/DD003506/DD003506.pdf)
(E) reference
For reference, I have attached another SPI ROM dump file of the machine manufactured by FUJITSU JAPAN which I have.
Please be aware that the parts considered to be UUID and MAC address are intentionally replaced by 00 00 00 00 00.
[F11_FMV-D550.bin]
FUJITSU JAPAN ESPRIMO FMV - D 550 / B (FMVDF 2 B 0 E 1) [intel ME does not exist]
The main specifications are as follows: [CPU = intel Core 2 duo E 7500 / intel G41 Express Chipset & ICH 7 / Mother Boad No. Wistron JIG 41 Y / Memory DDR 3 - 1066 2 GB x 2 TOTAL 4 GB)
(Spec: URL= http://www.fmworld.net/biz/fmv/esprimo/1104/d550b/spec.html)
(Users Manual: URL= http://www.fmworld.net/biz/fmv/support/f…df/B6FJ5351.pdf)
[F12_FMV-D751C. bin]
FUJITSU JAPAN ESPRIMO FMV-D751 / C (FMVDG 4N 0 E 1) [intel ME VER 7.0.10.1023]
The main specifications are as follows: [CPU = intel Core i5 2400 / intel Q67 Express Chipset / Mother Boad No. Wistron JIQ 67 Y / Memory DDR 3 - 1066 4 GB x 4 TOTAL 16 GB)
(Spec: URL= http://www.fmworld.net/biz/fmv/esprimo/1104/d751c/spec.html)
(Users Manual: URL= http://www.fmworld.net/biz/fmv/support/f…df/B6FJ6541.pdf)
-------------------------------------------------------------------- -------------
attached files
[F11 _ FMV - D 550. bin] SPI FLASH ROM DUMP FILE
[F12 _ FMV - D 751 C. bin] SPI FLASH ROM DUMP FILE
-------------------------------------------------------------------- -------------
Thank you for your consideration, please lend me the power.
kanta
Hello,
This is an extremely confusing post (book). It’s impossible for someone to follow. Please state briefly what exact machine has which problem. Also, attach/upload/link to the stock Jujitsu BIOS update package. That’s the best to have. Otherwise, at least the original/first dump before you made any modifications (F01 - F03 ?).
Hello
I am going to rewrite all the sentences. However, I briefly made a postscript at the beginning and deemed it. Is it okay with such a simple writing style?
1. Machines that currently have problems
(Machine 1)
FUJITU JAPAN ESPRIMO FMV-D 5380 No. 1 (FMVDC4F0C1)
2. The symptom of the problem
BIOS - SPI The computer malfunctions due to a data defect in the flash ROM.
3. Attempted repair part 1
I tried repairing data by copying data from the same model machine. At least AMIBIOS is working normally, but ME firmware could not be recovered.
4. Attempted repair part 2
As we determined that ME firmware needs to be cleared, [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
We cleared the data according to, but it did not solve it at all. Moreover, CPU FAN TACH ERROR which was not in the past occurred.
5. Attached file
FMVESPRIMO.ZIP. (Download URL = https://drive.google.com/file/d/1ld-LSmz…7-gYduOuHC/view)
The first dump of problem (Machine 1) is [F01_FMV-D5380-1.bin]
First dump of another same type machine (Machine 2) [F02_FMV-D5380-2.bin]
First dump of machines that closely resemble (Machine 3) [F03_FMV-D5370.Bin]
ME trying to clear the firmware dump [F04_FMV-D5380-1.bin]
Is a dump of the problem computer included, before anything was written to it’s flash chip? That is important if you have this, current dump of the problem machine is not necessary, only backup/dump from before anything was written to the chip.
Same type machine you included will help, but best if you have the original problem machine dump before anything done to try and fix it.
But, if bad BIOS flash or corrupted BIOS is the main cause of the initial issue, then backup of rom before any repair attempts most likely wont be useful.
Before even looking at BIOS files, based on what you said there may be some hardware failure or damage.
Due to if system 1 & 2 are exactly the same, and UUID/LAN MAC/Serial aside do not matter. The BIOS from 2 does not work on 1 properly, then there is either hardware failure somewhere or the systems are not exactly the same as you might think (Maybe some small hardware difference somewhere).
Because if the are the exact same boards, then rom swap or reprogram from 2 to 1 should work without issue.
Hello, Thank you for reading
Unfortunately, there is no previous dump / backup of the machine in question.
The dump before trying to repair the problem machine is [F01_FMV-D5380-1.bin]
A machine dump of the same model is [F02_FMV-D5380-2.bin]
A dump of a machine of a similar model is [F03_FMV-D5370. Bin]
Attachment
FMVESPRIMO.ZIP. (Download URL = https://drive.google.com/file/d/1ld-LSmz…7-gYduOuHC/view)
I understand what you are saying
However, unlike a general BIOS, this machine has a mechanism for tightly connecting the BIOS / ME - BIOS and the machine.
As a result of many experiments, we found that the mechanism to tightly connect machines is confused
But I do not know anything more.
Thanks, I downloaded files above, working and checking on things now.
Do you have link to stock BIOS from manufacturer, not a BIOS dump with programmer? If yes, please add link, thanks! Never mind, I found it!
Here if you need @plutomaniac http://www.fmworld.net/biz/fmv/support/d…2009_2/desktop/
http://azby.fmworld.net/app/customer/dri…Number=E1013243
See my edit above too, refresh page, in case you missed it, about possible hardware issue like you suspected.
BIOS and ME are always connected, same machine same BIOS will always work swap unless some stuff setup security-wise, but that will be cleared via programmer anyway vs BIOS flashing.
I will make you new BIOS to try programming, should work OK! Please give me maybe 30 minutes
BIOS link of manufacturer stock
FMV-D 5380 (Machine 1.2) http://www.fmworld.net/download/E1013243/E1013243.exe
FMV-D 5370 (Machine 3) http://www.fmworld.net/download/E1009029/E1009029.exe
But please be careful. ME Farmware is not included in the manufacturer’s stock BIOS.
It is much smaller than the dump file.
From the results of previous experiments I have found out that there is a mechanism to lock the machine inside the ME Farmware or ME region. I can not understand anything beyond that at the moment.
Yes, thanks, I found and posted link above. Yes, I know ME is not included, it’s not my first day today playing with BIOS 
BIOS_Data.rom is 1,644 kb do not worry, I know what I am doing and already see a problem in the dump BIOS from system1, probably the main problem!
I am only using FMV-D 5380 BIOS from 1 & 2 + Stock BIOS download, all will be working I think, don’t worry and wait a little bit and I shall have good BIOS for you I think!
@kanta - here is BIOS to try, I think this should fix everything unless there is some hardware failure. That could be possible, depending on how you originally shorted out the BIOS initially when problem first happened.
This is your BIOS image 0F01_FMV-D5380-1, edited to bring in two main BIOS volumes from stock BIOS download (last two volumes) in case of corruption, replacing original volumes in your F01_FMV-D5380-1 BIOS
ME settings checked and re-imported from F02_FMV-D5380-2 to new BIOS ME, ME region added in BIOS, then NVRam cleared leaving only stock data section.
ME Settings in original 01 file did not match 02 ME settings, a few settings were different regarding Intel AMT, so this may be some of the issue too
I think NVRam entries may have been the issue with fan and slow start etc. now it’s fresh clean, and only small main stock section like it would be when first turning on system brand new.
If this fails, I really do think some hardware also fried on you during the initial incident. I can try import the other way, main initial NVram data from 01 into BIOS 02, ME transfer, volume rebuild etc if this fails, but I think outcome would be the same as this BIOS if it doesn’t work
Please unplug the machine from the wall, while you prepare to program the BIOS, and remove the CMOS battery.
Then press and hold the power on button for 20-30 seconds or so, making sure board is totally drained of power for 1+ minutes This makes sure ME gets reset
Then you can put CMOS batter back, plug into the wall and program BIOS as you usually do.
Once you start up, enter the BIOS and load “Setup Defaults” and immediately save and apply then exit and reboot back to BIOS and make any changes you need.
https://www.sendspace.com/file/zyjo6q
*Edit - Above BIOS has original 01 ME settings @ Intel AMT - this BIOS below has the same settings as 02 BIOS (Sorry for the confusion here, I would remove BIOS above here, but leaving in case you already downloaded)
Please test this one first, I think it should work if machines are all exactly the same, as I expected the one above to do, but I forgot those two changes now in this one. Please do the power drain dance described above between each of these tests, that way ME is reset for each
https://www.sendspace.com/file/a8qa3l
Wait a minute, before you program anything can you confirm via CPU-z motherboard tab, upload an image. Is this Q45 chipset or B43?
Since you are not here, I went ahead and did the other way. Default ME in FIT app was setting McCreary ICH10D and that is only in B43, Q45 is Boulder Creek ICH10 (no D) (non-default FIT setting).
If you are certain it is Q45, then use BIOS below
https://www.sendspace.com/file/ee51ei
Also, I can update CPU microcodes later if you want, and put back in correct LAN MAC ID if you have it on board or LAN area etc, let me know once you test and hopefully this working, then if you need I can do those updates too.
Thank you for your reply.
Since I am not currently near the computer, I can not test these binaries right now.
There is no mistake in the Q45 chipset for those with built-in FMV-D 5380 (machines 1 and 2) problem.
We will report further detailed specifications (log file of CPU - Z etc.) later.
No need for CPU-z, as long as you are sure, check yourself with CPU-z, that’s good enough
Q45 Boulder Creek ICH10 (no D) BIOS is only last link I posted, don’t program first two linked BIOS I linked, they have ME set for B43 McCreary ICH10D
Hello. Thank you for yesterday.
I still seem to have some problem.
Binary [ME-NV-DuaLVL4-No-D.bin] was written to SPI Flash Rom of FMV - D 5380 (Machine 1), and CMOS reset was carried out reliably.
But the result is not much different from before.
State of machine before POST
------------------------------
CMOS reset → Power on → Automatically disconnected → Power on again → At about 30 seconds the fan is running at full speed → POST does not start, so turn off the power manually
→ Power on again → Automatically disconnected → Power on again → POST
------------------------------
After that, the message "ME Error: No Channel 0 Memory; disabling HECI messaging" is displayed and the fan is running at full speed.
After starting Windows 7, when I started up Speedfan 4.49 and confirmed it, no sensor etc was detected, and the intel QST is still not working.
Entering the BIOS, loading "Setup Defaults" did not change.
I tried binary[ME-NV-DuaLVL4-No-D.bin] with FMV-D5380 (Machine 2) just in case.
However, with this machine, POST did not start no matter how many times reset and power on / off were repeated.
Next, we tried binary [ME-NV-DuaLVL4-No-D.bin] with FMV-D5370 (machine 3), and it was almost the same result as FMV-D 5380 (Machine 1).
Supplement:
AMM BIOS of FMV-D 5380 (Machine 1) can operate without problems with FMV-D 5370 (Machine 3), everyday exclusively use this.
ME Firmware and ME Region are expected to operate if something is devised. But for now it has not been successful. This is the next goal.
You’re welcome, and sorry there is still issues! Thanks for the testing info, it helps prove some things to me in my opinion
I did see Intel QST in the ME settings, and made sure those were set to match your 02 BIOS from that second working exact same machine.
Machine 3 should not be used with this BIOS, or compared with any other BIOS from 1-2, at least not for this discussion since it’s not the same system and may not have same ME settings etc meaning any result cannot be reliable for comparison.
It seems to me something is broken or fried on system 01, dealing with QST, some sensor probably when the system was initially shorted or BIOS shorted etc whatever happened that caused all this.
Also, this BIOS I created, not working on System 02, proves to me that system is not the same as 01. So, the changes I made from 01 initial ME settings, to match system 02, could be cause of some problems with BIOS I made for 01.
This ME error about no memory, do you have the memory in the correct slots? If you are unsure, try the other two slots instead and see if same error appears.
Let’s redo that, without the use or settings of system 02, since it does not appear to be the same no matter what hardware stickers or case labels etc say on them.
I will edit in new test BIOS here, soon, please keep refreshing for update I will edit it into here.
WAIT!! Please read the post again I made earlier today at #9, I posted to only use last BIOS I put up, which you did not use. Please test last BIOS only - ME-NV-DuaLVL4-No-D.bin
And CMOS reset is not goal of what I posted, goal is reset ME, so please be sure all power drained and removed from the board for 1+ minutes before you reprogram BIOS
I just checked - iQST is enabled and unlocked, so if the ME-NV-DuaLVL4-No-D gives you same issue with this then there is some hardware failure, something shorted out etc.
QST is disabled in MEBx interface (Default setting), this is for AMT, which is also disabled, so you’d never access the MEBx interface anyway
I am sorry for giving a misunderstanding, Correction of # 12 sentence. We actually tested [ME - NV - DuaLVL 4 - No - D. bin], not [ME - NV - DuaLVL 3. bin].
There are no pins or switches in this machine for CMOS reset. For all reset, remove the battery and realize by turning off the main power switch (all power from the outlet is blocked).
Completely resetting is possible in about 20 seconds from experience in this state. I do not have to worry because I do this without fail during experiments.
We tested again with FMV-D 5380 (Machine 1), of course write [ME-NV-DuaLVL 4-No-D. bin] to the SPI-ROM.
There are only two memory slots in this machine. Therefore I removed the dust from the memory electrode and swapped 1 and 2.
This resulted in the same symptoms described in # 12.
OK, thanks for all the clarifications! For the memory issue, try one memory only, see if same, then try in other slot, same error still?
Try this BIOS, enabled QST at MEBx interface (control + P at startup to enter, same time you’d normally hit key to enter BIOS). Test going in here and make sure QST settings you want enabled are shown and enabled, also verify they are enabled in regular BIOS interface too.
https://www.sendspace.com/file/ibatar
Entering MEBx, can only be done after applying setup defaults and rebooting, it is disabled at failsafe settings, so optimal or setup defaults must be applied first, then reboot and do the control + P
Intel ME subsystem config (QST) in the BIOS is also disabled by default until after you apply setup defaults and then reboot back to BIOS.
If still no change, there is hardware failure, something shorted out during initial shorting problem.
That could be anything, some sensor or tiny resistor going to/from sensor, same with memory issue too I assume or that could be due to something related to the sensor failure too possibly.
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.