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.

    460m clocks running at about 1/3 speed

    Discussion in 'Alienware M15x' started by Jamaro85, May 19, 2011.

  1. Jamaro85

    Jamaro85 Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    Edit: Stealth mode is off this entire time.

    Until yesterday my GPU clocks were running at 570 MHz / 625 MHz / 1140 MHz (GPU clock, memory, shader).

    Since then I have been getting approximately the following:

    [​IMG]

    Everything was good until I tried to test my GPU's load temperature with FurMark's burn-in test. I ran the test for an hour before realizing that my GPU temp had not risen even one degree. I knew something wasn't right so I checked my GPU clocks. The screenshot above is exactly what I saw.

    I then stumbled across the "GPU Shark" monitoring tool within FurMark. It gave me some interesting information:

    [​IMG]

    As you can see this shows three "performance states". You can see my GPU's current performance state, which is the lowest. My GPU sometimes alternates between performance states 12 and 8, but it never sets to performance state 0. With that said, I have no idea whatsoever as to how any of this works.

    Any thoughts, ideas or insights are appreciated!
     
  2. Mexic00ls

    Mexic00ls Notebook Deity

    Reputations:
    563
    Messages:
    857
    Likes Received:
    23
    Trophy Points:
    31
    i would never use furmark for that long the longest ive used it is for 10 mins, ive had a similar problem since i updated to a09, and the only way to get the clocks working right is by toggling stealth mode on and then back off and the clocks usually go back to normal, since i have an ati card this might work different for u
     
  3. Jamaro85

    Jamaro85 Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    Thanks for the response, I am definitely going to try that when I get back to my computer.

    Also you recommend not running FurMark for a long period of time. Is it more dangerous for a GPU to reach it's highest temp for an extended period of time than it would be for a CPU?
     
  4. Jamaro85

    Jamaro85 Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    Thank you Mexic00ls!

    It was A09 screwing everything up. After reading your post I found this in the A09 thread:

    http://forum.notebookreview.com/7394110-post253.html

    He has the GTX 260m but had the exact same problem as me. I reverted back to A08, and voila, problem fixed. I'll post a link to this thread in the A09 thread as well. Hopefully it is noted before another future BiOS.
     
  5. pepemosca

    pepemosca Notebook Evangelist

    Reputations:
    153
    Messages:
    450
    Likes Received:
    0
    Trophy Points:
    30
  6. Mexic00ls

    Mexic00ls Notebook Deity

    Reputations:
    563
    Messages:
    857
    Likes Received:
    23
    Trophy Points:
    31
    glad everythings ok now, im still on a09 and have reinstalled it 3 different times with the same out come. yeah i wouldnt recommend running furmark for any longer than 10-15 mins and when i called dell and had them share my desktop and the tech saw that i had furmark as a shortcut, he flat out told me he could void my warranty so i just told him id look for help else where.


    my gpu doesnt run low all the time, every now and then ill run furmark (for a couple of seconds in window mode) and hwinfo32(with sensors) and just to see if my gpu is raising to maximum clock or not, its a hit or miss really.....

    remember that furmark is a gpu intense stress test, your running it at full load for what ever amount of time u let it run, i don't believe you'll ever encounter a game that will push it nearly this hard as it. if your clock run at max from the beginning you might hit 80c in a matter of mins if not seconds depending on cooling and paste/pad configurations. i cant imagine what could happen after letting it run of about an hour, it cant be anything good, might be a blue screen might be smoke....
     
  7. Jamaro85

    Jamaro85 Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    Definitely good to know. Thanks for the heads up!

    To pepemosca:

    You should try to put a load on your GPU with other programs as well. My GPU temps usually idle at the middle performance state (in the second screenshot of my first post) and sometimes at the lowest one. I've confirmed with many GPU intensive apps that my clocks do rise back to max when needed.

    Edit: Temps = clocks
     
  8. pepemosca

    pepemosca Notebook Evangelist

    Reputations:
    153
    Messages:
    450
    Likes Received:
    0
    Trophy Points:
    30
    Sorry, I don't understand your point.
    What do you want me to try?
     
  9. Jamaro85

    Jamaro85 Notebook Enthusiast

    Reputations:
    0
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    15
    Sorry, I typed that up five minutes after waking up. :p I think I misunderstood and thought that you were having problems still as well.
     
  10. papasan

    papasan Notebook Enthusiast

    Reputations:
    9
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    After reading your post you made me wonder what my speeds were at- without "Stealth Mode" enabled, I was getting normal expected clock speeds. After "ENABLING" Stealth Mode- my speeds dropped to what you have displayed on GPU-Z.

    If you updated your BIOS to resolve your issue- you would have disabled the Stealth Mode trigger with the update.