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.

    Problem ocing cpu and gpu on m860

    Discussion in 'Sager and Clevo' started by Ghostalker, Dec 13, 2009.

  1. Ghostalker

    Ghostalker Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Okay so i recently got my lovely clevo m860 and haven been doing some reading, modding (hdd cooling issue) and ocing and everything have going fine until today.

    So i started with a step i was familiar with which was ocing the gpu. Got a stable clock @ 625 1563 950 with a peak temp off 86~ or so in furmark. Could probably up the memory clock a bit more but was diffident feel like so i went on with the next step.

    I never really tried ocing a cpu on a laptop before due to locked bioses but after reading this thread i sad why not give it a shot? Everything went on fine except setfsb rebooted my computer out of no where, but cpu-z and rightmark reported the right clocks so everything was fine. Undervolted the cpu then and everything was still stable with reasonably good temp after a run with intel burn test.

    Now heres the problem. When i oced the cpu, the gpu had it default clocks so the issue havent come up yet. With both the cpu and gpu oc:ed and oddly when i opened hwmontior the gpu driver crashed and restarted. The gpu underclocked it self and went on the lowest default clock and pretty much stayed there until i reboot. Tried a bit more but basically every program that uses the graphic card to some extent crashes the gpu driver. I also noticed some minor artifact on the furmark test before it crashed so i guess i was unstable somehow, temps was fine fyi.

    Now have anyone even experienced this and dose anyone know how the get both the cpu and gpu oced without any crashes preferably with setfsb and ntune?

    Windows 7 - q9200 - 260m 186.47 / 186.62.
     
  2. MrDJ

    MrDJ Notebook Nobel Laureate

    Reputations:
    2,594
    Messages:
    10,832
    Likes Received:
    363
    Trophy Points:
    501
    firstly welcome to nbr Ghostalker

    just hope you havnt fried your card as you wont be covered by warranty.
     
  3. Eivind

    Eivind Notebook Evangelist

    Reputations:
    87
    Messages:
    668
    Likes Received:
    0
    Trophy Points:
    30
    Welcome to the forum :)

    Clockgen and SetFSB raises the FSB which means your whole laptop gets OCed, GPU too. As you may figure out now, the reason your GPU crashes is because its clocked too high, because of the FSB boost.

    Either you have to lower the GPU clocks so the FSB clock doesnt make it crash, or just skip the CPU OC. Most people skips the CPU. I find it a bit unstable, using setFSB even with zero GPU OC.
     
  4. Ghostalker

    Ghostalker Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Thanks guys, actually bean a member here since 2007 but havent really bothered to post. Somewhat off a lurker :rolleyes:

    Actually knew about the setfsb oc:ing my whole laptop, kinda slip through my mind so thanks for reminding me :)

    Checked rivatuner and indeed the core and shader is oc:ed by 8% as well as tge cpu, but the memory is still on its default clock. Dose that mean both the gpu memory and the physical memory in not oced?