druuzil Posted July 9, 2017 Share Posted July 9, 2017 I recently purchased a 16GB Corsair Vengeance RGB kit. The problem I'm having is that you cannot control the lights using Corsair Link. All it does is repeatedly cycle through the colors. None of the settings in Link work in regards to the RAM. You can change them, but they don't actually do anything. I have checked Google and found related threads on this site that claim you need to change a setting in the BIOS called "DRAM SPD Write" to Enabled. There is no such setting in my BIOS. I have an EVGA x99 Classified Edition board w/i7 5930k. I have updated the BIOS to the latest revision (2.04) which someone posting on this board in a previous thread claimed fixes the problem. It doesn't. There is still no option in the BIOS to alter anything resembling "DRAM SPD Write". I have spoken directly to EVGA and they couldn't tell me anything either. Does Corsair plan to fix this eventually? Any solutions anyone can think of besides the DRAM SPD setting that doesn't exist in my BIOS? Any thoughts would be appreciated. If I can't fix this within a week or so I'm going to just return the RAM to Best Buy. No point in buying RGB lighting that can't be controlled/doesn't work as advertised. Link to comment Share on other sites More sharing options...
red-ray Posted July 9, 2017 Share Posted July 9, 2017 How do you know DRAM SPD Write is disabled? The [MCH] panel of my SIV utility will tell you, see http://forum.corsair.com/forums/showthread.php?p=874699. DRAM SPD Write can only be changed in SMM which means it's got to be done by the BIOS and Corsair can't "fix" this. You may need to get EVGA to update their BIOS. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 The latest BIOS revision on the EVGA site claims it fixes issues with RAM RGB lighting in the release notes, as well as a thread I saw on this site where someone claimed that the update fixed the issue for them. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 I "think" based on the above that Write Access should be enabled. That being the case, the Link Software should be able to control the color schemes, but it can't. Link to comment Share on other sites More sharing options...
red-ray Posted July 9, 2017 Share Posted July 9, 2017 I "think" based on the above that Write Access should be enabled. That being the case, the Link Software should be able to control the color schemes, but it can't. Yes, SPD write is enabled, so CL 4.7.0.77 should work. Does CL 4.7.0.77 detect the RGB DIMMs, what does the [Home] tab look like? Try starting the service 30 seconds before the GUI and see if things are different, see http://forum.corsair.com/forums/showthread.php?p=906738 Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 Yes, SPD write is enabled, so CL 4.7.0.77 should work. Does CL 4.7.0.77 detect the RGB DIMMs, what does the [Home] tab look like? Try starting the service 30 seconds before the GUI and see if things are different, see http://forum.corsair.com/forums/showthread.php?p=906738 Yes, it detects the DIMMS. It lets me choose various color options/lighting schemes, but none of them do anything. Followed the instructions in your link (starting the service, waiting 40 seconds, etc). Doesn't do anything. Link to comment Share on other sites More sharing options...
red-ray Posted July 9, 2017 Share Posted July 9, 2017 If so try with just the 2 x RGB installed and also interposing the DIMMs. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 If so try with just the 2 x RGB installed and also interposing the DIMMs. lol, I just tried this like 2 minutes before you posted and sure enough, the RGB memory doesn't seem to function while I have non-RGB memory in the system. I took out my Vengeance LPX DDR4 and now the lighting works. Thanks for all the assistance sir. Link to comment Share on other sites More sharing options...
red-ray Posted July 9, 2017 Share Posted July 9, 2017 What about with the DIMMs interposed? Can you post [sPD] + [sMB Bus] so I can see where the DIMMs are on the SMBuses. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 As soon as I interpose the DIMM's it doesn't work again. I assume by interposed you mean including the RGB RAM and the non-RGB RAM? Any mix of the 2 kits seems to result in the Link software ceasing to be able to effect the lighting. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 Ok, so apparently if I keep the RGB DIMMS contiguous (ie, slit 1 and 2 are RGB, 3 and 4 are not) then it works. If I mix it up (1 RGB, 2 non RGB, 3 RGB, etc) it doesn't work. Link to comment Share on other sites More sharing options...
red-ray Posted July 9, 2017 Share Posted July 9, 2017 Good, I suspected one combination might work. I can't see why the others fail, poor design is my guess. Link to comment Share on other sites More sharing options...
druuzil Posted July 9, 2017 Author Share Posted July 9, 2017 Thanks again bud. Link to comment Share on other sites More sharing options...
justevanus Posted July 11, 2017 Share Posted July 11, 2017 good for you the root cause have been found and can be solved... as for me the problem still exist until god know when corsair will release next update on their corsair link software Link to comment Share on other sites More sharing options...
satinghostrider Posted July 14, 2017 Share Posted July 14, 2017 Another issue that you do not have color function is Corsair Link version 4.8. It seems to be broken in 4.8. Reverting back to 4.7 solved my problem. ::pirate:: Link to comment Share on other sites More sharing options...
red-ray Posted July 14, 2017 Share Posted July 14, 2017 Another issue that you do not have color function is Corsair Link version 4.8. It seems to be broken in 4.8. Reverting back to 4.7 solved my problem. ::pirate:: The CPUIDSDK.DLL (1.1.6.1) that comes with CL 4.7 has a load of bugs that are fixed in the CL 4.8 CPUIDSDK.DLL (1.1.6.5). I advise you to use the 4.8 one with 4.7 Link to comment Share on other sites More sharing options...
satinghostrider Posted July 17, 2017 Share Posted July 17, 2017 The CPUIDSDK.DLL (1.1.6.1) that comes with CL 4.7 has a load of bugs that are fixed in the CL 4.8 CPUIDSDK.DLL (1.1.6.5). I advise you to use the 4.8 one with 4.7 Thanks! I will try that out. :D: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.