New System gets a 1 second auido dropout ever 85-86 seconds

Help!!
 
Just built a i7-7700k with 16 Gigs ram, and SSD hard drive. My audio interface is a Focusrite Scarlette 2i2.
 
I get this weird audio dropout that occurs every 85-86 seconds and lasts for about 1 second. It doesn't matte what I am doing in Sonar. If I am tracking and the dropout occurs, the recording doesn't loose tempo, just the sound drops. If I am playing back same thing, the sound cuts out, but no tempo problems and no crashes. When I mix down, the audio drop gets printed on the exported audio.
 
How I determined the audio was dropping at precisely the same time was that I just listened to my song in sonar three times and wrote down when the audio dropped:
First time through was at 39 sec. and 125 sec.
Second time was 51 and 137.
Third time was 27 and 112.
 
So, my suspicion is... at least it seems like it to me... is that there is some program running on my system that is doing something every 85 seconds that affects Sonar.
 
Has anybody had this, or does anyone know how to fix it?
 
Thank you.
 
 

Gotta laugh as this has to be the most common thread title of all time. Even going back to W7. 
What happens is your system is just not optimized and things that were not there before now are. The new OS doesn't like your audio driver, your preferences in Sonar might be in correct etc. 
Zargg's advise is the best answer. 
And turn of the internet while trouble shooting at least. 
 

Same problem here. In my case it as due to my MIDI keyboard plugged into my interface (also a Scarlett, but it doesn't matter). The MIDI keyboard was sending a constant clock message to the Scarlett and that was causing it to glitch every 90 seconds or so. It was actually due to the USB port on my PC being on a virtual hub tied into the chipset. This was hogging bandwith along with other USB stuff on my PC.
 
If you haven't done this yet, try plugging the Scarlett into a USB port that isn't being shared with any other devices and has it's own root hub.
 
 

+1, network auto discovery is the number one latency offender. There is no reason to have your computer searching out others every 4 seconds.

LatecyMon is a great guide for you. Let that run for several minutes, then cycle through the tabs and sort each column by clicking on them to find the worst offenders. You can then Google each to find what program/process they are connected to. From there many can either be disabled or set to "manual" in system processes. Disabled makes it not run at all, manual runs things only when you click on it but won't autoload on boot.

Had that years ago when I cloned the system drive to a larger drive. Drove me crazy for a day. Some plug-in had de-authorized itself because of the drive change. No indication on the screen. At first I didn't play it long enough to hear the repetition of the dropout.