Real Temp - New temp program for Intel Core processors

[unclewebb]

Three cheers to some_one for coming up with the best solution for this problem.

Here's a program you can use to see if your computer has this timer issue.

WinTimerTester 1.1
http://www.mediafire.com/?xzo9n84d8lze9nb

I got my hands on an Asus board that has this problem when overclocking in Windows. The default base clock is 133.75 MHz. By using TurboV, I overclocked that up to 140.30 MHz.



You can see that by overclocking within Windows, this has screwed up the accuracy of the Windows QueryPerformanceCounter function by the same percent as I overclocked by.

140.30 / 133.750 = 1.0489

If you have this problem and you like overclocking within Windows by using SetFSB or a motherboard utility like TurboV; the best thing you can do is tell Windows to use a timer that runs at a fixed rate that doesn't have this issue.

To do that, open up a command window and type in:

bcdedit /set useplatformclock true

This tells Windows when it boots up next time to use a timer that runs at a fixed rate regardless if you're overclocking or not so it can be used for accurate timing.

Here are the results:



The QueryPerformanceCounter timer now runs at the correct speed when overclocking. You can see that QueryPerformanceFrequency is reporting a different speed which confirms that Windows is now using a different timer.

If you ever want to go back to the default Windows timer that has this timing bug then open up a command window and type in this.

bcdedit /deletevalue useplatformclock

I'll try to fix RealTemp someday so it better handles this problem but it makes more sense to fix the source of the problem which is Windows. Less work for me.

Here's some more background info which explains this bug further.

http://www-947.ibm.com/support/entry...d=MIGR-5084072

some_body says this fix is only for Windows 7 or Windows Server 2008 R2. Vista is not supported. My computer with Vista already uses the 14.31818 MHz timer by default so QueryPerformanceCounter works correctly, even when overclocking with SetFSB.