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.

    Problems with Nvidia Control Panel.

    Discussion in '2015+ Alienware 13 / 15 / 17' started by Betoguar, Mar 5, 2015.

  1. Betoguar

    Betoguar Notebook Enthusiast

    Reputations:
    2
    Messages:
    37
    Likes Received:
    2
    Trophy Points:
    16
    Any one had any luck saving setting in Nvidia Control Panel.. I have install and uninstall drivers and apparently nothing is working. I choose Pot Player or Windows Media to run on the GTX 980M card but somehow it always run on the integrated graphics card.. My 4k content runs like crap on the Intels Card.
     
  2. Betoguar

    Betoguar Notebook Enthusiast

    Reputations:
    2
    Messages:
    37
    Likes Received:
    2
    Trophy Points:
    16
    I contacted Tech Support, they tried to take control of my Laptop through Alien Contact but were not successful. After attempting several steps nothing worked out, 3 hours later my Cell Phone(I really need a Hardline) died and that was the end of it. Tech was polite and tried his best to help me, it just didn't work.. I came to the realization that I would sent back the Laptop but before I would tried a Clean Windows 8.1 Install... Followed every step and It work... My system is running flawless now.. Settings are saved, Pot Player and other programs are finally using the 980M.

    Reinstall Windows 8.1 and follow Driver Installation Order.. problem is fixed
     
  3. Alienware-L_Porras

    Alienware-L_Porras Company Representative

    Reputations:
    3,658
    Messages:
    6,874
    Likes Received:
    969
    Trophy Points:
    281
    We're glad it's working fine now. It may have been an update that was installed previously.