BIOS temps

[blue60007]

How close are the temps reported in BIOS to temps during a real load?

Software readings are reporting temps on the high side for me - about 15C if BIOS temps are about the same as a real load temp.

Thanks

[TwoRails]

Hi blue60007. Kinda hard to check BIOS temps under load, as it's at idle when you check it. Unless it's a really hot day, my box cools down very quickly after game play, meaning, it'll cool down a lot by the time I close everything and reboot into the BIOS. Hope that's what you mean. Also, do you mean 51C? I just got playing a little and was running at 53C, but then it's 90F in the house right now, too.

TR

[blue60007]

Well, BIOS temps aren't really idle - the CPU is running at 100% - at least I think. In Windows the "System Idle Process" tells the CPU to stop when it doesn't need to run...there's nothing in BIOS (also in DOS) that tells the CPU to stop (or I don't think so). I figure a real load temp would be a bit higher cause the L2 cache and such would be getting at work out...

Software is reporting temps 15C high (probably more around 10C though)...

[TwoRails]

There is nothing for it to "run." It's waiting instruction input from something such as a program. Look at it this way: If it were doing 100%, then just letting the BIOS "run" the temps would climb to game play temps. It doesn't. That's also why BIOS temps are always a little cooler than a Windows temp reporting utility, as in Windows there is a lot of crap running: Windows itself, services, the temp program, a/v program, a firewall, etc. There shouldn't be a jump of 15C, though. I'd try a different utility and see if the readings are different.

[blue60007]

From what I understand, BIOS is much like DOS.

http://blogs.msdn.com/virtual_pc_guy...20/327602.aspx

From time to time someone notices that when they run DOS under Virtual PC it uses 100% of the host CPU to do absolutely nothing, and wonder why this is the case. The answer is relatively simple - and it is: 'DOS is never actually doing nothing'. Most modern operating systems are designed with the concept of being able to 'do nothing'. That is - if the user is not actively providing input, and no programs are demanding attention - most operating systems will tell the CPU to 'do nothing' (usually through a HLT command - or through some more advanced power state commands). DOS does not do this. So when DOS is sitting at the command prompt 'doing nothing' it is actually in a very tight loop of code which is responsible for blinking the cursor and checking for new user input. As we operate at a very low level - there is no way for us to tell if DOS is actually doing something productive with the CPU or just 'running around in circles'. To help deal with this - there is a utility called 'IDLE.COM' that is part of the Virtual Machine Additions for DOS - which is able to send 'HLT' commands when it detects that DOS is 'doing nothing'. However if you start any program (like EDIT) then your CPU usage will go up to 100% again.

Not quite the same situation, but is the general idea.

I've tried other software too - I did read reviews saying it does report the temps as hotter than they really are. Doesn't really matter though - it's stable as a rock....just pondering...

[Mr.Ferrari]

Bios temps, are your realisitic idle temps. Theres idle windows, and idle bios.

Your idle bios is usually higher with Intel's as the C1 signals are not being read/sent while your in bios.
C1 signals are linked with speedstep and intel's thermal control.
That plus a few other factors result in bios temps being higher then windows idle.

In order to get full load temps you have to download a program such as speedfan, and either play a game or run prime95. After done playing the game you can open up speedfan, move your mouse over your cpu temp, and it will tell you your full load, your minimum, and average temperatures.


But, a motherboard sensors will always be a little off from real world temperatures. Because motherboard manufacturers dont take the time to precisely tune the sensors. So we always take into acount a variation of ~10c or less.

[blue60007]

That's true too, but on my other system the BIOS temp is right between the idle temp and the load temp (a bit closer to load temp) and there isn't any speedstep on that CPU...

Yeah, I certainly agree the mobo sensors are a bit off...I'm just trying to get an idea of how much.

[TwoRails]

All programs are in an "endless loop" and that is because they are waiting input. Even this little "quick post" box is in an endless loop. That is a lot different than running full throttle. Again, look at it this way: If I boot a system to DOS, it is in an "endless loop" like any other program, and it's (the system) temps will be low, but then launch a DOS game and boy howdy, the temps go up!! even though the game is also in an endless loop, it is running at full throttle while DOS is not.