Ryzen master would show 2 readings, 60 as an average of the first 3 seconds, 47 as an average of the second 3 seconds. You'd not see the others, including the spike to 70 unless running a graph. HWInfo reads every 2 seconds, so you'd see a 60, 40, 50. Let's say over a 6 second period, the cpu actually had 50-60-70-40-50-50. Ryzen master reads temps and averages every 3 seconds. Just have to understand that software is software and runs as it will, not as you expect it to.įor instance, HWInfo reads single temps periodically. ![]() Not to be confused with HWMonitor, which is a resounding : Absolutely Not. ![]() But since the only way to figure that out would be to calibrate against HWinfo's readings it kind of becomes absurd to even try.just use HWInfo. HWMonitor (and maybe Coretemp) might be good if I ever figured out which of the sensor readings meant what as they obviously aren't labeled right. That's also why it overclocks after boot-up as most processors have a 'cold bug' in that they won't boot up at an overclocked frequency (which BIOS overclocking requires) when below 0 degrees C. Ryzenmaster's true purpose is for overclockers and that's what AMD has said. ![]() Ryzenmaster reports only the average package temp, good to know the true thermal state of the processor but leaves you wondering why the fans pulse so much as it ignores instantaneous local temp when a core boosts. And temp readings include both the instantaneous CPU temp for each die (good for multi-die CPU's) as well as an 'average' temp for true thermal state of the processor. It gets frequent updates for new processors and improved readings, has a lot of sensors none others do (it even shows Ryzen sleep state for each core) as well as a very complete system information tree.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |