Help Pinpoint Packet Loss (Pingpath, Looking Glass, WinMTR)

Vyku-malganis · April 16, 2021, 12:02am

Elocin-mugthol · April 16, 2021, 4:17am

Well, there are some interesting errors.

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

Problem signature:
P1: 141

This is the GPU failing to respond to Windows in a timely manner and being rebooted.

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

Problem signature:
P1: Wow.exe

And it’s likely causing this apphang error.

Since this is happening, it’s very possible the problem is with the PC/drivers itself, and not so much with the connection. A clean install of the driver, or using Display driver uninstaller, may help.

Vyku-malganis · April 16, 2021, 5:28pm

Odd. I wonder if this has anything to do with the weird DX12 flickering issue. I do often select my gpu in WoW and apply in order to stop the flickering as recommended by many in these forums.

This lag issue was already happening after I moved to this apartment and got keystone fiber. Was not happening during the year I had Xfinity cable at the old place.

Whenever I do a clean install of windows, I use Display Driver Uninstaller. So that was already done a couple weeks ago when I tried refreshing. I can try it again though.

Vyku-malganis · April 17, 2021, 12:43am

Fresh install after DDU. New DxDiag, diagnostics data. I see Battle.net in there now.
---------------
Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1273894465777533413, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: nvgwls.exe
P2: 0.0.0.0
P3: 10.0.19041.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER1 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffd88fa976a010
P3: fffff8034d8a4ec0
P4: 0
P5: 1cc8
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER2 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffd88fa976a010
P3: fffff8034d8a4ec0
P4: 0
P5: 1cc8
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER3 +++:
Fault bucket 2205113917563550120, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Battle.net.exe
P2: 1.33.7.12803
P3: 60624b5f
P4: KERNELBASE.dll
P5: 10.0.19041.804
P6: b610d74d
P7: e0000008
P8: 0012a8b2
P9: 
P10: 


+++ WER4 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Battle.net.exe
P2: 1.33.7.12803
P3: 60624b5f
P4: KERNELBASE.dll
P5: 10.0.19041.804
P6: b610d74d
P7: e0000008
P8: 0012a8b2
P9: 
P10: 


+++ WER5 +++:
Fault bucket 1994430662353387231, type 5
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.925:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x1a5098f2
P7: 
P8: 
P9: 
P10: 


+++ WER6 +++:
Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.925:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x1a5098f2
P7: 
P8: 
P9: 
P10: 


+++ WER7 +++:
Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.925:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x1a5098f2
P7: 
P8: 
P9: 
P10: 


+++ WER8 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffcc8e84a2b220
P3: fffff80173864ec0
P4: 0
P5: 1e5c
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER9 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffcc8e84a2b220
P3: fffff80173864ec0
P4: 0
P5: 1e5c
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10:

Elocin-mugthol · April 17, 2021, 10:33pm

This report is now showing timeouts from the GPU. If everything is set to High Performance power mode, the GPU shouldn’t be timing out unless there is third-party conflict we can’t see in the reports, overheating (which you mentioned checking) or a physical problem with it (especially since you reinstalled the drivers).

Can I see some screenshots of HWMonitor with all of the hardware sections expanded? Not just the GPU/CPU, but everything.

You could also try some benchmarking software to see what happens. Here are some tools I use for testing hardware:

Entire system: UserBenchmark
GPU: Heaven
CPU: Prime95

Vyku-malganis · April 18, 2021, 12:17am

Yeah everything is High Performance.

Today, I decided to try with a different game. It does feel like my performance is definitely worse, in this game too. Apex has never had moments of stutter. I’ve been playing with different performance monitors open. I noticed that Apex is hitting 99% GPU utilization. Don’t know how often that happened before. GPU/CPU is typically around 50c and GPU only hitting 65c highs, temp wise.

Elocin-mugthol · April 18, 2021, 12:26am

What about the rest of the hardware though? Did you take some HWMonitor screenshots? Or try any of the benchmarking stuff?

Elocin-mugthol · April 18, 2021, 1:16am

What’s happening?

Vyku-malganis · April 18, 2021, 6:37am

I haven’t used any benchmarking in years. Redownloaded. I’ll link below.

Also, just tried a bunch of things. Switch GPU to the other PCIE slot and DDU/reinstall - same WER errors in DxDiag. Ran MemTest, no errors. Checked each stick separately too. Ran SFC, nothing, CHKDSK, nothing, DISM restore health, nothing. Underclocked GPU, nothing.

I see there are a lot of people with this 141 error, on this forum and elsewhere. No one ever seems to get it resolved. A couple claim it can be fixed with going to HKEY_LOCAL_MACHINE → SYSTEM → CurrentControlSet → Control → GraphicsDrivers and creating a new DWORD TdrDelay and setting it to 8. I haven’t tried this yet.

HWMonitor https://imgur.com/a/Ku76vCO

# Unigine Heaven Benchmark 4.0

|FPS:|**90.6**|
| --- | --- |
|Score:|**2283**|
|Min FPS:|**36.4**|
|Max FPS:|**176.7**|

## System

|Platform:|Windows NT 6.2 (build 9200) 64bit|
| --- | --- |
|CPU model:|AMD Ryzen 5 3600X 6-Core Processor (3799MHz) x6|
|GPU model:|NVIDIA GeForce RTX 2080 SUPER 27.21.14.6611 (4095MB) x1|

## Settings

|Render:|Direct3D11|
| --- | --- |
|Mode:|2560x1440 8xAA fullscreen|
|Preset|Custom|
|Quality|Ultra|
|Tessellation:|Extreme|

Should I be clearing logs before rerunning DxDiag? Are some of these old?

Interesting to see MemDiag in here. Is that just because I ran it? Not because of an issue?

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 45810158, type 5
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
P1: 4097
P2: Manual
P3: Immediate
P4: Pass
P5: Standard
P6: 0
P7: 0
P8: 1620
P9: 
P10: 


+++ WER1 +++:
Fault bucket , type 0
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
P1: 4097
P2: Manual
P3: Immediate
P4: Pass
P5: Standard
P6: 0
P7: 0
P8: 1620
P9: 
P10: 

+++ WER4 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffdb89c52de010
P3: fffff8005a274ec0
P4: 0
P5: 1f18
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER5 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffdb89c52de010
P3: fffff8005a274ec0
P4: 0
P5: 1f18
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER6 +++:
Fault bucket 1273894465777533413, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: nvgwls.exe
P2: 0.0.0.0
P3: 10.0.19041.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER7 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffd88fa976a010
P3: fffff8034d8a4ec0
P4: 0
P5: 1cc8
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER8 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffd88fa976a010
P3: fffff8034d8a4ec0
P4: 0
P5: 1cc8
P6: 10_0_19041
P7: 0_0
P8: 768_1
P9: 
P10: 


+++ WER9 +++:
Fault bucket 2205113917563550120, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Battle.net.exe
P2: 1.33.7.12803
P3: 60624b5f
P4: KERNELBASE.dll
P5: 10.0.19041.804
P6: b610d74d
P7: e0000008
P8: 0012a8b2
P9: 
P10:

Elocin-mugthol · April 18, 2021, 8:43am

It’s a generic windows error, and I can guarantee you will find it on every gaming forum, and probably a bunch of other application-centric forums, too. It literally means: “the GPU is not responding to instructions given to it by the operating system and has been rebooted to try to fix this issue.”

Yes, it’s there because you ran it. Yes, it’s good to clear the errors but I’ve been keeping track of what we’ve already seen.

At this point, I do think it might be best to consult with a PC technician to test the GPU. The benchmark test website, along with the Heaven results, both show it performing below expectations for such a nice card (and with the help of a nice CPU).

Vyku-malganis · April 18, 2021, 6:24pm

That would be my luck if the gpu is dying. It’s only maybe 9months of use at this point. It benched 136% so it’s “below” by 2%. It’s unfortunately a Ventus card and not a Gaming X Trio, or one of the other good ones. Figured the 2% below was just do to that.

Since the issue in wow made everyone run in place, then run turbo speed to catch up (and recently switched isp) I thought it had to be network. I thought gpu/cpu issues would be dropped frames, and my fps isn’t dropping. Guess the frames can all show up after the gpu reconnects and it would look like this without my fps dropping.

I asked about clearing the WER’s to make sure these 141s are actually still there after all the stuff I just recently did and not just still listed.

Wish it was easier to get ahold of a gpu right now so that I can test another one. I wanted to test my mobo and gpu a month ago. Just can’t get one.

Elocin-mugthol · April 18, 2021, 6:59pm

Yeah, the GPU rebooting can cause that behavior.

Well, of course you can clear them and check the report on your own. You also know what errors we’ve seen so far.

Vyku-malganis · April 18, 2021, 8:55pm

How do I clear the errors reported in DxDiag? I can’t find an answer that works on Google. Found multiple BAT files that I tried. “View all problem reports” has stayed empty after I cleared it a day or two ago.

Elocin-mugthol · April 18, 2021, 9:33pm

The Disk Cleanup tool should have an option to delete error reports. If not, you might be able to use CCleaner to clear them.

Vyku-malganis · April 18, 2021, 9:52pm

Disk Cleanup didn’t but CCleaner did. I always use it for registry, forgot about being able to clean up Windows files.

Thanks again for all your help.

Vyku-malganis · May 2, 2021, 10:13am

So, hours and hours and money later lol, it ended up being 3 things.

My GPU
One of the PSU cables
One of my SSDs

I think I may FINALLY be good now. Still testing different drivers.

Tratt-proudmoore · May 2, 2021, 10:23am

Woah - I just read through this epic troubleshoot you and Elocin hammered out. Good to see you may have it Vyku.

Vyku-malganis · May 5, 2021, 10:07pm

Yeah, I’d buy them a coffee if I knew how.

So something did end up also being wrong on my ISPs end, which is where all this started. Their data center went out a couple days ago and they had to replace some stuff. Cleaned up my pathping/tracert results.

Yesterday, I had some lag spikes again. Even saw a problem ID 141 again. It’s worrying but this new gpu is my friends - known to be working fine.

I am tempted to replace my mobo, ram, and PSU for science/paranoia but that’s a lot of money.

The latest reinstall of windows I did, after removing the problematic ssd, did have a hiccup at first. When I first rebooted after replacing the psu cable and removing the ssd, it didn’t boot and had a mobo light for CPU. I restarted and it had a mobo light for RAM. I restarted with a single stick and it started fine. I switched sticks and it restarted fine again. Put both sticks in and it restarted fine. So that was confusing.

After replacing the SSD, the issue I had with crazy frametimes in WoW and Apex was cleared up. I then installed a different game and frame times were awful. Rebooted Apex and WoW and frame times seemed fine. Weird that the other game acted that way. I blame the other game.

I’ve also been reading even more about the difficulties people have had with amd mobo bios since the 5xxx series launch. Investigating GPU issues have shown me how many people are having issues with nvidia bios since 3xxx came out as well.

With all this chaos going on, it is hard to narrow down if I have an issue or it’s a driver thing lol.

Elocin-mugthol · May 5, 2021, 11:39pm

Aww shucks.

This is… oof … I think testing another GPU vs replacing everything else might be a more plausible troubleshooting method.

Vyku-malganis · May 6, 2021, 1:17am

It was hard enough to get ahold of this second one let alone a third. I won’t have my GPU back from RMA for at least a month. I’ve built probably 40ish computers for me/others in my life and never had issues with any of them. This is the first time I’ve ever had this much trouble so I’m frustrated.

It might really be a driver/dx12 issue. Do you have MSI Afterburner? What’s your Frametime ms like in WoW? Mine seems to be jumping around again. I just don’t know if that’s borderline normal since WoW is so CPU bound and the number of people can vary. I tested it in oribos where no people were though.

[Album] imgur.com

I’m not alone