EVGATech_LeeM
As an update, we can reproduce the issue.  It appears to be a microcode issue at the moment when using the Vcore override mode, and we've reached out to Intel.  We've also confirmed this happens on boards from at least one other vendor.

Any updates on this? How likely is Intel to fix this anytime soon? Or should we just revert back to BIOS 1.17?  

makes me glad i didnt update from 1.17 quickly. Im sure a fix will be in the next update.

jasoncodispoti

EVGATech_LeeM
As an update, we can reproduce the issue.  It appears to be a microcode issue at the moment when using the Vcore override mode, and we've reached out to Intel.  We've also confirmed this happens on boards from at least one other vendor.

Any updates on this? How likely is Intel to fix this anytime soon? Or should we just revert back to BIOS 1.17?  

I'll check with our team tomorrow.
 
Edit:  Seems like we're waiting to hear back from Intel.

Hello,
 
Any updates on this issue?
 
Thanks,

DMIINC
Hello,
 
Any updates on this issue?
 
Thanks,

From what EVGATech_LeeM has indicated thus far it appear to be an issue with the Intel Microcode, which was update with BIOS v1.18. EVGA has reached out to Intel regarding the issue, but is still waiting on them to get back to them. From the testing that I have done thus far it only appears to be impacting AVX-512 work loads which are not very common. My recommendation would be to revert back to BIOS v1.17 if you are using AVX-512 work loads or if you think this may be impacting you in some way. IMO EVGA should pull BIOS v1.18 from there site... since the performance impact could be fairly large depending on your work load and most people will not realize what is happening. 

might be a bit unless its a quick fix from intel it seems.

Hello,
 
Any updates on this issue?
 
Thanks,

bump

@EVGA any updates on this? 

Wondering when EVGA will find a way to let us save our settings after a bios update. It would be pretty simple and a day long work at most.