• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

NZXT CAM and CPU usage

So I have been running into issues with 2 of my systems that I didn't realize were related until yesterday when I decided to drill down and get them fixed.

The first issue was really high idle temps on my CPU. I have an 1800x and a 2700x system, both are running custom loop cooling, and both were idling in the low to mid 40s, which is pretty high for a custom loop. They were both running about expected temps when under high load (mid 50s - low 60s).

The other issue was weird stutters every few minutes, that would get worse the longer the system had gone without rebooting. I'm not talking about uneven frame times, I'm talking about like 1/4-1/2 second pauses in games. I had originally though these were caused by pushing my memory too hard and getting errors, but resetting to standard timings/clock speed didn't fix it.

Anyhow, after taking a close look, I noticed that CAM was spiking up to 8-12% CPU usage when I was getting these stutters, so I uninstall it. Suddenly no more stutters, and my idle temps are back down where they should be at high 20s.

Just wondering if anyone else has had similar issues with CAM? Or maybe it just doesn't like something in my systems. I have a Hue+ lighting system which is why I had it installed in the first place, and it's a slick looking monitoring program so I just kept it.

My system specs for reference:

System 1
Ryzen 2700X
MSI X470 Gaming M7 AC
g.Skill TridentZ 3600 cl15 2x8gb
GTX 1080ti Founders

System 2
Ryzen 1800X
Asrock Taichi x370
g.Skill TridentZ 3600 cl15 2x8gb
MSI GTX1080
 
CAM is garbage. Use it to set the pump and fan speed (or other config) and then just close it. Also disable it from windows start up.
 
Back
Top