It uses it as part of the timer-hack detection. For all other purposes, it uses the performance counter - which is more accurate than ctime.h.
EDIT:
The Sanity Check Error is just a flag that comes out if the program thinks the clock has been tampered with. It's only purpose is in competitive benchmarking - which is irrelevant to this run.
So in the case of the overflow after 24.8 days, it wraps around - which has the same effect of setting the clock back 24.8 days (several times within a 90 day period).




Reply With Quote

Bookmarks