X370 Gaming X bad/null sensor?
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=5852
Printed Date: 25 Dec 2024 at 12:10am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Gaming X bad/null sensor?
Posted By: nky
Subject: X370 Gaming X bad/null sensor?
Date Posted: 15 Aug 2017 at 1:41pm
|
> Just curious what sensor is monitoring, since it seems not working and just stays there at 40C no matter what I do. > Since it's only temperature sensor, if its broken there is nothing to worry right? Since everything work fine though. https://postimg.org/image/gfoajy21f/" rel="nofollow">  hwmonitor - "TMPIN3" hwinfo64 - "CPU (PECI)" corsairlink - "TEMP#5" (user defined) Bios - none Cheers 
|
Replies:
Posted By: parsec
Date Posted: 15 Aug 2017 at 10:32pm
Not all of the sensor inputs and outputs of a sensor chip are used by every board. Monitoring programs must be coded to work with every different board, which is not always done. Also some systems don't use the same sensor outputs for their hardware. There are only a few standard sensor outputs that are common between systems. A perfect example of a system dependent sensor is the CPU (PECI) reading in HWiNFO. That is an Intel only reading, Platform Environment Control Interface, which does not apply to AMD. We then see Corsair Link and HWMonitor reading the same sensor output, that is not used on an AMD system. The CPU (PECI) reading never changes, since the input for that reading is not connected to anything. The 40C reading is just random data. The sensor is not broken, it is simply not used. It is unusual to only have one unused sensor reading, normally there are many more, particularly in HWiNFO, that is programmed better than any other monitoring program. Generic names like "Temp #1", etc, indicate very little programming done in that program, we are left to figure out what the reading belongs to. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
nky wrote: