I gave up trying to find it, almost had it I thought, screenshot'd a few remaining files to remove that it had to be in I thought, then removed those and it was still there.
It's in the region I showed above though, because I removed the entire region and issue was gone, put it back and back came the error, so if you go through one by one and remove, save, check, remove, save, check you will find it eventually.

I think that several modules cause the error. When I delete all the file inside "8C8CE578-8A3D-..." from the bottom up to "899407D7-..." (Setup) (not including this file) the error is still there, but when I include it the error disappears, which means that at least the file "Setup" is causing it. However, removing only "Setup" does not solve the issue...

**** EDIT ****

So, after a bit of work I found all the wrong modules. The list is:

- Setup
- ServerMgmtSetup
- ReFlash
- EventLogsSetupPage
- HDDSmart
- FboGroupForm
- AMITSE

When all these modules are removed the BIOS can be opened in AMIBCP v5.02 without any error.

Is it possible to solve the problem with the modules without removing them?

Great, I was almost there too! And thought I had a list like that, but after further narrowing trying to find the one I couldn't. Is that how you feel now too, you can't delete anymore of those to narrow it further down, it must be all of those?
If yes, then maybe same error is in all. Please upload those files in a zip and post here and I'll see if I can find the problem. Thank you for your work, I spent hours trying and every time I almost had it I got lost or it seemed the list I narrowed down to ended up not being it somehow.

Thank you ;)

Yes, all of them must be removed...

Which files do you need exactly ? I guess that you need to original BIOS but do you want me to extract the "faulty files" as .bin ?

Thanks to you too! Yes, only those modules you pointed out, please extract each one as-is and zip. Extract them with UEFITool - as-is, at the GUID Root level on each one.

Please find enclosed the files in .ffs.

Thanks, I will check. Did you already start looking in them? If yes, did you see anything promising yet?

Yes I tried to have a look at them but honestly I think I have reached my limits of competence. I have never done that before... I actually do not know what to look for. To me this error is very strange because the BIOS works fine, it is only AMIBCP that has problems reading it.


**** EDIT ****

So I have maybe something to start with.

I removed all the faulty files from the BIOS exept "HddSmart", the error was thus still there but only due to one file. Then, I erased different parts of "HddSmart" and replaced it in the modified BIOS until the error disappeared. It turns out that deleting the line at the offset 000053E0 solves the problem. Is this somehow helpfull?

**** Second EDIT ****

It seems that all the faulty files (except AMITSE) contain this series of bytes "00 48 00 49 00 49 00", which is not present in some "working" files that I have randomly picked.

Finally I also found the faulty sequence in AMITSE, it is located at the offset 0002A0B0, the sequence is :"F2 BC 65 CA E9 F9 BE 86 9E 1D 1C 61 91 FC 6F 09 A1 98 83 9E".

Replacing all the faulty sequences by 00 allows to open the BIOS without error. However doing so leaves "setup configuration" totally empty...

I thought you said it was above your pay grade? So, you got it figure out, somewhat? AMITSE is the setup menu text file, well some of it, I would not modify this one until you're sure you've found the problem in some other file first.
It would be great if we could get an IFR output from Amitse, but no dice. Universal IFR extractor might help you figure this out.

All your looking for here is a language name, which I assume would be English since that is the only language in this BIOS, and assumed maybe it was spelled wrong or something.
Even if it's not English, it should only be some word longer than 8 characters since that is the rule it's violating, probably they did on purpose so hinder editing, expecting this exact outcome but not expecting group like us to try and find and fix
I do bet it's English though, since it says Language name is violating this, not setting entry or setting name etc.

I will look tonight and this weekend

Yes, you are right, all the files contain the lines ".en-US..E.n.g.l.i.s.h..", but I do not see what is wrong with this...

I think that is OK too, only mentioned English because the error itself says Lanuguage name, but maybe that is wrong/misleading.

At first glance I noticed this in smallest file hddmsart, then looked in next few larger files and found the same. Since this is saved location from originating HDD I think, changing to "test" or some other name under 8 digits should be OK

UVWATAUAVAWH (12) - 55 56 57 41 54 41 55 41 56 41 57 48 - In hddsmart

VWATAUAVH (9) - 56 57 41 54 41 55 41 56 48

WATAVH (6)

word is there many times, sometimes little shorter, looks like a "file location path" on the builders HDD
I think this may be his name, or the main folder name, where the issue starts, other folders based on this named variant on all files
Either 9 or 12 above would be an issue to AMIBCP, if this is what it's complaining about.

It looks like "UVWATAUAVAWH" and its derivatives are something rather common, I am not sure that this is responsible for the error here...

http://www.hexacorn.com/blog/2013/05/16/...e-pushy-string/

I think that I have identified the faulty sequences because removing them fixes the error, however I do not understand what they are doing.

Btw, could you get usefull infomation with Universal IFR extractor ?

Good find, I didn't even think to look around about that, just assumed. I guess due to that, this is probably not it at all then!

What you mention may only be fixing the error because it's breaking the module, thus no setup tab loaded. You're only looking for some name longer than 8 characters, is everything OK if you FF the last three digits from sequence in post #24 >> remove these 98 83 9E

I think some files I looked at IFR output, but most were only the 1kb blanks

Yes, it is difficult to understand what is actually hapening when the lines are removed...

Replacing the last three digits of the sequence in AMITSE by "FF" solves the error (the other files must however be corected). Nevertheless, the folders in "setup configuration" appear without any name, i.e. it is like erasing the entire sequence.

The IFR of "setup" gives a longer file, but I did not find anyting usefull ... I attach the file to the post.