2016/11/04 15:53:53
bcavnaugh
I wonder with this Bios update if EVGA Precision OCX needs an update now?
2016/11/04 16:11:01
Sajin
Did you update both your vbioses or just the primary? The secondary shouldn't be affected if you only updated the primary.
2016/11/04 17:10:28
ComXERO
Sajin
Did you update both your vbioses or just the primary? The secondary shouldn't be affected if you only updated the primary.


Both. Hindsight is 20/20 though.
Do you guys have something you can send me along the lines of the update I received that would allow me to do a roll-back? If I could revert and run more tests, I could isolate the issue to the drivers themselves.


2016/11/04 17:13:08
Sajin
ComXERO
Sajin
Did you update both your vbioses or just the primary? The secondary shouldn't be affected if you only updated the primary.


Both. Hindsight is 20/20 though.
Do you guys have something you can send me along the lines of the update I received that would allow me to do a roll-back? If I could revert and run more tests, I could isolate the issue to the drivers themselves.

You'd have to ask evga for the original.
2016/11/04 17:47:15
ComXERO
I'll hit up support tomorrow and see what they can do for me. I will follow up with what I can figure out.
 
2016/11/05 10:13:51
Relentlessly
Hmm, interesting if you are talking about the vlotage limit flag going up (that is posting 1 in Px) then my card ftw 1080 has always done this and I'm still running the original BIOS. 86.04.17.00.80
 
I too lose 1 step clock boost.
 
I know this becuase the store I bought my GTX FTW 1080 from originally, sent me an opened FTW 1080. I complained obv and so they sent me another and let me test both to see which one I liked and I sent other card back. The original card they sent however was 13MHz faster on the boost clock. (I kept the unopened card).
 
Heres my post about it: http://forums.evga.com/GTX-1080-FTW-Volatge-Limit-flag-always-up-m2571401.aspx
 
Be interested with the outcome of this if this is what you mean. However I don't believe it is an error flag. If I adjusted the curveoffset and up the voltage slider I hit 2160 MHz on the cxard no problem. I only did this when I first got the card to see if it would go over 2100MHz.
 
Edit: an official response describing what the volatge limit flags means and what causes it would be useful. Or anyone that knows of course.
2016/11/07 18:01:02
Sajin
Any updates on this?
2016/11/08 10:23:35
ComXERO
I received another BIOS to try out, but unfortunately I am still encountering the same voltage limit and losing clock speed. 

Attached Image(s)

2016/11/08 11:12:33
Relentlessly
ComXERO
I received another BIOS to try out, but unfortunately I am still encountering the same voltage limit and losing clock speed. 




Yup you will, its hardware not software that's causing the flag to raise (I assume). Obv software is reading the register etc. Are you sure it wasn’t up before you had touched the card BIOS?
 
That’s why I'd like to have either an engineer or someone who has spoken to a tech guy who can explain exactly what this flag is for and what raises it. However, as far as I can tell you will only lose 13MHz against other cards etc. that do not raise this flag. I would assume it is a variance within hardware components which cause this flag to go up or not.
 
Could be completely wrong though so a formal explanation would be really nice.
 
As I said before though on my card I can hit a stable +150 core and have tried +400 on mem and everything works fine. The card settles (running heaven) at around 2122MHz down from 2160MHz so arguably with my silicone I could hit 2135MHz without this flag going up. Which of course relates to less than a frame per second.
 
Also, as I think I said the original card I had could not go 1MHz above 2100MHz. 2096-8 or something was fine 2100+ crash not matter what, but had no voltage flag raised. So.. I'm happy really. Just want to know what it is.
 
EDIT: previewing is hard
2016/11/08 11:18:55
ComXERO
Relentlessly
ComXERO
I received another BIOS to try out, but unfortunately I am still encountering the same voltage limit and losing clock speed. 




Yup you will, its hardware not software that's causing the flag to raise (I assume). Obv software is reading the register etc. Are you sure it wasn’t up before you had touched the card BIOS?
 
That’s why I'd like to have either an engineer or someone who has spoken to a tech guy who can explain exactly what this flag is for and what raises it. However, as far as I can tell you will only lose 13MHz against other cards etc. that do not raise this flag. I would assume it is a variance within hardware components which cause this flag to go up or not.
 
Could be completely wrong though so a formal explanation would be really nice.
 
As I said before though on my card I can hit a stable +150 core and have tried +400 on mem and everything works fine. The card settles (running heaven) at around 2122MHz down from 2160MHz so arguably with my silicone I could hit 2135MHz without this flag going up. Which of course relates to less than a frame per second.
 
Also, as I think I said the original card I had could not go 1MHz above 2100MHz. 2096-8 or something was fine 2100+ crash not matter what, but had no voltage flag raised. So.. I'm happy really. Just want to know what it is.
 
EDIT: previewing is hard


I'm gonna go ahead and put the issue to rest. I've gotten decent overclocks and not having stability or temp issues. I think that it's more of a curiosity now to figure out what is causing it. I'm at +180 on my core and +600 on mem and was able to hit a 99fps average with temps staying below 62C at 80% fan speed.

I'll take it.

Use My Existing Forum Account

Use My Social Media Account