corsair h100i v2 icue custom curves error

[Archaon89]

Hello guys

i have a problem with my h100i v2 that if presented since i changed platform i switched to a 5600x on x570 aorus elite and also changing the case with a corsair i am forced to use icue to control the led.

the problem is that after a few minutes that I play the monitoring stops and consequently the profile that I have customized for the fans remains constant.

do you have any ideas?

i set the fan speed to maximum from bios on cpu fan, but nothing

 

if set on balanced instead of my curve it does not lock but always goes to the maximum

 

https://freeimage.host/i/KpqaUu

[c-attack]

You need to show us the custom curve.

[Archaon89]

here is the curve

[c-attack]

That's the problem. CUE 3.37 is the first version that is able to read the CPU temperature of the AMD 5000 series. Older ones can't detect it. I have no idea what it does with the null value it gets. If you are not on 3.37 you have no hope of getting that to work.

 

The other issue is you shouldn't use CPU temp for fan control at all with a water cooling system. That's not how it works. The CPU is cooled conductively. Heat is transferred off into the coolant stream. The liquid, radiator, and fans work to dump that heat somewhere else. Coolant temperature (H100i v2 Temp) is the baseline or lowest possible CPU temp. +1C to coolant is +1C to CPU and same in reverse for cooling. How you adjust the fans will only affect the coolant temperature. It won't do anything for the CPU or the socket pins applying electricity underneath it. Furthermore, since the fan controller was designed for a fairly slow changing variable like coolant temperature, it does not do well went trying to respond to something extraordinarily dynamic like CPU temp. Even if you are on CUE 3.37, the fans are going to jump all over the place trying to match the CPU temp. They will always be a step behind and the shifting fan speed is both ineffective and annoying. Slow and steady fans do the job.

 

Change the sensor variable back to H100i v2 Temp and then click one of the three shape tools in the upper right corner of the graph. The first one corresponds to the Quiet preset, except now you can see the data points. Feel free to move those slightly up or down to get the idle fan speed you want and to limit the load speed. You don't need to run the fans at 2000 rpm when gaming and it can't reduce coolant temp below the interior case temperature which goes up from GPU waste heat.

[Archaon89]

That's the problem. CUE 3.37 is the first version that is able to read the CPU temperature of the AMD 5000 series. Older ones can't detect it. I have no idea what it does with the null value it gets. If you are not on 3.37 you have no hope of getting that to work.

 

The other issue is you shouldn't use CPU temp for fan control at all with a water cooling system. That's not how it works. The CPU is cooled conductively. Heat is transferred off into the coolant stream. The liquid, radiator, and fans work to dump that heat somewhere else. Coolant temperature (H100i v2 Temp) is the baseline or lowest possible CPU temp. +1C to coolant is +1C to CPU and same in reverse for cooling. How you adjust the fans will only affect the coolant temperature. It won't do anything for the CPU or the socket pins applying electricity underneath it. Furthermore, since the fan controller was designed for a fairly slow changing variable like coolant temperature, it does not do well went trying to respond to something extraordinarily dynamic like CPU temp. Even if you are on CUE 3.37, the fans are going to jump all over the place trying to match the CPU temp. They will always be a step behind and the shifting fan speed is both ineffective and annoying. Slow and steady fans do the job.

 

Change the sensor variable back to H100i v2 Temp and then click one of the three shape tools in the upper right corner of the graph. The first one corresponds to the Quiet preset, except now you can see the data points. Feel free to move those slightly up or down to get the idle fan speed you want and to limit the load speed. You don't need to run the fans at 2000 rpm when gaming and it can't reduce coolant temp below the interior case temperature which goes up from GPU waste heat.

 

with my old i7 4790k it worked fine ...

I set it like this, as you advised me, I try

[c-attack]

That's fine and the exact points are not overly important for cooling performance. There is not a meaningful difference between 1100 rpm and 1200 rpm. There is a meaningful difference between 750 rpm and 1300 rpm. As long as the fans keep turning and the liquid keeps flowing, you are releasing heat from the cooling system. You should adjust them to be comfortable for noise. You have a highly power efficient CPU. It may get warm on the CPU temp, but that is not something you can change with the fans. The coolant temp change is mostly CPU power (watts) and your TDP is going to be low. If the coolant temp does not go up, then more fan speed isn't going to help.

 

If you have not downloaded the CUE 3.37 update from last week, I suggest you do. All prior versions will be unable to read the CPU temperature for AMD 5000 series CPUs. that includes the dashboard where it is informational rather for fan control.

[Archaon89]

That's fine and the exact points are not overly important for cooling performance. There is not a meaningful difference between 1100 rpm and 1200 rpm. There is a meaningful difference between 750 rpm and 1300 rpm. As long as the fans keep turning and the liquid keeps flowing, you are releasing heat from the cooling system. You should adjust them to be comfortable for noise. You have a highly power efficient CPU. It may get warm on the CPU temp, but that is not something you can change with the fans. The coolant temp change is mostly CPU power (watts) and your TDP is going to be low. If the coolant temp does not go up, then more fan speed isn't going to help.

 

If you have not downloaded the CUE 3.37 update from last week, I suggest you do. All prior versions will be unable to read the CPU temperature for AMD 5000 series CPUs. that includes the dashboard where it is informational rather for fan control.

 

still the same problem, even with those settings as per screen:(:

i downloaded the latest version 3.37

[c-attack]

The fans on the H100i v2 are at the correct speed for that 34C coolant temperature per the graph you showed me 2 posts up. What is the problem? Are you saying the CUE application is freezing and does not respond?

[Archaon89]

The fans on the H100i v2 are at the correct speed for that 34C coolant temperature per the graph you showed me 2 posts up. What is the problem? Are you saying the CUE application is freezing and does not respond?

 

the dashboard freezes after a few minutes of play

without playing it works perfectly

I attach the screen of my bios fan

[c-attack]

It seems like the App is freezing/crashing and that is an entirely different problem. If it only happens when the H100i is using custom curves, that is an interesting fact but I cannot explain why. Nothing should have changed with any of that functionality any time recently. However, I would not be surprised to see the App or monitoring crash if you were trying to read AMD 5000 CPU temp on older CUE versions that cannot.

 

1) Make sure you are not running HWiNFO, HWMonitor, AIDA, or any other full spectrum monitoring program. They get entangled with CUE trying to read the Corsair devices like the AIO.

 

2) Go to CUE settings and turn on debug logging (checkbox). That will allow you to export your CUE logs the next time it freezes up. Contact Corsair Support through the ticket system.

 

3) Does the fan lighting for whatever RGB fans are on the Lighting Node Core also freeze up when this happens? Or just CUE monitoring?

 

4) If this does only happen when on a Custom fan profile, but them on Quiet and leave it for now. There are lots of threads with monitoring or app crashes for various reasons. However, I have not seen any in a long time that relate to fan control.

[Archaon89]

It seems like the App is freezing/crashing and that is an entirely different problem. If it only happens when the H100i is using custom curves, that is an interesting fact but I cannot explain why. Nothing should have changed with any of that functionality any time recently. However, I would not be surprised to see the App or monitoring crash if you were trying to read AMD 5000 CPU temp on older CUE versions that cannot.

 

1) Make sure you are not running HWiNFO, HWMonitor, AIDA, or any other full spectrum monitoring program. They get entangled with CUE trying to read the Corsair devices like the AIO.

 

2) Go to CUE settings and turn on debug logging (checkbox). That will allow you to export your CUE logs the next time it freezes up. Contact Corsair Support through the ticket system.

 

3) Does the fan lighting for whatever RGB fans are on the Lighting Node Core also freeze up when this happens? Or just CUE monitoring?

 

4) If this does only happen when on a Custom fan profile, but them on Quiet and leave it for now. There are lots of threads with monitoring or app crashes for various reasons. However, I have not seen any in a long time that relate to fan control.

 

 

1) it's the first thing I checked, everything turned off

 

2)I'll try to do it

 

3)rgb of the fans continue to work, the led of the h100i v2 stops and does not change color

 

4)I played for 2 hours with the balanced profile and had no problems. I think it is a bug of ICUE with custom profiles

 

I hope it resolves with the next updates

[c-attack]

1

4)I played for 2 hours with the balanced profile and had no problems. I think it is a bug of ICUE with custom profiles

 

It's possible, but I don't know why they would change anything related fan control at this point. Nothing has changed with that in a long time. I guess we will see and there are a lot of users using custom fan curves.

 

One other thing you can try... do a quick repair install of CUE. Windows Apps -> Corsair iCUE -> Modify. Follow the prompts for a repair install. This will not erase or alter any of your profiles or settings. It is useful for cleaning up weird issues and only takes 60 seconds. May not work, but harmless to try.