Jump to content

Gerder

Members
  • Posts

    6
  • Joined

Reputation

10 Good
  1. I might have found a possible reason this problem is occuring to some. I happen to have an Asus Maximus X code motherboard which has a LED code display which displays codes to determine possible issues with hardware. Normally when a system is done booting the code should be 'A0' This code means that the boot sequence test was completed and the OS was given control. Most of the time however, the display would show me a Code '40'. This means the PC awoke from a S4 sleep state. In short this is a mode which allows Windows to boot faster after a complete shutdown by saving system info and then starting from there the next time you boot your PC. Occasionally though my motherboard WOULD properly display the 'A0' code and when it did my Corsair RGB settings would load as normal. Something it didn't do when the final code was '40'. I think 'Icue' causes problems when waking a PC out of a sleep mode. Be it a deep sleep S4 or an ordinary sleep mode. Luckely the S4 feature can be disabled in Windows 10. The guy in this Youtube video will explain it. I tried it and it works perfectly. [ame] [/ame] There is a downside to this though. Windows 10 might boot a little slower than your used to. I personally don't think this is a big problem and I don't really notice it much either. Also this doesn't seem to be a solution when waking from normal sleep mode. This is still a problem to me. Hope this helps some people. It beats quiting the service in taskmanager on every startup. EDIT: If disabling S4 in Windows settings doesn't work for you, S4 can usually be disabled in your BIOS settings as well. It can usually be found in your boot settings.
  2. I'm using a NZXT internal USB hub since my MOBO only has one USB2 connector. Used it prior to when this problem occured though. Never had any issues before.
  3. Try Eddies idea. It works for me as the most easy temporary solution. Bring up Task Manager and end 'Corsair Service' process. This will bring back the right settings. Atleast for me
  4. In my case a Nodepro. Fans start as they usually do in rainbow wave mode. At the point they normally load into their appointed settings, they start flickering like mad
  5. I hope we get an official responds from Corsair. Its only fair considering the amount of money we have spend on corsair products
  6. I have the exact same issue since the latest update. I have 4 LL fans, 4 RGB strips, K95 platinum speed, Glaive and a Hydro H115i (old model) installed. All parts are working fine with the exception of all 4 fans. They start flickering in absolute seizure mode after a fresh (cold) boot or after waking out of sleep mode. Exactly like above shown GIF, even though rainbow is not my default color setting. Everything was working fine prior to the update. Only solution so far is to completely reboot from Windows. So not really a proper way to fix it. Small side note: I did swap RAM modules that same day but I can hardly believe that has anything to do with it.
×
×
  • Create New...