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.

    Issue after resume w Powerplay enabled - game crash

    Discussion in 'Alienware 17 and M17x' started by buiz, Apr 11, 2011.

  1. buiz

    buiz Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    I have a single 5870 in my m17x. After sleep/resume I noticed in gpu-z that my gpu clock stayed at 300/400 instead of clocking up to max at 700/1000 when running games. That was with Dell's own graphics drivers. I then installed AMD's reference drivers (11.3) in the hope that that would fix the issue, but lo and behold. Now when I start a game after sleep/resume, it just crashes. If I disable Powerplay, the clocks just stay at 300/400 come what may, which of course gives low framerates. If I put the laptop to sleep with Powerplay disabled and after resume re-enable Powerplay, then games work fine and the clock throttles properly up to the max of 700/1000 and down to 100/150 at no load.

    In conclusion, thus, it appears that Powerplay is unable to properly and safely sleep/resume a 5870. Something bad happens in the resume. If Powerplay is enabled outside the sleep/resume cycle, everything works well.

    I've read about various sleep/resume problems with m17x but I've not found "my" problem reported anywhere, although I assume I'm not alone?

    Anyone tried the same and more importantly know of a fix for this?

    EDIT: I have now observed graphics working properly after a sleep/resume, with Powerplay enabled. So it now appears to be a typical troubleshooting dilemma with unpredictable behaviour and no clear pattern. I would nevertheless still like to know if anybody else has experienced this. Oh, and I also have the "plugged in, not charging" likewise with no apparent pattern - I wonder if there is some kind of general power issue related to states going on in the m17x-r2?