# Possible cause of significant clock drifts

**URL:** <https://forum.inductiveautomation.com/t/possible-cause-of-significant-clock-drifts/110595>\
**Category:** General Discussion\
**Tags:** ignition80\
**Created:** [September 12, 2025, 11:00pm UTC](https://forum.inductiveautomation.com/t/possible-cause-of-significant-clock-drifts/110595 "2025-09-12T23:00:48Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 12, 2025, 11:13pm UTC](https://forum.inductiveautomation.com/t/possible-cause-of-significant-clock-drifts/110595/4 "2025-09-12T23:13:15Z")

</div>

That seems pretty fast... CMOS battery or problem with hardware RTC? Not sure...

edit: also some advice here about an alternative to W32Time, though it may not actually be your issue: [Critical ClockDriftDetector error - #5 by JordanCClark](https://forum.inductiveautomation.com/t/critical-clockdriftdetector-error/100055/5)

---

_[View the full topic](https://forum.inductiveautomation.com/t/possible-cause-of-significant-clock-drifts/110595)._