Strange temp readings after BIOS update

[AD-15]

hello,

I recently tried flashing my bios from v10 to v17 using the flashmenu utility in windows. However, once I'd flashed, I started getting issues with my BIOS, including the CMOS checksum error. I have fixed these now. However, I was still getting problems with very strange temperature readings from the BIOS. They would fluctuate a lot, and were higher than normal. About 10C higher. I used coretemp utility, and this confirmed the values the BIOS was reporting were incorrect. I tried flashing to v16 to solve this issue, this time from a floppy outside of windows, but the issue remained. I then tried reverting back to v10 BIOS, and this introduced a new issue with the temp readings. Rather than fluctuating and being very high, the reading was now stuck on 0. The BIOS sometimes reports 27C constantly as the temperature, sometimes it just says "N/A". As the CPU fan is controlled by the BIOS, the CPU RPM is stuck on a very low value.

How can I fix these problems?

[chuck4456]

hello,

hello,

I recently tried flashing my bios from v10 to v17 using the flashmenu utility in windows. However, once I'd flashed, I started getting issues with my BIOS, including the CMOS checksum error. I have fixed these now. However, I was still getting problems with very strange temperature readings from the BIOS. They would fluctuate a lot, and were higher than normal. About 10C higher. I used coretemp utility, and this confirmed the values the BIOS was reporting were incorrect. I tried flashing to v16 to solve this issue, this time from a floppy outside of windows, but the issue remained. I then tried reverting back to v10 BIOS, and this introduced a new issue with the temp readings. Rather than fluctuating and being very high, the reading was now stuck on 0. The BIOS sometimes reports 27C constantly as the temperature, sometimes it just says "N/A". As the CPU fan is controlled by the BIOS, the CPU RPM is stuck on a very low value.

How can I fix these problems?

IP35 PRO?
BIOS 11 is a good and reliable version for older Conroe chips and Q6600s.
I had funky readings with with a Q6600 and the new 17 and my fan duty cycles were stuck at 100/100%

[AD-15]

hello,

Thanks for the quick reply man. Yes, I'm using an IP-35 PRO motherboard, and the B2 revision E6600 duo CPU. Should I try flashing to v11 then?

[chuck4456]

hello,

Thanks for the quick reply man. Yes, I'm using an IP-35 PRO motherboard, and the B2 revision E6600 duo CPU. Should I try flashing to v11 then?

BIOS 11 seems to have always worked best with B2s and the other 1066 CPUs for me.

[AD-15]

hello,

Thanks for your help man.

I sent an email to Abit tech support with the same question, but haven't received an email back yet. Are there any tech support reps on this forum?

[chuck4456]

hello,

Thanks for your help man.

I sent an email to Abit tech support with the same question, but haven't received an email back yet. Are there any tech support reps on this forum?

I think ABIT_NL is one.
I'm new here.

[AD-15]

hello,

Thanks again. I'll get in touch with them ASAP.

[AD-15]

*bump*

I hope abit_nl sees it now.

[Abit_NL]

It is important to shutdown the PC after the flash and clear the CMOS (with battery or jumper) afterwards. The BIOS might miss some info or give strange values if you don't clear the CMOS afterwards. So if you didn't do that, try to flash again and try to clear the CMOS after the flash.