RobAP Posted November 25, 2018 Share Posted November 25, 2018 Running the H115i rgb pro. Also a set of ML140 rgb fans with the lighting node pro package. It all hooks up nicely. iCUE installs and works, and then after a day or so forgets my ******. The only cure for this is to uninstall/reinstall iCUE. There is no was to force a search for devices. My devices are attached to the USB headers on the lower of the motherboard and behind fans. Regardless of where they are plugged in, same result. Today it happened again, i uninstalled/reinstalled, and then after i came home and turned the thing on, it forget them again. PITA for sure. This is not a random issue with just me here. I wanted light, but not rainbow unicorn heaven at my desk. I don't run solid color. The funny thing, was after reinstalling, my profiles were there and i didn't have to set them up again. So I wonder just how much uninstalling the software actually accomplishes. Since this is version 3.3.xx, It is apparent that problems like this really necessitate a total rebuild of the software. Start from zero. This is windows 10, and you have one program to work with your one manufacturer set of items. This is not like you're trying to work an app through multiple skins of android or multiple manufacturers of a single item. You are the only manufacturer. This is the only program it works within. Specs. NEW BUILD. FRESH clean Windows 10 pro 64 install. r5 1500x (stop gap, waiting for the 3k series) msi b450m mortar Ti 16gb team dark pc3200 evga gtx 1070 sc 970evo m.2 all new. Link to comment Share on other sites More sharing options...
mpoffo Posted November 25, 2018 Share Posted November 25, 2018 I have noticed with the latest version it sometimes forgets my Glaive mouse. It still works though. A reboot usually resolves it. Also my keyboard (K95 Plat) sometimes takes a while to be recognized upon booting up. Both of these issues started with the last ICUE update. Link to comment Share on other sites More sharing options...
DevBiker Posted November 25, 2018 Share Posted November 25, 2018 If you are on version 3.3 ... well, that was one of the early betas of iCue. Get on the latest version. As far as necessitating a total rebuild ... if your issue was common, yes. It's not. And ... dealing with the PC ecosystem, especially hardware, is a lot more difficult that you might imagine. Link to comment Share on other sites More sharing options...
RobAP Posted November 25, 2018 Author Share Posted November 25, 2018 If you are on version 3.3 ... well, that was one of the early betas of iCue. Get on the latest version. As far as necessitating a total rebuild ... if your issue was common, yes. It's not. And ... dealing with the PC ecosystem, especially hardware, is a lot more difficult that you might imagine. I misspoke. 3.9.93 is current version displaying this exact problem. (I was typing out of frustration) I can imagine the ecosystem of hardware is a huge problem. Especially if that ecosystem was through multiple manufacturers you may try to play with. This is one company, manufacturer, software. All through one OS, Win10. The reason I suggest starting over with iCUE is because of all the issues constantly reported with it in these very forums. I should not have to uninstall and reinstall iCUE to get it to work. PERIOD. There may be issues or glitches, but this sort of work to get it to work on a fresh windows 10 install is sending up big red flags. The simple question is, WHY would there be these issues on a new fresh install of 10 on a new fresh build on a new fresh drive? Link to comment Share on other sites More sharing options...
Monster511 Posted November 25, 2018 Share Posted November 25, 2018 I posted having the same problems but only when I change the name of the CPUID files. Only my keyboard shows up. I have to change the CPUID file name or I black screen/lock up. Now I am finding I am starting to black screen/lock up even with the CPUID files name changed. This is on 3.9.93 Link to comment Share on other sites More sharing options...
DevBiker Posted November 25, 2018 Share Posted November 25, 2018 I misspoke. 3.9.93 is current version displaying this exact problem. (I was typing out of frustration) I can imagine the ecosystem of hardware is a huge problem. Especially if that ecosystem was through multiple manufacturers you may try to play with. This is one company, manufacturer, software. All through one OS, Win10. The reason I suggest starting over with iCUE is because of all the issues constantly reported with it in these very forums. I should not have to uninstall and reinstall iCUE to get it to work. PERIOD. There may be issues or glitches, but this sort of work to get it to work on a fresh windows 10 install is sending up big red flags. The simple question is, WHY would there be these issues on a new fresh install of 10 on a new fresh build on a new fresh drive? If you judge life in the US but watching the evening news, you'd think that every street was a war zone with fatality accidents and fires every other mile. Judging the overall stability by comments on the forum is the same ... people without issues just don't come here to post. And while it is one company, they have to play in an ecosystem where there are hundreds of manufacturers and variations ... for example, not all USB controllers behave the same way. Not to mention Windows will issue updates that breaks things. Why would you have these problems on a fresh install? Don't know. But so far you've seemed to want to complain - which is fine - rather than to troubleshoot any issues you may be having. Now, I can tell you from personal experience ... I have iCue and various Corsair devices running on a total of six systems in my home with no serious issues. Link to comment Share on other sites More sharing options...
RobAP Posted November 26, 2018 Author Share Posted November 26, 2018 the lets troubleshoot. after a while it will boot up and be standard slow rainbow, not seeing any devices. If I uninstall, then reinstall, no change. If I uninstall, shut down, reinstall, then it works again....until it decides to forget my devices. Another question about problems. I have experienced the 20 minuted of solid color then all dark like others on this forum have commented on. Did the newest version address that issue? Why was that even an issue? I will post again when it forgets my things and we will work from there. IS there a dump file the software generates when major changes happen, like sensing a change in componentry? Link to comment Share on other sites More sharing options...
RobAP Posted November 26, 2018 Author Share Posted November 26, 2018 ok i turned it off last night. booted up this morning, and it forgot everything. its in the system tray, running there. i right clicked it and quit. then opened up the progarm, and it worked again. I've had it revert to no recognition in the middle of the day. I've had the fan speeds ramp up to high out of nowhere in which case i just go to settings tab and click restart on the icue service note at the bottom. then things calm down to the quiet setting. i see load 53/idle 32 on quiet. Link to comment Share on other sites More sharing options...
DevBiker Posted November 26, 2018 Share Posted November 26, 2018 So ... you have a new system build. Did you install the drivers from the motherboard manufacturer or are you relying on Windows to install the drivers? Do the former, not the latter. When you say that it forgets your devices, you mean that nothing shows up in dashboard, not that any custom names are forgotten, correct? Also, it helps to turn off Windows Fast Startup (https://www.windowscentral.com/how-disable-windows-10-fast-startup) and, in some cases, Fast Boot in the BIOS. They are different things but both of them bypass some of the device initialization that happens when the machine boots. If you have an SSD as your boot drive, it's unlikely that you'll see much difference in boot times. Link to comment Share on other sites More sharing options...
RobAP Posted November 26, 2018 Author Share Posted November 26, 2018 msi drivers are used. and correct, 'no devices detected' upon boot of program, which sounds like attempted control priority over devices given its most commonly bootup issue. where those selections are available, done. Well see what happens. Link to comment Share on other sites More sharing options...
RobAP Posted November 27, 2018 Author Share Posted November 27, 2018 No joy. Booted up. no devices. Link to comment Share on other sites More sharing options...
DevBiker Posted November 27, 2018 Share Posted November 27, 2018 I'm not sure what "attempted control priority" is supposed to mean. From here - next time you boot and "no devices are detected", use USBDeView (https://www.nirsoft.net/utils/usb_devices_view.html) to see if Windows is detecting them at all. Corsair's Vendor ID (VID) is 1b1c. And you have the H115i Pro and the Lighting Node Pro only, correct? Also, while we are here, please make sure that Debug Logging is enabled - you'll find this under "Settings" on the "General" tab. Link to comment Share on other sites More sharing options...
RobAP Posted November 28, 2018 Author Share Posted November 28, 2018 okay. I will. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.