Check the thread on T|I
If you need to borrow my account to download, contact me.
Unfortunately not all GT 650M can reach 1000Mhz+
Sorry![]()
But can you overclock? If you apply the OC .bat profile does it stay at that value under 3d stress?
-
-
Hey guys,
Been trying to overclock my 650m ddr3 2gb, but having issues.
Firstly, im on latest driver 310.70 whql, and latest inspector 1.9.6.8. Default clocks are 835/900
Bascially, i only have P0 and P8 to choose from in in the drop down in inspector. I can't force any other pstate, tried P1 all the way to P7 lol. P0 and P8 work.
Tried on P8 but memory doesn't budge and i get less score on 3dmark if i try to overclock core, probably because of lower voltage. Though there isn't any throttling according to gpuz.
Next, i can't overclock the core on p0, i set it, but it always stays at default clock speed, 835mhz. Memory works though i can go to about +200 stable. 250 gets a couple of artifacts when running heaven.
I tried using other programs, afterburner, precision... same thing core won't budge above stock, but memory oc's ok. Boost doesn't seem to kick in either, never see it go above 835 during any 3d.
EDIT: OK i got it to work!!
Using -forcepstate:0,1 like others have said (doesn't show any change in pstate in inspector) made it work. I used this line: EDIT: Ok well after a restart i have to use pstate 0, but keeping the 0,1 behind setgpuclock and setmemoryclock, like so:
nvidiaInspector.exe -setBaseClockOffset:0,0,65 -setMemoryClockOffset:0,0,200 -setGpuClock:0,1,900 -setMemoryClock:0,1,1100 -forcepstate:0,0
GPUz shows clocks are set, 900/1100, voltage is 1.05v dropping down when under load to 1.025
Stock clocks get me about P7600 gpu score in vantage, 900/1100 got me 8512 gpu scoretime to crank it up further!
http://www.3dmark.com/3dmv/4471244 P10327! 1000/1100
EDIT: crazy clocker!! http://www.3dmark.com/3dmv/4471367 1225/1100, 10k gpu score, 11k overall
1250 crashed to desktop 30secs into heaven benchmark. Tried 1300 just to make sure and it crashed to desktop instantly upon starting. Settled at 1225mhz. Found my max clock, now to give other 3dmarks a run, along with some other benchmarks -
Are you sure it's stable at 1225MHz?
Don't test just by 3dmark, use furmark and prime95 over 6 hours (100% cpu/gpu load) to confirm the stability.
+rep for finding a new command line -
I'm pretty sure it wouldn't last furmark, only reason being that temps during these benchmarks go up to about 80-85c, so anything longer and im sure it would crash the overclock due to high heat. For example, when i was testing 1250, all was fine, as soon as it hit 85c it crashed to desktop.
Even at stock clocks, during heavy long gaming (farcry3) temps climbed slowly and reached 90c. I'm not planning on using this overclock for 24/7 anyway, probably something a lot less and reasonable like 1000/1000.
Thinking of getting a laptop cooling pad, stick it near an open window (it's winter here), and im sure i could be benching something more like 1250/1125
Anyway, 3dmark 06 NVIDIA GeForce GT 650M video card benchmark result - Intel Core i7-3630QM Processor,Compal Type2 - Board Product Name1 score: 16330 3DMarks says something about default settings not being used, think its the resolution. It's set default as 1280x768, can't change it
3dmark11 NVIDIA GeForce GT 650M video card benchmark result - Intel Core i7-3630QM Processor,Compal Type2 - Board Product Name1 score: P2994 3DMarks seen people getting 3k+guess it's because i have the gddr3 version... Accidentally ran the full 3dmark experience, so it ran the demo's too. Surprised it ran through all of that
Metro2033, 1366x768, dx9 medium settings, , aaa, af x4: 57.5fps. Stock clocks got me 45fps, huge difference.
Metro2033, 1366x768, dx11, very high settings, tessellation enabled, dof off, aaa, af x4: 30.5fps
Heaven benchmark, 1366x768, high shaders, tessellation normal, aa off, af x4: 38.7fps. Stock clocks got me 29fps.
Right, well just played farcry3 for half an hour or so at 1225/1100, temps reached 97c :S yeah... definitely not 24/7 clock.
Was seriously smoother though, i was able to bump up the settings a bit. Plays perfectly smooth at a mixture of high and very high settings (no ultra), dx11.
Very deeply considering that laptop cooling pad -
Well, after a lot of tweaking, i've hit my sweet spot
I started playing around in the P8 state, we know that performance is a bit lower compared to the normal P0 state at the same clocks.
default clocks 835/900, p0 1.025v, 41 fps in heaven no tessellation.
default clocks 835/900, p8 0.887v, 39 fps in heaven no tessellation.
But the temp difference was huge, 83c max recorded for the p0 state, and a mighty low 67c for the p8 state.
Then i tried overclocking, because frankly, any sort of overclock on the p0 state isn't reasonable, just gets too hot.
I found the max core clock it would do using 0.887v, it was around 1000mhz. 1100 crashes in heaven right away, 1050 after 30secs. 1000 will run anything i throw at it. I might settle at 970mhz as that is the max base clock offset at +135.
I had trouble overclocking the memory at first, it wouldn't go above the default 900mhz in the p8 state. Anything below would set, 850, 899... but 1mhz above 900 wouldn't set. I then changed the memory clock offset, and this was the trick. I used the following line:
nvidiaInspector.exe -setBaseClockOffset:0,0,135 -setMemoryClockOffset:0,0,200 -setGpuClock:0,0,970 -setMemoryClock:0,0,1100 -forcepstate:0,8
This allowed me 970/1100 with 0.887v.
Got me 46.5 in the heaven benchmark. So, default clocks 41.1fps and 80c+, or p8 state 970/1100 46.5fps and about a 10c drop in temps...hmmmmm
So even though i get ~2% less performance using the p8 state, i can overclock it well beyond stock performance and with a massive drop in temperature
Would just like to add, to make it easier for other people.
-setGpuClock: 0,0,970 some people might know already, but the number in bold, the first one represents which gpu it's applying to, 0 for the 1st gpu and 1 for the 2nd gpu (if u have one) and so on.
-setGpuClock:0, 0,970 the second number in bold, represents the performance level the clock is applying to, 0 would be performance level 0 (pstate 8), 1 would be level 1 (pstate 0, for me), for others it might be pstate 2 or 5, if so then performance level 2 would be pstate 0.
and of course the last number being the target core clock.
So for me, if i want say, 1200 core clock on pstate 0, i would put -setGpuClock:0,1,1200
But as i'm undervolting it in pstate8, i put -setGpuClock:0,0,970.
It's the same for setting the memory clock.
Offsets are a little different, i think the 2nd number represents which pstate itself it's applying to rather than the performance level, like u would apply to -forcepstate. I've found no use setting it anything other than 0. So for me i put -setBaseClockOffset:0,0,135
For example the line for my high benchmarking clocks is:
nvidiaInspector.exe -setBaseClockOffset:0,0,390 -setMemoryClockOffset:0,0,200 -setGpuClock:0,1,1225 -setMemoryClock:0,1,1100 -forcepstate:0,0
and for my pstate8 overclock:
nvidiaInspector.exe -setBaseClockOffset:0,0,135 -setMemoryClockOffset:0,0,200 -setGpuClock:0,0,970 -setMemoryClock:0,0,1100 -forcepstate:0,8
Hope this helps. -
Ah, P8 undervolts, but it throttles the GPU (that's why you get lower heaven FPS)
Try this tool to max out your fan
RWEverything | Read & Write Everything
Click on embedded controller Tab
Column 00 row 90, change value to "01"
needs to hibernate or a shutdown to reset the fan to auto speed -
I tried changing the value to 01 but seemed to not do anything.
It may be throttling or something, but i still can get higher performance with lower temps than stock.
I ran some tests, heaven default, tessellation off:
default, 835/900 P0: 41.1fps ~80-85c
1035/1100 P0: 50.0fps ~85c
1035/1100 P8: 48.2fps ~70-75c
Some 3dmark11
835/900 P0, gpu score 2060
1035/1100 P0, gpu score 2527
1035/1100 P8, gpu score 2392
Metro dx9 high
835/900 p0: 36.5fps
1035/1100 p0: 42.2fps
1035/1100 p8: 40.3fps -
Huh, mine isnt stable at as low as 1050MHz on the core and the voltage scales dynamically up to 1,037V. The P5 state was ok in 3Dmark at 1000MHz but it wont accept the clock if I put the memory anywhere above the default 2000. Combining it with the memory offset has no effect. The P8 state wont clock if I push the memory above 800 and it crashed immediately when I set it to 745/800. In the end the traditional method is probably the best option for me, using just the P0 state to add 135MHz to the core and 500MHz to the memory. It ends up at 970/2500 which should be even more stable than 1000/2000 and I already tried running at 950/2500 to imitate the GTX660M without any problems.
The way I see it its either a worse piece than other people have, or there is an issue with the 90W power adapter The latter isnt very likely because the i7 configuration drains 90W in heavy load and my i5 shows less than 20W in HW monitor under heavy load (compared to the 35TDP). Later on I might do some more testing to find out the stable value between 1000 and 1050MHz but compared to frequencies other people squeeze out it seems fairly pointless. Oh well -
Just for testings sake, try thiss. pstate 5 overclock
nvidiaInspector.exe -setBaseClockOffset:0,0,135 -setMemoryClockOffset:0,0,500 -setGpuClock:0,1,970 -setMemoryClock:0,1,2500 -forcepstate:0,5
is that right for the memory settings?
edit: zax, are not able to take the core above 970 in pstate 0 then?
try this maybe
nvidiaInspector.exe -setBaseClockOffset:0,0,165 -setMemoryClockOffset:0,0,500 -setGpuClock:0,2,1000 -setMemoryClock:0,2,2500 -forcepstate:0,0 -
I can get it above 970 in P5 but not the memory, in P0 I it’s vice versa. I could try the second line you suggested but the gist of it is that the core itself isn’t stable at 1050MHz which is relatively low compared to other overclocks. 970/2500MHz is convenient because I don’t have to force any pstate and the graphics card is cooler in idle. On top of that I just found out that a couple of days after I order mine Dell the shop offered the same model but already with 8GBs of ram (I had to buy 4 separately), 250GB larger HDD and an i7 CPU for extra approximately 100USD. The i7 configuration comes with a 130W power adapter which might be the better for overclocking the GPU. Nevertheless there still is the issue of higher temperatures with an i7 so I’m not sure.
PS: And there also is the Lenovo Y500 with GT650M in SLI and an i5 (with the option of installing an m-sata SSD) for the price of the Dell with i7 and one GT650M (approximately 1200USD). So I’m just a bit bummed. Happy Christmas everyone! xD. -
1050 wasn't stable, but wasn't that in p5? does it not use a lower voltage than p0 state. give the line a try, why not
-
-setBaseClockOffset:0,0,165 is an invalid line but lowering it to 135 with the rest the same worked at 1000/2500MHz. The line is:
-setBaseClockOffset:0,0,135 -setMemoryClockOffset:0,0,500 -setGpuClock:0,2,1000 -setMemoryClock:0,2,2500 -forcepstate:0,0
Still, I kind of like clocking it to 970/2500MHz via P0 without having to force the pstate because it clocks down automatically if it’s not needed. As for voltage, I tried 3DMark at 1100/2500MHz in P0 state and it locked up at 80% loading of the first test, the same happened with 1100/2000MHz in P5 state. I’d be interested to know if anyone with my Dell and an i5 has the same problem, if it’s better with the i7 configuration (130W adapter) or if mine is just a “lame horse” xD.
I didn’t plan on overclocking, personally I’d do it only with a beast like the Asus G55WV because it has way more cooling power than it needs. I tried playing Planetside 2 for a couple of hours and with 950/2500MHz I get a maximum of 74°C on the CPU and 72°C on the GPU which is 2°C and 5°C more than on the default clocks. For some people that’s low but I wouldn’t mind if it never went to 70°C because that’s around the temperature at which the fan goes from “don’t mind me” to “sup son”. -
There is a bios mod with unlocked OC abilities and advanced level BIOS menu
Might want to check that out -
Doublepost. sorry
-
wow i didnt know u can do that.
-
My settings are the following: 1090/2500.
nvidiaInspector.exe -setBaseClockOffset:0,0,345 -setMemoryClockOffset:0,0,500 -setpowertarget:0,111 -setVoltageOffset:0,0,0 -setGpuClock:0,2,1090 -setMemoryClock:0,2,2500 -forcepstate:0,0
I think it is stable, i played far cry3 more than 6hours. GPU temp: 57-60, core temp: 60-65 with turbo off. On the other hand Im using a coolermaster u2 cooler, which is the best for m14xr2 (in my opinion). I also tried to clock the core to 1150mhz, but it's not stable. After 1hours my m14 turned off suddenly. It's really interesting,because my computer used its battery, and almost full charged. After it turned off, i tried to turn on but i couldnt. The gpu temp was not too high. It was only possible when i plugged the power cable. The 3Dmarks 11 scores: 1150, and what im using:1090
NVIDIA GeForce GT 650M video card benchmark result - Intel Core i7-3630QM Processor,Alienware M14xR2 score: P3093 3DMarks
NVIDIA GeForce GT 650M video card benchmark result - Intel Core i7-3630QM Processor,Alienware M14xR2 score: P3032 3DMarks -
-
Thanks Mobius, I haven't known this before. That is the reason, that turn off...
I think 1150 will be stable)
-
Mine is stuck on 135/450
Could any1 post a .bat file I could use?
Lenovo Ideapad y500
650M DDR5 2GB -
-
Hello, guys and gals.
I am a proud owner of MacBook Pro 2012 (Intel i7 2.6 GHz, nVIDIA GeForce GT 650M 1 GB, 8 GB DDR3 1600 MHz, 15-inch 1680 x 1050 monitor, 750 GB HDD). I never had issues with performance of my laptop, however I decided to experiment with it and tried to overclock the VGA (Windows 7 Boot Camp). There are several good guides on how to overclock nVIDIA GeForce GT 650M but for some strange reason they did not work for me as they were supposed to...
First of all tools that I used:
MSI Afterburner
nVIDIA Inspector
FurMark
Articles that i tried to follow:
http://forum.notebookreview.com/gam...guide-workaround-max-clocks-oc-stability.html
http://forum.notebookreview.com/app...p-overclocking-results-gaming-benchmarks.html
My results:
MSI Afterburner
I have edited the MSIAfterburner.cfg file:
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 1
After the modification to the .cfg file the core clock is still locked and limited by 750 MHz
The memory is easily overclockable up to 2600 MHz (stable) and probably more
nVIDIA Inspector:
There are 3 levels of Performance:
Level [0] - (P8)
Level [1] - (P5)
Level [2] - (P1)
Level [2] - (P1) is completely locked and inaccessible
Level [1] - (P5) and Level [0] - (P8) - are not locked, however the memory clock speed bounces back every time I tried to move it. The core clock speed does not bounce back but for some reason it does not apply changes. As the result - core clock peed 750 MHz, memory clock speed without overclock...
I have also tried using the cmd command
nvidiaInspector.exe -forcepstate:0,1
but it did not work for me...
Please tell me what am I doing wrong...
Thanks in advance,
CHRONOSome -
nvidiaInspector.exe -forcepstate:0,0?
-
CHRONOsome, i think u mean P0 and not P1.
try this line:
nvidiaInspector.exe -setBaseClockOffset:0,0,50 -setMemoryClockOffset:0,0,600 -setGpuClock:0,2,800 -setMemoryClock:0,2,2600 -forcepstate:0,0
Just to confirm, your default clocks are 750 core and 2000 memory yeah? then this should work, should...
I'd like some help, i've found my perfect clock, 1035/1100 on P8. Temps rarely go above 70c. Highest i've ever seen it even after long gaming was 72c. However, i get 2-5% performance loss using P8, i get similar performance using 970/1100 on P0. But i also get 10-15c higher temps, i was getting around 85c after couple hours of farcry 3. Well worth the temperature drop imo.
Now my main question, i've been fiddling about with my cpu clocks using throttlestop. Using the turbo clock, 3.2ghz 1.1v on all four cores, temps are insane, only considerable on benchmarks, even then i cringe seeing the temp easily hit 90c. So i've succumbed to disabling turbo for 2.4ghz with 0.95v, temps are at a much more reasonable ~75c after long gaming.
But i've also figured out to be able to get inbetween clocks. I've found 2.7ghz at 1.0v a contender. Temps aren't so bad, but they do get up to about 85c max during long gaming, would u think this is ok for 24/7? I noticed no real fps improvement although the general gameplay is a tad overall smoother. -
You should try this: my-m14x-r2-experimental-cooling-mod-success.html -
Hmm, as much as i would like to, i only just got this laptop really, had it for few weeks.
Don't get me wrong i've built pc's in the past, but i've never popped open a laptop before. Maybe down the line if i get bored... or need the performance lol. -
-
Update:
I have tried the following line:
nvidiaInspector.exe -setBaseClockOffset:0,0,50 -setMemoryClockOffset:0,0,600 -setGpuClock:0,2,800 -setMemoryClock:0,2,2600 -forcepstate:0,0
The result is 797 MHz core, 2600 MHz memory.
How to get 1060 MHz core clock speed?
Can someone tell/show the link/article on how the clock offset works? -
does this also apply to watercooled cards?
-
I think if you use a desktop card, there is a community thread in OCN that makes their own modded vBIOS which enables user to tweak the vcore or has a higher vcore than normal
You can use this method in a desktop card, but it's not recommended to do so. -
I think if you use a desktop card, there is a community thread in OCN that makes their own modded vBIOS which enables user to tweak the vcore or has a higher vcore than normal
You can use this method in a desktop card, but it's not recommended to do so. -
Basically, -setGPUClock:0,0,0 and -setMemoryClock:0,0,0 are the main one's you want to be messing with.
0,0,0 the first 0 represents which gpu is applying to, since u only have one, u put 0, indicating the first card. The second 0 represents which performance level it's applying to, u have 0,1,2 (pstates 8,5,1), and the 3rd 0 represents the clock speed u want.
So if u wanted to put 1060mhz on pstate 1, u would put -setGPUClock:0,2,1060
The base clock offset, personally i've found no real use for this, it changes how gpuz will display the clock speed on the normal page, but -setGPUClock will always override in my experience. But what i have found strangely, it affects voltage. For example at my default frequencies 835/900, if i put -setBaseClockOffset:0,0,0 i get a normal voltage of 1.05v. If i set it to the maximum i can, -setBaseClockOffset:0,0,135, the voltage will actually go down... to 0.987v, and if i set it lower -setBaseClockOffset:0,0,-135, the voltage will go up, but not beyond the highest 1.05v. It also scales with frequency, so at 950 core clock with 135 base clock offset, i would get 1.037v, but setting the offset back to 0 the voltage would go up to 1.05v. Kinda useless imo i just leave it at 135 offset and just use -setGPUClock to set the actual frequency.
So for 1060/2600:
nvidiaInspector.exe -setBaseClockOffset:0,0,135 -setMemoryClockOffset:0,0,600 -setGpuClock:0,2,1060 -setMemoryClock:0,2,2600 -forcepstate:0,0
What i would also do after applying this, is to see what -forcepstate:0,1 will do and if it still works, considering that u don't actually have a pstate0.
EDIT: actually since u don't have pstate0, then the offsets will be different, considering that the second 0 in the 0,0,0 doesn't represent the performance level like -setGPUClock, but it represents the actual pstate value. So maybe for u have to put -setBaseClockOffset:0,1,135 for it to apply to pstate1.
Try this instead:
nvidiaInspector.exe -setBaseClockOffset:0,1,135 -setMemoryClockOffset:0,1,600 -setGpuClock:0,2,1060 -setMemoryClock:0,2,2600 -forcepstate:0,1
------------------------------------------------------
EDIT: Zax19, for testing purposes could u try this line and see if it's any better clocking above 1000mhz?
nvidiaInspector.exe -setBaseClockOffset:0,0,-135 -setMemoryClockOffset:0,0,500 -setGpuClock:0,2,1100 -setMemoryClock:0,2,2500 -forcepstate:0,0 -
Oz I also have the 650m gddr3 version, Is 1100mhz the best memory clock we can get? If i go above it i get artifacts in game, Im using this command.
nvidiaInspector.exe -setGpuClock:0,1,1000 -setMemoryClock:0,1,1100 -forcepstate:0,0 -
Well everybody's card is differennt, but yeah i get the same clock. 1150 artifacts nearly instantly and 1125 after a little while. 1100 i've never seen artifact in all the long hours of gaming i've done on it.
Wish i had the ddr5 versionlol feels like sometimes i'm bandwidth starved.
-
Thank you again for explaining everything.
I tried the following line:
Code:nvidiaInspector.exe -setBaseClockOffset:0,1,135 -setMemoryClockOffset:0,1,600 -setGpuClock:0,2,1060 -setMemoryClock:0,2,2600 -forcepstate:0,1
Code:nvidiaInspector.exe -setGpuClock:0,2,1060 -setMemoryClock:0,2,2600 -forcepstate:0,1
Now about issues.
The VGA is throttling... For instance if I have 1040 MHz core clock speed it is jumping down to 675 MHz. I have also tried using ThrottleStop and disabled the BD PROCHOT protocol, however it is still throttling...
Please find the log GPU-Z log file.
I don't know, may be it is normal for the mobile VGA, but in real life tests (games) the throttling is not noticeable. -
Excellent. Yeah the offsets aren't really needed. As i said i only found the baseclockoffset to affect voltage in a way, but is useless at higher clocks as its going to max out the voltage regardless.
The memory offset i need to use in the P8 state, as it's tied to the P0 clock. for -setmemoryclock:0,0,1100 on the p8 state i need to set the offset for the p0 state as well otherwise it won't set.
Strange about the clock dropping down. What game was it which made that happen?
oh and throttlestop is only for the cpu. -
-
here is my bios for dell 680m
hope it helps the modders and unlockers!
really looking forward for a mod, those eurocom cards are my envy!
http://dl.dropbox.com/u/32467782/680m.rom -
-
Hey! I'm really new to overclocking (started yesterday, lol).. and firstly, I'd like to thank Oz! for the usefull tips and commands.
Anyway I too have a GT650M 2Gb DDR3, and I'm using 970/1100, using the command Oz! posted a few comments back. The problem is I'm getting really high temps when gaming... like above 80ºc and near 90º sometimes... I'm guessing thats because I live in a really hot town... it's 32ºc now, and this is not a hot day...
My question is... will this high temps during gaming will fry my card in a short time? Is there any recommend temp for this cards? -
Tried repasting+using cooler pad? -
But after playing AC III for a while the max temp it got was 79ºc... so I guess I'm ok then
Will keep monitoring the temps after longer gaming sessions tho. -
Hello, I'm confused a little bit by the behavior of my card. It's a GT 650m 1GB GDDR5.
Now, I was on 306.97 WHQL and clocked my card at 1150 core, 2800 memory and it performed perfectly fine. However,when I updated to 310.70 WHQL I suddenly can't play at that clock anymore; my games crash. Should I go back? Or, is there something I'm doing wrong? -
Give it a try:
nvidiaInspector.exe -setMemoryClockOffset:0,0,200 -setGpuClock:0,0,1035 -setMemoryClock:0,0,1100 -forcepstate:0,8
oh and mobius, chronosome was one who said about using throttlestop for gpu -
Meaker@Sager Company Representative
Am I missing some new 680M development?
NVIDIA GeForce GTX 680M video card benchmark result - Intel(R) Core(TM) i7-3940XM CPU @ 3.00GHz,Micro-Star International Co., Ltd. MS-16F3 score: P8562 3DMarks
I score that at 1110mhz core clocks and 2525mhz memory clocks along with a 4.3ghz CPU and 1Ghz mem and I have seen people with lower clocks score in the 9000 region..... I am confused.
Maybe it's just optimus at this high level. -
Probably just user error....
-
Meaker@Sager Company Representative
Haha
Maybe, but if so I would like to find what is not set right
NVIDIA GeForce GTX 680M video card benchmark result - Intel(R) Core(TM) i7-3940XM CPU @ 3.00GHz,Micro-Star International Co., Ltd. MS-16F3 score: P8612 3DMarks
At 1110/2525.... -
Result -
I'm gona try the command you gave me now... im confident it will work just as good
Thanks again dude!
[EDIT]
I spoke too soon lol
At 1035, my card crashes instantly when i try to run a stress teste
At 1000 it crashes after 2-3 mins in the stress test...
I think i'll stay in the safe 970 gpu clock... im getting the perfomance i need from it and so far i havent got one single crash...
Note: All tests were in the p8 state -
-
P6914 with 888/1935 on the latest Dell bios and drivers on my Alienware M17x with no voltage changes. Max temp was 66C on 3dmark11
Good/bad/mediocre? How much further can I push it without voltage change?
EDIT: I think there was something wrong with the combined test, since Fraps was showing 26 FPS while 3dmark was showing just 10-19, and it definitely looked quite smooth
nVIDIA mobile Kepler 6xx MASTER overclocking guide. Workaround for max clocks/OC stability.
Discussion in 'Gaming (Software and Graphics Cards)' started by Mobius 1, Jul 14, 2012.