Jaan_Doh Posted February 11 Share Posted February 11 Hi all, I recently built a new system and everything was working fine, I'm not in to overclocking etc, I just buy the best spec according to my budget, rather than buying a mid level item and cranking the life out of it.. So everything was great running at default settings in the bios, no core boost, no XMP the ram was running at 4800mhz and I thought I'll sort that out later / last... Then I had the icue update to firmware two portions, one for command controller one for ram... At this point the icue popped up a message to say that one stick of ram has incorrect XMP setting? (something to that effect) and I thought I have a matched pair of 2x24gb as bought, both together, and no XMP 1 or XMP 2 settings were enabled in the bios, neither was core boost... But ever since then, one stick of ram remains yellow in color the full length of RGB strip on the ram stick... It changes color as per the profile once I've logged into windows but not before logging into windows.. I'm well cheesed off and wish I'd bought a different brand of ram and different brand 360mm cooler too, as this is doing my fruit in... Has anyone got any advice, on how to resolve or fix this, before I ask for a refund from the store I bought it from? I chose icue cappelix RGB 360 because the h100i with iLink on my other PC was a solid reliable piece of software, but Icue makes me worry that it might do serious damage to my pc. I have completely uninstalled icue, including profiles etc I uninstalled it because of the lack of confidence shown by many MANY users who all complain about the icue software, and how it's affecting their daily use of their PC that they have spent their hard earned cash on... My pc specs are Windows 11 MSI X670E Carbon Wifi Amd 7900x3d Corsair icue cappelix 360mm Corsair Ddr5 6000mhz 48gb (2x24gb) ram Corsair icue 5000x case Sapphire Radeon 7800xt 26gb vga card Corsair 850w gold psu The ram has never run at the advertised 6000mhz and still currently running at 4800mhz ... Thank you in advance, if you can help stop this nightmare from continuing... Link to comment Share on other sites More sharing options...
c-attack Posted February 11 Share Posted February 11 28 minutes ago, Jaan_Doh said: It changes color as per the profile once I've logged into windows but not before logging into windows.. This is normal. The Lighting Effects section in CUE governs lighting behavior when CUE is running. This has the most options and needs the PC resources to manage more complex effects. When CUE is not running, either during the boot/shutdown cycle or because you terminate the app, then each device shows it's saved colorways as set in the "Hardware Lighting" section for each device. It's not uncommon for the Hardware lighting effect stored in the RAM to go blank slate or skewed after a FW update. Go to the Hardware Lighting Effects section for the RAM and set anyeffect. If one is already selected, choose another to overwrite the current save. You'll notice a clear pause between when you select it on screen and what the physical RAM does inside the case -- that's the effect being written to modules. iCUE will "preview" the HW Lighting effect while you are selecting it. It will return to your set CUE software lighting effect once you leave that section of the app. XMP needs to be enabled within the BIOS. Regardless of DDR5's ability to live tweak timings from the OS level, I advise users not to do that. You have a solid chance of wrecking the OS installation with a false move. 36 minutes ago, Jaan_Doh said: I chose icue cappelix RGB 360 because the h100i with iLink on my other PC was a solid reliable piece of software, but Icue makes me worry that it might do serious damage to my pc. What's wrong with the AIO? Link to comment Share on other sites More sharing options...
Jaan_Doh Posted February 12 Author Share Posted February 12 8 hours ago, c-attack said: This is normal. The Lighting Effects section in CUE governs lighting behavior when CUE is running. This has the most options and needs the PC resources to manage more complex effects. When CUE is not running, either during the boot/shutdown cycle or because you terminate the app, then each device shows it's saved colorways as set in the "Hardware Lighting" section for each device. It's not uncommon for the Hardware lighting effect stored in the RAM to go blank slate or skewed after a FW update. Go to the Hardware Lighting Effects section for the RAM and set anyeffect. If one is already selected, choose another to overwrite the current save. You'll notice a clear pause between when you select it on screen and what the physical RAM does inside the case -- that's the effect being written to modules. iCUE will "preview" the HW Lighting effect while you are selecting it. It will return to your set CUE software lighting effect once you leave that section of the app. XMP needs to be enabled within the BIOS. Regardless of DDR5's ability to live tweak timings from the OS level, I advise users not to do that. You have a solid chance of wrecking the OS installation with a false move. What's wrong with the AIO? The lighting effects all worked fine when I first Installed it (v5.xx) Yes it's easy to tell when the profile is loading as all the RGB lights go off for about 1-2 seconds, and then the new profile kicks in... After the first update (I think it's updated twice in all) , when the message appeared saying something about XMP, the RGB on one stick of ram remains yellow, while the other goes through some lighting effects... This happens on every boot, not just after the firmware update... The cpu core boost and XMP are/were both disabled in bios, that's why I can't understand why the icue software popped up a warning message about XMP... The aio is currently working, but to be honest, I have lost faith in the brand, because quality control should catch these glitches before broadcasting them to the world for consumption... Even on the extreme profile settings the fan speeds rarely go up unless I manually switch to a steep fan curve I created to make sure the cpu stays cool... But cpu temp can go up to 69C in a blink of a eye... I have cleaned of the thermal paste and reapplied new paste, so it's not that causing issues, I'll be keeping an eye on the cpu temps all this since I've now uninstalled icue... All the problems seem to have started after the first firmware update, I'm not even sure what version it was, nor can I figure out how to diagnose or fix the issue... It's kind of depressed me to the point where, I no longer try to fix it and if I could afford to buy a new aio and ram, I'd do so... I tried to read up in the forums to see if anyone reported similar issues, in case one of their fixes might work for me too, but that just depressed me more, because there are so many with different problems that all seem to related to or in context with the icue software.. I also saw lots of threads mentioning nzxt software, I'm going to try and Google what the link between nzxt and corsair is, in case that might help end this nightmare... Thanks for trying to help too... Link to comment Share on other sites More sharing options...
c-attack Posted February 12 Share Posted February 12 11 hours ago, Jaan_Doh said: RGB on one stick of ram remains yellow, while the other goes through some lighting effects... This happens on every boot, not just after the firmware update... Right, so you need to go in and force it to save a new effect to the module and overwrite the corrupted save. If that does not work, then we know the issue was the FW write itself and you need to force update the current FW version again. CUE Settings -> Firmware -> Check for updates -> None or Up to Date. That then reveals a drop down menu for each device to "force update". Make sure you close any other RGB or broad monitoring programs when you do that. A lot of stuff tries to read the RAM. 11 hours ago, Jaan_Doh said: The cpu core boost and XMP are/were both disabled in bios, that's why I can't understand why the icue software popped up a warning message about XMP... I suspect in error and related to the new "in OS control" options that are possible with DDR5. The module glitched on its FW application and it's throwing up an incorrect error. If it does this every time, that is a further reason to reflash the current FW update. 11 hours ago, Jaan_Doh said: Even on the extreme profile settings the fan speeds rarely go up unless I manually switch to a steep fan curve I created to make sure the cpu stays cool... But cpu temp can go up to 69C in a blink of a eye... I have cleaned of the thermal paste and reapplied new paste, so it's not that causing issues, I'll be keeping an eye on the cpu temps all this since I've now uninstalled icue... That is how it works. Your CPU is cooled conductively, regardless of the cooling method type. The metal cold plate directs the CPUs heat somewhere else. The difference between various cooling methods and sizes is in how it disposes of the waste heat. A 240-360mm radiator is not a tiny CPU air fan. It doesn't need to react to momentary blips in CPU temp and fan speed does NOT directly affect CPU temp. The cold plate conducts the heat into the liquid stream. The liquid is the transport to the radiator where the fans blow it off elsewhere. The coolant temp or liquid temp value is the lowest possible CPU temp at 0v on the CPU. For each +1C increase in coolant temp, the baseline CPU temp increases by +1C. The same thing with cooling and -1 to coolant is -1C to CPU. The easiest way to describe the mechanics is what happens when you load a specific CPU with a static 100% load. Take three different cooling methods --- a small air cooler, a 360mm AIO, and a massive 1x1m external radiator array. You then load up the CPU with Test A to 100% static and all three with read 80C (or whatever) for the first several seconds. Conductive properties don't really change much between cooling methods outside of very exotic products not for normal use. It's the heat disposal that differentiates them. The little air cooler holds that 80C for maybe 10-15 seconds and then it will start to tick up +1C every few seconds up to maybe +15-25C above 80C depending on the radiator size. This is the CPU transmitting more watts into the metal radiator than the fans can blow off. Your 360mm AIO will hold 80C for 30-60s and then slowly start going +1C every 30-60s again up to +4-8C depending on the watts. The massive external radiator can dissipate every watt the CPU puts into the liquid stream in a single pass. As such, it stays at 80C indefinitely. All three coolers will register the 69C spike when you open Program X because that is a voltage spike directed at the underside of the CPU. The cooling method cannot prevent that, only dispose of that amount of heat. All modern CPUs are extremely reactive by design. The old days of the processor sitting at a flat 700 MHz with a temp baseline to match are gone. You cannot and do not want to curb that part of your system. The CPU cooler will do what it needs to do when you actually put enough watts into the system to affect change. That point is at a minimum 1C of coolant temp change and it will take a sustained effort to raise the coolant temp by 1C. This is why people like water cooling -- the fans do not need to keep changing speed every few seconds. Slow and steady does the job. 11 hours ago, Jaan_Doh said: also saw lots of threads mentioning nzxt software, I'm going to try and Google what the link between nzxt and corsair is, in case that might help end this nightmare... How does NZXT fit into this? Are you running their CAM software too? The connection is both CUE and CAM are trying to do the same thing. Over a period of several years, CAM has at time been very grabby with its communications and it and CUE get intertwined causing neither program to do what it should. Mixing components in this age of global app control can be difficult. Link to comment Share on other sites More sharing options...
Jaan_Doh Posted February 13 Author Share Posted February 13 Thank you, I'll try to do check and do the firmware updates when I get home from work tonight... 👍 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now