Christian Ney Posted May 12, 2012 Posted May 12, 2012 I have tested the ASUS GTX 670 DirectCU II Top GPU-Z is reading clock right but under GPU Tweak, GPU-Z monitoring (sensor), MSI Afterburner monitoring, the GPU Clock is up to 1300 MHz according to all those monitoring softwares. I would like to know if you guys had the same, if it's normal ? GPU Boost is really confusing me. Quote
BenchZowner Posted May 12, 2012 Posted May 12, 2012 Each card boosts to a different max clock. It depends on your luck ( core quality, conditions, temp, utilization, settings used, etc etc ). Have PrecisionX or Afterburner show the GPU Power %, GPU Clock, GPU Utilization in game at a 500ms refresh rate. That'll show you how it behaves. If it hits 1306MHz even for a few seconds on its own without you changing any overclock settings, chances are you've got a 1400+ card there. Quote
Christian Ney Posted May 12, 2012 Author Posted May 12, 2012 even if I lock it with GPU tweak this bitch goes up to 1300 MHz Quote
Crew Leeghoofd Posted May 12, 2012 Crew Posted May 12, 2012 You are never happy C, you get a specially handpicked GTX670 and you still want more Quote
Christian Ney Posted May 12, 2012 Author Posted May 12, 2012 In fact I want real clocks not BS clocks Quote
Christian Ney Posted May 12, 2012 Author Posted May 12, 2012 Got it now, worth an article, hope it will be out on monday Quote
BenchZowner Posted May 13, 2012 Posted May 13, 2012 You can also try with P2 performance state to keep turbo off and lock the card at a specific frequency in case your max turbo boost frequency fluctuates ( forgot to tell ya sorry ) Quote
Dualist Posted May 13, 2012 Posted May 13, 2012 Got it now, worth an article, hope it will be out on monday Looking forward to it. Quote
OBR Posted May 15, 2012 Posted May 15, 2012 I have tested the ASUS GTX 670 DirectCU II Top GPU-Z is reading clock right but under GPU Tweak, GPU-Z monitoring (sensor), MSI Afterburner monitoring, the GPU Clock is up to 1300 MHz according to all those monitoring softwares. I would like to know if you guys had the same, if it's normal ? GPU Boost is really confusing me. GPUz reading clock wrong ... its normal at GTX 670 Real clock is in Precision/Afterburner/GPU tweak monitor screen, not main screen! Quote
Christian Ney Posted May 15, 2012 Author Posted May 15, 2012 Yeah that's what I found, only when monitoring you read right clocks Quote
Christian Ney Posted May 16, 2012 Author Posted May 16, 2012 Article: GTX 670 & 680 Clock per Clock and GPU Boost Analysis Quote
OBR Posted May 17, 2012 Posted May 17, 2012 (edited) how you can set base clock the same as boost clock?, by bios editor? or power target tuning? Edited May 17, 2012 by OBR Quote
hokiealumnus Posted May 17, 2012 Posted May 17, 2012 I have one of these now and it, too, gets ~1,300 boost throughout testing. Impressive card right out of the box. Still trying to get used to the whole weird overclocking settings, but I'll get the hang of it before I publish a review. Quote
Christian Ney Posted May 17, 2012 Author Posted May 17, 2012 how you can set base clock the same as boost clock?, by bios editor? or power target tuning? cmd => disable pstate 10, use only pstate2 Quote
OBR Posted May 18, 2012 Posted May 18, 2012 cmd => disable pstate 10, use only pstate2 ok, open cmd, write "disable pstate 10?" or which is exact string? Quote
Christian Ney Posted May 18, 2012 Author Posted May 18, 2012 (edited) latest nvidia inspector > cmd prompt > nvidiainspector.exe -setPStateLimit:0,2 EDIT: It was nvidiainspector.exe -forcepstate:0,2 Edited May 21, 2012 by Christian Ney Quote
OBR Posted May 18, 2012 Posted May 18, 2012 ive tryed it yesterday thru nvinspector by setpstate. but its not working for me. clock is still 700 mhz and ocing not work. maybe old ver of inspector? Quote
Christian Ney Posted May 18, 2012 Author Posted May 18, 2012 (edited) nope, used 1.9.6.5 Edited May 18, 2012 by Christian Ney Quote
OBR Posted May 18, 2012 Posted May 18, 2012 (edited) i have latest inspector, but -setPStateLimit:0,2 is 705 MHz ... and cannot to change clock by afterburner or other tool edit: -forcepstate:0,2 is working, i can set base clock in nvinspector too ... thanks, great thing Edited May 18, 2012 by OBR Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.