nonamename

I'd like to see the monitoring dashboard useable as an overlay I can see while gaming. I see there's a Corsair gamebar app, perhaps adding monitoring to the game bar app?

my dashboard is also like this, completely blank but also, all my fan profiles are gone. I had to import an older profile with the profiles in it and it's back up and running now. This really sucks because if my fan profiles aren't working my system will overheat pretty quickly.

latest version fixed for me as well. I didn't need to uninstall first though, just did an upgrade.

4.18.209 seems to have fixed this for me. Oddly though, it now shows three sensors for the GPU instead of one. I'm almost certain there is only one sensor for the card though (EVGA 2080ti Black).

+1, no HXi in iCue. USB plugged directly into commander pro

thanks all. It clicked when I finally did the install and realized the fans have two cables, one for rgb and the other for fan speed.

Please add min/max to temp monitoring. It would be helpful to see those figures after running a game or doing a benchmark.

memory access violation. Check your RAM. If you have any XMP profile enabled, disable it. This isn't an exception from the iCue software, it's an exception being thrown by Windows.

commander pro lighting node core lighting node pro I'm confused why there are so many hubs. If you have commander pro, do you need lighting node core? I bought a case with the node core but I already have a commander pro... The case has the LL120 fans. Do the LL120 fans not work with commander pro? Also, is lighting node pro only for rgb strips and not fans?

see this thread: https://forum.corsair.com/v3/showthread.php?t=178964

they just need a repro so they can see the bug themselves, or they can add better logging to their service to understand where the fault is. I agree they haven't seemed to take this problem seriously enough.

for those that are experiencing this, can you add what temperature sensor you're using to drive your fans? My problem has been completely resolved by not using my video card temperature sensor anymore. I'd like to let corsair know I can reproduce this problem by switching to video card temperature sensor but I'm not going to go through creating a service ticket to let them know. If they browse this forum maybe they'll see this.

I'm not 100% sure yet, but I think I solved my issue. I was using my GTX 2080ti temperature to control fan curve and instead switched to the temp probe on the Commander Pro instead. So far, I've not had a single freeze.

that's not a fix but a work around, and not a good one, for me at least. The service will stop responding sometimes multipe times an hour, and usually when I check it after some time it's dead. I usually restart the service before starting a game, but even during gaming it will stop again!

i get the feeling it's something to do with usb as well but i'll be darned if i would now what it could be exactly. USB BIOS settings (hand-off setting), or driver used in Windows for the controller? Or could it be the fact I drive my fans off my video card temperature? Maybe they cannot reproduce the issue but it would be nice if there was some kind of debugging or something they could enable for us to do. What happens right before it fails? I have to restart the service many times and just leave iCue open so I can every once in a while open it an look at the dashboard to see if it's stopped working again. It will often stop randomly several times an hour. quickest way is open an elevated powershell prompt and type: Restart-Service CorsairService

debug means them, they have the source code. Other words, I'm confused as to why they have not done this yet to understand what's happening. At least mention it to us. Debugging is part of software development.

that's weird. This shouldn't be too tough to debug and find why it gets hung up. I wonder what the problem is.

anyone opened a case with corsair on this? I just booted my system and found icue was having this issue. Had to restart the corsair service and restart icue.

this is happening to me as well. When it does i just restart he icue service from the app and then restart icue as well.

I think I'm having the same issue. Out of blue, fans stop working according to their profile. I notice this when I start a game and expect the fans connected to commander pro to begin ramping up. Instead they don't. What I do then is check iCUE space, and I can see all graphs and stats are frozen, not moving. Then, I have to restart the iCUE service and restart the iCUE app itself, and it begins to work again.

if anyone is interested, I fixed the issue of the H80iv2 not being seen when plugged into the commander pro. The issue was the usb was plugged in incorrectly to the port. The port allows you to put the cable in incorrectly which is a first, the port itself is just too large, so you can have it on the second set of pins instead of the first, so it's not fully plugged in. This might help some others so I thought I'd post it.

might be true but people shouldn't have to go to forums to figure stuff out. A lot of people are busy and have things to do and expect the information to be there with the product so they can get it up and running and begin using it. It's not a valid excuse, at all.

That's good to know. There is so little documentation on the finer points of installing Corsair products it can lead to confusion. I wasn't even away iCue could read the motherboard sensors but was pretty glad when I saw it could. Again though they aren't needed but it sounds like you get a good benefit if you use one or more. Myself I just zip tied one to a cable in the case which left the probe right in the middle of the case in an open area and use it for all case fans that don't have a fixed rpm.

you don't even really need them. iCue software can read your motherboard temperature sensors just fine. So, set your fans to those instead. No reason to bother with the sensors from what I can realistically tell.

debug logging showed squat