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.

    what is maxim OC in NP9262

    Discussion in 'Sager and Clevo' started by shadowtails, Aug 1, 2008.

  1. shadowtails

    shadowtails Notebook Enthusiast

    Reputations:
    0
    Messages:
    44
    Likes Received:
    0
    Trophy Points:
    15
  2. Rorschach

    Rorschach Notebook Virtuoso NBR Reviewer

    Reputations:
    1,131
    Messages:
    3,552
    Likes Received:
    17
    Trophy Points:
    106
    no you cannot.
     
  3. eleron911

    eleron911 HighSpeedFreak

    Reputations:
    3,886
    Messages:
    11,104
    Likes Received:
    7
    Trophy Points:
    456
    Nope.
    You can only OC the CPU if it`s a q660 through a pin mode, which will eventually get your system fried.
    Ocing the GPUs is easy, with riva tuner, ntune or evga ocing utility.
     
  4. Gophn

    Gophn NBR Resident Assistant

    Reputations:
    4,843
    Messages:
    15,707
    Likes Received:
    3
    Trophy Points:
    456
    ^^ correct.

    There are no options in BIOS to OC the CPU, nor is there any software that can OC the CPU.

    The only OC that was successful was the "Q6600 pin-mod" that the above people have said.... which is not officially supported by Clevo or their vendors.
     
  5. baconcow

    baconcow Notebook Consultant

    Reputations:
    22
    Messages:
    225
    Likes Received:
    0
    Trophy Points:
    30
    This answered the question I had back in my thread about overclocking the Q6600 and Q9450. I guess the Q9450 is a better option between the two (and Q6700).
     
  6. sabregen

    sabregen Notebook Consultant

    Reputations:
    53
    Messages:
    135
    Likes Received:
    2
    Trophy Points:
    31
    FWIW, I attempted and successfully completed the pin mod on my q6600, and ran it at 3GHz for some months. THen I started getting BSODs, and it eventually corrupted my RAID-5 partition. It was unrecoverable, as the SATA controller threw a bit error during the rebuild (which is what RAID-6 is for...but not possible on the ICH8R chipset). I have to low-level all 3 of my disks independantly, then re-create my RAID arrays, partition, format, and re-install two OS's.

    This all happened because when you pin-mod the CPU it boosts the CPUs FSB to 1333, up from 1066. Keep in mind that when you do this on a desktop chipset, you can set PCI, PCI-E frequency locks, and also clock your RAM independantly of overthing else. Without that option on the P965 chipset that the D901C is based on, your CPU OC suddenly becomes an everything OC. Your PCI bus, your PCI-E bus (which is what the ICH8R controller resides on), and your RAM all get OC'd too. WIthout a way to lock the frequencies on each of these components independantly, you are kind of asking for issues. Well, the frequency thing, and that you can't boost voltages in order to keep BSODs from happening becuase you are operating our of spec with no extra voltage to accomodate that boost in operating speed.

    I'd say if you have a Q6600, do the mod, run CPU-Z, bench the machine, and then set it back to stock and be happy. Unless you're a tinkerer, this really isn't going to appeal to you, as you have to open the machine, put tape on the pins in question, and hope you don't corrupt your OS while you're running it that way.

    It should be noted that while my RAID-5 array absolutely failed to boot into Vista at the end of it all, my RAID-0 array could have cared less. This is because there's no parity check or calculations on the RAID-0 array. If the RAID-0 ran across a bit error in the array, it would either crash the programs that were open, or BSOD. The RAID-5, on the other hand, would detect the error, and attempt to fix it...then BSOD, then attempt to fix it, then BSOD...you get the idea.