Jump to content


Banned by Moderators
  • Posts

  • Joined

  • Days Won


red-ray last won the day on August 5 2017

red-ray had the most liked content!


81 Excellent


  • Interests
    Developing SIV


  • Occupation
    Windows Driver Developer (KMDF, UMDF 2 and WDM)


  • Homepage

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am used to this, but rather than saying sorry post [Link Status] as I asked :idea:. The manual says to use the CPU_FAN header and it's easier to help if you use the CPU_FAN header. If you wish me to try and help then use the CPU_FAN header :idea:. If you interpose the CLNP and H100iV2 what does [uSB Bus] report? Try using Device Manager to disable power saving for the CLCH (CLCP USB hub) :idea:.
  2. Not ideal, I asked for meaningful names, feel 1.3.png is not meaningful, you should have cropped the images, you failed to post [Link Status] and I am at a loss as to why you created the http://forum.corsair.com/forums/showthread.php?t=170897 thread. The H100iV2 is not showing up on the Corsair Link Commander Hub (CLCH) at all and wonder if it's correctly connected. It's possible to insert the header incorrectly, double check it's in the middle of the USB header socket and not offset to one side. It would also be worth plugging the CLNP into the other USB header and see if it is still detected. The CPU_FAN speed seems to be zero RPM. I guess the H100iV2 is plugged into the CPU_FAN header, is it? Assuming so have you set the CPU_FAN header to PWM mode in the BIOS so the H100iV2 get's the constant +12 volts it needs. The reported CPU_FAN speed should be half the H100iV2 pump speed so around 900 RPM.
  3. It's partially down to Corsair not having the CLCC firmware source, but I can't see any good reason why CL4 can't work around the CLCC firmware issues as I managed to do this in my software.
  4. Welcome to the forum and I can try and help, but for me to be able do this you need to post some debug information. Firstly the screen shot you posted does not show up, see http://forum.corsair.com/forums/showthread.php?p=853900 for how to attach a file/screen image to a post.
  5. I suspected it would and I think the root cause is the SIUSBXP driver does not handle Windows PNP power transitions correctly. In my code I worked around the issue by automatically doing the disable/enable when the system resumes from sleep, see http://forum.corsair.com/forums/showthread.php?p=857462 I am not sure what to suggest, you could try asking Corsair to fix their driver.
  6. If you exit CL4 then from Windows Device Manager you disable and then enable the H115i, restart CL4 can you then change the fan speeds?
  7. They are posted in http://forum.corsair.com/forums/showthread.php?t=170353, but you need to get a new firmware.bin from Corsair Support
  8. Yes, but I can't help you to do this. I expect you need to get a new firmware.bin, delete the old one and replace it with the new one. Ask Corsair support for help. I know this is possible as I and many others had the same issue with our CLNPs and posted http://forum.corsair.com/forums/showthread.php?p=892389 about this.
  9. As the CLNP V0.4.94 firmware allows 96 rather than 72 LEDs I have updated SIV to allow for this. It still only allows a total of 6 strips, but it's now possible to control 6 x 16 LED strips.
  10. All I did was attach the Corsair drivers to that post over a year ago. It's been downloaded 893 times so suspect it's helped quite a few members. The driver is OK on some systems and not others and I keep wondering why. It's OK on all my systems and am wondering what is different about your setup. I suspect there are SIV screens that would give a clue. I keep wondering if my SIV V5.22 driver will load on your system and it would be great if you would check. I have never hard a report of an issue on Windows 10 so I suspect it will load OK. Ideally post the SIV 5.22 initial screen + Menu->Windows->Startup + Menu->Hardware->ACPI Tables->UEFI Info screen shots as these may well provide some insight.
  11. There is something wrong with the CL driver signing, log a call via https://support.corsair.com/ and ask Corsair to fix this. In the meantime try using the drivers I attached to http://forum.corsair.com/forums/showthread.php?p=856104 Please let me know if this helps.
  12. Post the properties panel which shows the error code
  13. Yes, many times, but I would also expect to see it for string (3) rather than "7289_2.0". You should crop images and it would be easier to help you is you used http://forum.corsair.com/forums/profile.php?do=extra
  14. HUE+ uses the ADC to GND resistance to know how many LED strips are connected, but the CLCP/CNLP do not and you need to tell the control software how many there are. If you forget about ADC and hook up the XXXX LEDs they should just work. I don't have any XXXX LEDs to try this, but am 99.42% sure they will work.
  15. The CLCC is no longer available and suspect future PSUs will only have USB. BTW all of AIDA64 + HWiNFO + my SIV utility can also report Corsair PSU information.
  • Create New...