Update:
This is what I have done so far and all seems to have pretty much cleared the freezes\pauses for me at this time..................
1.) I switched browsers from IE to Mozilla Firefox then imported all my favorites over to FF then shut down IE. From doing this approx 6 days ago I haven't had a screen freeze\pause since. IMHO I think that this issue was 1 of the main contributors to my issues but time will tell....... So far, so good. What got me to go here was from watching my wife playing Pogo on her box.....finally paid attention that she's using FF to run Pogo on. Got my curiosity up so I ran a test on my box.......and the rest is history.
2.) I went into my new Netgear Nighthawk AC1900 D7000 modem\router and set my box to get the highest priority in QoS and left all else as normal. Yeah I've read the other threads discussing this and so on, but if QoS is all that is available to you you use what you got as using QoS is better than nothing at all. So far after setting all this up approx the same 6 days ago I have hardly seen any Internet-induced stuttering so until this proves otherwise this also appears to be handled. The true 1 Gigabit LAN speeds I'm getting now to my Bigfoot Killer NIC is also a factor as well as maxing out the transmit and receive buffers in the NIC to help smooth out packet flow.
Now what I'm about to post may be more cosmetic than anything else but I've also noticed when I'm running AHIII Dx11 version w\ my Crimson 16.11.2 driver set to "Enhance Application Settings" instead of "Use Application Settings" for AA then set the AA method to either "Adaptive Multisampling" or "Supersampling" the graphics look much, much better in every way. But the main thing that I've noticed w\ regards to the topic of this thread is that by using this combination this actually puts enough of an extra load on my GPU to get the GPU usage up to within the 70%-80% range where the game really does smooth out. This is also 1 of the items that--I'll say it again--I've noticed on my box running the AH Dx11 version since the Beta Patch 22 days forward across several Crimson driver versions.....on my box using the AH Dx11 version the GPU usage% load reduces a fairly large amount vs when running the AH Dx9 version using the exact same game\driver settings. Now this may not seem like much to some but the issue w\ this IMHO is centering around the AMD PowerTune 2.0 GPU control (same as GPU Boost 2.0 for Nvidia) reacting to this especially concerning the amount of power regulation supplied to the GPU due to the way PowerTune 2.0 works. For PowerTune 2.0 or Nvidia GPU Boost 2.0 to work efficiently the graphics rendering level settings as noted thru the DRIVERS, whether from the game itself or the drivers itself or any combination of the 2 are used to calculate the amount of power to apply to maintain the necessary GPU clock speed to render the work smoothly according to the actual GPU operational temps at hand....think "power per watt" here. From all my testing of these control programs (I've tested both of these extensively in times past and have the AMD engineering white papers on how PowerTune 2.0 actually works) the higher the graphics rendering level settings are PowerTune 2.0 will calculate to apply more power and allow the GPU to clock up and optimize GPU rendering performance as long as the GPU operating temps are\stay JUST below the BIOS-set GPU temp TDP threshold, but if the graphics rendering level settings are set too low, regardless of if\how far the GPU operating temps are below the TDP, both of these control programs WILL REDUCE the power output to the GPU due to the control calculating that according to the graphics rendering settings LEVELS the GPU shouldn't NEED above a certain amount of GPU power applied to do the work even though for a brief instance(s) due to various varibles the GPU may need to have more power applied to get thru it and thus may create a stutter but even potentially down to a GPU stall. Since AH Dx9 shows to put more of a graphics rendering load on my Fury X's GPU than AH Dx11 does (by approx 40%-50% more when viewed thru GPU usage % using the exact same in-game\driver graphics settings levels) that this has to be a contributor as well to the freezing\pausing going on mostly w\ AH III Dx11 version relative to the AH III Dx9 version......I believe is due to some coding difference(s) within the 2 versions of Dx that is causing the vast GPU usage % differences (GPU load vs power). This gets MUCH worse if Power Efficiency is enabled in the Crimson driver (when this is disabled it tells PowerTune 2.0 to allow the GPU clocks to go full instead of controlling them but I don't think this also disables the PowerTune 2.0 GPU power calcs....I think the same may prove out for Nvidia's GPU Boost 2.0 when you set the driver to prefer maximum performance vs adaptive but can't be for sure w\o actually testing it now vs when I did prove this some 1 1\2-2 yrs back when I ran a test between a GTX 780Ti vs a Radeon R9 290X on my prior X79 box). This could also very well be due to Dx11's Shader Model 5.x being more efficient vs Dx9's Shader Model 3.x performing the post-processing rendering work in AHIII which offloads the GPU much more (not to mention that these more modern graphics cards of either stripe are designed\tuned at the GPU\driver level to get more efficiency out of Dx11 than Dx9 since the vast majority of games out for some time have been written to use\optimize Dx11 and AH has now recently incorporated Dx11).
Could be as easy as doing some in-game post processing graphics rendering output level tuning (we don't have access to do this....only HTC does) to fix all this for the Dx11 version of the game...........which may call for the game to be physically separated into 2 fully separate AH III game versions..........
Just a thought......................
Anyway, hope this helps.
