
There is only two points label for the GHz, 1.6 and 2.5 and everything is so small it becomes unintuitive what you are doing. There is no value marked on the mV line after first number of 800?īasic: I first thought cool until I tried to use it. I'm not sure where the limit is, I'll keep pushing it soon, as I just wanted to get in and play some games with my new shiny.I had this same question and found the Frequency to Voltage curves with mV on the horizontal axis and GHz on the vertical. I've still not crashed the card with these clocks since going back to Afterburner. I'm now 100% stable in all benches and games I've tried over the last week and have overclocked the card to 1535/7600 and still climbing. Sure enough it was Precision causing all the issues. Time to uninstall Precision X and back to Afterburner and see where we stand. I think okay, it's worth a shot - it's the exact same symptoms I'm having. After some digging I see people reporting that Precision X is causing display driver crashes and hardlocks especially on 970's/980's. Off to Google we go to see if I can find more info. But no, that doesn't make much sense as it actually ran fine for a few hours at 1505 in multiple different games. I'm thinking fuck, did I get a faulty GPU or what. Nope, still crashing at or even below stock clocks now. So next I tried a few, only like 2-3 available drivers at the time, different driver versions thinking this could be the cause, doing a full clean install of the drivers each time. I was STILL having the exact same crashes, and sometimes it would hardlock the system. I went all the back to stock, which is listed as 1367 but in reality was 1418 for this card. So I dial back 5 at a time on the core clock to find stability. I thought damn, must have pushed it too far. I could "only" get the card to 1505 core at first then the screen, only on one monitor - the one with the benchmark runnin, would grey screen. Then I started started overclocking the card and the real problems started to come out.


At first it seemed okay, even though it'd randomly stop tracking some information such as framerate and frametime - and the OSD would only work sporadically. I picked up an EVGA GTX 980 last week and thought, what the hell - let's give Precision a go.
