- Joined
- May 3, 2014
- Messages
- 519 (0.13/day)
- Location
- UK
| System Name | Daedalus |
|---|---|
| Processor | AMD FX 6300 |
| Motherboard | ASUS M5A97 EVO R2.0 |
| Cooling | Coolermaster Hyper 212 EVO |
| Memory | 8GB Kingston HyperX Genesis (2x4GB) |
| Video Card(s) | MSI R9 270X Gaming 2GB |
| Storage | 1TB Seagate Barracuda |
| Display(s) | LG Flatron E2442 (main - 24in 1080p) |
| Case | NZXT Phantom 410 (Gunmetal Edition) |
| Power Supply | XFX Pro 650W |
| Mouse | Steelseries Siberia [RAW] |
Hello all,
So I decided to take the recently released NZXT CAM software for a spin. Here are some of my initial thoughts.
Layton
So I decided to take the recently released NZXT CAM software for a spin. Here are some of my initial thoughts.
- It can be a resource hog sometimes. General navigation of the application would result in ~10% CPU usage, which is pretty high for a program designed to be used in the background. But then it is monitoring quite a lot of data and then outputting it into graphs.
- There are some problems with the sensors. Immediately upon opening the application I was issued a warning that my motherboard had exceed 128 degrees C. I would know if my motherboard had that high temperatures, so either bad software reading or a dodgy sensor.
- I also think the software is reading my CPU socket temperature rather than the actual CPU temperature sensor for the CPU reading. I might be wrong, but I was under the impression that my AMD FX would be much hotter under load, not ~25 degrees C.
- One thing I do like though about the software is the realtime graphs. They're probably why the software is such a resource hog, but what looks amazing is that the monitoring data from your system is recorded and kept for a number of years. Could be useful for diagnosing problems. But then there's the issue that your data is recorded, and could be accessed by other people.
Layton