Which core clock speed is right.

[Harry Livesley]

Im doe with overclocking my gtx 970 hof edition. This is my first time, and msi afterburner lists the clock speed as 1613MHz and the memory as 3913MHz. HOWEVER, when i run unigen valley, it says i have 1740 MHz core, which is right?

[CoolaxGaming]

I may be dumb but 1.6 ghz on a core, isn't that like too high.

[Speedbird]

Im doe with overclocking my gtx 970 hof edition. This is my first time, and msi afterburner lists the clock speed as 1613MHz and the memory as 3913MHz. HOWEVER, when i run unigen valley, it says i have 1740 MHz core, which is right?

It's just GPU Boost 2.0 giving you a higher clock. Nothing to worry about. I would say both are correct.

I may be dumb but 1.6 ghz on a core, isn't that like too high.

It's a 970, they overclock pretty high.

[Sauron]

Im doe with overclocking my gtx 970 hof edition. This is my first time, and msi afterburner lists the clock speed as 1613MHz and the memory as 3913MHz. HOWEVER, when i run unigen valley, it says i have 1740 MHz core, which is right?

 

The 970 has a certain "turbo" speed increase it reach if the temperature and power allow it.

[Senzelian]

Download GPU-Z. 
It'll defnitly tell your the right clock speed.

I guess 1613 is the standard clock speed and 1740 is with the boost activated. You can find those stats in GPU-Z.

[Harry Livesley]

on a side note, valley keeps crashing late in (between scene 13-18) however heaven runs flawlessly, whats up with that?

[Harry Livesley]

Download GPU-Z. 

It'll defnitly tell your the right clock speed.

I guess 1613 is the standard clock speed and 1740 is with the boost activated. You can find those stats in GPU-Z.

i have too many things as it is (about 7 benchmarks, evga precision, msi afterburner, fraps, speccy, etc etc)

[CoolaxGaming]

on a side note, valley keeps crashing late in (between scene 13-18) however heaven runs flawlessly, whats up with that?

That means your oc is not stable bring it down

[Harry Livesley]

That means your oc is not stable bring it down

i dont understand though, on heaven benchmark it is perfectly stable, runs fine with no problems, 

[Doughnutnator]

Your OC is not stable if it's crashing. Valley doesn't show correct GPU clockspeeds, it's messed up, if you want to know the real clockspeeds see Afterburner or GPU-Z.

Test your OC with 3D Mark Firestrike & Skydiver, Unigine Heaven & Valley and the most important: Games

Be sure that your OC is stable in at least that benchmarks, if you want to be more sure download more benchmarks and test.

[Senzelian]

i dont understand though, on heaven benchmark it is perfectly stable, runs fine with no problems, 

Different benchmarks stress different components of your GPU. It's normal that one benchmark runs fine and another one crashes.

Edit.: So yeah, your overclock isn't stable. Clock it a bit down (just 20Mhz can already do the trick) and try again.

[Harry Livesley]

Different benchmarks stress different components of your GPU. It's normal that one benchmark runs fine and another one crashes.

Edit.: So yeah, your overclock isn't stable. Clock it a bit down (just 20Mhz can already do the trick) and try again.

this is what happened before. i reduced my settings and now valley insta crashes on startup.

[APrettyCoolWalrus]

GPU-Z should help

[Harry Livesley]

Your OC is not stable if it's crashing. Valley doesn't show correct GPU clockspeeds, it's messed up, if you want to know the real clockspeeds see Afterburner or GPU-Z.

Test your OC with 3D Mark Firestrike & Skydiver, Unigine Heaven & Valley and the most important: Games

Be sure that your OC is stable in at least that benchmarks, if you want to be more sure download more benchmarks and test.

God damnit, i got to a clock speed that worked fine on valley, andthen i ran firestrike. Lines and flashes and texture fails and everything in between, (this occured near the end of the "demo"), then it did a graphical test, and crashed.

[Clarkey]

Just ignore Unigine valley and heaven in terms of clockspeed. They just get it wrong.

[Doughnutnator]

God damnit, i got to a clock speed that worked fine on valley, andthen i ran firestrike. Lines and flashes and texture fails and everything in between, (this occured near the end of the "demo"), then it did a graphical test, and crashed.

Lower that, anyways at 1500Mhz a 970 is performing like a stock 980.

[Harry Livesley]

Lower that, anyways at 1500Mhz a 970 is performing like a stock 980.

but i want mooooaaaaar

[TheMcSame]

Cards can run higher than their rated boost clock. That being said, I wouldn't trust any unigine benchmark to tell me my GPU core clock, it told me I was running at 1.8GHz at one point.
 

God damnit, i got to a clock speed that worked fine on valley, andthen i ran firestrike. Lines and flashes and texture fails and everything in between, (this occured near the end of the "demo"), then it did a graphical test, and crashed.

Yeah that happens, firestrike seems to be much more intensive than unigine's benchmarks.

[pdv789]

Yeah, according to valley my core speed is along the lines of 1.7Ghz ... I freaking wish. But still, getting 1.6 on any benchmarking program is amazing. I can get close on valley and firestrike but they are extremely unstable. They don't artifact but the frame pacing is really bad. Would you be interested in doing some valley unigine runs and posting your results and scores in the linked thread? I would love to see what you can score on it since it seems yours can overclock so well.

 

 

http://linustechtips.com/main/topic/69448-unigine-valley-benchmark-scores-thread-over-250-submissions/

[Harry Livesley]

Ive somehow fucked everything up. nothing works even after i have reset all of my overclocks.

[Cheddle]

Afterburner is correct. Gpuz is wrong for me.

Once your driver crashes you need to reboot to be stable again.

Ive somehow fucked everything up. nothing works even after i have reset all of my overclocks.

[TheMcSame]

Ive somehow fucked everything up. nothing works even after i have reset all of my overclocks.

Benchmarks seem to do that a lot for me, once I push it too far and the bench crashes that's it, they wont even play nicely with stock clocks. Just wait it out or reboot.