BIOSTAR X370GT7 BIOS mod

@barisuraz & @Lost_N_BIOS you have PM.

Was all OK with the BIOS I sent @ket ? If not, let me know and I’ll redo with latest version UEFITool

@Lost_N_BIOS I think we have got everything here covered for now haven’t we? If not just shoot another PM.

I’m gonna be home in 2hrs. Expect the CBS mod to be done in 3-4hrs max. I’ll be using the BIOS @Lost_N_BIOS sent me with the updated Realtek and GOP/vBIOS drivers.

It’ll be interesting to see how this modded firmware does I’ve had issues Biostar have swore blind they cannot reproduce despite me giving them extremely precise details on how to reproduce it and the fact I can reproduce it 100% of the time. I do also wonder if the no POST issue I’ve reported to them when disabling Gear Down and / or setting Command Rate to 2T will be fixed with an updated CBS module.

I got home currently trying to transplant the CBS but the mobo doesn’t boot with my mod. The file I got from you guys boots perfectly fine. Gonna have to do some troubleshooting.

Edit: Still working on it. The board boots with my CBS mod and your Driver/UI mod but doesn’t boot when they are together lol. I’m gonna try to retrace your steps and try to do the changes you made on my own to see if it’ll work out or not and if it doesn’t, what causes it to break.

@barisuraz Ok. I’ll transplant my changes to your original file to see if they play nice together, if they do good chance the incompatibility is with one of the updated drivers from @LOST_N_BIOS I’d hazard a guess at the GOP drivers.

Well, I tried redoing what you guys did and the current binary I have works fine with my board. It has the Realtek drivers updated, layout modded a bit(might’ve forgotten some settings so I’ll send a PM your way with the BIOS first), CBS transplanted and I also updated the CPU microcode while I was at it. I haven’t touched the GOP drivers though so they might actually be the problem here.

That does indeed sound like the GOP drivers could be the culprit. Once I’ve transplanted the changes back over I’ll pass the new file along to @Lost_N_BIOS to make his changes again with the latest version of UEFITool.

I’ve lost track of where you guys are now, but yes if you need me to redo the EFI and orom Realtek LAN shoot me a file once you’re ready again

Yep some reworks are needed to ensure no bricked boards as the file @barisuraz sent me caused the board to not POST. I suspect that issue was caused by the microcode updates according to @Lost_N_BIOS the latest Biostar firmware has the new CPU microcode updates anyway. Me and Lost are working on it and should have something soon. Also, Biostar can be sneaky I’ve noticed them in the past making improvements to their firmware but uploading it with the same filename and release date so it might be worth occasionally downloading the latest file again to check for obvious changes.

The last file I sent you boots fine on my board though. Are you sure you tried the right file? I believe it was named mod_bios.rom

@barisuraz yep. The file with just the AMD CBS changes works fine, but not mod_bios. No rush at the moment anyway me and Lost need to track down some updated UEFI drivers once thats done I’ll test the changes Lost makes and perhaps by then I’ll have what appears to be some kind of lock on the Biostar setup module and AMD PBS module figured out.

That’s very weird the mod_bios works perfectly with my board. Maybe the CBS modded BIOS that didn’t work for me might boot for you.

Thats another theory I have which is why I’ve started looking at the CBS module already in Biostars firmware. I’m having trouble tracking down how to unlock specific features though there should be a line with “True {46 02}” but there isn’t.

Test theory, (Random example, intended change/edit in bold) -

Suppress If {0A 82}
QuestionId: 0x14F equals value 0x0 {12 06 4F 01 FF 00}

That change in Hex will change QuestionId: 0x14F equals value 0x0 to QuestionId: 0x14F equals value 0xFF in IFR output, but this I believe it effectively changing the original suppress or question ID to where it’s not working/not suppress anymore. But I cannot test this, I only have older AM3 boards.

I wonder if there’s any way to improve memory OC on this board. I’m literally getting cancer from trying to reach 3200Mhz with my Hynix MFR ram.

@barisuraz that problem should at least partially resolve itself if Biostar put the time in to fixing all the current issues I reported to them but yes they do need to do a lot more extensive testing with memory. A big problem is that (during my testing anyway) disabling Gear Down which should enable the 2T command rate outright resulted in the board refusing to POST. The added irony here is that I can get better performance results out of my kit of G.Skill RipjawsV at 2T than I can 1T.

Ohh noooooos, back to 2T with DDR4? We’re going back in time, should be new command rate 0.5 for DDR4

BIOS sent back with updated vBIOS/GOP

@Lost_N_BIOS The difference between 2T and 1T performance-wise isn’t that big, about 3GB/s on write commands and thats about it :wink: besides when I’m switching to 2T my kit of RipjawsV (F4-3200C15D-16GVK, Samsung B-Die) is running at almost 3700MHz with only 1.38v vs. 1.5V or so with 1T