MadManOriginal wrote:The CPU- and GPU-specific temps are fine. The motherboard temps that are 120C+ seem very high, I can't recall seeing motherboard temps that high in a system I've had. However, there's no real 'standard' for motherboard temperature sensors so it's hard to say whether those are acceptable or not for your specific motherboard. Another possibility is that CPUID is misreading the motherboard sensors and not reporting accurately, try the Asus utilities to compare and see if they're similar.
What motherboard is that? Post the model and others with that board can post here, or you can search around on the web.
Also, do you have decent general case airflow? Components with passive heatsinks or no heatsinks depend on convection and general case airflow for cooling.
JohnC wrote:General rule is: any temperature is "normal" as long as your system is stable Seriously, don't pay attention to it - there may be a bug in monitoring software or the thermistor might be defective or whatever.
No, it's definitely not the software: I just ran it for the first time in weeks when I read this thread and it is reporting the aberrant temp... because the machine has been through at least one (actually several) sleep cycles. But you may not have exactly the same problem: on other systems in the past I've seen sensors go wacky for no obvious reason whatsoever; sometimes a reboot temporarily fixes them, sometimes not. Sometimes they even fix themselves, temporarily, again for no obvious reason.MadManOriginal wrote:Interesting. So a way to verify this is cold boot (shut down/restart) and check temps at idle. Then run a load for a while and check temps, they should rise under load after some time. Then Sleep/Wake and compare the behavior...if it's the bug you describe, after the sleep/wake it will be stuck at the wrong temperatures. Does restarting the monitoring software make the temperatures read correctly? Maybe it's a bug in the monitoring software.
Users browsing this forum: Alexa [Bot], Bing [Bot] and 5 guests