Whitedog,
Accuracy is an issue, since the temp readings that Socket A mb's give are clearly very compressed. One easy example of this is the 5C difference betwene Idle and Full Load(which, even with poor HLT hardware options, would be a muhc bigger difference on a 60W cpu).
You claim they are consistent. Go to my first link in the thread above. Both JohnCar, Laughingman, and Shoartthing have numerous experiences, and long work expertise in thermodynamics. Those guys know their stuff.
Measuring from a secondary pathway results in both inaccurate results, and number that unpredictably accurate.
If Socket A temp readings showed full cpu temp changes, I wouldn't be complaining. But they don't. Much like hte Anandtech reviews PAL6035(.38C/W) only outperforming the C-orb(.55C/W) by 2c, when actual core temp difference is really something more like 12C. It is this compression of temp changes that makes comparison's impossible to do.
Obviously you have not read any of my posts. I do not complain about Tomhardware. I made issue, and helped to bring out a lot of information that was wrong on the Anandtech Heatsink review/comparison, and using socket a platforms for comparisons in general.
Also, if you could predict how the thermistor was off and still show temp changes in core effectively, i wouldn't say anything. IN that case, a simple modification/compensation in Motherboard Monitor would be all that is necessary to fix this problem.
But the socket A temp readings are not fixed this easily. They are inaccurate, and not even "relative" due to temp reading compression, which is caused by reading temp a secondary heat pathway.
Mike