@ket testing at stock speeds got me to a 1000% on HCI and swapping banks on the DIMMS did nothing either.Going to reflash the bios like you suggested and do a clean windows install, just in case i've corrupted the OS files. Checking the gold contacts there spotless except for the latch mark on them from inserting in the channel.

@Lost_N_BIOS The cpu overclock is rock solid I can actually run 4.2ghz at 1.44v but thats to high for daily use. Stability is my goal here so rest assured, everything else is sorted out on this rig. And just in case it had degraded or something I have ran these test at stock cpu speeds.


At this point I've already sunk 2 weeks into overclocking these things, think Im going to fresh install my stuff and just enjoy the 3400 14,15,14,30 i have stable. Wait for gigabyte to get off there ass and give us a new AGESA revision. pinnacle pi 1006 is already out on msi boards, and supposedly gives pretty decent improvements over the last used one.

Unfortunately just because someone else has 3466 ram at cas 14,13,10,11 doesnt mean you will, its all luck of the draw, 1.44v isnt too high thats about right. at stock the cpu can easily spike upto 1.5v

for example my 2700x runs at 4250mhz with the ram at 3520Mhz cas 14 and 53.3ohms, will even run 3600 at cas14

remember CBS pstate0 will automatically drop the vcore down to 0.4 to 0.8v

Zitat von redtopracer im Beitrag #973

---

Well Ive been screwing with them for 2+ weeks now and can only get 3400 14,15,14,30 stable with some atrocious secondary and tertiary timings. And even then I cant get them stabilized past 4000% on ram test. They still throw single errors every couple 1000%. Think im gonna do a hci test overnight on stock like you recommended. Ive been reseting the cmos after each failed mem training and its helped quite a bit. Ive only had to reflash the bios once in the past week doing it that way.


I think either I've got a bad stick, bad bios , or my memory holes stop right after 3400. Either way this has been a grind thats for sure. Ill look into your suggestions ket. The help is much appreciated.


Do you have any experience with cldp0_vddp voltage? Failing the previous suggestions thats the only thing left to try for better frequency. Otherwise I'm stumped on tweaking these sticks lol.

---

@ket I know the function and purpose of the cldp0_vddp voltage and what it does. I was curious if you knew of a better way than just trawling threw the entire spectrum?

At any rate i actually need help. Whenever i try to flash using your dos method I get error 46 problem getting the flash information.

what am i missing here to flash this?

@redtopracer if I recall you'll get that error with stock firmware because by default overwriting the boot block is locked, that issues is addressed with the modded firmware. Have you tried flashing leaving the switch out to flash the boot block? If you still get the error then you might need to update the EFI shell HERE is the link for that. As for good CLDO_VDDP voltage, 725 should work well for B-Die. You could also see what your VDDCR_SOC voltage is and try raising / lowering it. I wouldn't go above 1.15v and you shouldn't need more than 1.1v for the 3466 - 3600 range. You might also be able to drop vcore with an increased VDDCR_SOC.

I am running the moddified f23 from you and i can access the afuefix64 command and everything else but i can not access the bios image from inside the dos boot up. I will try with the updated efi files tonight, however I've had no luck so far I've even tried 1usmus's version of the efi archive and also tried afudos version as well. All the bios I've tried so far have been inaccessible from the dos command line. All bios and even reading the stock bios info to check the romid with afuefix64 gives the same error 46 error unable to access flash info. I'm gonna keep troubleshooting tonight

Obvious as it is, I take it you have placed the firmware images in EFI > BOOT?

Yes and I can see the rom file in the boot directory from dos with the "ls" command.

So I downloaded the newest afudos from the link you gave and tried it. Its saying my bios is write protected even Leaving out the /b command. I'm stumped

This is magical. now both bios are starting to corrupt. Was trying to get the bios to flash from the dos instance and shut it off and switched to bios b. (I run in single bios mode, to reduce the chance of this happening:/ )boot it up and its displaying the bios in 188p or something like it has in the past. I shut it down flip back to bios a and boot and its doing the same thing:/....................wtf and attempts to reflash with qflash fail to bring the resolution back. Fuck think I might have almost bricked my board.


Edit: and now its fine. I desperately need to figure out how to get this flashed through dos.

Flash from DOS using standard Gigabyte EFIFlash utility, add the /x or /z switch if it gives you grief. If that fails use Qflash (Suggested), I don't understand the issue aside from trying to use AFU when there is other easier methods listed before AFU in ket's instructions
Do you need help creating a DOS bootable USB, without RUFUS? If yes, use this method - <Request> Flagship X470 Gaming 7 Wifi Motherboard BIOS Fix
Ignore the EFIFlash if included in above linked download, I can't remember what board it was for but certainly not this one, use the standard one that comes with your BIOS.

The issue I'm having is bios f23 has a tendency to corrupt the bios image. Its generally assumed this is happening because previous bios and settings are not being properly deleted. This is Also effecting my stability and just general ability to use my board as intended. Ket suggested the use of his in depth method to completely clean the chips of old images.

The issue is that my bios is also apparently write protected or something. Because all attempts to flash in DOS have given an error code of unable to access flash info or bios is write protected. So far I have tried kets method, 1usmus's method(ryzn dram calc) and several different versions of afudos. All attempts (even attempts to flash without clearing the chips first) has given these 2 errors. Unable to access flash information, or bios is write protected.


I have also tried using both Rufus and the HP tool as well. Both results are the same.

Fuck it off, put it on ebay fella before its too late, they are shite, if you stick with any x370 gigabyte board you will be spending most of your time trying to fix problems than playing games. Or worse still wondering if it will boot the next time you switch it on. This thread proves it, 66 pages later and they still dont work properly.

Flash from DOS then using EFIFlash with the /X or /Z switch, it will erase the chip before writing, so does Qflash except for LAN MAC ID.
Set BIOS to single mode and keep there for now, once flashed and all setup you can enable double again and reflash backup chip to match main and then disable again to run on single BIOS only, that should help.
I only suggested the HP tool to make a bootable DOS stick, so you could use EFIFlash, AFU I never have luck with either and it has it's own issues aside from these so I always suggest some other method whenever possible.

I'll give it a try tonight and report back. I'm actually planning a switch to itx and sffc with zen2. I just need this board to last till I can get a decent x570 itx board lol.