LordRuin Posted May 1, 2016 Share Posted May 1, 2016 Recently I updating my corsair link, and now my h80i, leds, fans, pump, etc. is not being recognized. I uninstalled corsair link, and reinstalled it a few times, and it didn't help. Anyone have any suggestions on what to do? Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 Anyone have any suggestions on what to do? Is the H80i listed on Devices and Printers and/or by Device Manager? You should also complete you PC Specs especially the Windows version The SIV [uSB Bus], [Link Devices] and [Link Status] panels allow the root cause of many hardware issues to be determined and resolved. If you need help with a CL hardware issue I recommend posting these screen shots. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 No it is not listed under either of those. Also, I tried to fill out the specs to the best of my ability. There is something listed under "Unspecified" called "Integrated USB Bridge". Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 There is something listed under "Unspecified" called "Integrated USB Bridge". That is the H80i so Windows is detecting it. Is Device Manager showing any devices with yellow triangles? Were you to post the SIV screen shots I specified I could tell more. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 I hope this is what you were wanting. Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 I hope this is what you were wanting. [ATTACH]25044[/ATTACH] Not really, though I can see there are no device errors reported. Does C:\Users\All Users\CLink4\service.log exist? If you delete it does a new one get created? Does it mention the H80i? The SIV [uSB Bus], [Link Devices] and [Link Status] panels allow the root cause of many hardware issues to be determined and resolved. If you need help with a CL hardware issue I recommend posting these screen shots. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 Yes, It does exist, and a new one does get created. No, I don't see anything about the H80i in the log. 2016-05-01 04:55:48.9015 | 12 | DEBUG: DevicesMonitor | PauseComponent: reading sensors has been finished 2016-05-01 04:55:48.9015 | 12 | DEBUG: DevicesMonitor | Total reads: devices = 4, sensors = 22 2016-05-01 04:55:48.9015 | 12 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:48.9015 | 12 | DEBUG: DevicesMonitor | CpuIdComponent: start reading sensors 2016-05-01 04:55:49.0065 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.DeviceName: Device Name=ASRock P67 Pro3 SE 2016-05-01 04:55:49.0065 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #1=2331.00 2016-05-01 04:55:49.0065 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #2=831.00 2016-05-01 04:55:49.0065 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #3=667.00 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #1=37.00 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 37, #sensor = Temp #1 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #2=32.50 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 32.5, #sensor = Temp #2 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #3=10.00 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 10, #sensor = Temp #3 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #4=33.00 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 33, #sensor = Temp #4 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Voltage: VCPU=0.96 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId Processor.DeviceName: Device Name=Intel Core i7 2600K 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #1=32.00 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 32, #sensor = Core #1 2016-05-01 04:55:49.0115 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #2=28.00 2016-05-01 04:55:49.0115 | 9 | TRACE: GroupsService | Set temperature. #temp = 28, #sensor = Core #2 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #3=30.00 2016-05-01 04:55:49.0265 | 9 | TRACE: GroupsService | Set temperature. #temp = 30, #sensor = Core #3 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #4=33.00 2016-05-01 04:55:49.0265 | 9 | TRACE: GroupsService | Set temperature. #temp = 33, #sensor = Core #4 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Package=34.00 2016-05-01 04:55:49.0265 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Package 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Load: Load=5.86 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Drive.DeviceName: Device Name=ST31000524AS 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Drive.Temperature: Temp #1=34.00 2016-05-01 04:55:49.0265 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Temp #1 2016-05-01 04:55:49.0265 | 9 | DEBUG: SensorDataLogger | CpuId Drive.Temperature: Temp #2=34.00 2016-05-01 04:55:49.0265 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Temp #2 2016-05-01 04:55:49.0265 | 13 | DEBUG: DevicesMonitor | CpuIdComponent: reading sensors has been finished 2016-05-01 04:55:49.0265 | 13 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:49.0265 | 13 | DEBUG: DevicesMonitor | FlextronicsDeviceComponent: start reading sensors 2016-05-01 04:55:49.0265 | 11 | DEBUG: DevicesMonitor | FlextronicsDeviceComponent: reading sensors has been finished 2016-05-01 04:55:49.0265 | 11 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:49.0265 | 11 | DEBUG: DevicesMonitor | AsetekCoolerComponent: start reading sensors 2016-05-01 04:55:49.0265 | 4 | DEBUG: DevicesMonitor | AsetekCoolerComponent: reading sensors has been finished 2016-05-01 04:55:49.0265 | 4 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:49.0265 | 4 | DEBUG: DevicesMonitor | HidDevicesComponent: start reading sensors 2016-05-01 04:55:49.0415 | 15 | DEBUG: DevicesMonitor | HidDevicesComponent: reading sensors has been finished 2016-05-01 04:55:49.0415 | 15 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:49.0415 | 15 | DEBUG: DevicesMonitor | ClientSpecificDevicesComponent: start reading sensors 2016-05-01 04:55:49.0415 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.DeviceName: Device Name=AMD Radeon HD 6900 Series 2016-05-01 04:55:49.0415 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.Temperature: Temp=49.00 2016-05-01 04:55:49.0415 | 9 | TRACE: GroupsService | Set temperature. #temp = 49.0000038146973, #sensor = Temp 2016-05-01 04:55:49.0415 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.Fan: Fan=1547.00 2016-05-01 04:55:49.0415 | 12 | DEBUG: DevicesMonitor | ClientSpecificDevicesComponent: reading sensors has been finished 2016-05-01 04:55:49.0415 | 12 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:49.0415 | 12 | DEBUG: DevicesMonitor | PauseComponent: start reading sensors 2016-05-01 04:55:49.0415 | 9 | DEBUG: PauseComponent | Sleep 1000 ms 2016-05-01 04:55:50.0565 | 15 | DEBUG: DevicesMonitor | PauseComponent: reading sensors has been finished 2016-05-01 04:55:50.0565 | 15 | DEBUG: DevicesMonitor | Total reads: devices = 4, sensors = 22 2016-05-01 04:55:50.0565 | 15 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.0565 | 15 | DEBUG: DevicesMonitor | CpuIdComponent: start reading sensors 2016-05-01 04:55:50.1615 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.DeviceName: Device Name=ASRock P67 Pro3 SE 2016-05-01 04:55:50.1615 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #1=2327.00 2016-05-01 04:55:50.1615 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #2=836.00 2016-05-01 04:55:50.1615 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Fan: Fan #3=676.00 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #1=37.00 2016-05-01 04:55:50.1665 | 9 | TRACE: GroupsService | Set temperature. #temp = 37, #sensor = Temp #1 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #2=32.50 2016-05-01 04:55:50.1665 | 9 | TRACE: GroupsService | Set temperature. #temp = 32.5, #sensor = Temp #2 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #3=10.00 2016-05-01 04:55:50.1665 | 9 | TRACE: GroupsService | Set temperature. #temp = 10, #sensor = Temp #3 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Temperature: Temp #4=32.00 2016-05-01 04:55:50.1665 | 9 | TRACE: GroupsService | Set temperature. #temp = 32, #sensor = Temp #4 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId MainBoard.Voltage: VCPU=0.98 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId Processor.DeviceName: Device Name=Intel Core i7 2600K 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #1=32.00 2016-05-01 04:55:50.1665 | 9 | TRACE: GroupsService | Set temperature. #temp = 32, #sensor = Core #1 2016-05-01 04:55:50.1665 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #2=28.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 28, #sensor = Core #2 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #3=30.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 30, #sensor = Core #3 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Core #4=33.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 33, #sensor = Core #4 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Temperature: Package=34.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Package 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Processor.Load: Load=2.50 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Drive.DeviceName: Device Name=ST31000524AS 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Drive.Temperature: Temp #1=34.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Temp #1 2016-05-01 04:55:50.1815 | 9 | DEBUG: SensorDataLogger | CpuId Drive.Temperature: Temp #2=34.00 2016-05-01 04:55:50.1815 | 9 | TRACE: GroupsService | Set temperature. #temp = 34, #sensor = Temp #2 2016-05-01 04:55:50.1815 | 12 | DEBUG: DevicesMonitor | CpuIdComponent: reading sensors has been finished 2016-05-01 04:55:50.1815 | 12 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.1815 | 12 | DEBUG: DevicesMonitor | FlextronicsDeviceComponent: start reading sensors 2016-05-01 04:55:50.1815 | 8 | DEBUG: DevicesMonitor | FlextronicsDeviceComponent: reading sensors has been finished 2016-05-01 04:55:50.1815 | 8 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.1815 | 8 | DEBUG: DevicesMonitor | AsetekCoolerComponent: start reading sensors 2016-05-01 04:55:50.1815 | 4 | DEBUG: DevicesMonitor | AsetekCoolerComponent: reading sensors has been finished 2016-05-01 04:55:50.1815 | 4 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.1815 | 4 | DEBUG: DevicesMonitor | HidDevicesComponent: start reading sensors 2016-05-01 04:55:50.1965 | 15 | DEBUG: DevicesMonitor | HidDevicesComponent: reading sensors has been finished 2016-05-01 04:55:50.1965 | 15 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.1965 | 15 | DEBUG: DevicesMonitor | ClientSpecificDevicesComponent: start reading sensors 2016-05-01 04:55:50.1965 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.DeviceName: Device Name=AMD Radeon HD 6900 Series 2016-05-01 04:55:50.1965 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.Temperature: Temp=49.00 2016-05-01 04:55:50.1965 | 9 | TRACE: GroupsService | Set temperature. #temp = 49.0000038146973, #sensor = Temp 2016-05-01 04:55:50.1965 | 9 | DEBUG: SensorDataLogger | CpuId DisplayAdapter.Fan: Fan=1547.00 2016-05-01 04:55:50.1965 | 8 | DEBUG: DevicesMonitor | ClientSpecificDevicesComponent: reading sensors has been finished 2016-05-01 04:55:50.1965 | 8 | DEBUG: DevicesMonitor | Need to send reboot message = False 2016-05-01 04:55:50.1965 | 8 | DEBUG: DevicesMonitor | PauseComponent: start reading sensors 2016-05-01 04:55:50.1965 | 9 | DEBUG: PauseComponent | Sleep 1000 ms Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 Yes, It does exist, and a new one does get created. No, I don't see anything about the H80i in the log. 2016-05-01 04:55:49.0265 | 4 | DEBUG: DevicesMonitor | HidDevicesComponent: start reading sensors 2016-05-01 04:55:49.0415 | 15 | DEBUG: DevicesMonitor | HidDevicesComponent: reading sensors has been finished 2016-05-01 04:55:49.0415 | 15 | DEBUG: DevicesMonitor | Need to send reboot message = False The H80i should be listed in the above section. Unless you post the SIV screen shots I can't help you. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 Is this the SIV screen cap you wanted? Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 I'm sorry for my inanity, I'm not exactly the best at computers. I'm just getting into it all. Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 Is this the SIV screen cap you wanted? [ATTACH]25045[/ATTACH] No. It is not even a SIV screen shot! Have you looked at http://forum.corsair.com/forums/showthread.php?t=140665 which the quote links to? Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 Unfortuntely I did not see that. Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 There is a hardware issue with the H80i. There should not be the I/O Error 31 on [uSB Bus] or the red blob on [Link Devices]. If you hover the mouse over the red blob there will be s Tool Tip that says this. It's possible the H80i firmware has crashed. Try doing as follows: Change the CL4 setup so that it does not start when the system starts. Power down the system and unplug it for two minutes. Double check the H80i USB + Power cables are correctly connected. Reboot and see what SIV reports. If [Link Status] lists the H80i post a new screen shot so I can see the firmware versions. If the I/O Error 31 is still there then I suspect you will have to RMA the H80i. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 I did what you suggested. I set it to not run on start up, I powered down for a couple of minutes, and I checked all of the H80is' connections. Link to comment Share on other sites More sharing options...
red-ray Posted May 1, 2016 Share Posted May 1, 2016 I can see there is no real change and I am running out of ideas. Before you updated to CL 4.2.2.27 what version of CL were you using? If you revert to that version does it report the H80i OK? Do you know what firmware version is in the H80i? The latest firmware is 1.1.3 and I know SIV reports an H80i with 1.0.4 OK. Link to comment Share on other sites More sharing options...
LordRuin Posted May 1, 2016 Author Share Posted May 1, 2016 I don't know what the firmware is. I think I had Corsair Link 2.7 which worked fine. Then I updated windows, and it started acting strange (the LED colors were tinted yellow, brown or purple, and wouldnt remain changed after rebooting when i adjusted the colors). However, the pump, and the fans were showing up in link, and I could also adjust the speed of the fans. Then I updated to the recent version of link, and the pump, fans, and LED don't show up. I tried uninstalling all the corsair stuff, and tried reinstalling different versions of link. But, nothing worked... so I decided to come here. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.