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.

    Low (31%) GPU Usage

    Discussion in 'Sager and Clevo' started by JackNaylorPE, Sep 2, 2012.

  1. JackNaylorPE

    JackNaylorPE Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Been having issues w/ BSOD's caused by nvlddmkm.sys error so started by checking GPU temps w/ OCCT. Using MSI Afterburner to monitor temps, ran OCCT GPU test.

    GPU usage shot up to 100% as expected ....for a few seconds. After initial burst, remains throttled as follows:

    GPU Usage = 31%
    GPU Fan Speed = 100% (tho it's dead silent and can barely feel exhaust
    GPU Temp = 58C

    Seems to me getting 31% of ya GPU's output would be below most people's expectations.

    That temp seems awful low for throttling to occur. Sager NP9170 w/ nVidia 675M, 16GB, Momentus 750 GB and i7-3720QM.

    Optimus is set top run OCCT on 675M.

    Everything else I run OCCT on pegs the GPU at 100%

    Also found it unusual that I had to install Afterburner to monitor GPU temps ... OCCT did not sense GPU temps.

    CPU test showed 70, 77,78, 72 C .... by comparison, normal numbers.

    NOTE: Afterburner used strictly for temperature monitoring, no OC applied
     
    JackNaylorPE, Sep 2, 2012
    #1
  2. jaybee83

    jaybee83 Biotech-Doc

    Reputations:
    4,125
    Messages:
    11,571
    Likes Received:
    9,150
    Trophy Points:
    931
    OCCT is a bad choice when it comes to nvidia mobile gpus, they all have an automated throttling mechanism hardwired in them,being activated once OCCT is detected. i would rather check with msi kombustor or 3dmark11 in loop or maybe a gaming benchmark :)

    Sent from my Galaxy Nexus using Tapatalk 2
     
    jaybee83, Sep 2, 2012
    #2
  3. JackNaylorPE

    JackNaylorPE Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Drats..... was using it since kept getting crashes w/ nvldmkm.sys

    Now using Beta 306.02 driver
     
    JackNaylorPE, Sep 2, 2012
    #3
  4. JackNaylorPE

    JackNaylorPE Newbie

    Reputations:
    0
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    5
    Still continuing to receive nvldmkm.sys errors ..... now using beta 306.02 driver. Sometimes I can have game open a few hours .... today crashed after less than 20 minutes in consecutive failures ..... tho furmark ran fine (1 hour)

    Sux having a 675M and having to sue on board GFX ..... detail and dump files here:

    SysWOW64\ntdll.dll Errors - Windows 7 Forums
     
    JackNaylorPE, Sep 16, 2012
    #4