Cheat Engine

[Corruptor]

Well, headline sums it up pretty well i guess, is there any way to count them? (like, except for step-by-steping manually, which usually takes a lot of time)

[Dark Byte]

Breakpoints take way to long:
Bp interrupt fires, windows checks where to pass it off to. Wait till the debugger thread gets a cpu slice, handle the breakpoint, do stuff...
Mark process as executable again and wait
Then finally the process that the breakpoint happened in gets to continue

In short the breakpoint itself would most likely take up more time than the number of cpu ticks the code would have taken normally

Go with small code injections instead. Do a code injection at point 1 and a code injection at point 2

in code injection 1 do a rdtsc to store the current timestamp

in code injection 2 call rdtsc again, take the difference, and you'll have something that resembles the clock cycles between the two points

Note though that this can be variable due to task-switches occurring between the two spots

The only perfect way to count all instructions is to single step every single one of them, including kernelmode

[Corruptor]

thx, worked perfectly again