|
Post by scruffy1 on May 27, 2021 4:41:00 GMT -5
having played around with hwinfo64, hwmonitor, speccy and more, i happened upon the one in the title only a day ago
not dissimilar to all the others, but with added functionality
it will autolaunch on starting windows (like my old friend coretemp), but apart from logging the readings (and exporting them in spreadsheet format if you desire), it allows you to define what you want to keep an eye on, and draws a real time plot - which has finally confirmed that my speeds and volts ate where they seem to be - voltage spikes and 4700+ would seem to be errors rather than anything routinely visible
recommended !
|
|
|
Post by ShrimpBrime on May 27, 2021 5:36:07 GMT -5
If it was a little more accurate.
CCD 2 for example reads 204c
|
|
|
Post by scruffy1 on May 27, 2021 8:18:58 GMT -5
yeah, i figure that bit is total fabrication; but the bits i want to monitor are clearly graphed, and i like that feature
and the numbers for clock and voltage concur with hwinfo64 - if only that prog would autogenerate a graph i'd happily use it
but logging as csv makes work for me to use the data in a convenient visual format
|
|
|
Post by ShrimpBrime on May 27, 2021 17:09:11 GMT -5
yeah, i figure that bit is total fabrication; but the bits i want to monitor are clearly graphed, and i like that feature and the numbers for clock and voltage concur with hwinfo64 - if only that prog would autogenerate a graph i'd happily use it but logging as csv makes work for me to use the data in a convenient visual format None of these programs are accurate and seem to become "bugged" after extended periods of time and in particular using multiple monitoring apps (including windows task manager). But I also like it's simplicity and layout. But it seems the least reliable for AMD systems. That's not meant to offend anyone either, just seems it's difficult to trust I suppose. (from the way I look at it) Anyhow, you can collapse the readings that seem off I think. Out of site, out of mind, so they say..
|
|
|
Post by george on May 28, 2021 3:51:39 GMT -5
Speaking of monitoring, for the most time I use HWinfo64.
Now I have totally forgot about OCCT, it was popular during socket A times. Graphs are provided via it too. Seem it is still around and developed.
|
|
|
Post by freeagent on May 28, 2021 12:17:31 GMT -5
I like OCCT for checking FCLK speeds, and maybe when using Curve Optimizer too.. and maybe a quick and dirty memory test. It roots out those little interconnect errors nicely. I haven't used it for well over a decade until I got a Ryzen. I can run FCLK up to 2100, but OCCT will only pass up to 2000 for my CPU with this current AGESA update.. maybe more will open up later, who knows.. I think my limit is with AGESA though.. maybe. I do disable all of the monitoring though and just HWinfo. A mod over at TPU turned me on to it, as I was passing with high FCLK but not passing OCCT I actually thought it was a rigged program at first because they want you to sub to it.
|
|