The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Overclocking my nvidia gt 630m 2gb

    Discussion in 'Gaming (Software and Graphics Cards)' started by justatest, Dec 13, 2014.

  1. justatest

    justatest Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    i am using nvidia inspector to oc my card, and it works, and when i went to return settings to default it returned to normal values. However, when i recently oc'ed it, after i closed my game and returned settings to normal, the core clock and shader clock idled at a higher value then the current (default) set value. The memory clock is what it should be, but not what is used to idle.

    They used to idle at:

    core clock: 135
    memory: 405
    shader: 200 ish, i dont remember exactly

    This is what i get now:
    http://i.imgur.com/oWxQGZs.png

    For some reason when i bring the shader clock to exactly match the current value ( the core clock value is affected directly by the shader value), it jumps up more and if i repeat it jumps up even further. If i default the settings, the values return to those seen in the first picture.
    http://i.imgur.com/iAjSXg0.png


    Any idea how i can get it to idle at the old values it used to idle at??

    thanks in advance
     
  2. King of Interns

    King of Interns Simply a laptop enthusiast

    Reputations:
    1,329
    Messages:
    5,418
    Likes Received:
    1,096
    Trophy Points:
    331
    Of course the shaders are directly connected with the core clock speed. Raise the core speed raises the shader speed and vice versa.

    Hit apply default and clocks will return to normal.
     
  3. justatest

    justatest Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    That is my problem, the settings wont go back to default even after i hit apply default,its what I have been trying to say.

    And as for the shader clock thing please be patient with me, I am a newbie at this.
     
  4. King of Interns

    King of Interns Simply a laptop enthusiast

    Reputations:
    1,329
    Messages:
    5,418
    Likes Received:
    1,096
    Trophy Points:
    331
    Hmm have you checked your clock speeds in GPUz too? Perhaps inspector is giving the wrong clock speed read outs. Worth trying.
     
  5. justatest

    justatest Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    i checked gpuz before and openhardwaremonitor and i got the same reading.


    ok i guess after leaving it for a while it is now idling at:

    core clock: 135
    memory: 405
    shader: 270

    if i click apply default it jumps up to the 'default' value, then lowers itself again to the above values.

    Seems to not lower itself until i have exited the game and left it for a while.

    Ok, i guess thats that, thx for everything!
     
  6. octiceps

    octiceps Nimrod

    Reputations:
    3,147
    Messages:
    9,944
    Likes Received:
    4,194
    Trophy Points:
    431
    Moral of the story: Patience, young grasshopper.
     
  7. justatest

    justatest Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    haha lesson learned