Random freezing issue/WinMTR reports

Explodinator-argent-dawn · December 2, 2020, 6:40pm

Hello,
Per another thread requesting output from WinMTR due to freezing issues, I am posting here. If it matters, I am hardwired and on a GB internet service.
~~|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| G3100.myfiosgateway.com - 0 | 919 | 919 | 0 | 0 | 16 | 0 |

| 24.105.62.129 - 0 | 919 | 919 | 1 | 4 | 375 | 1 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~
~~|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| G3100.myfiosgateway.com - 0 | 1629 | 1629 | 0 | 7 | 17 | 0 |

| 137.221.105.2 - 0 | 1629 | 1629 | 1 | 9 | 86 | 18 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider~~

Please let me know if you have questions.
Thanks for your help to resolve this.

Elocin-mugthol · December 2, 2020, 8:21pm

Unfortunately, FiOS services block the ability to use a WinMTR diagnostic because the app only supports IPv4.

You could try the Blizzard Looking Glass instead.

Explodinator-argent-dawn · December 2, 2020, 8:25pm

Thanks for the info and the additional link. Does this help?

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.480 ms 1.467 ms 1.974 ms
2 24.105.18.2 (24.105.18.2) 3.246 ms 3.247 ms 3.248 ms
3 137.221.105.14 (137.221.105.14) 2.042 ms 2.088 ms 2.091 ms
4 137.221.66.22 (137.221.66.22) 1.993 ms 2.008 ms 2.056 ms
5 137.221.83.86 (137.221.83.86) 544.196 ms 544.205 ms 762.247 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.103 ms 6.075 ms 6.077 ms
8 las-b21-link.telia.net (62.115.178.200) 5.870 ms 5.915 ms 5.920 ms
9 157.130.245.25 (157.130.245.25) 5.651 ms 5.621 ms 5.581 ms
10 ae199-21.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.95) 63.886 ms 63.862 ms 63.961 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 64.068 ms 64.079 ms 64.402 ms

02/12/2020 20:23:28 UTC

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.219 ms 0.229 ms 0.239 ms
2 24.105.18.2 (24.105.18.2) 0.549 ms 0.882 ms 0.898 ms
3 137.221.105.14 (137.221.105.14) 0.857 ms 0.885 ms 0.894 ms
4 137.221.66.22 (137.221.66.22) 0.651 ms 0.680 ms 0.689 ms
5 137.221.83.86 (137.221.83.86) 763.885 ms 985.013 ms 985.049 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.943 ms 6.203 ms 6.415 ms
8 las-b21-link.telia.net (62.115.178.200) 5.513 ms 5.919 ms 5.945 ms
9 157.130.245.25 (157.130.245.25) 5.676 ms 5.565 ms 5.536 ms
10 ae199-21.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.95) 64.526 ms 63.755 ms 63.682 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 63.711 ms 63.463 ms 63.457 ms

02/12/2020 20:23:28 UTC

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.229 ms 0.240 ms 0.250 ms
2 24.105.18.2 (24.105.18.2) 0.902 ms 0.932 ms 0.941 ms
3 137.221.105.14 (137.221.105.14) 1.732 ms 1.771 ms 1.779 ms
4 137.221.66.22 (137.221.66.22) 0.426 ms 0.454 ms 0.467 ms
5 137.221.83.86 (137.221.83.86) 776.122 ms 776.160 ms 776.174 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.848 ms 7.570 ms 7.619 ms
8 las-b21-link.telia.net (62.115.178.200) 5.617 ms 7.004 ms 6.991 ms
9 157.130.245.25 (157.130.245.25) 6.974 ms 6.512 ms 6.473 ms
10 ae199-21.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.95) 63.829 ms 63.767 ms 65.288 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 63.701 ms 63.820 ms 64.016 ms

02/12/2020 20:23:28 UTC

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.234 ms 0.235 ms 0.234 ms
2 37.244.23.3 (37.244.23.3) 0.417 ms 0.508 ms 0.585 ms
3 24.105.62.148 (24.105.62.148) 0.693 ms 0.704 ms 0.772 ms
4 137.221.66.8 (137.221.66.8) 61.105 ms 61.141 ms 61.149 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.618 ms 2.039 ms 2.275 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 2.237 ms 1.666 ms 1.639 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 4.796 ms 4.254 ms 4.231 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 2.882 ms 2.889 ms 2.990 ms
10 ae199-21.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.95) 25.862 ms 25.861 ms 25.859 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 24.941 ms 25.003 ms 25.032 ms

02/12/2020 20:23:30 UTC

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.276 ms 0.273 ms 0.273 ms
2 37.244.23.131 (37.244.23.131) 0.501 ms 0.527 ms 0.613 ms
3 24.105.62.148 (24.105.62.148) 0.715 ms 0.738 ms 0.809 ms
4 137.221.66.12 (137.221.66.12) 18.763 ms 18.770 ms 18.777 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 10.360 ms 7.086 ms 7.041 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 2.006 ms 1.998 ms 1.999 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 15.425 ms 14.654 ms 14.620 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 2.864 ms 2.952 ms 2.802 ms
10 ae198-20.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.93) 25.266 ms 25.229 ms 25.188 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 26.194 ms 25.948 ms 25.961 ms

02/12/2020 20:23:32 UTC

MTR:
Start: Wed Dec 2 20:23:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 24.105.18.2 0.0% 10 0.8 4.5 0.5 15.9 5.8
3.|-- 137.221.105.14 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 26.5 3.2 0.5 26.5 8.2
5.|-- 137.221.83.86 0.0% 10 83.9 608.4 83.9 1229. 432.6
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 8.9 5.9 34.5 9.0
8.|-- las-b21-link.telia.net 0.0% 10 8.2 6.0 5.5 8.2 0.7
9.|-- 157.130.245.25 0.0% 10 5.7 5.7 5.6 6.0 0.0
10.|-- ae199-21.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 64.0 63.9 63.8 64.1 0.0
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 64.2 64.3 63.6 64.8 0.0

02/12/2020 20:23:28 UTC

MTR:
Start: Wed Dec 2 20:23:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 2.4 0.3
2.|-- 24.105.18.2 0.0% 10 0.6 1.4 0.5 8.8 2.5
3.|-- 137.221.105.14 0.0% 10 0.9 0.9 0.8 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 6.7 6.3 0.3 16.1 6.5
5.|-- 137.221.83.86 0.0% 10 212.2 673.6 140.7 1615. 480.3
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 63.5 13.9 5.9 63.5 17.9
8.|-- las-b21-link.telia.net 0.0% 10 6.0 5.8 5.5 6.0 0.0
9.|-- 157.130.245.25 0.0% 10 5.8 5.7 5.6 5.8 0.0
10.|-- ae199-21.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 64.0 64.4 63.8 67.9 1.2
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 64.5 64.2 63.4 64.9 0.0

02/12/2020 20:23:28 UTC

MTR:
Start: Wed Dec 2 20:23:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 24.105.18.2 0.0% 10 0.7 1.3 0.5 6.8 1.9
3.|-- 137.221.105.14 0.0% 10 0.9 0.9 0.7 1.1 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.6 0.4 0.8 0.0
5.|-- 137.221.83.86 0.0% 10 1667. 821.6 147.9 1667. 523.0
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 6.6 5.9 11.5 1.7
8.|-- las-b21-link.telia.net 0.0% 10 5.8 5.8 5.5 6.1 0.0
9.|-- 157.130.245.25 0.0% 10 5.9 5.7 5.5 5.9 0.0
10.|-- ae199-21.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 64.0 64.0 63.7 65.1 0.3
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 65.0 64.3 63.8 65.0 0.0

02/12/2020 20:23:28 UTC

MTR:
Start: Wed Dec 2 20:23:30 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.2 0.2 0.3 0.0
2.|-- 37.244.23.3 0.0% 10 0.7 0.5 0.4 0.7 0.0
3.|-- 24.105.62.148 0.0% 10 0.8 0.8 0.7 1.0 0.0
4.|-- 137.221.66.8 0.0% 10 1.1 2.9 1.0 18.4 5.4
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.4 7.6 1.9 56.6 17.2
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 1.7 1.7 1.5 1.8 0.0
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 18.4 8.6 2.3 18.4 4.8
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 2.9 2.9 2.8 2.9 0.0
10.|-- ae199-21.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 25.4 25.5 25.3 26.9 0.3
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 25.7 25.6 25.0 26.2 0.0

02/12/2020 20:23:30 UTC

TRACEROUTE:
traceroute to 100.40.205.66 (100.40.205.66), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.218 ms 0.223 ms 0.237 ms
2 37.244.23.3 (37.244.23.3) 0.436 ms 0.525 ms 0.609 ms
3 24.105.62.148 (24.105.62.148) 0.738 ms 0.751 ms 0.837 ms
4 137.221.66.8 (137.221.66.8) 1.109 ms 1.126 ms 1.099 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 15.512 ms 13.184 ms 13.163 ms
7 7-1-4.ear7.Chicago2.Level3.net (4.7.196.133) 1.589 ms 1.573 ms 1.624 ms
8 ae-1-3510.edge1.Chicago10.Level3.net (4.69.219.14) 14.859 ms 14.121 ms 14.086 ms
9 Verizon-level3-Chicago10.Level3.net (4.68.37.186) 2.866 ms 2.869 ms 2.881 ms
10 ae199-21.PGHKNY-VFTTP-301.verizon-gni.net (100.41.23.95) 25.421 ms 25.461 ms 25.470 ms
11 pool-100-40-205-66.pghkny.fios.verizon.net (100.40.205.66) 26.516 ms 25.694 ms 26.105 ms

02/12/2020 20:23:43 UTC

MTR:
Start: Wed Dec 2 20:23:30 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.7 0.5 1.8 0.3
3.|-- 24.105.62.148 0.0% 10 0.8 0.9 0.7 2.0 0.3
4.|-- 137.221.66.12 0.0% 10 2.4 6.0 1.8 38.4 11.4
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.4 6.5 2.3 42.9 12.8
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 2.1 2.1 2.0 2.2 0.0
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 5.0 5.6 2.8 14.5 3.7
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 2.8 3.3 2.8 6.2 0.9
10.|-- ae198-20.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 27.1 25.8 25.3 27.1 0.5
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 26.0 26.0 25.5 26.4 0.0

02/12/2020 20:23:30 UTC

MTR:
Start: Wed Dec 2 20:23:35 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0
2.|-- 37.244.23.3 0.0% 10 0.8 0.5 0.4 0.8 0.0
3.|-- 24.105.62.148 0.0% 10 0.7 0.9 0.7 1.1 0.0
4.|-- 137.221.66.8 0.0% 10 1.2 5.2 0.9 42.3 13.0
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.9 8.2 1.9 45.2 13.9
7.|-- 7-1-4.ear7.Chicago2.Level3.net 0.0% 10 1.7 1.6 1.5 1.8 0.0
8.|-- ae-1-3510.edge1.Chicago10.Level3.net 0.0% 10 2.3 5.5 2.1 17.5 5.8
9.|-- Verizon-level3-Chicago10.Level3.net 0.0% 10 2.9 4.9 2.8 19.6 5.2
10.|-- ae199-21.PGHKNY-VFTTP-301.verizon-gni.net 0.0% 10 25.4 27.0 25.3 41.9 5.2
11.|-- pool-100-40-205-66.pghkny.fios.verizon.net 0.0% 10 25.9 25.7 25.4 26.5 0.0

02/12/2020 20:23:35 UTC

Elocin-mugthol · December 2, 2020, 8:40pm

Those tests look really good, so it seems unlikely this is a connection-related issue.

Can you describe the issue you’re seeing/when it’s happening? And can you also add a DxDiag?

Click here to show/hide DxDiag instructions

Press Windows Key + R, then type DxDiag and press Enter.
In the DxDiag window, click Save All Information.
Name the file “dxdiag” and click Save.

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.

While you wait for assistance, I suggest opening the Windows Reliability History tool, which may show you what’s happening in the background to cause any errors.

Explodinator-argent-dawn · December 2, 2020, 8:57pm

The issue I’m having is that WoW will sporadically freeze for a few seconds every minute or so- like an extreme lag spike. I don’t have this issue with anything else on my system- games, or otherwise. It doesn’t seem to have a trigger like a specific location or a spell being cast. I tried removing my Interface, WTF, and Cache folders and had the same issue with all default settings.

Here is the DxDiag on Pastebin:

/5YUc7evL

Explodinator-argent-dawn · December 2, 2020, 9:03pm

The spikes aren’t showing anything on the Reliability/Performance tool you linked, unfortunately. Thanks for providing that though.

Elocin-mugthol · December 2, 2020, 9:25pm

Well, that’s a nice PC!

…back on track…

Problem signature:
P1: Corsair.Service.DisplayAdapter

Are you still using any Corsair hardware? I saw one driver listed, but it doesn’t have a device name. If you’re not, track down their software trying to display stats and get rid of it. I’ve seen this cause lots of problems for Overwatch players (that’s the forum I’ve frequented most til recently).

Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: 0x80070645
P2: ProductSearch
P3: N/A
P4: 1.1.17640.0
P5: mpsigstub.exe

Usually, this type of error pops up when there’s a problem with the updater for Windows. You can sometimes resolve it with the System File Checker or DISM repair, and then manually check for updates again. More info on the tool here: https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

Explodinator-argent-dawn · December 2, 2020, 9:54pm

Thanks! I just built it a couple of weeks ago

I currently have Corsair Vengeance RGB Pro Ram installed (64GB). Your note prompted me to open Corsair’s software- iCue- to look at the RAM though. When I opened it, I noticed a red triangle with a red exclamation point in it. Firmware was up to date, but I forced a firmware update with the same version. That cleared the error. I restarted the computer, and it seems to be going much better now.

Not sure why I wouldn’t experience issues with other programs if there was a RAM issue, but it seems to have resolved for now so I’ll take it!

As for the windows update, yeah it was stuck with a cumulative update- I’ve since cleared that out too and Update is back to working normally.

Thanks so much for your help with troubleshooting this!

Elocin-mugthol · December 2, 2020, 10:19pm

You’re welcome. Hopefully all the issues are cleared up now

Explodinator-argent-dawn · December 4, 2020, 5:36pm

Hey, so the issue is back. I replaced my Corair Vengeance RAM with G.Skll Ripjaws V that I had around. I uninstalled Corsair’s iCue software and deleted the Corsair folder from the registry. Still have the same issue. Any suggestions on next steps?

Elocin-mugthol · December 4, 2020, 10:49pm

You could look in the Windows Event Viewer under system logs to see if anything is registering there. And if you run a utility like CCleaner and sweep the registry, you could run another DxDiag and post it here.

Explodinator-argent-dawn · December 8, 2020, 8:44pm

So I’ve run CCleaner inlcuding registry cleaner, DDU in safe mode for a clean video driver install, and swapped out my RAM to G.Skill Trident Neo 32GB (2x16GB). I can still use my Corsair RAM In my old build so not a complete waste! Still having the issue though. I’m at a loss for what to do next.

pastebin link to new DxDiag file: /F4TxGL4u

Elocin-mugthol · December 8, 2020, 9:47pm

Did you check the system logs in the Event Viewer?

Malware Bytes seems to be causing some issue. I recommend completely removing it for testing.

Additionally, some GPU timeout errors are now appearing. Microsoft has an error page with more info:
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x117---video-tdr-timeout-detected

Explodinator-argent-dawn · December 8, 2020, 10:31pm

I disabled Malware Bytes and restarted the computer. All of those previous errors are gone now (mbam, 117) when I run a new DxDiag (replaced with new errors re: MS Edge updates, of course but they don’t seem to be causing any issues).

Fortunately the servers came back up for me to test, and in about 10 minutes of playtime did not experience the issue again. I do have Malware Bytes installed on my laptop too, so I’ll disable it there and test that.

Since the repeating errors I’ve been seeing are now gone completely, I’m hopeful this is resolved!

Thanks for your help with all of this- I greatly appreciate it!

Elocin-mugthol · December 8, 2020, 10:45pm

I hope this is the last step needed to error-free gaming!

Explodinator-argent-dawn · December 16, 2020, 6:59pm

You’re not going to believe this, but I found the fix. Malware bytes ended up not being the issue. I tried something I read on some random forum after the problem came back even after uninstalling Malware Bytes.

In Windows Settings>Personalization>Colors, I unchecked the “Automatically pick an accent color from my background.” Believe it or not, all of the freezing/stuttering across all of my games stopped after I unchecked this. This one, stupid little checkbox… I haven’t had the problem return in many hours of gaming since.

Maybe this nugget of info will help others. Figured I’d circle back with you since you were helping me through this. Again, much appreciated!

Elocin-mugthol · December 18, 2020, 5:51pm

Thank you for reporting back. That doesn’t seem to be a default setting, but it’s definitely possible other people may have it setup that way, so this may help them.