H310M/M.2 Bios Reporting Incorrect CPU Temperature
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=11036
Printed Date: 05 Aug 2025 at 1:25pm Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: H310M/M.2 Bios Reporting Incorrect CPU Temperature
Posted By: fishdom49
Subject: H310M/M.2 Bios Reporting Incorrect CPU Temperature
Date Posted: 07 Mar 2019 at 6:25am
Hi all,
I just installed an AsRock H310m/M.2 motherboard and an Intel I3-8100 CPU with a stock cooler. The idle temps reported from the bios are significantly higher than temperatures reported by other third 3rd party apps.
Bios - 39.5C Speccy - 28C CPUID - 27C to 29C
I have a feeling the bios temperature is being incorrectly reported. You feedback will be greatly appreciated.
Thanks!
|
Replies:
Posted By: Xaltar
Date Posted: 07 Mar 2019 at 3:54pm
The BIOS does not report idle temps, the CPU is under load while in the UEFI. It is a common misconception that UEFI temp readings are idle temps, this may have been closer to the truth with the BIOS systems of the past but UEFI is a different animal. Even in old BIOS based systems the reading was not a true idle temp but the load the BIOS placed on the CPU was minuscule compared to modern UEFI.
I hope this clears things up for you
-------------
|
Posted By: fishdom49
Date Posted: 07 Mar 2019 at 11:59pm
Xaltar wrote:
The BIOS does not report idle temps, the CPU is under load while in the UEFI. It is a common misconception that UEFI temp readings are idle temps, this may have been closer to the truth with the BIOS systems of the past but UEFI is a different animal. Even in old BIOS based systems the reading was not a true idle temp but the load the BIOS placed on the CPU was minuscule compared to modern UEFI.
I hope this clears things up for you  |
Hi Xaltar,
Thank you for you response. It did shed some light on the fact that I was using the term "idle" incorrectly; however, I am still not convinced that your explanation may be 100% accurate in my case for the following reasons:
If what you say is true, then accessing the BIOS must be placing a tremendous load on the CPU. And, this load must be equal to/greater than anything I have encountered while using the PC routinely because I have never had any temperature rise (verified by speccy64,hwmonitor64, and siv64x), that is close to the one that is shown when viewing the BIOS.
In summary, if accessing the BIOS does place a tremendous load on the CPU, then you hit the nail on the head; however, right now I am going to assume my 3rd party recorded temps are accurate and I have no thermal worries at this point.
Thanks again!
fishdom49
|
Posted By: Xaltar
Date Posted: 08 Mar 2019 at 12:32am
The UEFI is not an operating system, the operating system is optimized and refined to utilize the system's resources in an efficient manner. The size restriction of a ROM chip prevents such optimizations. In the UEFI so there is no multi-threading or code optimization beyond the most basic. This means that everything it does is performed on a single core and all it's functions are permanently active, there is no "idle" code that turns off a process when it isn't in use. Consider the amount of functions in the UEFI and how it needs to access the system. I would be surprised if the core it uses is ever under 90% utilized.
It's a fascinating topic, sadly that is as far as my own investigation into the matter went. Much like yourself, when I was first exposed to the UEFI I had the same question about temps. It took a lot of digging to uncover the why and how. I hope that answers your question. It's always nice to see another inquisitive mind that wants more than "that's just how it works" 
-------------
|
Posted By: fishdom49
Date Posted: 08 Mar 2019 at 8:08am
Xaltar wrote:
The UEFI is not an operating system, the operating system is optimized and refined to utilize the system's resources in an efficient manner. The size restriction of a ROM chip prevents such optimizations. In the UEFI so there is no multi-threading or code optimization beyond the most basic. This means that everything it does is performed on a single core and all it's functions are permanently active, there is no "idle" code that turns off a process when it isn't in use. Consider the amount of functions in the UEFI and how it needs to access the system. I would be surprised if the core it uses is ever under 90% utilized.
It's a fascinating topic, sadly that is as far as my own investigation into the matter went. Much like yourself, when I was first exposed to the UEFI I had the same question about temps. It took a lot of digging to uncover the why and how. I hope that answers your question. It's always nice to see another inquisitive mind that wants more than "that's just how it works"  |
Hi again Xaltar,
I think you hit a home run with your latest explanation so thanks a bunch!
Regards,
fishdom49
|
|