Should I stop overclocking?

[Mr.Hdd]

 

That is my max core clock but should i overclock memory clock until the gpu crashes or what

[Jurrunio]

Until it starts to crash, then you back down. However you should do the memory then do the core, since more memory speed to lead to running slightly lower core clocks (less memory bottleneck = core does more work at the same clocks = more prone to crashing)

[bellabichon]

Have you properly stress-tested that config? You might be able to get a higher memory overclock. 

[Mr.Hdd]

Just now, bellabichon said:

Have you properly stress-tested that config? You might be able to get a higher memory overclock. 

Im using the furbench or whatever it is but  if i go above that core clock the app crashes so im overclocking the memory now untill it crashes. What should I do. Do I stop overclocking the memory or what. Im new to overclocking

[RONOTHAN##]

With my experiences overclocking cards with GDDR5 like your 1060, +310 is a middle of the road OC. You won't be able to get a ton more out of it, but I would try to push it a little harder, but if you can't get any higher easily, don't bother.

[Mr.Hdd]

Just now, RONOTHAN## said:

With my experiences overclocking cards with GDDR5 like your 1060, +310 is a middle of the road OC. You won't be able to get a ton more out of it, but I would try to push it a little harder, but if you can't get any higher easily, don't bother.

So I should push mem untill it crashes then little the clock a little

[RONOTHAN##]

Just now, Mr.Hdd said:

So I should push mem untill it crashes then little the clock a little

I would just push the memory. That core clock looks about right for one of those card. You can always try pushing it, but I wouldn't expect much if anything to come from it.

[Mr.Hdd]

Just now, RONOTHAN## said:

I would just push the memory. That core clock looks about right for one of those card. You can always try pushing it, but I wouldn't expect much if anything to come from it.

Like I said thats all the core can do. If I push more it crashes. Do I push mem first then core or what

[Mr.Hdd]

So push the memory until it crashes then try core again

[RONOTHAN##]

1 minute ago, Mr.Hdd said:

Like I said thats all the core can do. If I push more it crashes. Do I push mem first then core or what

I usually push core then I push memory. It would be a difference of 2 FPS most of the time. Unless you are going to restart your overclock, don't push the core after you do memory, as you won't be able to get any higher numbers.

[Mr.Hdd]

Just now, RONOTHAN## said:

I usually push core then I push memory. It would be a difference of 2 FPS most of the time. Unless you are going to restart your overclock, don't push the core after you do memory, as you won't be able to get any higher numbers.

Alright after pushing memory the core let me add another 15. 

[Mr.Hdd]

[VeganJoy]

28 minutes ago, Jurrunio said:

Until it starts to crash, then you back down. However you should do the memory then do the core, since more memory speed to lead to running slightly lower core clocks (less memory bottleneck = core does more work at the same clocks = more prone to crashing)

i thought it was recommended to go for core clocks first, then memory?

 

26 minutes ago, Mr.Hdd said:

Im using the furbench or whatever it is but  if i go above that core clock the app crashes so im overclocking the memory now untill it crashes. What should I do. Do I stop overclocking the memory or what. Im new to overclocking

furmark is a little optimistic compared to an actual gaming load, i paid 4 bucks for 3dmark on steam and their stress testing feature is well worth the spare change. gives you a percentage of instability in your overclock that you can either accept or dial back (<97% is a fail, i'm fine with 99% or better). i use furmark to get a very, very vague idea of the card's capabilities. even with the x8 MSAA option, my max overclocks in furmark always crash in 3dmark or games. usually have to tone core back by 30-50mhz and memory by 100-150 lol.

 

as an aside, memory overclocking on the last few generations of cards is a little tricky cause they have a basic element of error correction. your memory overclock can be unstable without any artifacting, the only way to tell is by the performance as when you overclock too far it'll waste resources error correcting artifacts. so keep track of what setting actually yields the best score, i use 3dmark time spy for that (the benchmark is free iirc) to help as it tracks clockspeeds. i also use gpu-z to see what kind of memory i have on a card; on most of my pascal cards with micron gddr5 (all of my 1070s), i get +350 to +450mhz with one outlier card that could do +600mhz. with samsung gddr5 (the couple of 1070ti's i've tested), i get +650 to +800mhz.