@SoniX
An update, the ones i have tried so far with both HDMI (not DP yet), all have worked, so i will wait for my Asus board to arrive tomorrow Before testing more,
as this problem seems to mostly affect Asus, though possibly some others also.
The MRC theory sounds very likely, to me atleast, would have to be investigated more.
Also have you got any results from others trying this, maybe with other boards.
@Pacman
Unfortunately, no results yet. All seemed scared and waiting for the result of the other. 
I updated the package to test up to 0.3
Added the ability to decompress OROM/GOP/EFI_VBIOS with another or with the current BIOS file.
When unpacking the OROM it there and then you can add the “Custom” menu, when unpacking the GOP just moved to OROM/EFI Replace, EFI_VBIOS when you unpack the renamed VBIOS\EFI_VBIOS.FFS or refine the script.
Good hunting and good luck to all of us. How will the news, immediately I will report. 
That is a shame, it would have been helpful.
The new 0.3 sounds very interesting, i will try it out.
Also, a strange thing about the 878AC2CC module, looked at a Asrock BIOS and found version 2125, but the date is 10/12/2011, i’ve attached it if you want.
878AC2CC_2125.zip (1.67 KB)
@ Pacman and SoniX:
What you are doing is really amazing! 
As soon as you found new Intel VGA ROM modules, which are suitable for a bigger variety of different mainboards, please let me know it. Then I will add them into the start post of >this< thread.
What the users additionally will need is an exact statement, for which mainboard types the related VGA ROM module will be usable, resp. a short guide how to customize it.
They do not raise above OROM VBIOS 2166 even.
@Fernando
Well, till if only for the GigaByte from MSI OROM VBIOS2175?
And GOP-driver 5.0.1029 GUID 5BBA83E6 should work with no problems at all.
@SoniX
I just have to say that the new features in 0.3 are excellent!
I really like being able to see the versions of all the relevant modules at once, that makes checking and extracting very fast.
@Fernando
Yes, hopefully this could be done, of course it is also the problem with lack of testers.
Agree.
If you are searching for a tester with a Z77 system, I will be present.
@SoniX
Here is Intel Haswell GOP Driver 5.0.1032, if you want, from MSI BIOS, i have not tested it myself yet.
@Fernando
Unfortunatley, i’m quite sure it wouldn’t work on Z77, but of course, if you have time for it,
you could Always have Another look at the files and see if you could figure anything else out.
EDIT: Fernando, of course you probably meant testing a Sandy/Ivy VBIOS on your Z77, i was to into the Haswell VBIOSes
The thing about Sandy/Ivy VBIOS files is that even though they are also different depending on MB maker, they seem to work on all boards.
Intel_GOP_501032.zip (25.4 KB)
Hooray. Thank you, thank you …
The most interesting is that the GOP has no problems at all motherboards Z87.
Will update later in the basic package
@Sonix
I just tried 1032, and i only get error in replacing file?
EDIT: Only with my Z87X-OC BIOS, Asus Z87M-Plus seems to work.
If i also replace the IntelSaGopDriver, i can replace the IntelGopDriver.
Flashed it, and it works on my Gigabyte
IntelSaGopDriver.zip (2.71 KB)
Sorry, I didn’t understand the question.
I have now replaced 1032 on Z87X-OC BIOS version F5q, everything is good. If you were asking about it.
What is the difference between an "IntelSaGopDriver" and an "IntelGopDriver" resp. what are they good for?
I don’t quite understand the purpose of this IntelSaGopDriver driver.
@SoniX
I Think i figured it out, somewhat.
When modding the original Z87X-OC 5q BIOS it works,
When i modded also with 2175 MSI VBIOS, then i got this error, but worked when i also replaced the SaGopDriver.
EDIT: No, sorry it was after replacing the Intel RAID OROM and SataDriver with 12.7.0.1936, that was the cause of the error it seems, but like Fernando, i’m not sure what the SaGopDriver is.
But is working now.
@Pacman
Error when you replace is likely to lack of free space.
1
2
3
2
3
Firmware Volume : 02
.........
Bytes Free : 0014CE ( 5 KB) Bytes Used : DEAB32 (14250 KB)
Because of this, I'm in my package, all modules of compress.
ADD: The same problem occurs with ASRock
Ah, yes of course, you are right,
in the Gigabyte BIOS the SaGopDriver is uncompressed, but in MSI it’s compressed, so of course there is more space after replacing the SaGopDriver
GopDriver 5.0.1032 takes a Little more space in the BIOS.
Original:
Bytes Free : 00190E ( 6 KB) Bytes Used : DEA6F2 (14249 KB)
With just the new GopDriver:
Bytes Free : 0014CE ( 5 KB) Bytes Used : DEAB32 (14250 KB)
With new GopDriver AND SaGopDriver:
Bytes Free : 001E3A ( 7 KB) Bytes Used : DEA1C6 (14248 KB)
EDIT:
Original, but with 12.7 RAID OROM AND SataDriver:
Bytes Free : 000631 ( 1 KB) Bytes Used : DEB9CF (14254 KB)
@Pacman
Please, Extract UnCompressed the module IntelSaGopDriver GUID 5C266089 and see the contents. I do not advise you to change it in other motherboards. For example, MSI, this module there is a line "E7811IMS. 117", ASUS has its own and so on.
@SoniX
Yes, i see now, they all have a filename in the SaGop, i did not notice Before, thanks for the info.
i still have not found any information about what it does though.
Going to have to free up space in the BIOS some other way.
EDIT: I solved it by only replacing the IntelGopDriver and the SataDriver, it was Close they wouldn’t fit though.
Bytes Free : 0007F1 ( 1 KB) Bytes Used : DEB80F (14254 KB)