Ryzen temp monitor?

[punkncat]

Before you say "Ryzen Master"....

I have a "mild" OC on my Ryzen 7, done through the motherboard. 3700 @ 1.325V Been working fine for a few weeks. I got a GTX1080, put it in. Been running all of my games basically maxed out for a week. Yesterday two of my games crashed mid game. I started doing a bit of benchmarking and temperature monitoring...or at least attempting to.


HWMonitor will not read anything so far as motherboard or chip with this build, not even something wildly wrong. Numbers are static. Same issue with MBM. I remembered that Ryzen Master has a temp reading for the chip, so I installed it to use as "read only"

OK, so when I have the OC going off Mobo, my computer will dynamically change frequency and everything, just like it did "stock". I see speeds down to about 1.5-ish and all the way up to 4.3 on one core. If I am not doing anything, it will go all the way down to 1% utilization in task manager utility. The moment that I turn on Ryzen Master as "read only" one of the cores jumps to 3.7 and sits there. Utilization jumps to around 60% and sits there. My dynamic throttling (or whatever it's called) still works to some degree, but never goes below around 2.3 or so on the remaining cores.


Even more troubling....it will come on reading around 35C. Within a few moments of "Master" running, I am sitting on 50+C temps just on idle, doing nothing. Benchmark a game and it will jump to around 75C. Even when sitting on idle, the program will be reading say 50, then suddenly jump to 65, with nothing at all going on. The "back of the hand" test on the air exhaust does not seem to indicate these temps unless gaming...ie, cool to slightly warm air coming out the vent on anything but the hardest bench...then it gets towards hot.


The moment I close "Master" the proc starts throttling and the utilization goes to normal.

Short of getting an IR gun, is there any program I can use to determine real temps, or even if the temp sensor(s) are bad?


Just as background notes:

Ashes of the Singularity on "Crazy", everything on max the proc will hit just at 75 at the hardest point. The 1080 will just approach 70 with the fan curve on "user". If I turn the settings down to "Extreme" the 1080 goes down to the 40's and 50's and the CPU runs down to around 60-65.


If I completely undo the mobo OC and turn on Ryzen Master after all the loading up gets done, it will typically settle down around 35, but sits and jumps up to 50-60 with nothing going on.

 

[Darkbreeze]

HWmonitor, Open hardware monitor, Realtemp, CPU-Z and most of the bundled motherboard utilities are not terribly accurate. Some are actually grossly inaccurate, especially with some chipsets or specific sensors that for whatever reason they tend to not like or work well with. I've found HWinfo or CoreTemp to be the MOST accurate with the broadest range of chipsets and sensors. They are also almost religiously kept up to date.

CoreTemp is great for just CPU thermals including core temps or distance to TJmax on AMD platforms.

HWinfo is great for pretty much EVERYTHING, including CPU thermals, core loads, core temps, package temps, GPU sensors, HDD and SSD sensors, motherboard chipset and VRM sensor, all of it. Always select the "Sensors only" option when running HWinfo.

In cases where it is relevant and you are seeking help, then in order to help you, it's often necessary to SEE what's going on, in the event one of us can pick something out that seems out of place, or other indicators that just can't be communicated via a text only post. In these cases, posting an image of the HWinfo sensors or something else can be extremely helpful. That may not be the case in YOUR thread, but if it is then the information at the following link will show you how to do that:

*How to post images in Tom's hardware forums



Run HWinfo and look at system voltages and other sensor readings.

Monitoring temperatures, core speeds, voltages, clock ratios and other reported sensor data can often help to pick out an issue right off the bat. HWinfo is a good way to get that data and in my experience tends to be more accurate than some of the other utilities available. CPU-Z, GPU-Z and Core Temp all have their uses but HWinfo tends to have it all laid out in a more convenient fashion so you can usually see what one sensor is reporting while looking at another instead of having to flip through various tabs that have specific groupings.

After installation, run the utility and when asked, choose "sensors only". The other window options have some use but in most cases everything you need will be located in the sensors window. If you're taking screenshots to post for troubleshooting, it will most likely require taking three screenshots and scrolling down the sensors window between screenshots in order to capture them all.

It is most helpful if you can take a series of HWinfo screenshots at idle, after a cold boot to the desktop. Open HWinfo and wait for all of the Windows startup processes to complete. Usually about four or five minutes should be plenty. Take screenshots of all the HWinfo sensors.

Next, run something demanding like Prime95 version 26.6 or Heaven benchmark. Take another set of screenshots while either of those is running so we can see what the hardware is doing while under a load.

*Download HWinfo


For temperature monitoring only, I feel Core Temp is the most accurate and also offers a quick visual reference for core speed, load and CPU voltage:

*Download Core Temp

When it comes to temperature issues, especially if this is a build that has been running for a year or more, taking care of the basics first might save everybody involved a lot of time and frustration.

Check the CPU fan heatsink for dust accumulation and blow or clean out as necessary. Avoid using a vacuum if possible as vacuums are known to create static electricity that can, in some cases, zap small components.

Other areas that may benefit from a cleaning include fans, power supply internals, storage and optical drives, the motherboard surfaces and RAM. Keeping the inside of your rig clean is a high priority and should be done on a regular basis using 90 psi or lower compressed air from a compressor or compressed canned air.

Use common sense based on what PSU your compressor is set to. Don't "blast" your motherboard or hardware to pieces. Start from an adequate distance until you can judge what is enough to just get the job done. When using canned air use only short blasts moving from place to place frequently to avoid "frosting" components.

 

[punkncat]

^ Wow, thanks. Very informative as far as programs to try.

This is a new-ish build and I keep all my machines free of dust on a schedule. It was actually the first thing I considered, even though there wasn't enough on the screens or inside to hardly see...as I say new build.

I am going to try those two programs and see if I can tell what's going on. The way the game froze on one made me think video card issue. The other makes me think proc...but neither of them even with the strange numbers are showing anything that is outside a normal operating range. Heck, with the stock fan curve the GTX1080 doesn't even turn fans ON until 70.

 

[punkncat]

As predicted..sitting here doing much of nothing and I see 33C, up to 44C "surfing". Going to do a few benchmarks now...

Thanks again.

 

[punkncat]

Nice, so it appears that "Master" was showing some high numbers on me. The most I could bring with settings this time was 72, but mostly running in the 60's along with the GPU during the hard bench.

Now to see if I can duplicate the crash.

 

[Darkbreeze]

There is an option in the settings section of Core Temp to not place an icon in the taskbar I believe. Personally, unlike you are ONLY worried about CPU core temps, which is very accurate in Core Temp on nearly all chipsets, I prefer HWinfo. Be sure to use the "sensors only" option, as the rest is practically pointless and can be confusing. There is a lot more information in HWinfo than there is in Core Temp.

Also, if you get any messages saying something like there being a problem with one of the sensors and do you want to disable readings for that sensor, always choose to disable just to be safe. Not disabling a sensor that triggers warnings can result in errors so just disable to avoid that. Usually that is only on a few select motherboard sensors from older chipsets, but you never know. Worth mentioning anyhow.