Thread: Athlon X2 5000 BE wrong temperature readings

I bought me a new rig a month ago, check sig, and I am wondering how come the temperature of the CPU's cores is about 15-20C lower than actual?
I read on the net that this is a bug of all BRISBANE cores but still how come AMD hasn't fixed this yet?

CPUZ info||||||||||||||HWMONITOR:


And also on the Core Temp forums they say that AMD has acknowledged that the bug exists in their Brisbane cores that the Cores DTS puts out wrong temperature readings and thus any program, Core Temp, HWMonitor, that reads the DTS directly is showing the wrong numbers.
http://alcpu.com/forums/viewtopic.php?t=374

Originally Posted by ashrack

I read on the net that this is a bug of all BRISBANE cores but still how come AMD hasn't fixed this yet?

have you tried to email them?

They said its "relative" to some number. A NORMAL temperature sensor would give the temperature relative to ... oh I dont know... 0* perhaps? Amd though they could do better and made it relative to a random number perhaps?

yes they are all off. i like coretemp

ZL1Killa
They are all off including Core Temp since all of those are reading from DTS which is somehow screwed in the Brisbane cores

Yea its best to use the motherboard sensors with these chips, I'm not sure why AMD hasn't fixed this yet, my guess is that they don't really care about it.

Heh, coretemp isn't even all that great with my 5000BE. Usually reads -4 to 0c idle.. and 6-11c loaded. Everest shows the mb cpu temp in the 40's while loaded. Its running at 3.2, 1.35v. I had figured it was just me.. that I had gotten some copper residue in the pins during lapping that didn't clean out all the way. This is making me rethink that a bit.
I've been hesitant to push the OC any more without a reliable frame of reference for the temps. And AMD overdrive claiming it can't find the 7x0 chipset =P hasn't helped either.

Hymay
U need latest overdrive I believe it's 0.14 beta which usually works. Or in my case, MSI K9a2, I had to use the OVERDRIVE from the MSI site to support my chipset and temperatures correctly.

I find this a really bad thing for AMD. They designed the 7xx chipsets and now their own OverDrive doesn't even support them fully.

And about the temperatures do not worry. The motherboard sensor is usually ~5C lower than the CPU DIE temperature.
Its the same as I had to do with SOCKET A which usually had only the motherboard sensor and not the true CPU one.

Agreed, it is pretty disheartening.
And 2.0.14.beta.msi is what I had installed.. It gives me no love at all. Says it cannot find the r700 chipset. The mobo I am using is Asus m3a.. perhaps I need a different copy.

CoreTemps being worked on again so hopefully that will be more accurate. The latest BETA won't open in Vista 64 though...

shaz

I already stated in OP that it is not CORE TEMPs fault. Core Temp just reads DTS which is on the CPU. But since the BRISBANE's CPUs output the wrong temperature monitor there is nothing Core Temp can do about it.
Here's a reference link:
http://alcpu.com/forums/viewtopic.php?t=374

here is a similar disscusion @AMD:
http://forums.amd.com/forum/messagev...threadid=92860