I’ve been playing Overwatch just fine, but over the past few days, I’ve witnessed random, high ping spikes which really hurt my gameplay.
Here’s some output from MTR on the 1st and 2nd occurrences. I’m playing on a wired Ethernet connection (directly to my cable modem).
Please let me know if:
This seems normal
and
Why the last hop has more than 1k+ lag?
1st occurrence:
Host
%
Sent
Recv
Best
Avrg
Wrst
Last
192.168.0.1
1
1954
1950
1
7
152
1
10.122.24.137
0
1969
1969
8
17
211
18
071-044-060-015(dot)res(dot)timewarner(dot)com
0
1969
1969
9
18
194
20
bundle-ether24(dot)ORLD08-CAR1(dot)bhn(dot)net
0
1969
1969
11
23
225
21
ten0-2-0-0.orld71-car1(dot)bhn(dot)net
0
1969
1969
13
25
215
22
072-031-188-170(dot)res(dot)timewarner(dot)com
0
1969
1969
16
25
214
25
10.bu-ether15.orldfljo00w-bcr00.tbone.rr(dot)com
0
1969
1969
15
26
222
27
66.109.5.131
0
1969
1969
24
38
220
31
ae-15-312.pr0.dca10.tbone.rr(dot)com
0
1969
1969
22
36
222
24
ae1-br01-eqmi2.as57976(dot)net
0
1969
1969
59
74
240
66
xe-0-0-0-1-br01-eqat2.as57976(dot)net
0
1969
1969
59
73
273
63
et-0-0-4-br02-eqch2.as57976(dot)net
0
1969
1969
56
81
1119
74
No response from host
100
395
0
0
0
0
0
No response from host
100
395
0
0
0
0
0
No response from host
100
395
0
0
0
0
0
2nd occurrence:
Host
%
Sent
Recv
Best
Avrg
Wrst
Last
192.168.0.1
0
1581
1581
1
5
144
3
10.122.24.137
0
1581
1581
9
16
176
13
ten0-1-0-1.orld01-ser2.bhn(dot)net
0
1581
1581
9
17
180
11
bundle-ether24.ORLD08-CAR2.bhn(dot)net
0
1581
1581
11
23
174
18
ten0-2-0-0.orld71-car2.bhn(dot)net
0
1581
1581
14
22
178
20
072-031-188-176.res.timewarner(dot)com
0
1581
1581
13
23
174
18
bu-ether44.tustca4200w-bcr00.tbone.rr(dot)com
0
1581
1581
14
26
178
23
66.109.5.131
0
1581
1581
22
33
194
35
ae-15-312.pr0.dca10.tbone.rr(dot)com
0
1581
1581
20
35
224
28
ae1-br01-eqmi2.as57976(dot)net
0
1581
1581
57
70
340
70
xe-0-0-0-1-br01-eqat2.as57976(dot)net
0
1581
1581
56
70
224
64
et-0-0-4-br02-eqch2.as57976(dot)net
0
1580
1580
54
79
1570
69
No response from host
100
316
0
0
0
0
0
No response from host
100
316
0
0
0
0
0
No response from host
100
316
0
0
0
0
0
At the very least, please answer the following 3 questions (repeating myself again):
Is the above test result “normal” ???
and
Why the last hop has more than 1k+ lag, specifically the “1119” and “1570” spikes?
and
What can I do to minimize these spikes?
Edit: I am from NA, playing from Florida, USA.
Thank you in advance!
The ping to your home network isn’t normal, spiking to 152ms. This means the connection to the modem is delayed. I recommend rebooting all of your network equipment, switching cables or ports on the device, and finally calling your ISP for assistance to replace the modem.
The reason these hops on Blizzard’s network show insane worst ping values is because they are designed to ignore most ping traffic to protect against DDoS attacks. This results in an inflated ping value as it delays responses/ignores them.
Thanks for the help. I replaced my home cable modem and now the results I’m seeing in WinMTR are much better as far as the default gateway is concerned; however, I’m still experiencing some really severe Rubber Banding (in Custom Games with just 11 bots and myself) and need help rectifying this, please!
Again, I’m playing on a wired ethernet connection, and I even tried adding my computer to the “DMZ” (which still didn’t help).
My computer is directly connected to the Cable Modem (which is connected via Coax to the Wall outlet).
New WinMTR Results with the new Cable Modem:
<html><head><title>WinMTR Statistics</title></head><body bgcolor="white">
<center><h2>WinMTR statistics</h2></center>
<p align="center"> <table border="1" align="center">
<tr><td>Host</td> <td>%</td> <td>Sent</td> <td>Recv</td> <td>Best</td> <td>Avrg</td> <td>Wrst</td> <td>Last</td></tr>
<tr><td>192.168.0.1</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 0</td> <td> 0</td> <td> 1</td> <td> 0</td></tr>
<tr><td>10.122.24.137</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 7</td> <td> 8</td> <td> 14</td> <td> 9</td></tr>
<tr><td>071-044-060-015.res.timewarner(dot)com</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 7</td> <td> 10</td> <td> 16</td> <td> 10</td></tr>
<tr><td>bundle-ether24.ORLD08-CAR1.bhn(dot)net</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 10</td> <td> 16</td> <td> 29</td> <td> 14</td></tr>
<tr><td>ten0-2-0-0.orld71-car1.bhn.net</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 12</td> <td> 15</td> <td> 22</td> <td> 14</td></tr>
<tr><td>072-031-188-170.res.timewarner(dot)com</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 12</td> <td> 15</td> <td> 27</td> <td> 16</td></tr>
<tr><td>bu-ether44.tustca4200w-bcr00.tbone.rr(dot)com</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 14</td> <td> 21</td> <td> 30</td> <td> 18</td></tr>
<tr><td>66.109.5.131</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 21</td> <td> 25</td> <td> 52</td> <td> 24</td></tr>
<tr><td>ae-15-312.pr0.dca10.tbone.rr(dot)com</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 20</td> <td> 28</td> <td> 100</td> <td> 22</td></tr>
<tr><td>ae1-br01-eqmi2.as57976(dot)net</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 56</td> <td> 61</td> <td> 118</td> <td> 57</td></tr>
<tr><td>xe-0-0-0-1-br01-eqat2.as57976(dot)net</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 54</td> <td> 60</td> <td> 131</td> <td> 56</td></tr>
<tr><td>et-0-0-4-br02-eqch2.as57976(dot)net</td> <td> 0</td> <td> 130</td> <td> 130</td> <td> 58</td> <td> 94</td> <td> 928</td> <td> 63</td></tr>
<tr><td>No response from host</td> <td> 100</td> <td> 39</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td></tr>
<tr><td>No response from host</td> <td> 100</td> <td> 39</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td></tr>
<tr><td>No response from host</td> <td> 100</td> <td> 39</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td> <td> 0</td></tr>
</table></body></html>
Here's some additional results using the Battle(dot)net "Looking-Glass" 2.1.0 Tool.
"Battle.net Authentication:"
TRACEROUTE:
traceroute to 35.141.60.23 (35.141.60.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.211 ms 0.213 ms 0.214 ms
2 24.105.18.3 (24.105.18.3) 0.905 ms 0.922 ms 0.929 ms
3 137.221.105.12 (137.221.105.12) 1.099 ms 1.103 ms 1.107 ms
4 137.221.66.20 (137.221.66.20) 1.044 ms 1.056 ms 1.061 ms
5 137.221.83.84 (137.221.83.84) 6.005 ms 6.046 ms 6.050 ms
6 137.221.65.68 (137.221.65.68) 5.747 ms 5.886 ms 5.880 ms
7 137.221.68.32 (137.221.68.32) 6.151 ms 5.927 ms 6.237 ms
8 ae34.pr1.lax10.tbone.rr(dot)com (66.109.9.160) 5.419 ms 5.433 ms 5.432 ms
9 66.109.5.240 (66.109.5.240) 62.355 ms 61.939 ms 61.927 ms
10 bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com (66.109.6.1) 64.802 ms 63.443 ms 62.803 ms
11 so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com (66.109.6.91) 63.141 ms 62.640 ms 68.621 ms
12 bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com (66.109.1.71) 68.422 ms 68.488 ms 68.544 ms
13 so-0-0-2.ar1.cdp01.tbone.rr(dot)com (66.109.6.97) 63.185 ms 62.619 ms 62.573 ms
14 hun0-0-0-0.tamp20-car2.bhn(dot)net (72.31.3.96) 65.649 ms 66.891 ms 66.879 ms
15 bu-14-orld71-car2.bhn(dot)net (71.44.1.215) 69.257 ms 69.968 ms 69.964 ms
21/02/2020 17:08:02 UTC
--------------------
PING:
PING 35.141.60.23 (35.141.60.23) 56(84) bytes of data.
64 bytes from 35.141.60.23: icmp_seq=1 ttl=49 time=74.3 ms
64 bytes from 35.141.60.23: icmp_seq=2 ttl=49 time=74.6 ms
64 bytes from 35.141.60.23: icmp_seq=3 ttl=49 time=73.7 ms
64 bytes from 35.141.60.23: icmp_seq=4 ttl=49 time=74.5 ms
--- 35.141.60.23 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 73.712/74.310/74.636/0.495 ms
21/02/2020 17:08:02 UTC
--------------------
MTR:
Start: Fri Feb 21 17:08:02 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 1.9 0.5 8.8 2.7
3.|-- 137.221.105.12 0.0% 10 1.2 0.9 0.7 1.2 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 5.3 0.3 45.2 14.0
5.|-- 137.221.83.84 0.0% 10 5.9 8.4 5.8 29.9 7.5
6.|-- 137.221.65.68 0.0% 10 5.9 11.8 5.8 32.0 9.9
7.|-- 137.221.68.32 0.0% 10 6.1 7.5 5.9 20.5 4.5
8.|-- ae34.pr1.lax10.tbone.rr(dot)com 0.0% 10 7.5 6.0 5.4 7.5 0.7
9.|-- 66.109.5.240 0.0% 10 64.2 65.5 61.7 68.6 2.0
10.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com 0.0% 10 65.3 65.1 61.8 68.4 2.3
11.|-- so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com 0.0% 10 63.6 65.1 61.2 68.5 2.4
12.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com 0.0% 10 61.0 64.3 61.0 68.0 2.0
13.|-- so-0-0-2.ar1.cdp01.tbone.rr(dot)com 0.0% 10 62.7 63.4 62.2 64.1 0.3
14.|-- hun0-0-0-0.tamp20-car2.bhn(dot)net 0.0% 10 66.4 66.9 66.2 67.7 0.0
15.|-- bu-14-orld71-car2.bhn(dot)net 0.0% 10 69.1 68.9 68.1 70.1 0.3
16.|-- ten0-0-0-0.orld48-car2.bhn(dot)net 0.0% 10 72.2 69.6 66.4 73.1 2.3
17.|-- bundle-ether2.orld17-ser2.bhn(dot)net 0.0% 10 68.0 68.4 67.9 71.4 0.9
18.|-- 071-044-060-102.res.timewarner(dot)com 0.0% 10 65.7 65.5 65.3 65.8 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- 035-141-060-023.dhcp.bhn(dot)net 0.0% 10 75.1 74.6 73.9 75.3 0.0
21/02/2020 17:08:02 UTC
--------------------
"Overwatch:"
TRACEROUTE:
traceroute to 35.141.60.23 (35.141.60.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.374 ms 3.370 ms 3.376 ms
2 24.105.18.3 (24.105.18.3) 9.820 ms 9.852 ms 9.835 ms
3 137.221.105.12 (137.221.105.12) 5.264 ms 5.272 ms 5.280 ms
4 137.221.66.20 (137.221.66.20) 5.183 ms 5.217 ms 5.226 ms
5 137.221.83.84 (137.221.83.84) 9.327 ms 9.345 ms 9.353 ms
6 137.221.65.68 (137.221.65.68) 8.927 ms 6.489 ms 6.462 ms
7 137.221.68.32 (137.221.68.32) 6.437 ms 6.424 ms 6.429 ms
8 ae34.pr1.lax10.tbone.rr(dot)com (66.109.9.160) 6.988 ms 6.990 ms 6.995 ms
9 66.109.5.240 (66.109.5.240) 65.159 ms 62.961 ms 62.980 ms
10 bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com (66.109.6.1) 65.887 ms 65.894 ms 64.355 ms
11 so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com (66.109.6.91) 65.577 ms 69.407 ms 69.237 ms
12 bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com (66.109.1.71) 67.994 ms 67.648 ms 67.696 ms
13 so-0-0-2.ar1.cdp01.tbone.rr(dot)com (66.109.6.97) 63.669 ms 63.127 ms 63.113 ms
14 hun0-0-0-0.tamp20-car2.bhn(dot)net (72.31.3.96) 66.922 ms 66.238 ms 66.236 ms
15 bu-14-orld71-car2.bhn(dot)net (71.44.1.215) 69.134 ms 71.166 ms 71.101 ms
21/02/2020 17:08:50 UTC
--------------------
TRACEROUTE:
traceroute to 35.141.60.23 (35.141.60.23), 15 hops max, 60 byte packets
1 Blizzard Blizzard 5.443 ms 5.486 ms 5.530 ms
2 24.105.18.3 (24.105.18.3) 19.741 ms 19.783 ms 20.051 ms
3 137.221.105.12 (137.221.105.12) 12.034 ms 12.043 ms 12.053 ms
4 137.221.66.20 (137.221.66.20) 11.907 ms 11.928 ms 11.941 ms
5 137.221.83.84 (137.221.83.84) 12.102 ms 12.109 ms 12.117 ms
6 137.221.65.68 (137.221.65.68) 14.524 ms 7.363 ms 7.325 ms
7 137.221.68.32 (137.221.68.32) 7.804 ms 7.809 ms 7.813 ms
8 ae34.pr1.lax10.tbone.rr(dot)com (66.109.9.160) 9.069 ms 9.095 ms 9.103 ms
9 66.109.5.240 (66.109.5.240) 67.232 ms 67.238 ms 67.220 ms
10 bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com (66.109.6.1) 70.096 ms 70.427 ms 65.867 ms
11 so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com (66.109.6.91) 67.144 ms 62.487 ms 62.374 ms
12 bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com (66.109.1.71) 68.827 ms 67.639 ms 67.624 ms
13 so-0-0-2.ar1.cdp01.tbone.rr(dot)com (66.109.6.97) 63.612 ms 62.997 ms 62.984 ms
14 hun0-0-0-0.tamp20-car2.bhn(dot)net (72.31.3.96) 66.791 ms 66.212 ms 66.417 ms
15 bu-14-orld71-car2.bhn(dot)net (71.44.1.215) 69.323 ms 68.216 ms 68.215 ms
21/02/2020 17:08:50 UTC
--------------------
PING:
PING 35.141.60.23 (35.141.60.23) 56(84) bytes of data.
64 bytes from 35.141.60.23: icmp_seq=1 ttl=49 time=73.4 ms
64 bytes from 35.141.60.23: icmp_seq=2 ttl=49 time=74.5 ms
64 bytes from 35.141.60.23: icmp_seq=3 ttl=49 time=74.0 ms
64 bytes from 35.141.60.23: icmp_seq=4 ttl=49 time=73.1 ms
--- 35.141.60.23 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 73.158/73.814/74.582/0.645 ms
21/02/2020 17:08:50 UTC
--------------------
PING:
PING 35.141.60.23 (35.141.60.23) 56(84) bytes of data.
64 bytes from 35.141.60.23: icmp_seq=1 ttl=49 time=74.9 ms
64 bytes from 35.141.60.23: icmp_seq=2 ttl=49 time=73.7 ms
64 bytes from 35.141.60.23: icmp_seq=3 ttl=49 time=86.0 ms
64 bytes from 35.141.60.23: icmp_seq=4 ttl=49 time=73.3 ms
--- 35.141.60.23 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 73.387/77.041/86.063/5.253 ms
21/02/2020 17:08:50 UTC
--------------------
MTR:
Start: Fri Feb 21 17:08:50 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.3 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 1.4 0.5 4.2 1.2
3.|-- 137.221.105.12 0.0% 10 0.8 0.9 0.7 1.0 0.0
4.|-- 137.221.66.20 0.0% 10 0.5 0.5 0.3 0.8 0.0
5.|-- 137.221.83.84 0.0% 10 6.0 9.5 5.7 36.1 9.4
6.|-- 137.221.65.68 0.0% 10 5.8 17.7 5.6 105.7 31.5
7.|-- 137.221.68.32 0.0% 10 6.1 10.2 5.9 47.9 13.2
8.|-- ae34.pr1.lax10.tbone.rr(dot)com 0.0% 10 5.5 6.1 5.4 11.3 1.7
9.|-- 66.109.5.240 0.0% 10 67.9 66.0 62.7 68.7 1.6
10.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com 0.0% 10 68.6 65.1 61.6 68.6 2.3
11.|-- so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com 0.0% 10 68.0 64.5 61.0 68.0 2.2
12.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com 0.0% 10 65.4 64.6 61.2 67.9 2.1
13.|-- so-0-0-2.ar1.cdp01.tbone.rr(dot)com 0.0% 10 62.8 63.1 62.1 64.1 0.3
14.|-- hun0-0-0-0.tamp20-car2.bhn(dot)net 0.0% 10 67.0 66.8 65.7 67.7 0.7
15.|-- bu-14-orld71-car2.bhn(dot)net 0.0% 10 69.8 69.3 68.1 70.9 0.7
16.|-- ten0-0-0-0.orld48-car2.bhn(dot)net 0.0% 10 67.4 69.4 66.5 74.9 2.7
17.|-- bundle-ether2.orld17-ser2.bhn(dot)net 0.0% 10 68.0 68.0 67.9 68.3 0.0
18.|-- 071-044-060-102.res.timewarner(dot)com 0.0% 10 65.6 65.5 65.3 65.7 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- 035-141-060-023.dhcp.bhn(dot)net 0.0% 10 75.3 74.2 73.1 75.3 0.5
21/02/2020 17:08:50 UTC
--------------------
MTR:
Start: Fri Feb 21 17:08:50 2020 Blizzard
1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.4 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.6 0.6 0.8 0.0
3.|-- 137.221.105.12 0.0% 10 1.0 0.9 0.6 1.2 0.0
4.|-- 137.221.66.20 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.83.84 0.0% 10 5.7 9.9 5.7 39.6 10.5
6.|-- 137.221.65.68 0.0% 10 5.9 10.2 5.6 29.3 7.8
7.|-- 137.221.68.32 0.0% 10 5.9 6.5 5.9 11.3 1.6
8.|-- ae34.pr1.lax10.tbone.rr(dot)com 0.0% 10 5.4 7.2 5.4 17.8 3.8
9.|-- 66.109.5.240 0.0% 10 61.2 65.7 61.2 69.0 2.4
10.|-- bu-ether16.dllstx976iw-bcr00.tbone.rr(dot)com 0.0% 10 62.0 64.1 61.0 67.6 2.4
11.|-- so-1-0-0.plmnwa-rtr2.natnow.rr(dot)com 0.0% 10 61.5 64.4 61.2 68.5 2.3
12.|-- bu-ether11.tamsflde20w-bcr00.tbone.rr(dot)com 0.0% 10 66.9 64.4 61.2 67.1 2.0
13.|-- so-0-0-2.ar1.cdp01.tbone.rr(dot)com 0.0% 10 62.8 63.4 62.7 64.8 0.3
14.|-- hun0-0-0-0.tamp20-car2.bhn(dot)net 0.0% 10 66.4 66.9 65.9 67.8 0.0
15.|-- bu-14-orld71-car2.bhn(dot)net 0.0% 10 69.4 69.2 68.3 70.1 0.0
16.|-- ten0-0-0-0.orld48-car2.bhn(dot)net 0.0% 10 68.9 68.9 66.2 72.6 1.9
17.|-- bundle-ether2.orld17-ser2.bhn(dot)net 0.0% 10 67.9 68.0 67.9 68.3 0.0
18.|-- 071-044-060-102.res.timewarner(dot)com 0.0% 10 65.4 65.5 65.4 65.6 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- 035-141-060-023.dhcp.bhn(dot)net 0.0% 10 74.7 74.3 73.1 75.9 0.7
21/02/2020 17:08:50 UTC
--------------------
Is there an issue with these results? Is my connection to blame for the massive Rubber-Banding issue I’m constantly seeing, even when my computer is in the DMZ ???
I’ve tried just about everything I can imagine to fix this issue of Overwatch Rubber Banding, but nothing seems to help!!! Please help! (I also have dxdiag output I can reply with, but it might exceed the post length counter)
The WinMTR looks fine. You can go ahead with the DxDiag.
To add it to your reply here:
Open the text file and copy all of the text.
Paste the text in your reply.
Highlight the pasted text and click </> on the post editor.
If your DxDiag does not fit in one message DO NOT shorten it. Instead, post it on Pastebin.com and provide the hash code (the numbers/letters after the .com) in your reply.
It was too long, here’s the hash code. 4t8tccgK.
https:**pastebin(dot)com/4t8tccgK
My system has both an Integrated GPU and also the NVIDIA GeForce RTX 2080 (which I made sure OW is using)
Edit:
To further describe the problem I’m having, the “SIM”, “PNG”, and “RTT” values are always sky-rocketing for me. And I’m attaching some pics of this severe ping/lag issue so you can see it, in addition to my settings. Since I can’t post links, please change ** to // :
My Overwatch Settings: https**postimg.cc/wR1KpVKd
My Ping/Lag Issue (SIM spike to “292”, PNG “288”, RTT “121”, IND was only “54”) https:**postimg.cc/7fTvtmM3
Another pic just a few seconds later: https:**postimg.cc/RqhxKMWb
This is the problem in a nutshell - it usually does this intermittently (randomly) and the returns to normal - but it’s doing it so often that it makes playing OW completely unplayable.
This translates into a very laggy (slow screen updates) in games - the above pics are when I was in the “DMZ” too.
Hope this helps further describe the problem I’m having.
292 is extremely high. With your system, you shouldn’t see over 25 for SIM. Something’s happening with the hardware or the way it’s interacting with Windows.
Event Name: CLR20r3
Response: Not available
Cab Id: 0
I also noticed your GPU drivers are pretty old, from Sept 2019. I recommend getting Display Driver Uninstaller and removing all trace of them, the installing the latest.
Finally, more often than not when I see these types of huge spikes it’s because of a hardware/overheating issue. Can you run HWMonitor for a bit and take some screenshots with ALL hardware expanded? It will be several photos.
P.S. You can take the screenshots with Alt+PrtSc to just capture the main window.
So I went ahead and installed updated drivers for:
The Intel Rapid Storage Technology - version 17.5.0.1017
NVIDIA GeForce RTX 2080 - latest version from 01/28/2020
Intel UHD Graphics 630 - latest version from 02/04/2020
The link you posted from infopackets said that I could just update the driver, so that’s what I did.
Then I rebooted my PC.
After running Overwatch with these changes, it still didn’t resolve the problem, so then I tried actually Stopping the IAStorDataMgrSvc Service and also tried stopping the iaStorAfsService (from the Task Manager) and tried playing Overwatch again (rebooting here didn’t help either), but this time I made sure to gather the data you requested from the HWMonitor which are included below. I’ve also included an additional snapshot (via pastebin) showing the updated driver information.
I’m not sure how this will help diagnose or fix the problem I’m having, but
I ran User Benchmark and here are the results:
https:**www.userbenchmark_com/UserRun/24856923
(don’t forget to substitute ** and _ )
If anyone can help w/ why I’m getting immediately high SIM, RTT, and PNG spikes (from the pics I posted above already), that would be great!!!
Based on all of that information, as well as your userbenchmark, something really odd is going on here. It almost looks like your PC simply stops processing the data packets. The data appears to be getting to you correctly, but once it does it’s either getting throttled or bottlenecked somehow. If you have any software on your PC which has quality of service functions, I’d disable it. An example of this would be Killer Network Manager, if there’s a Killer network card in the PC.
Similarly, if you have any third party security programs, try temporarily uninstalling those. They may be denying access to core files and causing us to do things more slowly than we want to be doing them.
The biggest thing I’m seeing in your Userbenchmark is that most of your PC is absolutely crushing it, which is cool. What is odd is that both of your harddrives, while fast, appear to be underpeforming significantly. If what I mentioned here doesn’t help, you might poke MSI and see if they can help you optimize those. Something was causing them to slow down in the test and USUALLY asset loading isn’t going to be the cause of your issue, you’ve exhausted most of the other things we recommend for this by the time you read this paragraph. If it is actually a hardware bottleneck of some kind, it’s most likely the drive rather than any of your other hardware.
I want to give a big Thank You out to both @Nicole and @Drakuloth for your help with this issue! After working most of the weekend on trying different things out (i.e. Uninstalling IRST, re-installing Overwatch, retrying the Scan and Repair Tool, disabling my AntiMalware tools), none of which worked, I was able to get this issue resolved, but not without a clean install of my OS (Windows 10).
Thanks for reporting back. It’s a bummer it took a full reinstall of Windows 10, but at least you can play without those annoying hiccups anymore. Happy gaming!
