Reading Core Temps on Socket 939

Belisarius · 24 Sep 2007 at 13:33

Hi again,

Still been having issues with my 4200 s939 temps (core 0 idles at c.20C, core 1 at c.40C. CPU temp shoes as c.25C)

However, I found a post on another forum where someone was suggesting that the reading of individual core temps didn't work on socket 939 dual cores or possibly just 939 X2 chips? This facility was something added with AM2 (or possibly later CPU models - mine is a Toledo?).

Does anyone have a socket 939 dual core setup and are getting sensible readings for individual cores?

Has anyone heard of this being a possible issue with socket 939.

I have a RMA for my CPU but want to exhaust all possibilities before returning it.

Once again, any comments gratefully recieved.

Cheers

Andy

Defcon5 · 24 Sep 2007 at 13:44

If you pop the IHS they will probably even out. Also, if you are running a single threaded app then only one core will be loaded

Using coretemp, I have 1 core at 25 and the other at 40, thats with windows and ff running

str · 24 Sep 2007 at 13:47

Uninstall and then reinstall the AMD CPU driver and see if the problem goes away.

GeForce · 24 Sep 2007 at 16:00

Never heard of that 939 temp reading issue. Not true as far as I know.

Most people's chips give sensible readings. 4400+ X2 sitting at idle here, 27C on Core 0 and 28C on Core 1.

Reinstalling the driver is a good idea.

@Defcon: Not entirely true. If you run a single threaded app (eg. one instance of Prime95) and watch task manager, you'll probably notice both cores are at around 50%, rather than one being at 100% and the other being at 0%. Unless you specifically set core affinity. It's just the API moving the thread between cores. So it doesn't really explain the massive difference in temps.

Jon

Biffa · 24 Sep 2007 at 17:11

Urban legend TBH, never had a problem with coretemp measurments on my 4800+

str · 24 Sep 2007 at 18:05

The history of reading core temps goes back to single core AMD CPUs and the readings have always been considered accurate for them all until the AM2 Brisbane CPUs since core temps for those are wrong for example 10c readings when ambient air temp is 20c.

There can be an issue with the AMD CPU driver causing high idle temps (meaning the hight temp is real). The problem if it exists with your setup can be seen in RMClock and the fix is to uninstall and reinstall the AMD CPU driver.

Belisarius · 24 Sep 2007 at 22:29

Well, having read of a few issues with temp reading when upgrading to latest BIOS I decided to drop my BIOS version back to the first version that supported Dual Cores.

And now it won't even post. I've given up for the night and tomorrow will try ripping everything out to see what can be done.

I'm beginning to think my last attempt at getting more life out of my 939 mobo is doomed

Andy