Forum Discussion
Windows 11 22H2 broke G.Skill Trident Z Neo Series 32GB RGB
After the update my RAM RGB can no longer be controlled and it is stuck in the default rainbow mode. My relative has the same issue with the same RAM after the update, was working fine before the upd...
Having the same issue with my G.Skill Trident Z Neo Series 16GB RGB also, hope there is a fix somewhere it's annoying stuck on rainbow mode with no control using any of the RGB apps..
Ghostimage0101 if you find a fix let me know please. I was unable to fix it. Last thing to try is updating my bios but I really don’t want to do that.
hawkeye1194 I wouldn’t update the bios, mine is up to date and it has not fixed the issue, I posted on the G.Skill forum about the issue and another person has the same problem, seems it’s all to do with the update, also had it pop up in windows now under the security about a problem with memory integrity and has now disabled it, so it’s definitely something to do with the update and G.Skill memory…
- For sure. Well this sucks, I sure hope it’s just temporarily not working and didn’t brick the ram RGB permanently.
- ok I found a fix for my memory integrity issue, I only recently upgraded to windows 11, seems others had a heap of RGB issues a while ago and not able to control them to do with a older system file called ENE.SYS which became unsigned due to a previous update while made it not trusted by the system, I MSI Dragon Center installed which I replace with MSI Center and then installed Mystic Lights using that which replaced the main system ENE.SYS file with an updated signed one... Now to do with TridentZ Lighting they use there own one of this file if you look under "Program Files (x86)\G.SKILL\Trident Z Lighting Control\Aac" there is an install for there version under there so I'm guessing that is what is causing the issue, probably there version has become unsigned and windows won't use it and I believe it's what is used to communicate between windows and the LED's on the memory.... I have also posted this on the G.Skill forum under DDR3 memory category so I hope someone comes up with a fix....