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.

    G50v CPU Issue

    Discussion in 'Asus' started by Errant33, Oct 22, 2008.

  1. Errant33

    Errant33 Notebook Enthusiast

    Reputations:
    15
    Messages:
    46
    Likes Received:
    0
    Trophy Points:
    15
    I have a 2.53 dual core installed and according to rightmark CPU clock utility on maximum performance i am getting 2527mhz from core one and 2394 from core 2. The temperature difference between cores is also 1-2 degrees Celsius too.

    These results are reflected when using turbo mode as well theirs is about a 100mhz diff between cores.

    Can anyone else Confirm these results or is it just me
     
  2. Qwakrz

    Qwakrz Notebook Consultant

    Reputations:
    182
    Messages:
    206
    Likes Received:
    0
    Trophy Points:
    30
    Its a bug in RMClock

    I have a 2.53GHz T9400 and it is supposed to run on a 9.5x multiplier but RMClock can only see whole multipliers which limits the speed to 2.4GHz
     
  3. Errant33

    Errant33 Notebook Enthusiast

    Reputations:
    15
    Messages:
    46
    Likes Received:
    0
    Trophy Points:
    15
    But even if i put no management then push its speeds up with asus's direct console i still see the same discrepancy between speeds even when pushed up to 2.8ghz OC with direct console RMCLOCK show cpu0 at 2.8ghz and cpu1 at 2.7ghz
     
  4. E.B.E.

    E.B.E. NBR Procrastinator

    Reputations:
    1,572
    Messages:
    8,632
    Likes Received:
    4
    Trophy Points:
    206
    I somehow highly doubt that the hardware is able to run at this frequency differential (although IDA is able to push one core higher and turn the other off, so I can't really be sure).

    So I suspect a faulty RMClock readout, really.

    Try CPU-Z, or Everest. They are somewhat more reliable.