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.

    M17x R3 Not Recognizing 1600 RAM

    Discussion in 'Alienware 17 and M17x' started by ElixirLT, Aug 5, 2011.

  1. ElixirLT

    ElixirLT Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    5
    Well I've gotten my M17x finally and have been loving it, I skimped on the bad RAM from Alienware and ordered 8GB (4x2) 1600Mhz G.Skill RAM off Newegg. It's arrived and my computer can recognize all 8GB of RAM, however the Crucial System Scanner for Memory Speed/Amount is picking up that I'm running 1333Mhz RAM on my computer. So I went into the BIOS and turned on Performance Options and set my Memory Frequency to 1600Mhz and it's still showing that it's only using 1333Mhz ram (10600).

    My laptop has the Intel i7-2720QM which support up to 1600Mhz RAM, but the G.Skill was unbuffered, non-PnP RAM.

    Do I have to enable an XMP profile to be able to take advantage of the 1600Mhz RAM, or is the Crucial System Scanner just not picking up that it's 1600Mhz? Is there another way of checking what the RAM in my computer is running at frequency-wise? I'm kind of at a loss =/

    Thanks for any help in advance!
     
  2. ElixirLT

    ElixirLT Notebook Enthusiast

    Reputations:
    0
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    5
    Woops! I went and downloaded CPU-Z and checked out my system settings and it appears that the Crucial System Scanner doesn't work properly! I checked it in CPU-Z and its reporting my RAM at 797.5 Frequency, and went multiplied by two (dual channel RAM) I get 1595, which is pretty dang close to 1600Mhz. I'm guessing that system scanner doesn't work properly so oh well! Answered my own question!