Open the file with HxD. Then you will find the offset 0x07 hex code pair within the first line (= offset 0) at the column "07".
By the way: You can easily find out yourself the offset 0x07 by comparing the hex code of the Intel LAN ROMs v1.5.43 for DEV_1502 and for DEV_1503. Although both files contain different DeviceID hex code entries ("02 15" resp. "03 15"), they have the exactly same checksum-8 "00". The simple reason: The checksum has been customzed at offset 0x07.
Everything clear now?
Thanks a lot mate.
Open the file with HxD. Then you will find the offset 0x07 hex code pair within the first line (= offset 0) at the column "07".
By the way: You can easily find out yourself the offset 0x07 by comparing the hex code of the Intel LAN ROMs v1.5.43 for DEV_1502 and for DEV_1503. Although both files contain different DeviceID hex code entries ("02 15" resp. "03 15"), they have the exactly same checksum-8 "00". The simple reason: The checksum has been customzed at offset 0x07.
Everything clear now?
Yes all clear now.
Does anyone have the actual bsf files for Intel Haswell vBIOS v2177-2180?
Pacman and/or SoniX may have them. To be sure, that they read your question, you should send them a PM.
I only have a 2170 and 2173. 
Thanks for the info.
Yes. I know that (Station-Drivers.com is our partner site), but the recovering of the database with all previously linked ROM modules will take a while.
So if you or someone else should find actual USB 3.0 ROM modules, which are delivered from the various USB Controller manufacturers, please let me know it.
Seems that they’ve gotten back on their feet now with new stuff showing up on a regular basis.
Wish there was an English language option on the site though.
Nope, sorry, was just to define the range…
Well, maybe will be. 
It’s a pity that there is no BSF-file for 2179. From 2170/2173 is not very suitable.
Hey Fernando, your IntelIvbGopDriver says (I used Unicode to get it readable and … replaces the empty areas between each value/word):
I extracted the one in my MSI Z77A-GD65 bios (stock 10.11) and it says:
Which one is actually the newest?
(I’ve got the 3570K installed).
Here’s a link to my IvbGop: https://mega.co.nz/#!TdInzBbA!3PrcazutOb…vEhpDdoNQ4F1a2g
@ Scyphe:
AFAIK the Intel IvyBridge GopDriver v3.0.1023 ist the newest.
Changing the ID and replace the orom is already enough, is there no kind of checksum to correct or something?
I have the 8168 id in mmtool and PCI\VEN_10EC&DEV_8168&SUBSYS_76991462&REV_06
in device manager.
AFAIK the MMTool will correct the checksum automaticly while doing the PCI OROM replacement. A manual checksum correction (by using a hex editor) is only needed for other (not PCI OROM) BIOS modules.
@ SoniX:
I just extracted it from the newest ASUS Z97 Sabertooth MK1 BIOS 0901, which has been offered by Raja@ASUS within the start post of >this< thread.
You can find the download link to the extracted Intel VGA-ROM v2180 for DEV_0406 within the start post of this thread.
I am sorry, but I didn’t realize, that you had already added the missing Intel VGA-ROM v2180.
By the way: Your v2180 module is slightly different from the module, which is within the newest ASUS BIOSes (different dates and some other differences).
Yes, this is the original modules that need to be set by the editor BMP.
Each motherboard OROM VBIOS has its own settings.
Thanks for the clarification.
Does that mean, that I have to remove the links to the DeviceID related "universally" usable Intel VGA-ROM modules, which I am offering within the start post of this thread?
Those who in the first post of this topic should be removed, as they will only run on motherboards where taken.
Thanks, SoniX, I will do that.
Additional question: What about the Intel GopDriver modules, which I am offering >here<? Shall I remove them as well?