@molex
My motherboard model is GA-MA69VM-S2,

In attach you can find original bios

@Lost_N_BIOS @molex
since the rom is only 512kb I am simulating how to move the modules, to understand how to size the dummy, my best simulation is attached, the only way to fit all the modules is to move the epn module at the end, but i don't know if this is feasible.

Thanks for your time

@vash_85 not good (bad) power system for phenom II x6...

@molex

I know, i have budget to use a phenom X6 95w, due to split power plane incompatibility, at now system work with a phenom x4 95w

@vash_85 - you should have $2 programmer and at least $3.50 SOIC8 test clip cable, then there is NO risk of bricked board. Why would you mess with BIOS at all, without having these VERY cheap tools in hand?

@molex - is package at post #88 two BIOS only, one before, one after? If yes, then I will look Motherboard works, boots, and works properly is two very different things
You mentioned having CPU related issues, and memory issues too, possible both due to Agesa update not done fully/correctly. You need to edit and update the holes when you do the Agesa swap, since you didn't this may be the reason for your issues.
You will need to find a guide about editing holes, I don't think you can simple swap them, and all may not be related either.

Probably clean install, or driver updates fixed your LAN. The BIOS LAN module has nothing at all to do with what you use in windows.

@Lost_N_BIOS yes BIOS_orig.bin is original FKe BIOS and BIOS_Build.bin - BIOS after update.

BIOS of 770 and 785 motherboards have one difference in hole0. Hole0 for 770 have cimrd790 rom, and for 785 cimrs880 rom.
Hmm another question, if I find BIOS from another 770 motherboard manufactured by another vendor (msi for example) with new agesa and holes similar to gigabyte mobo. Can I use agesa and meminit modules from another vendor mobo, or 100% brick?

And I cant use meminit from AM3 DDR3 motherboards, right?

Thanks, I will look and see what you did. This model is obviously unusual for Gigabyte, if you moved the sensitive modules (GV3 (Agesa or PPMinit), Minit/MemInit, and sometimes HTInit/HT.Dll), most you cannot move, resize, or relocate (and you should make a habit of working around that as a given)
On the holes you mentioned, did you extract and compare all the others via hex and they are same, except for the two you mentioned? There is a guide somewhere about these holes, I'm not sure if it's here or somewhere else, but I read an depth one before.
It was about editing, moving, how the work, how they relate to Agesa and other modules in the BIOS, and how other modules point to them, or how they point to other modules or hold the locations etc. I'll have to see if I can find that for you again

I don't think you can simply transfer holes around without editing, even between two same brand and similar model boards, they need edited due to holing location specific details (offsets of other stuff)
Sorry, I don't know about the Meminit either, only to say that no, you shouldn't touch it at all (sensitive module, work around it ) Maybe Modfreaks batch files make it possible to relocate any sensitive module?
I do notice ht.dll remains in same location in his example, but as I mentioned before, maybe he knows in this BIOS the other ones are sensitive like usual for most Gigabyte BIOS.

I see you increased meminit size, other two untouched in size, but aside from that all three are in same location/count and not moved (order-wise)
MemInitEntrypoint is unchanged, but I do see GV3 (in this case = Agesa) is not in same hex location for each either, due to dummy above GV3 (For no reason??)
Dummy would be placed above to keep sensitive module in same place, yet the modules it's above here is moved so moot point / there is no need for dummy.

In summary, I think you have a odd BIOS that is not affected so much by the general rules that should be followed for Gigabyte BIOS, since that edited BIOS boots for you.
The way that is edited by those tools, it seems that only MemInitEntryPoint and HT.dll is the only two things he coded for sensitivity in that batch file for that particular BIOS.

@Lost_N_BIOS
Yep, for sure I have to buy a flash programmer this is out of discuss
@Lost_N_BIOS @molex
I read on other topics, some time ago, that only HT and HT32GATE can't be moved or modified, maybe this explain why we can modify the meminit module.
Then i compared meminit and agesa module from modfreak mod and i see that he "deleted" some "0" in the structure in order to fit it well, is it possible?
Thanks

In all my experiences, main ones were GV3 and MemInit always had to remain in exact place, meaning if you wanted to mod anything above them you had to replace it with dummy to keep GV3/MemInitEntryPoint in place and then anything new put below those/at bottom
HT/HT32 always directly below those too usually anyway, so already remaining in place always how I do the edits.
I linked an example of one of my recent edits around these issues on post #81 on page 6 of this thread, at that linked post you can see before/after images of everything I compared and you can see what was kept in place
That edit shows example of keeping GV3 in place, with Minit what I edited. I've posted a few others around here, but I don't know where they are so can't link them

@Lost_N_BIOS

Thanks for your all preciuous contents, I really appreciate it!

I found another interesting topic where @lordkag discouss about the memint module (post nr7)
Help extracting AGESA OrochiPI v1.5.0.6 from (Dell Server BIOS M915 Version 3.2.2)

You're welcome. Which thread did you mean, where lordkag talks about Meminit at post #7?

little offtop , how can I extract agesa from AMI bios? Im use mmtool, and cant find it. Already extract all modules, but cant find agesa among them
(im find 770 bard with agesa 3.7.1.1 but bios AMI)

You probably can't put AMI Agesa module into Award BIOS anyway, probably coded different, certainly would be different headers
Link me to AMI BIOS you want Agesa from and I will check and let you know

*Edit - Ahh! See above link by Vash, AMI Agesa explained there too Summary, as mentioned, you wont be taking anything from AMI to Award

this is from msi 770-C45

See my edit above

Thanks Vash, did you follow his link in the Minit lurb, and read those other posts too? If not, check those out as well, it pretty much says what I've been saying all along about all these sensitive modules (and also notes, sometimes some may not be like here, but general they all are).

Hmm, Im open my BIOS_build.bin in hex editor and try to search "AGESA". I have 5 results, two of them are 3.7.1.2 and refer to agesa and meminit module that Im update. But three another has version 3.7.1.0 and I cant understand which modules do they belong to. I am open all extracted modules of bios_build in hex editor and dont find "agesa 3.7.1.0" in any module. Im try to insert new holes and check again.

upd1. Cbrom dont allow simply add hole0 to the bios. Im release hole0 and search agesa in hex editor again, and results contain 3.7.1.0 links, does that means there's agesa 3.7.1.0 links dont bound to hole0 module?

upd2. Stop, agesa 3710 links is in bios_blank.bin, and I am dont know what to do

upd3. eeeeh, okay. Original BIOS have some code with links to default 3710 agesa, this code is located between some modules and this code does not affected by the operations that we did when modifying BIOS with modfreakz-summoner scripts. As result new BIOS with new agesa and meminit have some code blocks with links to old agesa. Maybe this causing issues with memory. I have only one idea: take two bioses from 770 board with agesa 3710, and 785 board with agesa 3712, release all modules from them, and after that modify clean 770 bios in hex editor by replacing code from 785 bios... Sounds crazy .