Jump to content
Corsair Community


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


  • Location
    England (GMT+1)


  • Interests
    Developing SIV


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


  • Optical Drive # 1


  • Homepage
  1. There should be a link to a return shipping label with the address. Yes, send all the cables. The usual UK RMA location is basically Scan Computers in Bolton. I have not done this for a few years, but you should just need to do what the e-mails say to do.
  2. Thank you, you did, please try SIV 5.24 Beta-10 or later. Just drop the beta over the SIV 5.23 release and all the silly temperatures and voltages should be gone, are they? Do Menu->File->Download->SIV Beta to get the latest SIV beta.
  3. Thank you, but it's the SIV_IHOMES.txt + SIV_IHOMES.dmi that I need, please ZIP then and attach the ZIP file. I guess your network is not setup, so do [save Local] :idea:
  4. Thank you. It helps to being 64-bit :biggrin:. I need to add EP2C612 WS support and it would make this much easier if you generated and attached the two SIV save files so I can test the changes. See http://forum.corsair.com/forums/showthread.php?p=788225 for what I would like/need.
  5. Nice system by the way, I would be interested to see how well my SIV utility reports it. I expect SIV64X will report all 28 core temperatures with no real issues, but suspect I might need to improve the motherboard reporting. I though all DDR4 ECC DIMMs reported a temperature and wonder if SIV reports them. If not then Menu->Hardware->SPD Thermal + Menu->Hardware->SPD Summary might provide some insight.
  6. No it's not, he has 2 x Xeon so 28 cores or 56 threads. Below you can see only two cores are reported for the 2nd Xeon.
  7. As CL4 is only a 32 bit application then it can only report the first 32 CPUs/16 Cores. You would need Corsair to make CL4 into a 64-bit application for it to report all your 56 CPUs/28 cores. AFAIK this is not planned.
  8. No idea, but for me it's \\RED\F\Corsair\Firmware\ :bigeyes: CLCP + CLNP Firmware.zip
  9. I have updated http://forum.corsair.com/forums/showthread.php?p=892389 to include the 0.5.104 firmware.
  10. When I have both CL and SIV active at the same time SIV is unable to report the CLCP fan speeds and I suspect this is down to CL failing to correctly use the Global\CorsairLinkReadWriteGuardMutex named mutex to interlock access :mad: Below you can see that both CL + SIV are reporting incorrect information for my 2 x CLCP. OK, I have known this was likely to happen since Wed 14-Jun-2017 @ 23:12, but the CL release notes totally fail to mention this planned regression when they should do :p:. Note you will also get the same issue if you use AIDA64 or HWiNFO to report your CLCP :bigeyes:. None of the issues I raised in http://forum.corsair.com/forums/showthread.php?p=920210 seem to have been addressed :(:. This is reported as a error code 52 error in Device Manager and I posted http://forum.corsair.com/forums/showthread.php?p=917533 which specified what I think is the root cause of the issue. If Windows Device Manager reports an error code 52 for your Asetek cooler or AXi PSU I recommend using the correctly signed Corsair drivers I attached to: http://forum.corsair.com/forums/showthread.php?p=856104 (Asetek coolers). http://forum.corsair.com/forums/showthread.php?p=888388 (AXi PSUs).
  11. Don't use SIV if you have ASUS AI Suite active!, see http://forum.corsair.com/forums/showthread.php?t=141037 There are many posts about ASUS AI Suite + CL4 "not getting along" and I advise against trying to do this.
  12. If in Device Manager you Right/Click on the device with the yellow triangle what error code does the properties panel report?
  13. You should use 4-pin PWM fans so the sensible option is to use HD120 RGB LED fans :nodding:. No, SP120 RGB LED fans are 3-pin voltage so can't be controlled by a H100iV2 :(:
  14. As your AX860i is connected via the H80i C-Link port then all the posts I made about the SIUSBXP driver don't apply. This driver is only used when the Corsair Link AXi PSU USB Dongle is used to connect AXi PSUs. SIV reports your AX860i so the hardware is fine and CL4 should also report it :nodding:, but I have no real idea as to why CL4:!oops: fails. I suggest you log a call via https://support.corsair.com/ and ask Corsair to fix their software :rant2:, remember to upload your original invoice. As no fans are connected to the H80i I guess you must be using the motherboard to control them, are you? Assuming so I guess you have no real need to use CL4. Looking at your http://forum.corsair.com/forums/showthread.php?p=903638 post my guess is that things went wonky in CL I would be inclined to try CL with the CPUIDSDK.dll from CL
  15. Given they are different revisions I guess they came from different kits and in general mixing DIMMs from different kits may not work. My first step would use my SIV utility to look at the SPD and check all four have the same timings.
  • Create New...