FullSky: Thanks for confirming this. When I first observed my Q6600 suddenly reporting different values than what it's been reporting for the last 3 months I thought I was losing my marbles! My first thought was that I did something and screwed up RealTemp but then I found that every other temp program was confirming that something had changed. Hard to use RealTemp's calibration features if the center two cores swap back and forth at random.

Luckily my simple fix to test for and to correct this problem is working 100% so far during testing. CPU-Z is the only utility I've found that is correctly handling this issue and reporting the cores in their logical order with core0 and core1 being joined as well as core2 / core3. This bug also effects the SetAffinity... options within the XP Task Manager. It could be a hardware feature so when software asks to use core1 it gives them core2 instead and when software asks to use core2 it returns core1. It might be some scheme to balance the load and the temps across all 4 cores. Either that or it's Windows bug #3,435,278.

I'll probably have to include an option to disable this new feature because I'm sure there will be users that will never believe or understand it when RealTemp goes off on another tangent and starts reporting data that is different than all of the competition, again.