I realize this is an ancient thread but there is finally a solution for this common SetFSB problem.Using SetFSB can screw up the internal timing mechanism in Windows 7 which can screw up a lot of games and benchmark programs that don't adjust for this. Most desktop computers have overclocking options in the bios so you can avoid this issue but on many laptops, SetFSB is the only overclocking option.If you use SetFSB and are running Windows 7 then there is a way to test for this problem.WinTimerTester 1.1http://www.mediafire.com/?xzo9n84d8lze9nbhttp://www.sendspace.com/file/xadvheThis program compares two timers within your computer and in theory they should be running at a perfect 1.0000:1 ratio, usually within 60 to 100 seconds.If they are not running in sync then you need to correct the accuracy of the Windows QueryPerformanceCounter function that many applications depend on for accurate time measurement. To do this you have to tell Windows to measure time using an internal clock that runs at a fixed rate of speed and is not influenced by SetFSB. Open up a command line window and type in this.(ctrl-shift-enter)bcdedit /set useplatformclock trueIf you ever want to restore Windows to use the default timer then you can open a command window and type in this.bcdedit /deletevalue useplatformclockHave a look at the first post in this NBR forum for examples and some more details.http://forum.notebookreview.com/asus...lem-g60jx.html If you've ever played some games after using SetFSB and they run at variable rates of speed or the sound is corrupted then this should correct that problem.