Earendil3

OK, I ended up posting here and eventually received a fix for the "bricked" H115i I thought I had. Thanks Corsair! I also had trouble setting pump and fan speeds, they would never stay where I put them. After much clicking I now get it to stay constant but I still have to reset it after every reboot. I created a custom filter called "Max" under the "Performance" sub-menu, selected "Custom curve" and selected "2950X Package #1" (otherwise known as Tdie node#0, the hottest) as the temp sensor. I reboot and it went back to the "Extreme" filter so I had to select Max again and set up the "Custom curve" again. Another thing is only the three filters "Quiet", "Balanced" and "Extreme" can set pump speed. I wonder why? At least that always stays at "Extreme". So I set the "Custom curve" for max fan speed under all temps and exited iCUE. I ran HWiNFO64 all night with extensive graphing at max load (SETI on all cores). The temps are similar to when I thought the H115i was bricked and running flat out (see above). I am disappointed the CPU temps are so close to 68C. I may follow DevBiker's lead and look at the HydroX solution. Another thing was the recent announcement of the 3950X. I may just let the 2950X burn itself out and thus I have an excuse to get a 3950X which has the same amount of cores, roughly the same core speeds and uses less power. Then I'd have the same as before but the H115i could keep up hoping the CPU wouldn't get so hot. Oh well. :rolleyes:

Actually the few minutes I ran both HWiNFO64 and iCUE in the beginning I saw strange coolant temps like 0C and 100C. After that I did as you already suggested, don't run both at the same time and haven't for a while. I know my last post suggested it but I didn't. Once I set iCUE's fan and pump speeds, I exited it and ran HWiNFO64 all night since I could graph everything I wanted to see (Tdie node#0, Tdie node#1 [both from the CPU], Tcpu [from the m/b], Tcoolant [from the H115i]) over a long period of time.

Update: I took it to Corsair support and they came back with some instructions to follow: uninstall iCUE and the Corsair Utility service. I could only find evidence of the service in the Registry but I followed all the instructions. Then they gave me a link to iCUE version 3.18.77 to download and install. I restarted and re-installed like I had done many times before. Well the purging of the Registry and some files under the Windows user directory for my account seems to have done the job. iCUE identified the H115i firmware as "v.1.?" but after I did an update which took about a minute, I was updated to "v.1.01.15". A few minutes later iCUE recognized the H115i (as did HWiNFO64) and I had indication and control of the pump, fans and lighting. I guess it wasn't bricked after all, great news. Thanks Corsair. :greengrin

OK, some of the things you are mentioning are making sense since a I have had an issue with an iCUE firmware update (posted here). For a few days my H115i has run flat out (fan noise is the most noticeable thing) and my system temps have moved down a little. Tdie on CPU node #0 is most comparable to the m/b CPU temp (a sensor on the case) and it remains mostly below 65C instead of above it like before. So I take back the claim that the H115i cannot keep the 2950X cool enough. :o: Yes, I am bucking your convention of assuming Tdie node #0 & #1 and Tcpu from the m/b is not exactly Tcase but it's all I have. I have read about Tctl and I neglect it because of artificial inflation, as a test engineer I deal in data as real as possible. :nodding: Sorry, I simplified things mentioning a cooler basement but the other things you mentioned apply as well. In my situation my EATX-fitting Rise computer case has lots of room for air flow and lots of fans (three in the front [inward], two in the back including the PSU one [outward] and two in the top thanks to the H115i [outward]). The Rise sits on a porcelain tile covered cement floor thus where the "cool" comes from. Just sayin'. I read up on the PBO or more specifically PB2 on the 2950X. I restarted and enabled it in the BIOS. Besides my issue with H115i (I think it's bricked) at least it fails full on and thus provides maximum cooling. As my previous pics show I have those weird spikes on Tdie but with PBO enabled they are completely removed from the HWiNFO64 graphs. Since the BIOS was initially set to Auto I would guess PBO was starting and stopping but now it is enabled the temps are more stable - over 10 mins: Tdie node #0 67.5C (steady), Tdie node #1 ~67C (fluctuates a little) and m/b Tcpu at 67C (steady). CPU-Z says core speed is jumping around like a cat on a hot tin roof but then that sounds like PBO is working all the time so it's fine. So now it's on to customer support... :(:

I restarted the computer and didn't even start HWiNFO64, now iCUE cannot see coolant temp or fans RPM. Sigh! According to another thread here I have a bricked H115i occurring during an iCUE firmware update. Guess I'll be going to customer support. :(:

I installed the iCUE program and all seemed to work - at first. I then loaded my 2950X with SETI (i.e. makes all 32 logical cores run at 100%) and had high temps of which I posted about here. I tried to increase cooling through iCUE but it appeared to work versus some temp sensor, i.e. when set to extreme or fixed fans at 100% the fans would slow and speed up like it was temperature controlled instead of full on. In trying to get deeper into reducing the temps I discovered iCUE can check for updates. I updated iCUE within iCUE. I then updated the H115i firmware within iCUE and it got stuck. So I left iCUE and did other things on the computer when iCUE crashed to desktop an hour later. Later I restarted the computer and now my H115i is running flat out, fans on full like I wanted in the first place. Also before the firmware update I had lighting swirl, after the update and before the restart no lights at all and after the restart the lights are on, colorful but not rotating any more. So now the issues: I cannot control the fan speeds (no immediate problem for me because I wanted full on). Pump appears to be full on as well. Cannot control lighting. Not crucial but would be nice. Another attempt at updating the H115i firmware makes it get stuck again (says "Firmware v.1.01.15" with a moving, non-loading bar and threats of firmware corruption if stopped so iCUE stays on until it crashes). As expected, when updating the firmware iCUE cannot detect the H115i. No H115i data now shows up in HWiNFO64 v6.14 like it used to (just coolant temp and the two fan's RPM) before the firmware update getting stuck. Just to be clear I only cared about Tdie temps in HWiNFO64 and used iCUE for H115i for coolant temp and fan RPM. I ONCE graphed coolant temp in HWiNFO64 and did indeed saw 0C and 100C spikes which is why I reverted to iCUE only for coolant temp as it did not spike even with HWiNFO64 running.It appears the H115i has failed full on in my case which isn't a current problem but may be in the future if I wish to update, use the lights, control the fans and pump, etc. In other words get the full value for my H115i. :o:

Understand about Tctl and thus I am not looking at it nor is that the temp I am graphing. But you mention a Tcase temp and I thought that Tdie is the closest. There are m/b temps and one identified by HWiNFO64 as the "CPU temp" (not the "CPU socket temp") which is also high and comparable to Tdie temps. Maybe that is Tcase or a close analog. I have to respectfully deny that my H115i is cooling my 2950X well enough if the Tdie and CPU temps are >= 68C. Everything is stock and I am in a chilly basement at ~22C. I wish I had 50C. I Googled around and HWiNFO64 was mentioned the most as the most accurate. iCUE appears to give similar, correct temps. I tried to install Asus Armoury Crate and it wouldn't work, wouldn't update and took hours to delete - 3 hrs of my life wasted. I recently started getting ANOTHER issue (extreme and fixed profiles are now not consistant) with the H115i which I'll be starting another thread for. Sigh! :[pouts:

Understand the coolant temp is only 26C but that is not the CPU temp of which for a 2950X it has two Tdie temps (actual temperature of each die in a Threadripper) and I show them to be around 68C which is the maximum AMD recommends for a Threadripper. These Tdie temps are what I am asking about, if they are too high for a flat maxxed out H115i. Actually I mentioned the CPU load is 100% by SETI, not CPUZ. The CPUZ screen is just to show I am not overclocking. So the coolant value has steadied out as you can see the Tdie temps have been showing in the graphs for about two minutes (26C is the steady state coolant temp when I let it sit for 10s of minutes at load). The H115i's fans are already maxxed out by the display of iCUE showing the extreme profile which is maxxed out fan and pump speed (which minimizes the time to achieve a steady state coolant temp as well). I have a H100i running for 6 years (continuously due to SETI) on an 8 core AMD FX 8350 and never saw 50C deltas, more like 20C. Since I do not overclock I stay at stock for all settings, as you noted.

I think my temps are too high for my AMD Ryzen Threadripper 2950X not overclocked and running SETI on all 16 cores (i.e. CPU at 100%). I realize actual (Tdie) max temp for Ryzens is 68C. I have taken a screen shot of several programs running: CPU-Z to show CPU is not overclocked; iCUE to show that the H115i (actual AIO cooler type is in system stats) is maxxed out in fan & pump speed; HWiNFO showing both die temps (graphs showing idle temps (no SETI) and then 100% load temps (SETI on)). Of course room temp is normal, ~22C. I had a system installer do the install and except for the H115i not covering the entire Threadripper CPU case (as expected), all mounts and thermal pastes were applied correctly. Any ideas? :sigh!: PS. Corsair sells coolers but there is no entry in the system stats for a cooler description? I placed mine as the second video card so it could be seen... :bigeyes: