Windows 10 clock issue.
Windows 10 clock issue.
Hello all, Here's my system, for future reference: R5 3600, Asrock x570 Phantom Gaming ITX-TB3, MSI Ventus RTX 2060 Super, 16(2x8)gb Gskill Ripjaws 5 3600mhz, Crucial 512gb NVME, Samsung 850 Evo 1tb, WD Blue 4tb, Ncase M1, Silverstone 700W SFX PSU. My current issue is that windows time and date service isn't keeping, well up to date. I've already looked around online and have tried restarting the windows time service in services.msc, as well as changing the time server. Every time I turn off my pc, and start it back up again, the time doesn't update the the current time, even after waiting a few minutes and doing some work. If I turn my PC off at 11pm the night before, it will resume from 11pm the next day and continue on without realizing its mistake and changing the time. The only to solve this problem is manually press the sync now button. I've also run the sfc/scannow to see if there were any issues, none to be found. I have no pending windows updates. My last resort is the CMOS battery, though I doubt that is the issue. I run an undervolt on my ryzen system, as well as an xmp profile, and it hasn't been resetting regularly, so I don't believe that's it. Plus, I'm really not into putting the effort into dismantling the system at the moment just to get to CMOS. If it comes to that, I will. I'd appreciate all your help. If you think that this doesn't belong in this section of the forum, let me know. Thanks!
Your device isn't keeping track of time while it's off or asleep because the tiny battery is gone.
Unfortunately, the system isn't functioning as expected. Verify your BIOS settings to ensure the displayed time aligns with real-time. If accurate, attempt these steps: Launch Windows, navigate to Settings > Time & Language > Date & Time (press Win+R, type ms-settings:dateandtime). Note the reported time. Power off your machine for 15 minutes, then restart and compare the discrepancy. This suggests a potential Windows-specific problem rather than a BIOS issue. If the difference is significant, a full reinstall might be necessary. Given the unclear nature of the problem, troubleshooting could be unproductive. For confirmation, consider using a Ubuntu Live environment to isolate the source.
It's interesting I saw the same problem yesterday... I suspect the Windows time servers might be faulty. I clicked on time to reconnect and it refreshed the clock, but before that, the time was off by several minutes—probably because it hadn't synced recently.