Jump to content
Corsair Community

Search the Community

Showing results for tags 'icue stops'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CORSAIR COMMS DEPARTMENT
    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
  • COMMUNITY DISCUSSIONS
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
  • TECHNICAL SUPPORT & CUSTOMER SERVICE
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
  • PRODUCT DISCUSSIONS
    • CORSAIR iCUE
    • Build Hardware
    • Gaming Peripherals
    • Audio Devices
    • Battlestation Hardware: Ambient Lighting, Furniture, etc.
    • CORSAIR Pre-Built Systems
    • CORSAIR Technologies Q&A
  • Alternative Languages
    • Deutscher Support (German Support)
    • French Support
    • Spanish Support
  • LEGACY TOPICS
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service

Categories

  • System Build Inspiration
  • Memory
  • Cases
  • iCUE CONTROLLERS
  • Maximizing Performance
  • Peripherals
  • Storage
  • Liquid Cooling
  • Gaming Mice
  • News and Events
  • How-tos and DIY
  • USB Drives
  • Extreme OC Mods
  • Gaming Keyboards
  • Power Supply Units
  • Gaming Headsets
  • Uncategorized

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

Found 2 results

  1. I have been using iCUE for over a year and I have noticed in the past couple months that iCUE appears randomly to stop reading ALL sensor data. When I view the Dashboard, where all the system metrics displayed, everything is flatlined. This is seriously problematic because my CPU cooler fans are controlled through iCUE and when the temps rise and iCUE freezes, my fans to not accelerate as they should. I have done plenty of reading on this already and have tried several different possible solutions but have had no success in correcting this issue. Please help, I don't want my CPU to get cooked because of a software issue (if that's the case). ADDITIONAL SPECS: I have my PC specs listed on my profile, however, it does not mention that I am using the Commander Pro. I have 3 Corsair LL140 140 mm Fan and 3 Corsair RGB LED Light Strips connected to it. Also, I am using the Corsair H115i PRO as my CPU cooler. I have attached the system and info logs to this thread: icue-sensors-stop-reading.zip
  2. I hope this is the right spot in the forum. This appears to be a software issue and not an actual issue with the STRAFE RGB keyboard itself. I recently (almost 2 weeks ago) built the three systems (identical save the mice, mouse pads, monitors) for my kids and all keyboards share the same problem: the STRAFE RGB lighting effects cease to work after the computer fully boots up. Once the computer is up, I can go to Start-Settings-Apps-Apps & Features-Corsair Utility Engine and select "Modify" and then "Repair" and the keyboard will work fine until the computer is either restarted or rebooted (shutdown then start). The software for the keyboards is ver 3.5.111 and the firmware is ver 2.05. Windows 10 is running build 1803. I would not say it is a conflict with another device since all computers have the same issue. Even the computer running a generic mouse and standard mouse pad is having this issue. Other than a couple of games and virus scan (Kaspersky), they don't have any extra software installed on the systems. I've tried uninstalling/installing the keyboard and playing around with the software version it came with (2.24.50), but the same thing happens. The RGB settings fall back to the default red colored keyboard. With ver 2.24.50, when the keyboard falls back to the default red color, I loose all functionality with the CUE software. So the old software wasn't my answer. I again updated the keyboard software to ver 3.5.111 and everything works fine until I restart/reboot the computer. I can see iCUE kicking in (the selected RGB lighting scheme starts), but after 30 seconds of the desired RGB scheme initiating the keyboard goes back to its default red color. To get the lighting scheme working again I have to go to Start-Settings-Apps-Apps & Features-Corsair Utility Engine and select "Modify" and then "Repair". I even tried uninstalling the keyboard and then installing Corsair Link 4 first. I saw in a post that unsupported devices needed Corsair Link 4 installed first before moving on to iCUE 3.5.111. By itself the Link 4 software didn't solve my issue, but I thought that maybe the keyboard would work if it was treated like an unsupported device. I then upgraded to iCUE ver 3.5.111. The same RGB issued remained. I do notice a discrepancy in what appears to be some sort of version number. When I go to Start-Settings-Apps-Apps & Features-Corsair Utility Engine to "Modify" the program I noticed that it has 3.4.95 under the application name "CORSAIR iCUE Software". When I'm in the iCUE software it shows 3.5.111 as the version. I'm going to try to attach a picture showing where the 3.4.95 number is showing up. Is this difference in "versions" an issue? I'm stuck on where to go now to resolve this issue. Anyone know how to retain the RGB settings on a STRAFE RGB keyboard after a system startup/reboot?
×
×
  • Create New...