I have 3 possible solutions, 1 of them worked for me (first try). We found the timer in the ECU was off in relation to the .net framework v2. The first one worked for me, and the first 2 should work for anybody with an EeePC that is still having trouble. The third is a great possible attempt.

http://support.microsoft.com/kb/895980
Add /usepmtimer option in your boot.ini as they suggest


----------------------------


http://support.microsoft.com/kb/896256



Click Start, click Run, type regedit, and then click OK.
Right-click HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager, point to New, and then click Key.
Type Throttle for the new key name.
Right-click Throttle, point to New, and then click DWORD Value.
Type PerfEnablePackageIdle for the value name.
Right-click PerfEnablePackageIdle, and then click Modify.
In the Value data box, type 0. Make sure that Hexadecimal is selected in the Edit DWORD Value dialog box, and then click OK.

Note You can type 1 in the Value data box to enable the new performance state policy behavior.
Quit Registry Editor.

-----------------

Task Manager -> process -> right click (the evoscan process) -> processor Affinity
Then try untick one of the cpus.




------------------Hamish was incredibly helpful with fixing this. Even though I bought his software, I still feel like I owe him a beer. +1 for EvoScan!

 

should be: "We found the timer in the Laptop CPU was off in relation to a windows kernel function called QueryPerformanceCounter."
This problem is not specific to evoscan, it also affects other high performance programs on your computer, i.e games. etc.

evoscan v2.6beta19: There is a new option on the logging menu called "Apply CPU Timer Fix" this will give you some information about how accurate the CPU timer is.

 

Hamish I PM'ed you about this exact issue. Laptop is an HP HDX16 running Vista64. I have tried on an XP laptop as well, same issues. How can i get it to log?