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.

    GPU running on max clocks while idle

    Discussion in 'Gaming (Software and Graphics Cards)' started by Scrub, Jun 22, 2012.

  1. Scrub

    Scrub Notebook Enthusiast

    Reputations:
    0
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    5
    I have a GeForce GTX 260M on a Asus G51VX-RX05 with the latest drivers.

    While idle, according to GPU-Z my core, memory, and shader clocks are maxed out at 500, 799.2, and 1250 MHz respectively. My temperature when idle is 81C. When I use Dox's Forceware 195.62 from 2010 I don't experience these problems.

    Is there any way to continue using the latest drivers without experiencing this problem? Should I revert back to my old drivers? What could be causing this?

    Thanks.
     
  2. Kingpinzero

    Kingpinzero ROUND ONE,FIGHT! You Win!

    Reputations:
    1,439
    Messages:
    2,332
    Likes Received:
    6
    Trophy Points:
    55
    There are some issues with P states in latest geforce betas.
    First make sure you have installed your gpu drivers using the clean method. I wrote a guide that its still working flawlessy here:

    http://forum.notebookreview.com/asu...pdate-nvidia-drivers-any-windows-version.html

    After you did all the correct steps, boot in windows, and be sure you dont have any automatic overclocks set with programs like Afterburner or Nvidia inspector.

    If you want to make a "clean" test, unistall both before trying new drivers, if u use them, then install them afterwards.

    I would advice to start testing if the issue comes up again with 296.10 whql drivers, then slowing going up.
    Or if you want, try last stable whql that should be 301.42.
    Hope it helps.