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.

    ASUS GPU incorrect frequencies... ??? (i really dont know)

    Discussion in 'Asus' started by maximumcoder, Jul 29, 2008.

  1. maximumcoder

    maximumcoder Notebook Enthusiast

    Reputations:
    0
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    Hi..
    I just installed rivatuner to monitor my tempratures and possibly do some OC.
    I noticed a wierd thing.

    I have an ASUS G1Sn-X1 with nv9500GS DDR2 w 512mb

    My default clocks are supposed to be

    169/338/100 (Standard 2D)
    275/550/200 (Low Power 3D)
    475/950/400 (performance 3D)

    But in the rivatuner hardware monitor. My frequencies are seen as

    182.25/364.5/100 (Standard 2D)
    297/594/199.8 (Lowpower 3D)
    513/1026/399 (performance 3D)

    I have failed to understand the skewed freqency reports in rivatuner.

    I have seen the same effect in 177.31/175.80/174.31 drivers.

    Attached is a screenshot of the same.

    This is on a newly installed machine, and absolutely NO overclock done.


    PS: i dont know if this is the right section to post this in. Mods plz move it if needed.
     

    Attached Files:

    maximumcoder, Jul 29, 2008
    #1
  2. JCMS

    JCMS Notebook Prophet

    Reputations:
    455
    Messages:
    4,674
    Likes Received:
    0
    Trophy Points:
    105
    Yeah it's normal. Don't ask me why though
     
    JCMS, Jul 29, 2008
    #2
  3. E.B.E.

    E.B.E. NBR Procrastinator

    Reputations:
    1,572
    Messages:
    8,632
    Likes Received:
    4
    Trophy Points:
    206
    I can also confirm that RivaTuner makes that kind of errors. The orders of magnitude of the clocks are right, but the numbers themselves are slightly wrong, in all the mobile GPUs I ran it.

    Maybe the developer failed the math class or something :p Nah, I think it's just that mobile GPUs are not really fully supported.

    I think GPU-Z gives correct readings BTW.
     
    E.B.E., Jul 29, 2008
    #3