@Sonix: There is some verify needed in order to check the Rev 1B of the Ivy Bridge
Guys don’t integrate Rev. 1B for Ivy Bridge because there are some problems…I’ve done it with the latest UBU 1.65 Beta on the F12J of the Gigabyte Z77X-UP5 TH and it has bricked my main BIOS.
The MoBo made and endless mini-boot and suddenly shut down until i stopped it manually.
Thankfully Gigabyte has a solid routine that detect the corruption of the main BIOS and overwrite it with the backup-BIOS and now everything is fine.
I insert it (manually) to my ASRock Z68Ext3 and no problems.
Manually (using AMITool) integrated ucode from UBU 1.65 - looks ok.
Edit: I see why it bricked: Checksum in module not correct.
Attached module with correct checksum. Should work ok.
Look up file name in ubu, rename attached file to it and let ubu insert it.
https://www.sendspace.com/file/7gx48k
These checksums MMTool forms and never had problems.
@SoniX
It is possible that the new Asmedia OROM is for 1062 or 1062R. I see here that they should have 4 controllers, but here it seems that they share the same ID, even though it should be 1B21:0611 for 1061, 1B21:0612 for 1062. From a quick look for asm1062, it would seem that there are a few boards with 1062/1062R controller: Crosshair V Formula, Z77 Pro4, Z87 Extreme6, Z97-A with 1062R, Asus Hyper Express with 1062R. If you can get a user with any of these boards to test this new OROM/firmware, maybe we would know for sure. In fact, any user with Asmedia controller should visually check his board: if he sees a Asmedia ASM1062/ASM1062R, he can test it.
@mictlan
Your changes don’t make any sense. You first changed the EFI_FFS_FILE_ATTRIBUTES, but in a wrong way. Usually 0x08 is for dummy microcodes and 0x48 for full microcodes (but they can also be found reversed). Then you calculate a bad module checksum - it should be 00 for entire module, yours is 03.
Sonix has done everything right. If there is a problem, it is either in the microcode itself or in the process of replacing. If one user reports a fail, while other(s) report a success, I would say it is the later case.
@lordkag
Ok. Made a request to the specified motherboard is, I hope that someone will respond. Honestly, this version is already intriguing 3.xx. 
Add
@lordkag
Chip: asmedia/ASM1061/BG644101A2/1143
OROM v3.070 not working.
Waiting for someone on board ASM1062(-R).
Thanks you all but in my previous post i’ve missed an info about the module i’ve tried to insert that is the "CPU Micro Code 28 for Sandy Bridge and 1B for Ivy Bridge" (i have some Sandy Bridge to test and i prefer the Rev. 28) and i hope this info can help you guys to track the potential problem. 
Did anybody try the microcode update function in UBU on an Asus Maximus VI Formula bios?
I successfully updated Intel RST and all LAN modules, but left the microcode untouched (06C3, on latest original bios 1505 it is still rev. 19).
@ killkernel:
Welcome at Win-RAID Forum and thanks for your contributions!
Regards
Fernando
@lordkag
I rewrote Update Marvell EFI modules, but I still available for testing:
Asus GUID 43… - only AHCI module
GB GUID A2… - only RAID module
EVGA GUID 49…1 and 49…2 - modules AHCI and RAID.
I do not found module RAID in BIOS Asus and similar module AHCI in BIOS GB.
Also do not know if these modules in BIOS MSI and AsRock.
Currently available are 2 versions:
AHCI - 1.1.0.1006
RAID - 1.1.0.1007
Edit:
Release UBU v1.7.0
Yeah I did it on my Z87-Pro, have not noticed anything "wrong" as of yet. The only oddity was that I usually use the mmtool to update it, this did not work there (size doesn’t match either).
add: also, sometime in the past and currently, the LAN EFI driver stops me being able to change anything in the BIOS itself (ie: WOL). Ethernet etc works just fine, all the BIOS options are greyed out however. Current version: 5.4.19.
add2: am I meant to see Asmedia option in UBU? I’ve got ASM1061 controller but it’s not showing up as an option to update or what version it has now…
Thanks a lot, it worked! 
This is the module with the latest CPU micro-code for Sandy Bridge (Rev. 29) and the 1B for Ivy Bridge, could you check and correct the one with the Sandy Bridge micro-code Rev. 28 and the 1B for Ivy Bridge?
Thanks in advance for your patience and the time you’ll deserve to me.
EDIT by Fernando: Unneeded quoted text deleted (to save space)
Here you go: https://www.sendspace.com/file/6rz6b3
Please post back if it works!
EDIT by Fernando: Unneeded quoted text deleted (to save space)
Many thanks, tomorrow morning i’ll be at home, i will do the integration and i’ll post if it works.
Thanks again and have a nice evening.
KK
ASUS Maximus V Extreme - Asmedia Previously OROM 0.954
new 3.70 not added!
1.67 beta replace to 3.70/ now try flash BIOS.
In the BIOS motherboard is Asus MVE OROM Asmedia not inherent. Check VID and DID you used when you insert version 0.954. Must be 1b21 - 611/612/613
I use M5E Bios modified with 0.951
find here http://www.overclock.net/t/1244232/asus-…0#post_21466815
- than add 0.954 by UBU (and all work)
with 0.954 on postBIOS screen I can see OROM message and in BIOS can choose attached to asmedia as boot.
with 3.70 no message and no as boot device
P.S. after replace by UBU Intel SATA UEFI to 13.1.0.2126 - it disappear in UEFI BIOS
Means the controller is not compatible with version 3.70. By the way, that the chip Asmedia written?
from Device Manager info is enough? or you want that print on chip?
Yes.
Yesss…it works! 
Definetely they must be corrected.
Thanks a lot for your patience and your time. 
Have a nice evening.
Cheers,
KK