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.

Possible GPU upgrade for Precision M4600

Discussion in 'Dell Latitude, Vostro, and Precision' started by garmac, Mar 6, 2015.

  1. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
    Yeah, exactly what I wanted:) So, what I see: you have 3x 4Gb 1333Mhz sticks and one 8Gb 1600Mhz. Samsung stick is 100% unlocked and can be flashed without problems to JEDEC 1600Mhz. First 128 byte region is 100% locked in ASint modules. But overall, there is no problem to flash XMP to any of them (2nd 128 byte region is unlocked on every RAM, XMP profiles are stored here).

    Luckily, I have the same ASint 4Gb module laying around and I've decided to test it before you do. Good news: 1600Mhz XMP with 9 timings works well, Linx 30 min test passed. Screenshot attached to see it's glory lol:D

    Ok, now is most interesting how-to part:
    1. Download RWEvrything
    2. Open it, go to Access >> DIMM SPD and after this Access >> SMBus Device. Now you should have two windows inside main program window.
    3. Now, let's make backups of current SPDs. Use DIMM SPD window for that. You should see 0xA0, 0xA2, 0xA4 and 0xA6 devices - it's your RAM modules. 0xA0 and 0xA4 located on the bottom of the laptop. Select device, click save button (F2) and save the dumps.
    4. Next thing we do is writing XMP to the SPD. Go to the second window and there you need to type some values at the top menu string:
      SMBus.png
    5. After that, unzip the archive with XMPs, click on load (F3) button and select, for example, xmp_A0.rw file. You should load all the files like this. Every file corresponds to it's own DIMM address.
    6. When done with flashing, it's time to check if it was flashed as it should. In the first window re-read all the DIMMs to see if they are looking good
    Before rebooting, we need to create FAT32 usb with NVRAM editor (attached to the post). Just extract it to the root of the thumb drive. Idk, if Dell will pick up XMP profile automatically, but to be sure that XMP is enabled we need to do this manually:
    1. Boot from USB drive in UEFI mode.
    2. When command line will appear execute the following:
      Code:
      setup_var 0xC4 0x01
    3. Then shutdown and boot up.
    That's all:) Have fun:)

    P.S. ASint modules should run without any problems with these timings, don't sure about ADATA and Samsung module. In any case, the recovery process is super easy so don't worry about that:)
     

    Attached Files:

    Last edited: Jun 4, 2017
  2. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
  3. Reciever

    Reciever D! For Dragon!

    Reputations:
    1,510
    Messages:
    5,333
    Likes Received:
    4,190
    Trophy Points:
    431
    Ok completed the guide and now I can see the memory is reporting XMP when I look at CPU-Z or HWInfo

    But active speed still seems to be 1333mhz? Ill run that command line again just to see if it didnt stick in the mean time.

    Memory1333mhz.PNG


    Do you think its possible to push 2133Mhz RAM to faster speeds?
     
  4. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
    @TheReciever
    Have you followed steps with NVRAM editing?
     
  5. Reciever

    Reciever D! For Dragon!

    Reputations:
    1,510
    Messages:
    5,333
    Likes Received:
    4,190
    Trophy Points:
    431
    Yep! I did it twice now and still not pushing 1600mhz quite yet.

    When I submitted the command you provided I get more or less this response: GUID does not match expected GUID, taking nevertheless.....
    Then ends in : setting offset 0xC4 to 0x01
     
  6. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
    Hm... Your system have changed the timings BTW. K, firstly, try to run the system with only ASint sticks. Just need to be sure that we are set the BIOS good. After, try to add one more stick.
     
  7. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
    It's ok. But to be sure, boot from USB again and execute "setup_var 0xC4". If you'll see 0x01 - we are ok.

    Also, would be nice if you share your dumps from RWEverything.
     
    Last edited: Jun 5, 2017
  8. Reciever

    Reciever D! For Dragon!

    Reputations:
    1,510
    Messages:
    5,333
    Likes Received:
    4,190
    Trophy Points:
    431
    Sure Ill run it again :)

    Do you mean like this? 11.PNG 22.PNG 33.PNG 44.PNG
     
  9. valuxin

    valuxin Notebook Evangelist

    Reputations:
    146
    Messages:
    456
    Likes Received:
    159
    Trophy Points:
    56
    Yeah, but not screens - I need rw files you've made:)
     
  10. Reciever

    Reciever D! For Dragon!

    Reputations:
    1,510
    Messages:
    5,333
    Likes Received:
    4,190
    Trophy Points:
    431
    Oh ok my mistake
    This is I believe before and after.

    Also I just realized when I was going through the BIOS earlier that my boot drive is on legacy....So Im thinking that may be why NVRAM was throwing the error about the GUID maybe?
     

    Attached Files:

Loading...

Share This Page