Jump to content

msuguy71

Members
  • Posts

    19
  • Joined

Reputation

10 Good

About msuguy71

  • Birthday 10/25/1971

Converted

  • Occupation
    Medical
  1. Thank you C-attack and LeDoyen. It was the HWInfo update after all. I am not sure why I couldn't get ICUE fixed initially whenC-attack mentioned it.
  2. I quit HWInfo and ICUE. When I restarted ICUE, the fan's LEDs started working. It seems it was HWInfo this whole time! How infuriating.
  3. So, I am tired of waiting for tech support. I just submitted a RMA request. Sadly, that will probably take forever as well.
  4. Ok. I quit out of HWInfo and retested everything. No change. The commander core RGB controller is stone cold dead. I will look at disabling monitoring of these items in HWInfo going forward, but in fairness, I have running ICUE and HWInfo with this AIO and controller since I built the computer in late December without issue.
  5. Good point, I am running HWInfo as well. I did contact Corsair support about 2 weeks ago or so I think it was. Have heard nothing. Really disappointed.
  6. Installed Corsair's USB expander and no change. I think the commander core's RGB and PWM controller died.
  7. Hi, thanks for the reply! I am not having any problems with the LCD screen at all. it is working great. The pump runs, but does not respond to speed change requests. The ring around the screen is flashing off and on and does not respond to software. All of the fans connected to the commander core work, but also do not respond to speed change requests and their RGB leds do not light. I now get a response from the autodetection. It comes back with no fans found. Nothing is listed when I switch to manual either. I uninstalled armoury crate and ICUE. I then removed as much left over stuff that I could from the drive and the registry for both. I then reinstalled ICUE and left amoury crate uninstalled for now. I also loaded the default settings in the BIOS and just changed two settings (EXPO II and eco mode). Everything else in the BIOS is auto. Nothing fixed the commander core. Finally, I hooked everything up to my old commander pro and the fans and their LEDs started working. The only thing that was a problem there was that the fan graph/setting widgets kept disappearing and reappearing in ICU. I think it is because my current USB hub only uses the top four wires. The commander core uses only 4 USB wires, but the commander core has six. I have my USB hub connected to SATA power though. I have Corsair's USB hub arriving today. My PSU is more than strong enough for anything I throw at it (1600W).
  8. After reading through this thread, I am even more dismayed at Corsair's abysmal customer service with regard to tech issues and RMAs. These parts are not cheap and while I don't think anyone expects immediate service, they do not even appear to try. I am pretty deep down the Corsair rabbit hole at this point and changing will be costly. The sad part is that I also convinced my buddy to buy his first Corsair AIO (the H150i Elite LCD) and a pack of fans as well. I hope his does not die in the first couple months like mine did.
  9. I submitted a support ticket last week because the commander core for my H150i Elite LCD stopped working. Prior to this incident, the AIO worked great and all the RGB worked. The pump and PWM fan controller portions work, but the fan RGB and ring RGB controllers are not working correctly when connected to USB port. When not connected, all fans and ring light up in hardware mode. When connected, some fans have hardware lighting, some have none. LCD ring light blinks a red ring. Setup wizard not autodetecting any fans and they are not being displayed any more. Reinstalled ICUE and forced firmware reinstall on commander core. Tried different USB port. CPU temp and pump RPMs correctly reading on LCD screen. The log files have a number of lines stating, "2023-04-01T20:31:26 W cue.llaccess.util: dramReadByte failed "Dram [0:58]" cmd: 36" and "2023-04-02T12:22:17 W cue.llaccess.util: dramReadByte failed "Dram [0:58]" cmd: 36". There are seven logs that have multiple lines of this. Support has not responded. Does anyone know how long it takes for support to reply? Thanks
×
×
  • Create New...