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.

    Laptop screen automatically dims on higher power settings, repeatedly!

    Discussion in 'Alienware 17 and M17x' started by Blazertrek50, Apr 21, 2011.

  1. Blazertrek50

    Blazertrek50 Notebook Evangelist

    Reputations:
    62
    Messages:
    666
    Likes Received:
    114
    Trophy Points:
    56
    This just started happening this morning after booting up. Please understand that I have two external monitors connected to my M17x-R2, one by the HDMI port and one by a USB port. Those two screens do not dim but the laptop one continues to even when I after I reset it. I have checked the power settings and changed them to dim screen, never, but still it dims after a few minutes. Can anyone think of why this is happening and how to fix it?

    Thanks!
     
    Blazertrek50, Apr 21, 2011
    #1
  2. Huuy

    Huuy Notebook Evangelist

    Reputations:
    40
    Messages:
    337
    Likes Received:
    0
    Trophy Points:
    30
    I have the same problem, it dims when windows starts up. The only fix i can think of is going into CCC and manually turning up the brightness.
     
    Huuy, Apr 21, 2011
    #2
  3. Huuy

    Huuy Notebook Evangelist

    Reputations:
    40
    Messages:
    337
    Likes Received:
    0
    Trophy Points:
    30
    Has anyone else experienced this problem, and know how to fix it?
     
    Huuy, Apr 21, 2011
    #3
  4. Blazertrek50

    Blazertrek50 Notebook Evangelist

    Reputations:
    62
    Messages:
    666
    Likes Received:
    114
    Trophy Points:
    56
    I ended up restarting and everything was fine since then, weird huh? Probably a driver glitch.
     
    Blazertrek50, Apr 22, 2011
    #4