Hey. Hum, well. I wouldn't try to describe it, since it's too difficult for me due to my vocabulary issues (I am from Brazil, cheers). But since you guys look to be pretty nice fellas, I'll give myself a try. So let's do it:
It's like, hum. How can I put it in words? It's not like it's lagged or anything. I am running smoothly at something like 30~35FPS and then the screen just kinda stops for a few milliseconds and then it comes back to normal 30~35FPS, which means that it's not the usual lag we commonly see when the hardware can't stand for the game resources. Also, I have tested it myself: have put my old 15" CRT monitor into use beside the laptop and extended it so I'd make two desktops for me. The first monitor was showing the game in full-screen and the second one was AMD Overdrive's CPU Status. What I noticed is that the load between the two cores was shared, but whenever those strange "stops" in the screen took place, the multipliers of each cores would change and so I presumed that it might be something related to the API management of the two CPU cores. I have also tried setting affinity of the "speed.exe" process on just one of the cores and it resolved the problem somehow. But I'm still looking for something else better than this.