Zero939

TheAffxct
So what you guys are saying is this BIOS sucks?

If you want to test your max memory OC, it's good. For daily driving? no.

babayega

Zero939

TheAffxct
So what you guys are saying is this BIOS sucks?

If you want to test your max memory OC, it's good. For daily driving? no.

not really... if u disable ecores, ring gets fixed.

Zero939

babayega

Zero939

TheAffxct
So what you guys are saying is this BIOS sucks?

If you want to test your max memory OC, it's good. For daily driving? no.

not really... if u disable ecores, ring gets fixed.

It makes 0 sense for me to have to disable E cores with 13700

vertex72
Hello, 
There is some bug about cpu oc on 12900KS (and maybe other ADL cpu).
 
First : The thermal velocity boost must be disable or the cpu will clock down during workload, also downclock with cstate off
Second : Ring ration can't be set, while i set 44 on bios i still have 36 under OS, with Eleet X1 it show 36, and changing the value on it doesn't change the ring at all.
 
For mem OC it's fine, in can do 8000c32 / 8200c34 or 8400c34 easly with 12900ks and A die, daily oc kharu Ycruncher stable at 7600c36 1.4v on hynix green stick.

98AMcFadden
My 7600 cl 36 kit seems to run great with this bios. Only issue i'm having is the Ring ration wont set for some reason. I set my ring to x53 in bios, but its being reported at x45 when in Windows. 

Thewebsiteisdown
If you reset your bios from the back panel for thirty seconds with power still on for the psu and start over completely and don't touch adaptive voltage and only use set manually for vcore and then only set your cpu multiplier to " manual - ratio limit " instead of per core everything works correctly. I had to set my vcore manual voltage to 1.32v at a vdroop of +75 to get my ecores to flip over to the 47 limit I set for them.
 
I had to reset my BIOS though to get everything to go back to normal otherwise it was bugged out and nothing worked. It would seem that adaptive voltage and the vf table are not working correctly for me. Unless there's a trick to get it to work correctly which I tried almost everything but could have missed something you never know.
 
I have my pcores set to 58 and the ecores set to 47 and the ring to 50. I noticed that the ring flexes now to 50 instead of staying at 50. mines goes from 4600MHz up to 5000MHz.

Mr. Fox
Weird. The exact opposite is true for me. My generic green M-die sticks maxed out at 6800 before 2.04 and now they can run 7800. Do you have A-die?
For what it's worth, if you are trying to use the same memory settings that worked in 2.03 you're probably going to have to start over on the memory tuning. My manual 6800 memory overclock settings were totally unbootable with 2.04. 
 
I just checked and you are correct. For some goofy reason they removed 2.03 from the EVGA Download Center. They need to put it back. 
Yes, flashing back to 2.03 works normally. I've done it twice already trying to make this messy BIOS work for me.
 
Here is a link to download it from my OneDrive folder. https://1drv.ms/u/s!AtvVypqAtWDahYksVp3Ag8fDGcck3Q 

Kadao
To be honest I just assembled the PC on Friday, so I have no baseline or anything to compare with.
But with 2.03 I can change bios settings with no problem. With 2.04 I can do the OC robot and it works, but if I go and change settings that affect memory, even only voltages, I get stuck in the 53, 54, 7F loop. I need to reset the bios to be able to use it again. Same thing happens with just 1 stick. Sometimes when I go to bios, I get a message that the memory was changed from nowhere.
However this seems limited to my new 7200 A-die sticks, because if I swap the memory to a teamgroup t-force 6400 kit the pc just straight up boots with no problems, no need to reset the bios. Even if it was stuck on the 53, 54, 7F loop with the A-dies, if I power off and swap the memory kit, tt just retrains and it's up and running. I'm typing this on the t-force sticks @ 6800.
With 2.04 I can't use the A-dies.

EdgyBloke
Ok I’ve been talking to EVGA and let’s clear a few things up. There are issues, but some reports on here are nonsense.

No this BIOS won’t damage your board, but it does seem to treat Vcore differently than 1.03. Now another issue is that ring is absolutely locked to 4.5GHz. After extensive testing these are the only 2 oddities I can confirm. If your downclocking it means your thermal throttling, because tbh most overclocks people show me are wildly unstable or have way too high of voltage realistically.

EVGA is already investigating the ring lock and it’s likely 2.05 will be available soon. I’ll talk to them again and see if they are able to push it out early this coming week, but idk a for sure timeline.

EdgyBloke
I also want to add that in terms of Vcore being handled differently for example I used to need 1.28V for 5.6GHz. Now I can do it at 1.25V. Basically it seems to be supplying more voltage than it used to at least for me. This is probably why people are reporting higher temps. Id like to see people try and set negative offsets if they aren’t overclocking and report their results.