Now I am definitely stumped. I turned off both Point-In-Time Restore and System Protection and made sure they remained off at the time I made the test. I opened my media player (JRiver Media Center 35) and began playing an audio file at 11:59 AM. The computer clock in the system tray flipped over to 12:00 PM and it hiccuped at the usual point, 12:00:14 (give or take a second or two using a stopwatch timer). I double checked that System Restore and Point-In-Time Restore remained off by checking both again. I looked at Event Viewer and say the same two events that appear every day at noon: Event Log at 12:00:00 PM and then Ntfs (Microsoft-Windows-Ntfs) at 12:00:17 (a few seconds later than usual, that NTFS event usually happens at 12:00:13 or 12:00:14).


I'm not 100% certain but it seems highly probable that that NTFS event which gets logged in Event Viewer under Windows Logs>System every day is the thing causing the audio glitch - but turning off System Protection and Point-In-Time Restore does nothing to prevent that NTFS event from happening every day at the same time, synchronous with the audio hiccup in playback.
Could there be some other Windows process that is triggering that NTFS event daily at noon? Or is it something in the audio player JRiver MC35, perhaps that is going off at 12:00:00 noon when the program is running. I have automatic imports turned off in JRiver, so it's not that it's scanning for updates to my library. And I added a whole long list of exceptions for JRiver in Windows Security as directed at
this page.
JRiver is a very solid player in terms of performance and I very rarely hear glitches or hiccups during playback. And as a rule I close out all other apps and windows and folders and files on the PC when I'm playing music (of course there are inevitably some apps running in the background by default in Windows, so I don't know if it's one of those background apps causing this hiccup every day at the same time, though I'm still inclined to blame it on that NTFS event shown in Event Viewer logged at the exact same time the audio glitch happens).
If anyone has any further ideas for troubleshooting, I'm all ears. If I don't figure this out then I will just avoid playing audio on my computer at 12:00 noon (unless I'm willing to put up with the glitch). It's not the end of the world, but I'd still like to get to the bottom of this annoying glitch.