I am afraid this is not a reliable way to compute the unbiased time. Random factors may influence this and it looks challenging (even if possible) to implement a reliable bias. IMO if we have to implement that we'd be better off detecting suspend in some way and use our own current bias always, which, even if not 100% correct, would at least be consistent over time and would not introduce random time jumps. Also note that, as Rémi noted in the linked MR, that an ability to use RtlQueryUnbiasedInterruptTime() doesn't help winevulkan: it has to convert between CLOCK_MONOTONIC or CLOCK_MONOTONIC_RAW and QPC time, it is not free to choose unibiased QPC time instead, that is not what apps may expect. Unless we are known to have something depending on CLOCK_BOOTTIME now, I'd also suggest to revert MR 8916 for now and help both this aspect with now wrong unbiased time and winevulkan. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9875#note_126636