Retail Yorkfield, load distribution issues?

[T_M]

Last night i tested Retail Yorkfield QX9650 on GA-P35-DQ6, after noticing odd behaviour on the weekend while benching under DICE.

What i had previously observed was in quad core benches my scores were lower clock for clock than other's results on hwbot (not just tweaking, a whole 150-200MHz slower). Then i found that in wPrime, one thread (3) was consistantly slower than the rest by a great deal, to the point where the end of a 1024M run should have been finished yet thread 3 was still only at 97% and still running for a good 6s+ after that.

Here's a screeny of 1024M at 3600MHz with thread 3 still running.
This screenshot is not as obvious as my DICE results which had 1,2,4 all finishing at the same time, then 3 later.


Thinking it might be a board/BIOS conflict with my X38T-DQ6, i swapped onto P35-DQ6 on air at 3600MHz.
I ran a series of checks and noticed the same behvious yet again.
Youtube videos below show good examples of what i noticed, however the compressions has made it difficult to see perfectly so i'll do my best to describe:

http://www.youtube.com/watch?v=DOeNdbM2zos
A video showing wPrime 1024M starting, then as it proceeds you can notice thread 3 slower than the rest and eventually getting overtaken in % complete by the others.
Task manager showing full 4 core loading running beside.

http://www.youtube.com/watch?v=_LGxmZ6iF9E
This is the crucial video.
SuperPI 8M started with no priority or affinity set.
Load is placed entirely 100% on core 2 (thread 3 equivalent) and remains there the entire test.
SuperPI restarted with affinity on all except core 2 (thread 3 equivalent).
Load is distributed evenly as normally experienced on other systems.

Why is all load being placed on core 2?
Why is my thread 3 lagging so much?

I discussed this observation with OPB last night on MSN, and he said he's noticed the same thing with over 20 different yorks.
He puts it down as just something we need to accept from these chips, however i dont agree.
Why didnt we see the same from ES versions of the York?

Please can some people with ES or Retail Yorks run similar checks and post results?
Im guessing that the faster times on hwbot are from ES chips that dont have this issue.

Or maybe Gigabyte's BIOS's have an issue?