Chungerz

If you have a Google home and/or Chromecast device, it may be the cause of your wifi dropouts.
 
It seems to affect people who have android phones and google home and/or chromecast devices connected to their home wifi network.  Initial reports mentions that the router being used is the TP-Link Archer C7 router, but it has been found that other routers including Synology, Netgear, Linksys and Asus are also affected
 
"This issue stems from these devices' "Cast" feature, which sends MDNS multicast discovery packets in order to discover and keep a live connection with Google products such as Google Home. These packets normally sent in a 20-second interval. However, we have discovered that the devices will sometimes broadcast a large amount of these packets at a very high speed in a short amount of time. This occurs when the device is awakened from its "sleep" state, and could exceed more than 100,000 packets. The longer your device is in "sleep", the larger this packet burst will be. This issue may eventually cause some of router's primary features to shut down - including wireless connectivity."
 
Source: https://www.gizmodo.com.au/2018/01/your-chromecast-or-google-home-might-be-screwing-up-your-wi-fi/
Source: https://www.cnet.com/how-to/how-to-keep-google-home-chromecast-from-killing-your-wi-fi/
Source: https://9to5google.com/2018/01/15/google-chromecast-home-wifi-outage/
Source: http://www.androidpolice.com/2018/01/14/google-home-max-appears-killing-wifi-networks/
 
Google forums also point to Google devices killing home wifi :
 
https://productforums.google.com/forum/#!msg/googlehome/MmnsVnSxdQc/qBJF2KJ1AQAJ
 
The issue has been confirmed with google:
 
https://support.google.com/googlehome/answer/7634752
 
The fix appears to be an update to Google Play Services version 11.9.75 (you may have to sign up for the beta program to get this version)
 

I had a similar issue a few years back with my old machine. it turned out to be the stock CPU fan clogged with dust and dried out thermal paste.
If it is not that, i'd try replacing the power chord (i once had a dodgy power chord which gave the power supply a high pitch coil whine) before you replace the power supply. 

There have been hundreds of posts on the 970 "issue". It is old.
 
I explained this to someone earlier, the ROPS and cache weren't advertised to the public. They were sent to reviewers, and most reviews didn't mention ROPs or cache. I understand getting on the bandwagon is fun, but you are in the wrong. Misinformation and lying aren't the same thing.
 
Stop sh** talking about something that doesn't revolve around you. I didn't insult you in any way shape or form... Just know what you are talking about, and don't give misinformation like you have. You didn't listen to me about your build, but please listen to me now.

great job Brandon! really well presented and it is great to see the other members of the LMG to host/co-host from time to time.

If you got the cash, the ROG Swift is pretty amazing. I took the plunge yesterday after contemplating between the same two monitors.
from what i can see the frame rates appear to be the same, but the graphics look so much smoother. It is hard to describe, but once you experience it, you wont go back.
 
The panel is TN, so the colours are not as good, but it really isnt as bad as I thought it would be. In fact I'm very happy with the colours and viewing angles.
 
It is expensive, and i don't recommend it if you are mostly playing games like Starcraft, DoTa or League of Legends etc. but for First Person shooters, or fast paced games, you will see what the benefit G-Sync provides. It is really awesome.
 
The only feature i don't use is the 3D vision capability, so I can't give you any experience about that.