|
Sounds to me like, instead of using the system clock to determine when X time has passed, the coders of your driver got lazy and used execution loops. You would get the same screwball effect on games made for 386 processors, when run on pentiums, because the games didn't time their events by any accurate clock, they just added loops into the code, then adjusted those until they where the right "time".
How to fix it? Find the code that is being used to produce the heartbeat event and increase the loop delay (but be warned that you lose all benefit gained by the faster system doing this, since you can't make "shorter" event cycles that way), or... recode the damn thing to use the system clock to figure out when to generate a heartbeat, so its based on something rational, not the fiddly BS they appear to be using.
Mind you, its only a guess that this is the problem, having never looked at the code for the driver, but it seems very probable.
|