• Sign in to follow this  
    Followers 0

    NVIDIA GTX 980M Hynix to Samsung Memory Swap


    Khenglish

    So I didn't like that the memory on my 980m only clocked to 6.4 GHz after raising the voltage to 1.48V from 1.35V, and wanted my memory to run even faster. I knew someone with a spare 970, so we made a deal where I buy the card, and if it still worked after I switched all the memory chips, he'd buy it back (for reduced amount if it could no longer do 7GHz, but at least 6GHz). Long story short, he bought the card back and I got faster memory.

     

    MSI 970 4GB Lightning original memory: Samsung K4G41325FC-HC28 (7GHz rating, 8GHz max overclock)
    MSI 980m 4GB original memory: Hynix H5GQ4H24MFR-T2C (6 GHz rating, 6.4GHz max overclock)

     

    Both cards are GM204 chips. The 980m has one less CUDA core block enabled than the 970, but it has the full 256-bit memory interface and L2 cache with no 3.5GB issues, while the 970 is 224-bit with 1/8th of the L2 cache disabled. Both cards are 4GB with 8 memory chips.

     

    I highly suspected this memory swap would work because video cards read literally nothing from a memory chip. There is no asking for what the chip is or even the capacity. They write data to it and hope they can read it back. Memory manufacturer information read by programs like GPU-z isn't even read from the memory. It's set by an on-board resistor. I also had changed multiple memory chips in the past, so was fairly confident I could physically do the job.

     

    I started with just one chip switched from both cards. This meant both cards were running a mix of memory from different manufacturers and of different speed ratings, but same internal DRAM array configuration. Both cards worked. Here is a picture of the 980m with one chip switched over:

     

    JXVyaWy.jpg

     

    Now how did the cards react? The 980m behaved no differently. No change in max overclock. The 970 though... I expected it to be slower... but...

     

    970 with 1 Hynix chip, 7 Samsung (originally 8 Samsung)
    7GHz = Artifacts like a crashed NES even at desktop
    6GHz = Artifacts like a crashed NES even at desktop
    5GHz = Artifacts like a crashed NES even at desktop
    2GHz = Fully Stable, 2d and 3d

     

    I didn't try 3GHz or 4GHz, but yeah, HUGE clock decrease. I shrugged though and kept switching all the memory figuring that as long as it worked at any speed, I could figure out the issue later. With switching more chips through 7/8 switched there was no change in max memory clocks.

     

    What was really fun was when I had 7/8 chips done. My GDDR5 stencil got stuck and ripped 3 pads off the final Samsung chip. Needless to say there was a very long swearing spree. Looking up the datasheet I found that 2 pads were GND, and a 3rd was some active low reset. Hoping that the reset was unused, I checked the 970's side of the pad and found it was hardwired to GND. This meant the signal was unused. I also got a solder ball on a sliver of one of the GND pads that was left, so I was effectively only missing a single GND connection.

     

    I put the mangled 8th chip in the 980m and it worked. Net gain after all of this... 25 MHz max overclock. Something was obviously missing. I figured I would switch the memory manufacturer resistor, hoping that would do something. I saw that Clyde found this resistor on a k5000m, and switching it to the Hynix value from Samsung had no effect for him. He found that for Hynix on the k5000m the value was 35k Ohms, and for Samsung 45k Ohms. I searched the ENTIRE card and never found a single 35k Ohm resistor. Meanwhile the 970 also worked with all 8 chips swapped, at a paltry 2.1 GHz.

     

    Then I got lucky. Someone with a Clevo 980m killed his card when trying to change resistor values to raise his memory voltage. His card had Samsung memory. He sent his card to me to fix, and after doing so I spent hours comparing every single resistor on our boards looking for a variation. Outside of VRM resistors there was just a single difference:

     

    AIU6Ph3.jpg

     

    On his card (his is shown here) the boxed resistor was 20k Ohms. On mine it was 15k Ohms. I scraped my resistor with a straight edge razor (I could not find a single unused 20k resistor on any of my dead boards) raising it to 19.2k, hoping it was close enough.

     

    And it was! Prior to this I also raised the memory voltage a little more from 1.48V to 1.53V. My max stable clocks prior to the ID resistor change were 6552 MHz. They are now 6930 MHz. 378 Mhz improvement.

     

    Here's a 3dm11 run at 7.5 GHz (not stable, but still ran)
    http://www.3dmark.com/3dm11/10673982

     

    Now what about the poor 2GHz 970? I found its memory ID resistor too:

    6q6iGuQ.jpg

     

    Memory improved from 2.1 GHz to 6.264 GHz. Surprisingly the memory was slower than it was on the 980m. I expected the 970's vBIOS to have looser timings built in to run the memory faster. As for why the memory was over 100MHz slower than the 980m, 980m actually has better memory cooling than the 970. With the core at 61C I read the 970's backside memory at 86C with an IR thermometer. The Meanwhile the 980m has active cooling on all memory chips, so they will be cooler than the core. In addition, the 980m's memory traces are slightly shorter, which may also help.

     

    The 980m at 6.93 GHz is still slower than the 8 GHz that the 970 was capable of with the same memory. I'm not sure why this is. Maybe memory timings are still an issue. Maybe since MSI never released a Hynix version of the 970 meant leftover timings for an older card like a 680 were run, instead of looser timings that should have been used (I know in system BIOS tons of old, unused code get pushed on generation after generation). I don't know, just guessing. Talking to someone who knows how this stuff works would be great. I still want 8 GHz.

     

    Some more pics. Here's one with the 970 about to get its 3rd and 4th Hynix chips:
    Xuu0dxa.jpg

     

    Here's my 980m with all memory switched to Samsung. Sorry for the blurriness:
    7B8bHQm.jpg

     

    So in summary:

     

    1. It is possible to mix Samsung and Hynix memory, or switch entirely from one manufacturer to another, with some limitations.

     

    2. There is a resistor on the pcb that is responsible for telling the GPU what memory manufacturer is connected to it. This affects memory timings, and maybe termination. It has a large impact on memory speed, especially for Hynix memory. This resistor value can be changed to another manufacturer. It is not guaranteed that the vBIOS will contain the other manufacturer's timings. If it does they may not be 100% correct for your replacement memory.

     

    3. If you take a card meant for Hynix memory, you can mix Samsung memory of the same size if it is a faster memory. If the memory is the same speed, the penalty for running Samsung with Hynix timings may hurt memory clocks.

     

    4. If you take a card meant for Samsung memory, you cannot mix any Hynix memory without MAJOR clock speed reductions without also changing the memory manufacturer resistor. It is not guaranteed that the vBIOS will contain the other manufacturer's timings, or if it does 100% proper timings for your specific memory.

     

    5. For Kepler cards the Samsung resistor value is 45k, and for Hynix 35k. For Maxwell cards the Samsung resistor value is 20k, and Hynix 15k.

     

    Next up is changing the hardware ID to be a 980 notebook. Clyde  also found HWID to have an impact on the number of CUDA core blocks enabled. In about a month I can get a hold of a 970m that someone is willing to let me measure the resistor values on. It has the same pcb as the 980m. Does Nvidia still laser cut the GPU core package? We will find out.

     

     

    Full thread can be found here: https://www.techinferno.com/index.php?/forums/topic/9021-hardware-mod-gtx980m-hynix-to-samsung-memory-swap/#comment-134361

     


    10 people like this
    Sign in to follow this  
    Followers 0


    User Feedback


    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!


    Register a new account

    Sign in

    Already have an account? Sign in here.


    Sign In Now

  • Similar Content

    • By J95
      Game Ready
        •Provides the optimal gaming experience for Sniper Elite 4, For Honor, and Halo Wars 2.

      New Features:
        Video SDK 8.0
        •High-bit-depth (10/12-bit) decoding (VP9/HEVC)
        •OpenGL input surface support for encoder
        •Weighted Prediction
        •H.264 ME-only mode enhancements

      Application SLI Profiles:
        •No SLI profiles were added with this version.
       
      Added or updated the following 3DV profiles:
        •Sniper elite 4 - Not recommended

      3D Compatibility Mode Profiles:
        •Sniper Elite 4 - Excellent
        •For Honor - Excellent

      Changes and Fixed Issues in Version 378.66:
        •[Surround]: Surround cannot be enabled on the XGPU. [200236703]
        •[G-Sync]: With G-Sync and V-Sync both enabled, there is a long delay when switching a game from full-screen mode to windowed mode.[1867557]
        •[Second Life 64-bit]: World view is tinted blue after disabling Advanced Lighting Model. [200274562]
        •[The Division]: Shadows flicker after enabling PCSS. [1867573]
        •[Kepler GPUs][Battlefield 1]: There is flickering in the game when using TAA. [1865681]
        •[SLI][Battlefield Day28 Patch]: The menu text becomes jittery with SLI is enabled. [1837721]
        •[SLI][Surround][GeForce GTX 1080]: The system crashes when launching games in SLI Surround using HDMI 2.0 connections. [1834142]
        •[GeForce GTX 1080][Heroes of Storm]: The game crashes when launched. [200274793]
        •[GeForce 860M][Notebook]: Direct X games crash. [1868454]
        •[Minecraft]: Java SE Binary crashes pointing to nvinitx.dll. [200274582]
        •[GeForce GTX 980 Ti]: The driver is unable to detect multiple TV models. [1788948]

      Software Module Versions
        •NView - 148.47
        •HD Audio Driver - 1.3.34.21
        •PhysX System Software - 9.16.0318
        •GeForce Experience - 3.1.2.31
        •CUDA - 8.0
       
       
       
      Windows 10
       64-bit
        32-bit 
             Windows 7 & 8.1
       64-bit
       32-bit
       
    • By J95
      Please follow the instructions below.
      • Specs.
      • Device manager ->Display Adapters ->Details ->Device Description ->Hardware Ids, post results (request).
      - Extract downloaded driver using 7-Zip/winrar.
      - Extracted Nvidia...International\Display.Driver folder\ -> copy/overwrite nvdmi.inf
      - Nvidia...International folder\ -> run setup.exe
      - Windows 8 - disable driver signing
      Command Prompt (Admin) Win key + X Type:
        bcdedit /set {current} testsigning yes -> "The operation completed successfully" ->reboot ->Install drivers.
      Exit test mode, cmd (admin).
        bcdedit /set {current} testsigning no ->reboot.
      - Use DDU to remove previous drivers/GPU installations (Nvidia & AMD), create restore point then select first uninstall option (safe mode).
      GeForce 334.89 WHQL
      Modded nvdmi.inf v334.89 AW M17XR2/R3/R4 3D + M18XR1/R2 GTX 680M / 780M
      Modded nvdmi.inf v334.89 AW M18XR1/R2 GTX 680M / 780M SLI Enabled
      - - - Updated - - -
      Quadro Notebook Driver 334.95
      PhysX 9.13.1220
      - Extract
      - Nvidia...International folder\ -> delete the following folders:
      Display.NView
      Display.Update
      Display.Optimus
      NVWMI
      - Display.Driver copy/overwrite nvdmwi.inf
      - Nvidia...International\ -> run setup exe
      - Install Physx -> reboot
      Fire Strike NVIDIA GeForce GTX 780M video card benchmark result - Intel Core i7-3940XM,Alienware M17xR4
      [
      nvdmwi.inf_v334.95_AW_M17XR2_R3_R4_3D_M18XR1_R2_GTX_680M_780M.zip
      nvdmwi.inf_v334.95_AW_M18XR1_R2_GTX_680M_780M_SLI_Enabled.zip
    • By 750dmg
      Hi guys,
      I succesfully flashed v2 vbios from prema and I tried 1v and and oc but I couldnt. I think it was power suply. Mine is 230w. And I tried 0.75 0.50 0.25 and 0 volt. But now I m trying game, benchmark screen goes dark and after beeping at 0 volt. Is this a hardware damage? I used just 1v max.(temperature max 70c)
      I tried
      cmos reset
      DDU
      Xtu uninstall
      And come back to stock vbios
      I think my card is dying
      Please help me!
       
    • By J95
      Game Ready
        •Provides the optimal gaming experience for Resident Evil 7 Biohazard, Conan Exiles early access, and the For Honor closed beta.

      Added support for the following products:
        •GeForce GTX 1050 notebook
        •GeForce GTX 1050 Ti notebook

      Added or updated the following SLI profiles:
        •Battlefield 1
        •Deus Ex: Breach Standalone - added DirectX 11 profile
        •Diablo III - added DirectX 11 profile
        •Dreadnought(2016) - added DirectX 11 profile
        •LEGO: Minifigures Online - added SLI-Single profile
        •Sid Meier's Civilization VI
        •Shooter Game (HDR) - added DirectX 11 profile
        •Sniper Elite 4 - added DirectX 11 profile
        •Space Hulk: DeathWing - added SLI-Single profile
        •Tom Clancy's Ghost Recon: Wildlands
        •Watch Dogs 2

      3D Vision Profiles:
        •Resident Evil 7 - not recommended
        •Conan Exiles - not recommended

      3D Compatibility Mode Profiles:
        •Watch Dogs 2 - excellent

      Windows 10 Fixed Issues:
        •[GeForce TITAN X][Just Cause 3] Randomflashes occur in the game. [1846802]
        •[GeForce GTX 1080][Wargames: Red Dragon]: The system reboots after switching to full-screen mode while playing the game. [1838863]
        •[GeForce GTX1080]: Random TDR/black screens occur when running GPU-intensive Direct X applications after updating to Windows 10 Anniversary Update. [1811614]
        •[GeForce GTX 1070][Alienware Graphics Amplifier] The graphics card is not detected upon installing the driver. [200236450]
        •[GeForce GTX 1070][Battlefield 1] Rain puddles appear dark. [1853262]
        •[GeForce GTX 1060] A superfluous audio end point entry appears in the Windows Sound Devices panel after resuming from hibernate mode. [200253633]
        •[Assassins Creed - Syndicate shows intermittent flickering black or white patches on game character faces. [200211264]
        •[SLI][Battlefield 1]: Texture flickering occurs in the game with SLI enabled. [200252872]
        •[Hitman pro][DirectX 12] Flickering corruption appears in the game if the multi-GPU option is enabled from the in-game settings. [200252498]
        •[Folding @ Home] Work unit errors occur. [200262613/1831430]
        •[Diablo 3 DirectX 11] SLI profile needed. [1859126]


      Software Module Versions
        •NView - 148.47
        •HD Audio Driver - 1.3.34.21
        •NVIDIA PhysX System Software - 9.16.0318
        •CUDA - 8.0
       
       
       
      Windows 10
       64-bit
        32-bit 
             Windows 7 & 8.1
       64-bit
       32-bit
       
    • By J95
      Game Ready
        •Call of Duty: Infinite Warfare, Call of Duty: Modern Warfare Remastered, The Elder Scrolls V: Skyrim Special Edition, Obduction, Titanfall 2
        •Battlefield 1, Civilization VI, Steep: Open Beta, Tom Clancy’s The Division Survival DLC, Watch Dogs 2

      Game Ready VR
        •Eagle Flight, Obduction, Serious Sam VR: The Last Hope, and the Oculus Touch launch titles

      New Features
        •Enhanced the performance and quality of the motion vectors provided by the Motion-Estimation-Only mode of the video encoder, specifically in stereo VR use cases.

      This version adds several security improvements.

      Added or updated the following SLI profiles:
        •Titanfall 2 - disabled SLI

      3D Vision Profiles
        •No 3D Vision profiles were added with this version.

      3D Compatibility Mode Profiles
        •No compatibility mode profiles were added with this version.
       
      Windows 10 Fixed Issues:
      Install the Display Container via co-installer. [200228206]
        •[375.86, GP104] Corruption in YouTube video playback when two or more videos are playing at the same time in Chrome. [1843100]
        •Clean up the escape calls that use physical addresses. [1626231]

      Windows 8.1/Windows 8/Windows 7 Fixed Issues:
        •Install the Display Container via co-installer. [200228206]
        •NV_ESC_ID_NVAPI_REPORT_WFD_HOTPLUG and NV_ESC_ID_NVAPI_ENUM_DISPLAYIDS_EX don't validate the size of input, causing a KERNEL_SECURITY_CHECK_FAILURE. [1808374]
        •Clean up the escape calls that use physical addresses. [1626231]
        •NVL_ESC_ID_COMMON_REGISTRY_ACCESS escalates user privileges when the registry is accessed. [1359976]


      Software Module Versions
        •NView - 148.03
        •HD Audio Driver - 1.3.34.17
        •NVIDIA PhysX System Software - 9.16.0318
        •GeForce Experience - 3.2 (3.2.0.91)
        •CUDA - 8.0
       
       
       
      Windows 10
       64-bit
        32-bit 
             Windows 7 & 8.1
       64-bit
       32-bit