I have quite a toughie I am battling with.
We are administering a bunch of "digital signage PCs", and I have a curious problem where the clock would seem to just stop ticking.
I have RSS feeds, weather, and system time on the digital presentation. We normally notice the clock stopping on the presentation, as the complete presentation itself then stops. It does not "hang", it stops. Taking focus off of the signage player and onto the desktop, I can see that the time is at the exact time it "froze" on the signage screen, but it now starts counting again. Adjusting the time to the correct time immediately affects the slides, which start playing again in the signage presentation.
The PC itself always responds and never hangs. Focusing the desktop makes the system time start counting again, but only from where it last hung. Using "time" in
cmd reports the same time displayed by Windows
This issue happens erratically on every other PC in a group of about 15. The PCs are new, so I doubt it's the CMOS battery.
The software developer reports they don't have any such issue reported.
A few other facts:
- PC - small form factor media PC
- OS - Windows 7 Starter or Home Basic, kept up-to-date via Windows Update
- PCs are generally rebooted once a day by signage software
- PCs are on a secluded network with a 3G router serving as the WAN side. WiFi and Ethernet have been used with no discernible pattern between them.
- Power management is set to "Always On" with a batch script on PC boot (power management kept reverting to default settings on these machines - suspending the screen when idle)
- Have tried both using and not using the time server sync
- Have re-installed and updated all software and cleared all possible caches
- This issue can happen after a couple of minutes or after hours, sometimes days, of no issues
How do I finish troubleshooting this issue?