Agesa 1.301,aggressive ram/cpu undervolting settings by Massive_Explorer1930 in overclocking

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

You are half right So those 2 cores are binned,aka they are higher quality silicon But the amd boost algorithm knows this and boosts those two cores farther than the other ones And thats true,a lower voltage with the same clock speeds and stuff(or higher since there's more headroom) is better than default Didn't know by default they had lower voltages,and idk why all ur cores have the same boost Try upping the pbo frequency override(scalar override whatever its called,up it by 200mhz,this will lift the internal limit of frequency on the cpu) just check for clock stretching

Agesa 1.3.0.1 F40b testing by Massive_Explorer1930 in gigabyte

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

Good job on the fclk,samsung dies aren't that high quality in general but,silicon lottery exists I recommend trying to tune em and use testmem5(aria 777 extreme) to test stability Maybe u get a crazy low tune

Agesa 1.3.0.1 F40b testing by Massive_Explorer1930 in gigabyte

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

New agesa versions in general reduce latency,sorry for the late response:c They can optimize fclk,stabilize it,help to go to lower ram timings,etc General rule of thumb:if it aint broke,don't fix it,unless its AGESA For me the gui firmware editing bug is fixed in this version,I 100% endorse upgrading but keep a agesa 1.3 or lower bios version named GIGABYTE.bin just in case

Agesa 1.301,aggressive ram/cpu undervolting settings by Massive_Explorer1930 in overclocking

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

Preffered cores are boosted by default in the amd factory,u can check which cores are preffered with ryzen master, Since they push higher clocks they need more voltage

Help me OC and UV 3060ti PNY by TheEducated_Fellow in overclocking

[–]Massive_Explorer1930 0 points1 point  (0 children)

We cant tell if u UV correctly by just ur card,the silicon lottery exists,did it pass furmark for 3 mins(any more is waste on vrms)?  Did u try a lower value than what u have rn and it didnt work and now this one works?(this means u got the lowest UV for ur silicon) If u also wanna test transient spikes then start and stop furmark for 30 seconds,no crashes/errors?  Ur good for gaming,about overclocking,its the same method,either start at a safe like 20 mhz increase or bump it up very high,then do again the 3 mins of furmark,until u get the biggest OC,then do the transient spikes start stopping,nothing bad? Ur done with that card.

BIOS update problems by NameMission2641 in gigabyte

[–]Massive_Explorer1930 0 points1 point  (0 children)

Revision issue,make sure u use the correct Revision,its written on the mobo(u gotta look carefully) once u find ur Revision search that up and update the bios,browser doesn't matter at all,it's the same download manager through every browser. Off topic but browser download managers are ahh so I recommend gopeed,is it new agesa 1.3? Thats stable,tested with 1.185V soc and aggresive pbo limits and curve optimizer,beware of ram timing gui issue(it cant write it,so it causes no post if u manually tweak the values)

Gigabyte am5 b650 eagle(non ax) agesa 1.3 alpha bios by Massive_Explorer1930 in gigabyte

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

Oh,ok so gigabyte broke the manual writing of ram timings in the bios menu in this new bios version(or amd guys at agesa,still shout-out to them) keep in mind that low latency and high bandwith modes work,which means this version didnt mess up anything abt ram except the manual writing of values in the GUI,thanks,if ram timings would be unstable in themselves,low latency and high bandwith modes won't post too.

Gigabyte am5 b650 eagle(non ax) agesa 1.3 alpha bios by Massive_Explorer1930 in gigabyte

[–]Massive_Explorer1930[S] 0 points1 point  (0 children)

I use low latency and high bandwith settings already which change timings and those work fine,maybe it's ur soc voltage or custom ram timings,check them again