My current rig...
E6600
Big Typhoon CPU cooler
Arctic Silver 5
ASUS p5w dh deluxe
When I overclocked the CPU over 2 years ago I remember my temps being 35 - 39 degrees C. After a couple of days of burning in, the temps was always within the normal range. Since then I only monitored the temps in the BIOS every 6 months or so. The reason being is because I just assumed everything was OK as long as Windows was booting up.
Well, two weeks ago, the power went out and the motherboard reset to factory default. After a week, I decided to check the temps again. I used Realtemps and CPU-z and noticed that the temps was in the 60 - 65 degrees C range. A little concern, I decided to reboot into the BIOS and see what the BIOS said the temps were. So when I rebooted the BIOS said that the temps were in the 35 - 38 degrees C range. When Windows booted up I checked AiBooster to see what the temps were and it was what the BIOS said range.
Because of the electricity going out, is a temp sensor messed up or is this normal because the program is reading a different sensor?
E6600
Big Typhoon CPU cooler
Arctic Silver 5
ASUS p5w dh deluxe
When I overclocked the CPU over 2 years ago I remember my temps being 35 - 39 degrees C. After a couple of days of burning in, the temps was always within the normal range. Since then I only monitored the temps in the BIOS every 6 months or so. The reason being is because I just assumed everything was OK as long as Windows was booting up.
Well, two weeks ago, the power went out and the motherboard reset to factory default. After a week, I decided to check the temps again. I used Realtemps and CPU-z and noticed that the temps was in the 60 - 65 degrees C range. A little concern, I decided to reboot into the BIOS and see what the BIOS said the temps were. So when I rebooted the BIOS said that the temps were in the 35 - 38 degrees C range. When Windows booted up I checked AiBooster to see what the temps were and it was what the BIOS said range.
Because of the electricity going out, is a temp sensor messed up or is this normal because the program is reading a different sensor?