phenom x2 940 quad deneb core black edition

[leezaal]

love core temp, great tool. It was working great with my dual core amd 6000+ but now shows 0 temp on my new amd quad 940 BE.
I updated my GA-M720-US3 mobo bios to latest version F6 to resolve it but it still shows 0 for temps.
it displays all for cores at correct speeds, have tried various power saving modes in win 7 but still not working.
I know the 940 has been around for a while so is there a fix to get core temp working ?

[SithBoxer]

I have this exact same cpu and this EXACT same problem. I am going to take a blind guess and say its due to AMD microcode BIOS updates because this wasnt a problem until i updated to one of the more recent bioses that have the updates. If i go back to an older BIOS the problem seems to go away but OC's arent as solid so I guess I will just do without CoreTemp for now and use Everest which sees the temp sensor perfectly.

I believe this is something that should be adressed as you now have 2 different cases with different motherboards but same CPU that have the same problem. I have a DFI DK 790FX-M2RSH and a RB-C2 revision Phenom II X4 940 with ACC enabled.

[JuoppoSepi]

I have exactly same problem. I also have Phenom II 940 BE RB-C2 processor and Dfi Lanparty DK 790FXB-M2RSH motherboard. According to cpu-z my bios version is 6.00 PG. My ACC is set to auto and I am running Windows 7 ultimate x64. Some kind of solution would be very much appreciated.

[The Coolest]

I'm aware of this problem. It seems to appear all of a sudden when you update the BIOS or change some of the BIOS settings.
This is not a Core Temp issue per-se, but the access to the hardware is blocked and Core Temp can't report the temperature.
You'll notice that it occurs in other monitoring software as well.
Some users reported that clearing the CMOS helped, some fixed it by flashing back to older BIOS versions (if the new version supported rollbacks). Either methods only helped in some cases, but not all of them.

[gegewali]

What happens if i change the ram frequency in bios? I currently have 800mhz ram and in the bios you can manually set the frequency of the ram. If i change the ram frequency setting to 1066mhz will anything happen, for example will a increase in performance happen?

[Zen Ith]

This is not a Core Temp issue per-se, but the access to the hardware is blocked and Core Temp can't report the temperature.
You'll notice that it occurs in other monitoring software as well.

This machine is an Asus M4A890GTD-PRO with Phenom XII 555 running dual boot Win 7 and Fedora 13.
lm-sensors work under Fedora and show the temperatures just fine.
But under 7 there is no reading. This must be Win 7 thing then.

[The Coolest]

The problem has to do with the ACC or different Core Unlocking features recent motherboards have.
If you have ACC or core unlocking enabled, you will lose temperature monitoring. I have no idea why exactly this happens, but its a side effect, that affects pretty much all of the processors.

[Zen Ith]

The problem has to do with the ACC or different Core Unlocking features recent motherboards have.
If you have ACC or core unlocking enabled, you will lose temperature monitoring. I have no idea why exactly this happens, but its a side effect, that affects pretty much all of the processors.

Strange indeed. With or w/o core unlocking, lm-sensors work fine. I've just removed old i845 mobo/cpu, installed AMD890 with Phenom, ran sensors-detect and they worked. Then I unlocked 2 more cores and the sensors continued working.

[The Coolest]

I'm not sure whether lm-sensors reports Core temperature the same way that Core Temp does, it may simply be reporting the temperature from the motherboard sensor.

[Zen Ith]

lm sensors source code is at http://www.lm-sensors.org/
I do believe that they report whatever sensors are available to them, including CPU, mobo or HDD.
At least they are getting the readings.

[Zen Ith]

I've checked for you. Lm-sensors uses ANY sensor available, and in the case of Phenom XII they use built in CPU sensor. So it's not hopeless and should not be BIOS/mobo dependent. I was wrong stating that you should use at lm-sensors code - try looking at linux k10sensors module - they got it.

[The Coolest]

I'll look into this some more.
It just seems that all Windows based monitoring tools are plagued with this problem.

[Zen Ith]

I'll look into this some more.
It just seems that all Windows based monitoring tools are plagued with this problem.

Sorry, I've mislead you! the k10temp driver does not work - it reports random t° (0 or 13 etc)'

The module that works is ASUS's atk0110

I had both of them registered in KSensors and confused the names when booted into Windows - sorry!

[The Coolest]

I looked at the source code of the k10temp driver, and it uses the same method I do, so there was not much chance for it to work.
No worries.

[Zen Ith]

I looked at the source code of the k10temp driver, and it uses the same method I do, so there was not much chance for it to work.
No worries.

Try atk0110, maybe that has something different.

[The Coolest]

It uses the motherboard sensors. Core Temp only uses sensors found in the processors themselves.

[andrewz]

love core temp, great tool. It was working great with my dual core amd 6000+ but now shows 0 temp on my new amd quad 940 BE.
I updated my GA-M720-US3 mobo bios to latest version F6 to resolve it but it still shows 0 for temps.

It needs special drivers )
i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70i70инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо

[The Coolest]

The cause of this problem has been found, check section #6 of the FAQ