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.

Thread Status:
Not open for further replies.
  1. Mobius 1

    Mobius 1 Notebook Nobel Laureate

    Reputations:
    3,345
    Messages:
    9,069
    Likes Received:
    6,373
    Trophy Points:
    681
    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?
     
  2. Oz!

    Oz! Notebook Enthusiast

    Reputations:
    11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    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 score :) time 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 :D

    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 :)
     
  3. Mobius 1

    Mobius 1 Notebook Nobel Laureate

    Reputations:
    3,345
    Messages:
    9,069
    Likes Received:
    6,373
    Trophy Points:
    681
    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
     
  4. Oz!

    Oz! Notebook Enthusiast

    Reputations:
    11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    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 ;)
     
  5. Oz!

    Oz! Notebook Enthusiast

    Reputations:
    11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    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.
     
  6. Mobius 1

    Mobius 1 Notebook Nobel Laureate

    Reputations:
    3,345
    Messages:
    9,069
    Likes Received:
    6,373
    Trophy Points:
    681
    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
     
  7. Oz!

    Oz! Notebook Enthusiast

    Reputations:
    11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    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
     
  8. Zax19

    Zax19 Notebook Enthusiast

    Reputations:
    0
    Messages:
    28
    Likes Received:
    1
    Trophy Points:
    6
    Huh, mine isn’t 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 won’t 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 won’t 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 it’s either a worse piece than other people have, or there is an issue with the 90W power adapter The latter isn’t 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…
     
  9. Oz!

    Oz! Notebook Enthusiast

    Reputations:
    11
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    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
     
  10. Zax19

    Zax19 Notebook Enthusiast

    Reputations:
    0
    Messages:
    28
    Likes Received:
    1
    Trophy Points:
    6
    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.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page