I'm a gamer (not hardcore) and haven't had to install nothing special. As others haven't either. Its apparently because some games use the rdtsc cycle counter and thus, when Windows switches the game from core0/core1, it gets alittle screwy because of the rdtsc value of core0 being out of sync with core1's rdtsc cycle value and vice-versa.
I made my own realtime clockspeed monitor and had the same problem. It would show the proper 2600mhz and then the next loop would show 1370 or whatever, then 5500 or something, then back to 2600mhz and what-not. Once I set the affinity of the thread to either core0/core1, then the clockspeed would be perfectly stable and the calculated rdtsc values would be the accurate, true clockspeed.
I installed the so-called DualCore optimizer and I know longer have to set the affinity of the clockspeed monitor I made to either core0/core1. I can let Windows determine the affinity back and forth and the rdtsc is in perfect sync.
So, that appears to be why some games had the timing problems on the x2's. From what I can gather anyways
Jason