I noticed that my CPU temps seem to be sitting above 80 degC in games and I don't recall it being this high after setting up the PC. I gave my system a clean and repasted the CPU as it was a few years old but running prime 95 (all cores) still saw it climb to 90 degC rapidly before settling in at 88 degC once the fan ramped up. I only have a Ryzen 3600x (stock) and it is using the 140mm AIO included with the NZXT H1 (1st gen) so seems odd to be hitting such high temps. I would of expected closer to 60-70 degC range without the fans running at high levels. I would rather not just go for a more agressive fan curve as it is already fairly noisy but would welcome any suggestions. There is still visible dust on the radiator fins but they aren't blocked or anything like that and the radiator isn't particularly warm to the touch. Maybe an issue with liquid flow in the AIO? Any other suggestions? The fact that the temp immediately spikes (i.e a couple of seconds) makes me suspicious. However it does return to sub 40 degC after returning to idle very rapidly (again a few secs) so could just be an issue with getting heat out of the chip rapidly. Snapshot from HW Info under prime95 test, Fan 0 is the PWM fan (4 pin) on the AIO and Fan1 is the pump (3 pin): Temperature 0 89 degC (192 degF) (Package (Node 0)) Voltage 0 1.09 Volts (CPU VDD (Node 0)) Voltage 1 1.20 Volts (VID #0) Voltage 2 1.19 Volts (VID #1) Voltage 3 1.19 Volts (VID #2) Voltage 4 1.20 Volts (VID #3) Voltage 5 1.18 Volts (VID #4) Voltage 6 1.20 Volts (VID #5) Power 00 72.16 W (Package) Power 01 11.68 W (Core #0) Power 02 11.81 W (Core #1) Power 03 11.92 W (Core #2) Power 04 11.87 W (Core #3) Power 05 11.72 W (Core #4) Power 06 11.71 W (Core #5) Power 07 70.69 W (Cores) Clock Speed 0 3917.06 MHz (Core #0) Clock Speed 1 3917.06 MHz (Core #1) Clock Speed 2 3917.06 MHz (Core #2) Clock Speed 3 3917.06 MHz (Core #3) Clock Speed 4 3917.06 MHz (Core #4) Clock Speed 5 3917.06 MHz (Core #5) Hardware monitor ITE IT8686 Voltage 0 1.21 Volts [0x65] (CPU VCORE) Voltage 1 2.03 Volts [0xA9] (VIN1) Voltage 2 2.02 Volts [0xA8] (VIN2) Voltage 3 2.03 Volts [0xA9] (VIN3) Voltage 4 1.12 Volts [0x5D] (VIN4) Voltage 5 0.91 Volts [0x4C] (VIN5) Voltage 6 1.38 Volts [0x73] (VIN6) Voltage 7 1.66 Volts [0x8A] (VIN7) Temperature 0 36 degC (96 degF) [0x24] (TMPIN0) Temperature 1 40 degC (104 degF) [0x28] (TMPIN1) Temperature 2 89 degC (192 degF) [0x59] (TMPIN2) Temperature 3 16 degC (60 degF) [0x10] (TMPIN3) Temperature 4 57 degC (134 degF) [0x39] (TMPIN4) Temperature 5 49 degC (120 degF) [0x31] (TMPIN5) Fan 0 1772 RPM [0x17D] (CPU) Fan 1 4193 RPM [0xA1] (FANIN1) Fan PWM 0 0 pc [0x0] (FANPWM0) Fan PWM 1 0 pc [0x0] (FANPWM1) Fan PWM 2 0 pc [0x0] (FANPWM2)
You haven't left the poly film on the aio coldplate, have you? I've done that at least twice over the years. Either way I'd remove it, check the mounting system, repaste and refit.
Nope, cleaned off the stock aio paste (used for over a year or so) and re applied with arctic. I'll remove again and check the coverage as it's a 2 min job.
Checked the paste and it was fine and then did it again! Also flashed to the latest bios in case of some shenanigans. In short it now reaches 80c under prime 95 but I suspect that is because of reverting to a default fan curve. Other bonus is that my ram now runs in xmp mode for the first time (used to have to reduce it to 3000mhz) Edit: Just checked in a gaming session and its now back into the 50-60 range - I'll assume it was the old paste that caused a problem.
Combination of the new paste, possible mounting pressure (or last thereof before) and unrealistic real world load. Temps looks more in check now, especially under gaming. I am running the same AIO albeit in a NR200 case (PSU and AIO from the H1 fit quite nicely) on a 5900X. Things get a little toasty when multiple cores get hit all at once but I also have the fans on a minimal curve until ~85C when they ramp. Not heard it ramp thus assume CPU is staying below this level under normal gaming load. I wouldn't use this setup if I was hitting the CPU hard continuously but with my current use case this isn't an issue.
