Thanks for the BIOS an images. I am not expert in ME, so I am not sure about your last question, on how that could be possible. I think @Fernando would be able to better answer that when he has a little time to spare, he is ME expert! Thanks Fernando

Wait a sec, that was Microcode not ME in BIOS image, sorry I missed what you said there still sleeping Well maybe Fernando can still offer some advice on the ME error shown below, is it OK or possibly cause of the ME N/A issue

I was wondering if maybe AIDA64 was maybe giving that based only on CPU detection alone, but still not sure how this is happening, it shows F which is close to 1F too.
I don't know, can't find reference of that microcode anywhere on Google either, so maybe BIOS and AIDA64 both give F/1F only based on CPU detection not actually microcode detection.
Maybe it has to be in there somewhere? Surely if only incorrect CPUID microcode is there, and not one for your CPU, it wouldn't load/POST at all? I will keep looking around and hopefully find this 1F code

FD is all unlocked, so you can write ME to flash rom, that is good. Always check FD is all unlocked every time with UEFITool before you flash or program any BIOS to the chip, if you see lock on something don't flash until you can change it to unlocked first, that way it stays unlocked on your board.
If you need me to show you how to always check BIOS before flashing, for this lock/unlock let me know and I will show you image and link tool.

I checked the ME you uploaded, thanks. I see a warning, but I'm not sure if that is common, or OK, or if maybe causing this ME problem?


I will try making you a clean new ME tonight and see if I get same error from that version software that made it and same version ME.
Can you load ME drivers in windows, or do you get error no matter what when trying to install? Version shown below in this error image, so you can see what version drivers to try

Ahh! Sorry for the wrong praise Fernando
I always see you posting tips and info, but maybe now that you mention it your expertise is Intel RAID drivers of course. Duh, name of site, I should have remembered correctly due to that alone!

Well, I did a clean new ME, and get exact same error still. I did not use exact same version ME due to none in repository were exact match, and not same FITC tool version either, so didn't expect to see same error.

I used newer version (next version up), but after mod I see it is older build date, that doesn't seem usual for Intel? Maybe @plutomaniac will be able to comment about this version/date and size/padding warning when he has a second.
The files look OK and obviously it runs like that because you're using the SPI Dump I first noticed this with so it's OK as far as booting the board, but maybe this is why or part of why ME is not working too?
I do see a lot of padding at the end of the file, but same padding in output ME directly from FITC too (If leaving generate intermediate files left checked, I redid to verify that would happen or not)
So seems normal probably, it looks to be around 500kb FF padding increasing file size to match 2,044kb from original 1,524kb

Could be maybe the error is due to how UEFITool extracts the ME region, I compared both dump SPI and new build SPI (No error in MEA)


But when extracting ME from both to verify w/ UEIFTool, same file size/padding error


Here is new BIOS, built from the last full SPI dump you sent, with now updated version cleaned ME
http://www.filedropper.com/newmebiostest

Close any open windows or programs, be ready for reboot. Open command prompt at the unzipped folders location, if you are unsure how do shift + right click on the folder itself, or anywhere blank area inside the folder, then choose "Open Command Window Here"
Then flash with included FPT from the command prompt with these two commands as follows:
1. fptw -savemac -rewrite -f NewMEBIOS.bin
2. fptw -greset (Run this after above step completes, before closing the prompt window)

Let the system flash and then it should shut down and reboot after command #2, if for some reason it does not shut down after flash completes go ahead and manually shut down once you are certain the flashing is complete.
Then unplug power supply from the wall and wait one minute. Plug it back in and start the system again and go into BIOS and load optimal defaults, then any other changes you need like RAID or AHCI etc and then reboot back to BIOS.
Once in BIOS check ME version, then to windows and run MEInfoWin (included too) from another command prompt and see what it says (Post image here) Intel ME v10 drivers will have to be installed if not already

Thanks so much.

I will have a try once I am free.But I will have to stay in the hospital for 2-3 days.So it would take some time.
Sorry for that.

You're welcome and I hope you get better quickly!
No rush at all!

I had tried your newMEbios.bin,but it didn't work,still showed "N/A".
And the Intel ME v10 drivers could not be installed,but showed some errors like"platform not supported"etc.

I installed Windows 7,but couldn't open it again after installed or upgraded the drivers of motherboard chips,vedio card and other hardwares.(what the hell?)

And I got something what may be useful.
In win10,whether the microcode version showed "not loaded" (by the complied BIOS bin) or "16"(by the original BIOS bin) in the BIOS,the microcode version of CPUID section always showed "1Fh" in AIDA64.
In win7,there was no the microcode version item at all.(before installed the drivers)

And another bad news is I had bricked the motherboard becauce of tring flashing other manufacturer's similar BIOS.
So I have been tring to recovery the BIOS.Good news is that there is some tools like burning clip which can help flash the BIOS without removing the BIOS chip.
I will be back after I recovery it.

Sorry to hear the board now needs recovered from other brand BIOS flash! When you get programmer, you will be able to much easier flash in whatever ME version you want, this will help a lot I think!

I still am unable to find microcode 1Fh, it would be great to get a copy somewhere so I can find where it is in the BIOS.
If you need help picking out BIOS recovery tools let me know, I just picked up some cheap on ebay to compare with my more expensive ones, and to be able to be more familiar with cheaper programmers when trying to assist others using them here.
I got the blue/green CH341A for $3.50 and the black version for $2.45, and jumper cable for $2.42. If you want links to those let me know and I will post, it's on ebay from China so long wait on shipping unless you are close to there.

Thanks @plutomaniac - I thought that's probably what's going on, but how does it even boot to OS to get a microcode from OS?
His CPU is i5-5250U CPUID 306D4, and the only microcode contained in the BIOS that I can find is for CPUID 306C3

Thanks for that.
I was busy these days and had a wrong method to flash the BIOS.
So it took a long time for recovring it.
But thank Godness,I succeeded just ten minutes ago.

So now I can try the BIOS which had been got the lastest and correct microcode,although I don't think it can change a lot.

Good you finally got it recovered. You have flash programmer now? If yes, then no worries, you can always fix if bad BOS flashed in during testing BIOS mods.

Good you are feeling better now too!

Yes,I have an XTW100 programmer and a burning clip (which can help to flash BIOS without removing the BIOS chip) now.

So would you post the BIOS file with the lastest and correct microcode for me?I just want to have a try.

And I will have another try flashing your newMEBIOS.bin.Can you give me a link where I can download the Intel ME v10 drivers?Because I am not sure the Intel ME v10 drivers that I dowloaded before is the correct one.

First you must test your programmer, make a few backups from known working BIOS and make sure it verifies correctly (Do a few times to be sure). Then, do the same by writing any working BIOS to the chip, and verify.
This is important, because you may find some software versions give error when dumping or writing to, and if that happens you need to try other version until it doesn't happen so that you can then be sure any failed BIOS is failed BIOS not failed due programmer error

Latest BIOS I made is in post #19, program that one, and follow instructions I posted about draining all power from board after you program for at least 1+ minutes. I have found that error I mentioned with extra padding is normal on some extractions of ME so ignore my thoughts about that.
Once programming is complete, unplug power supply from wall, remove CMOS Battery and press the power on/off button on the case or short power on/off ins a few times, leave board sitting without any power for 1= minutes.
This resets the ME state, if board does no start fully once you are done with that, remove one stick of memory, if still not starting then programming likely failed and you should dump and verify to confirm program fail or BIOS itself fail.

Drivers for all ME are here, but I am not sure which one is best for your system, and maybe these could not install before because maybe ME didn't get reset (Showing N/A is problem) - Intel Management Engine: Drivers, Firmware & System Tools
@plutomaniac - can you please and thanks, could you tell us which is correct ME driver version for this system, it's using this BGA1168 CPU - http://www.cpu-world.com/CPUs/Core_i5/In...0processor.html
@sugo - what is chipset in this board, in case that also matter to which ME driver version

I tried the BIOS of MSI cubi on my MiniPC.It's lucky that the computer can run with it.But the ME item in the BIOS still showed "N/A" and the wireless devices didn't work,neither the freezing problems.So I flash back.

I tried your newMEbios too.I am sure that there is no the lastest and correct microcode in it.Can you please make another one with the correct microcode?
And I had done as your instruction,but the ME item in the BIOS still showed "N/A".What a hopeless situation!

And the chipset of my MiniPC: