![[-]](https://www.bios-mods.com/forum/images/black/collapse.png "[-]")
01-11-2019, 02:40 PM
(This post was last modified: 01-11-2019, 02:47 PM by Lost_N_BIOS.)
I don't know about imgur images, remember, and I thought that was about BIOS flashing not vBIOS editing anyway?
I meant there was two Intel onboard vBIOS too, but I mentioned there being three before I checked things out, and saw you had edited the correct one. There's actually four, two Intel EFI Roms, and an Intel orom, and then NVidia orom. You did edit the correct vBIOS, the other ones I was referring to are for Intel onboard usage.
On the base clock, that's up to you, not sure what your intended changes were is why I mentioned you only edited boost clock. Setting higher boost clock only increased max allowed, not sure if that would show up in whatever you are checking with post-flash (GPU-z?)
I also mentioned due to what you said about not seeing changes reflected. All that may be due to the BIOS was rebuilt incorrectly, so the vBIOS may not have been updated during the reflash due to incorrect checksums (Skipped over during update possibly) Only way for you to know for sure is to reflash the BIOS I posted above, then if you see changed reflected you initially expected to see then you'll know that's what happened.
Nothing noob there, we all have to learn sometime, and BIOS is very tricky, especially editing vBIOS too.
I do not, would not, use PhoenixTool for this, or really wouldn't use MMTool either, but that's just me
Obviously one of those, probably PhoenixTool is not rebuilding the BIOS correctly, but it's hard to say which for sure since I did not check BIOS after each edit throughout your process. The file I attached above has only one edit, with UEFITool, I edited stock BIOS, and reinserted your edited vBIOS body, checksums are corrected on rebuild/save. vBIOS checksum itself was correct in your edited vBIOS, but in the header the contents data checksum was incorrect due to your changes, and then whatever tool rebuilt after reinsertion did not correct that, and it also messed up the microcode file on rebuild (unaligned)
I meant there was two Intel onboard vBIOS too, but I mentioned there being three before I checked things out, and saw you had edited the correct one. There's actually four, two Intel EFI Roms, and an Intel orom, and then NVidia orom. You did edit the correct vBIOS, the other ones I was referring to are for Intel onboard usage.
On the base clock, that's up to you, not sure what your intended changes were is why I mentioned you only edited boost clock. Setting higher boost clock only increased max allowed, not sure if that would show up in whatever you are checking with post-flash (GPU-z?)
I also mentioned due to what you said about not seeing changes reflected. All that may be due to the BIOS was rebuilt incorrectly, so the vBIOS may not have been updated during the reflash due to incorrect checksums (Skipped over during update possibly) Only way for you to know for sure is to reflash the BIOS I posted above, then if you see changed reflected you initially expected to see then you'll know that's what happened.
Nothing noob there, we all have to learn sometime, and BIOS is very tricky, especially editing vBIOS too.
I do not, would not, use PhoenixTool for this, or really wouldn't use MMTool either, but that's just me
Obviously one of those, probably PhoenixTool is not rebuilding the BIOS correctly, but it's hard to say which for sure since I did not check BIOS after each edit throughout your process. The file I attached above has only one edit, with UEFITool, I edited stock BIOS, and reinserted your edited vBIOS body, checksums are corrected on rebuild/save. vBIOS checksum itself was correct in your edited vBIOS, but in the header the contents data checksum was incorrect due to your changes, and then whatever tool rebuilt after reinsertion did not correct that, and it also messed up the microcode file on rebuild (unaligned)
![[Valid RSS]](valid-rss.png "Validate my RSS feed")