Vengeance Pro RGB, two sticks not lighting (Aorus Gaming 7 Z370)

[JerryCooke]

I recently built a new system and installed 32GB of 3200 Vengeance Pro RGB in the form of four dimms. They worked fine to begin with, but now only two sticks change colour properly, with the other two lighting up the wrong colour, only on the top and bottom.



As you can see, when I change colour, they partially change.



I have removed all Gigabyte software and updated the BIOS to the newest version, so there should be no conflict.

[Violents]

3 things to try. Reinstall icue. swap the modules that dont light right to the side that does. change the setup to 1x2 and see if one of the right ones lights up correctly.

[JerryCooke]

Originally Posted by Violents

3 things to try. Reinstall icue. swap the modules that dont light right to the side that does. change the setup to 1x2 and see if one of the right ones lights up correctly.

Re-installing iCUE had no noticeable effect.

Swapping the modules 2 for right 2 made it clear that it's the modules, not the DIMM slots that are the controlling factor.

https://imgur.com/lYHrGqb

Running just those two DIMMs by themselves didn't have any effect.

https://imgur.com/DWGuWyT

[MalakaiAE]

Same thing is happening to me.

memory was working fine, installed iCUE and now one stick works, one stick seems to be in some default unchangeable dim pattern.

removing/reinstalling iCUE does not help. Can't configure via iCUE nor Gigabytes RGB app.

[DevBiker]

Try a complete power down (unplug) and then restart. I've seen them get "stuck" and that resolved it.

Also, sometimes it take a couple of "tries" before the lighting effect seems to "stick".

Finally, make sure the SPD Write is enabled in your BIOS.

[MalakaiAE]

I've done the following

1. Shut down
2. Reboot
3. Move ram around to different ram banks.
4. Swapped ram between slots. Power was off/removed from the system for hours after this.
5. Cleared bios settings
6. Turned SPD Write off and on
7. Reinstalled iCue
8. Removed iCue
9. Installed Gigabyte RGB Fusion
10. Removed Gigabyte RGB Fusion
11. Removed NZXT CAM
12. Installed Corsair Link
13. Removed Corsair Link
14. Removed all software
15. Reinstalled windows.
16. Installed the older Cue (does not support Vengeance Pro) Then updated to the latest release from within the software.
17. Enabled XMP Profile
18. Disabled XMP Profile
19. Turned Windows Fastboot off
20. Disabled Fastboot in the Bios

Nothing works, and at this point I'm considering returning the ram.

[PJH]

Hey, hey!

Lots of issues on z370 Gigabyte and MSI boards with this ram from what I've been seeing on other tech forums.

[JerryCooke]

This is disappointing, I've tried everything that has been suggested and to no avail either.

It's very sad since two of the sticks work fine and they're just plain beautiful. I'd love it if somebody from Corsair would actually comment with some ideas.

[Corsair Rick]

Hello JerryCooke,

When it comes to odd issues that crop up seemingly randomly, the first thing I check is if any Windows 10 updates were installed when the issue started. If that's the case, then I restore to that point and verify the issue no longer occurs. If it isn't then delete the software (iCUE in this case) and allow Windows to update. After it is and you've restarted, you should be fine to reinstall.

If that isn't the case, then I would suggest making sure that all your drivers are up to date. I assume they are, but it's always good to double check. Failing this, please contact our support team at support.corsair.com by creating a ticket. That way we can look into this issue further.

EDIT: One other thing to try. Fully remove power for the system, physically remove the CMOS battery, and wait about a minute before plugging it back in and attaching the power cable.

[Corsair CJ]

Commenting here for reference, I'm working with JerryCooke over PM to see what's going on with his modules.

[MalakaiAE]

Doing some research, it seems the SPD is corrupted. No idea how to if I can fix it yet as the links talking about this are all about a different vendors ram

https://www.whiskey-foxtrot.com/2017...gb-restore-it/

[munkon]

Doing some research, it seems the SPD is corrupted. No idea how to if I can fix it yet as the links talking about this are all about a different vendors ram why not lighting.

https://www.whiskey-foxtrot.com/2017...gb-restore-it/

Restore process isn't same? They are recommending a paid software($16) for this solution. I doubt it worth solution or not.

[MalakaiAE]

Originally Posted by munkon

Restore process isn't same? They are recommending a paid software($16) for this solution. I doubt it worth solution or not.

You need a good dump of the SPD to restore. Their database doesn't have it yet. I'm exchanging my ram tomorrow, I'll grab a dump for people to use.

This problem looks to be easy to replicate. Multiple RGB Programs are reading/writing to the SPD at the same time and corrupting it. Poor coding and poor hardware allows this and no vendor has even acknowledged it. There are videos all over youtube. $16 is a lot but I consider it well worth if it this problem happens often.

[Cpt.Planet]

Originally Posted by MalakaiAE

Doing some research, it seems the SPD is corrupted. No idea how to if I can fix it yet as the links talking about this are all about a different vendors ram

https://www.whiskey-foxtrot.com/2017...gb-restore-it/

Can you attach a dump of your SPD? I really doubt this is an SPD issue.

[Cpt.Planet]

Originally Posted by MalakaiAE

You need a good dump of the SPD to restore. Their database doesn't have it yet. I'm exchanging my ram tomorrow, I'll grab a dump for people to use.

This problem looks to be easy to replicate. Multiple RGB Programs are reading/writing to the SPD at the same time and corrupting it. Poor coding and poor hardware allows this and no vendor has even acknowledged it. There are videos all over youtube. $16 is a lot but I consider it well worth if it this problem happens often.

The Corsair's don't write to the SPD EEPROM they write to an MCU instead. The reason G.Skill's modules had this issue was due to improperly designed PCB. They left a resistor off which led to it becoming corrupted after multiple reboots.