A core temp of mid 30s C is quite cool.
It probably can't be below room temp - e.g. 2x C - unless you're using a chilled cooling method.
wes and anyone
The short answer.....
- there is probably a Gigabyte supplied hardware monitoring utility that you can install in Windows, on the CD that came with the mboard, or if not, that you can download from the Gigabyte web site, perhaps in the software downloads for the model, that is probably more accurate than SpeedFan or other third party utilities.
The same applies to most if not all non brand name system mboards.
The hardware monitoring utility for a non brand name system mboard can be used for a brand name system mboard if you can dertermine who actually made the mboard - in most cases the brand name system manufacturer did not make the mboard - but the readings and the labeling may not be as accurate - go by the readings in the bios.
The mboard must have hardware monitoring capabilty built into it in order for SpeedFan or any program to be able to find something to read.
When your mboard has hardware monitoring capability, the mboard's bios probably has a place where you can examine the current temps, fan rpms, and voltage readings.
Usually the readings have been tweaked in the bios version's code to make them as accurate as possible for the mboard model.
Third party programs like SpeedFan make assumptions about what the readings from sensors should be according to the particular hardware monitoring chip, or built in hardware monitoring support the main chipset has, and where which sensor for what are supposed to be connected according to the chip manufacturer's specs.
The mboard manufacturer sometimes has not connected a sensor to an input at all, or it's connected to a different location that the chip manufacturer specified.
Some mboards have a header an optional external temp sensor can be connected to - that sensor is not connected by default. The mboard may or may not have come with that external sensor.
(E.g. I have an Epox mboard that has that and it came with the sensor.)
The bios version will not show readings for an input a sensor is not connected to, unless it has that header for an external sensor and there is no sensor connected to it, and if a sensor is not connected to an input it is supposed to be connected to according to the chip manufacturer, the bios version likely has the correct labeling for the reading.
The third party program such as SpeedFan usually lists the readings from ALL possible inputs, whether they actually have a sensor connected to them or not.
The readings from those inputs that have no sensor connected to them never change and may yield an oddball or an impossible reading.
If the mboard manufacturer connected a sensor but did not connect it to the input the hardware monitoring chip manufacturer specified, you can usually change the labeling in the third party program to correct that to jive with the labeling in the bios version .
If the temp or the voltage or the rpm for the same thing is considerably different in the mboard's bios, go by the reading in the bios, and usually you can tweak the reading in the third party program to make it the same or nearly the same.
The rpm of some fans may not be detected in the bios due to it not spinning within an expected range built into the bios code - e.g. it spins slower than the bottom of the rpm range, or it's a temp controlled variable speed fan in the PS that has external wiring to connect a plug to a mboard fan header, and it spins slower than the bottom of the rpm range when the PS is cool.
Sometimes you can tweak a setting in a third party program in Windows to get a reading from such a fan.
(The CPU fan rpm reading MUST be within the range the bios expects, otherwise the bios detects no rpm and the mboard will probably shut off automatically a short time after booting, after no more than a few minutes, often much less than that) .