Intel® VGA ROM 2179
http://www.mediafire.com/?3xoc3hs8oc350do
Build Number: 2179 PC 14.34 10/07/2013
This is important: The VBIOS 2179 which motherboard?
Add after testing.
The latest F8g beta for GA-Z87X-UD3H contains it.
https://www.dropbox.com/s/msyinduydtv6v5c/Z87XUD3H.8g.zip
Will need to be reconfigured, the Asus does not work. 
@ ALL
Hello.
There is a solution to the processor microcode updates LGA2011.
Please, tell me, what are the CPUID is relevant at this point?
Thanks.
Edit:
The issue is cleared.
Topical CPUID
SandyBridge-E 6D6 - 416 and 6D7 -710
IvyBridge-E 6E4 - 416 and 6E6 - 600
These the microcodes will be added in the next version of UBU.
@Sonix, @Fernando
I have used PR16 to prepare a BIOS updated from BIOS 2104 for ASUS P8Z77-V DELUXE mboard.
I get no problem with the tool but I have a question about CPU microcode update. (At the moment I have not yet flashed this new BIOS).
I use a IvyBridge i7 3777K CPU.
Question:
IF i update this CPU microcode and IF there is a problem after flashing the new BIOS , can we come back to previous stable BIOS version without CPU microcode modification (i.e. flashing back the official ASUS 2104) ?
@ 100PIER
Yes. Just flash the official BIOS through the EZ-Flash or BUpdater.
Thanks very much for the tool, only seen it now. It appears to update everything though I haven’t had to actually do the BIOS update.
Question; with the Microcode replacement and I see it was discussed earlier - extract both 01:00 and 04:02, then replace 04:02 with 01:00. This will give you access to change the micro-code. Once complete, you put the original 04:02 back. This way you can retain the BIOS structure as-is. Is this possible to implement, I can see the delete command and the tool appears to allow both extract and replacement commands via command-line?
Now, I don’t know if that works on other platforms but it works on my Z87-Pro.
Thanks for having developed and published the first final release of your awesome UEFI BIOS Modding tool!
Meanwhile I have started to customize the start post. As soon as possible I will replace the pictures as well.
Regards
Fernando
Hey SoniX, I think you have a little typo in the VerDID.txt:
Should be:
@SoniX :
In the new Z77 Betas from MSI is the Asmedia area converted!
can you make an update for the tool?
link to new beta
Download E7757IMS.182.zip
@ SoniX:
Once again I want to thank you on behalf of all Forum members for your work you have done with the development of the UBU Tool, which now reached the status “Final Release”. You deserve our absolute admiration - congratulations!
As already announced, I have completely refreshed the start post of this thread and attached completely new pictures taken with the final UBU v1.1.0 .
I hope, that my updated guide is easy to understand and doesn’t contain any mistakes.
If you should have any remarks or advices, please let me know it.
Kind regards
Fernando
@ Fernando
Thank you. 
I think you need to add a "Note" to update OROM VBIOS Haswell, not GOP Haswell.
"Because the modules OROM VBIOS Haswell are personalized, on some motherboards may not display video at some of video ports (D-SUB. DVI. HDMI or DP), as well as sound."
@ SimpleTech
Thanks, will fix.
@ error-id10t
mmtool /?
If you know the solution as, for different motherboards using MMTool from command line replace all modules without disturbing the structure of the BIOS, then I will be very happy to see your specific suggestions.
@ Fischer
Zitat
In the new Z77 Betas from MSI is the Asmedia area converted!can you make an update for the tool?
Adding new modules and deleting existing, will not be supported.
In BIOS E7757IMS. 182, module OROM ASMedia 106x does not exist. Its functions are performed by the module EFI GUID A05F5C06-1782-48AA-962A-86A0892022B6
If you want to use the old OROM, add it yourself. To do this, look here.
I don’t have the skills to write a program but if you run these commands via the cmd prompt, you gain access to the CPU Patch / micro-code tab.
extract to name 0100:
mmtool Z87P.CAP /e B52282EE-9B66-44B9-B1CF-7E5040F787C1 0100
extract to name 0402:
mmtool Z87P.CAP /e 17088572-377F-44EF-8F4E-B09FFF46A070 0402
replace 04:02 with 01:00:
mmtool Z87P.CAP /r 17088572-377F-44EF-8F4E-B09FFF46A070 0100 0402
Then once you’ve done the micro-code update, you run the below to put the original 0402 back allowing you to retain the format:
mmtool Z87P.CAP /r 17088572-377F-44EF-8F4E-B09FFF46A070 0402 0402
If it were so easy.
This is understandable if we know the numbers Volumes and Indexes. But we do not know and on various motherboards, the numbers Volumes and Indexes in the BIOS, may be different. Do not limit yourself only to Asus. Download the different BIOS manufacturer MSI, ASRock, gigabyte, etc and see the numbering of the Volumes and Indexes.
In addition, there is no processing "Errolevel" in MMTool, that will lead to permanent errors on the screen.
Fernando, SoniX , blogthis, Others
This is a fairly long post so please bear with me. Some sections may not be applicable to this thread but maybe of interest to others.
My System: Asus P9X79 Deluxe MoBo, Win8Pro 64b, 2x OCZ Vector 256 SSD’s as Raid 0, Intel RSTe Orom V 3.5.0.1005, Intel RSTe drvs V 3.8.0.1106 (From 3.8.0.1111 package), Raid drive partitioned x 4 (System on one), other specs aren’t relative here.
My Objective: To have TRIM function correctly on Raid 0 using SSD’s on an X79 board. I, like everybody else, have been waiting a long time for this. I am aware of Nodens RST Mods.
As noted by blogthis further back in this thread (and elsewhere) Intel now claim TRIM does function correctly on Raid 0 using SSD’s running RSTe. Support added from Ver 3.7.0.1093 RSTe http://downloadmirror.intel.com/23257/en…111_readme.txt
Have done WEI and Optimize for relative drives.
Observations1: Using TrimCheck on the system drive (Raid0) results usually are ‘INDETERMINATE’ after waiting a minimum of 20 secs. After running say 5 times result is then ‘NOT WORKING’. Rarely, I do get a ‘WORKING’ on a first run, which to me means TRIM is present and trying BUT not working correctly. After a reboot same results.
Using TrimCheck on the other non system drives (Raid0) results are always ‘NOT WORKING’
Observations2: Using Fernando’s HxEd method and that more or less verifies TrimCheck results above.
Note. Test file is also always deleted from Recycle Bin. Used a .Jpg file and others
Results for HxEd for System drive data is usually overwritten in the applicable area (Offset/Sector) meaning ‘INDETERMINATE’ but very occasionally I get 00 or FF meaning ‘WORKING’.
Results for HxEd for Other drives data is never overwritten in the applicable area (Offset/Sector) meaning ‘NOT WORKING’.
Fernando the ‘test data block’, which I know to be unique, can always be found elsewhere (Different Offset/Sector) and sometimes in a few places. Could this be a ‘clipboard or recent file’ windows thing? I don’t know but it’s there.
My conclusion and I’m no whiz kid is OCZ garbage collection and Trim maybe in some sort of ‘conflict’ or whatever AND/ OR there still is a problem with TRIM in this setup even though ‘blogthis’ had positive results with the latest RSTe drivers and with the 3.5.0.1005 Orom.
Next (Sorry)
As I wish to stay with the RSTe setup up AND hoping TRIM would work correctly if I updated the Orom to a closer version to the current RSTe drivers I modified my current/latest Asus bios ver 4502 (has 3.5.0.1005 Orom ) using the method outlined in Fernando/SoniX ‘UEFI BIOS Updater’ thread. I only modified the RSTe Orom and EFI SataDriver to ver 3.8.0.1029/12.7.0.1936
Checked this with Aptio MMTool/HxEd and all is well 3.8.0.1029 confirmed . (ven8086/dev2826)
Problem: Cannot install Mod BIOS 4502 using Asus USB Flashback. Correct naming used (P9X79D.CAP).
Flashback flashes for about 1 or 2 seconds then stops. Update fails.
I also tried ‘Bupdater’ v1.24 but it would not recognize installed bios or Mod 4502 bios on USB stick. Maybe I used the wrong version.
Guys any help/suggestions/observations very much appreciated.
Once again sorry for the long post and thanks for all your work.
MaxTrax
@ MaxTrax
P9X79 Deluxe in BIOS 4502 there are OROM IRST 12.7.0.1936 (Device ID 2822). Flashing original BIOS and turn on the IRST 12.7 and install the drivers 12.8. I think everything will work fine.
Yeah, I see what you’re saying and I also had made an error on my original post above, the last part:
mmtool Z87P.CAP /r 17088572-377F-44EF-8F4E-B09FFF46A070 0402 0402
The above doesn’t have the intended consequences because there is no 17088572- GUID anymore. It was replaced with B52282EE- (d’oh). The tool doesn’t show errors but now you have 2 GUID entries of B52282EE- still which is not what we wanted. Because mmtool replaces modules per 1st hit, it won’t touch the 2nd one which in our case here is what we want replaced! The work-around (painful) is to replace now both B52282EE- GUIDs with 17088572- GUID. Then you run the replace command once more using B52282EE-. lol
Now you have the original ASUS BIOS back in it’s original state. Painful to say the least via cmd prompt with no scripts.
I then used the Z87-XPOWER BIOS from station drivers using this method. Because the order of 17088572- GUID and B52282EE- GUID is reversed, you basically do the above in reverse.
However, the Asrock Z87M Pro4 BIOS is a PITA because they have 2 entries for 17088572-377F-44EF-8F4E-B09FFF46A070. Replacing just one (either) won’t allow access to the CPU Patch tab. So again you have to do the above but now twice, then rinse and repeat with replacing it back to the original state.
Like I said originally, I’m no programmer/script writer but if that can somehow magically be done then there is a “work-around”. The Index / Volume doesn’t matter, as long as the GUID exists, that’s what we’re extracting and replacing - however and as noted, the order does matter. All that said, the current method in the script works (simply deleting it).
@ error-id10t
By the way! You gave me a good idea! 
Will have to check out this idea.
Create a empty module with GUID 00000000-0000-…
Then all modules with GUID 17088572-… replace the module with GUID 00000000-…
And then return back to the modules with GUID 17088572-… instead of modules with GUID 00000000-…
Of course taking the control and verification.
Probably will have to make 2 module with the GUID 00000000-… for complete modules and with the GUID 00000001-… for one blank module.
Thus we will preserve the integrity of the structure of the BIOS and all modules.
PS Of course will increase the time module updates, but all modules will be as in the original BIOS. 
@ MaxTrax
P9X79 Deluxe in BIOS 4502 there are OROM IRST 12.7.0.1936 (Device ID 2822). Flashing original BIOS and turn on the IRST 12.7 and install the drivers 12.8. I think everything will work fine.
Thanks for the reply SoniX but I wanted to stay with RSTe. One reason is according to Asus (Says so In BIOS 4502) you have to reinstall the Operating System if you switch to IRST from RSTe and I have other reasons.
Is switching to IRST the only answer because as I explained TRIM is supposed to now work in RSTe .
Thanks