Update:
Messing around this afternoon I got to thinking about this screen pausing\freezing issue some more then went back thru the saved MSI AB graphs that I had captured showing these screen freezes & I finally noticed that the CPU was also showing to slow down as well as the GPU when these would occur.
So I started AHIII Dx11 but instead of going online I went offline (to eliminate the Internet\Nighthawk\Intel LAN) and flew around for a while shooting at the drones trying to push my box as hard as I could then shut down & pulled up my MSI AB graphs of my box running and quickly noticed that the GPU frametime, FPS, CPU core usage graphs were showing the game to run extraordinarily smooth & very steady......when I compared these against the graphs that I snipped after online sessions this indicated to me that my CPU was getting hammered thru the connection which would be directly related to the setup of my Intel NIC so I went into the NIC settings & started making some setting changes then would go online, run the game from the same place on the map to try to maintain some semblance of consistency.
What I've found out is that I had made some setting changes that I thought were helping my connection get better but in the process actually had increased the amount of CPU utilization by a LOT & this excessively high CPU utilization just may have been the culprit that was causing the screen freezes. I'll continue to test after this but so far so good.
The LAN settings that I made corrections to are as follows:
Jumbo Packet Size---this setting will allow a packet to become larger than the std MTU packet size in order to reduce the amount of CPU utilization IF the routing equipment along the way supports this. I had set this to the max size of 9K thinking this would help since I have this Netgear Nighthawk AC1900 ADSL modem\router running 1Gb link speed....but found that this was actually hurting my connection by excessive packet fragmentation causing the CPU to waste cycles sorting all this out. I have now disabled this setting so that the packets will return back to the set MTU size of 1.5K or 1500. This made a BIG difference.
Packet Priority & VLAN--this setting enables priority sending & receiving of certain types of packets that are tagged for priority (QoS) or are tagged for use across a VLAN. I found this setting enabled to provide both priority & VLAN tagging.....so I disabled this as I don't operate a data center network that could use this & upon testing in-game noted my CPU utilization drop some more. Made more of a difference.
Transmit & Receive Buffers--these settings set the buffer size in system mem for the NIC to use when writing packet data that is to be transmitted out across the Internet (so the NIC can continue to process outgoing packet data w\o a buffer overrun) or storing data received from the Internet to allow the NIC to continue to receive incoming packet data while processing packet data that the CPU can then fetch the stored sequential packet data from this buffer w\o overrun. Typically I have set these to the largest buffer size allowed by the NIC driver...which was 2048 for both transmit & receive buffers but I reset these back to the default size of 256 for the receive buffer & 512 for the transmit buffer which seemed to help the CPU even more but it also showed to be a little too small as I started seeing warping show up on my end so I reset these buffers as follows: transmit buffer @ 1024 & receive buffer @ 512. After doing this my connection calmed down & all was smooth & steady w\ the running CPU thread usage hardly going over 55% & the GPU frametime graph line was showing the cleanest, smoothest graph line I have witnessed to date from my Team Red box & all was just beautiful..........so far I haven't witnessed a screen freeze\pause since doing all this.
Yep, we've been here before on other occasions so I will run this for some time to see if this was really the cause of this issue on my box. Can't explain why AHIII Dx9 client would run using my Intel LAN set up the way it was prior w\o screen pauses\freezes.........
If this does pan out to be true then I will be kicking myself for not checking this out earlier...................
FYI..........................
.