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.

    Alienware sudden issue - Low FPS?

    Discussion in 'Alienware 17 and M17x' started by vree, Jun 22, 2013.

  1. vree

    vree Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Manufacturer Alienware M17xR3
    Processor Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz
    Memory 8192MB RAM
    Hard Drive 750 GB Total
    Motherboard Not Available
    Operating System Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110408-1631)
    Video Card 2GB GDDR5 AMD Radeon HD 6990M

    So I moved my alienware laptop from my house to some friends to do some gaming.

    but suddenly I noticed an extremely low FPS in minecraft. So I started up Metro Last Light.
    Wich had low FPS and graphics where completely messed up.

    Jut some extra info: I was on the latest drivers, but couldn't use integraded Graphics card anymore. but didn't care about that.

    So if I pressed F7 and FN it would pop up "witchable graphics key press detected. choose yes to enable or no to cancel" But that doens't do anything.

    This is how my CCC used to look:
    2ppihjl.png

    And this is how it looks now:
    Knipsel.PNG

    And this is how my hardware thingy looks like:
    Knipsel2.PNG

    I also tried removing the GPU and putting it back. that didn't do anything.
    Also system restore didn't do anything.

    what should I do next?
    Did my graphics card die????

    Please help I'm completely stuck here :S
     
  2. TR2N

    TR2N Notebook Deity

    Reputations:
    301
    Messages:
    1,347
    Likes Received:
    255
    Trophy Points:
    101
    Trace back to when it was good and to when it changed. Looks like if no software changes occurred or new AMD drivers were installed, then something cactus went with the 6990m.
    In your windows device manager there is nothing shown that it is been detected so maybe move into the bios to check that the 6990m is being detected there.

    I am sure the r3 experts will give you more feedback but it could also be related to the switching between the dGPU and iGPU and there maybe a setting in bios for that? Don't quote me on that one..
    One thing you might like try is atiman uninstaller and reinstall the AMD drivers as there could be registry corruption in the driver.
    Here is a link to it
    http://www.mediafire.com/download/sja6d1z3t2ld6as/Atiman+Uninstaller+v.6.3.1.msi
    Instructions:
    1. run ATIMAN (do the automated process)
    2. Restart computer and run drivers sweeper (check AMD) after ATIMAN has completed.
    3. After restart re-install AMD Drivers.

    Best of luck :)
     
  3. vree

    vree Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Got this when checking the BIOS.

    foto.jpg

    Didn't try the Atiman thing yet.
    I did try just overwriting the drivers. But that didn't change anything.
     
  4. vree

    vree Notebook Enthusiast

    Reputations:
    0
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    5
    Fixed it for now.

    Seems like a problem other people got too.
    http://en.community.dell.com/owners-club/alienware/f/3746/t/19459015.aspx?PageIndex=5
    And dell doesn't provide a fix.... Not a free one....

    Read trought the whole topic.

    Some said by removing the GPU it worked. But I already tried that.
    But what did I ahd to loose. So I did it again. And messed arround with the power save settings like other people suggested.
    Rebooted. And now it reshowed in the bios. So it worked fine again.

    But I'm afraid it might come back, like it did with other people. And there doesn't seem to be a real fix or whatever....

    Still thanks for the support. I might be back if all goes to hell again xD