Semi-consistent Heavy Stuttering & Lag

I’ve been having this problem for a real long time now, probably since the 64bit patch.

Almost every match starts fine, but get heavy stuttering at around the 7:10 minutes mark, which lasts until about 10:30 then the game returns to normal. There are a few cases where it happens earlier in the match or less frequently, but it’s rare.

During the 7:10 to 10:30 timeframe it’s common for the stuttering to be so heavy that i get multiple disconnects/reconnects, in some cases i can’t reconnect to the match at all as it ends before my game resumes.

My system information:

System Information
------------------
      Time of this report: 5/22/2019, 14:55:07
             Machine name: DESKTOP-BG3R5IG
               Machine Id: {C98D3E7C-45AC-4F2A-9A68-8FA4B1C2C967}
         Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
                 Language: Portuguese (Regional Setting: Portuguese)
      System Manufacturer: ASUS
             System Model: All Series
                     BIOS: 2107 (type: UEFI)
                Processor: n/a
                   Memory: 4096MB RAM
      Available OS Memory: 4002MB RAM
                Page File: 5556MB used, 5743MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.17134.0001 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
           Card name: NVIDIA GeForce GTX 750 Ti
        Manufacturer: NVIDIA
           Chip type: GeForce GTX 750 Ti
            DAC type: Integrated RAMDAC
         Device Type: Full Device (POST)
          Device Key: Enum\PCI\VEN_10DE&DEV_1380&SUBSYS_105F10DE&REV_A2
       Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 4008 MB
    Dedicated Memory: 2007 MB
       Shared Memory: 2000 MB
        Current Mode: 1920 x 1080 (32 bit) (60Hz)
         HDR Support: Not Supported
    Display Topology: Internal
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.647961,0.333508), Green(0.332531,0.626477), Blue(0.156750,0.052258), White Point(0.313000,0.329602)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: T22B300
          Monitor Id: SAM092B
         Native Mode: 1920 x 1080(p) (60.000Hz)
         Output Type: HD15
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_33844b3d8c39ff4a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_33844b3d8c39ff4a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_33844b3d8c39ff4a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_desktop_ref4i.inf_amd64_33844b3d8c39ff4a\nvldumdx.dll
 Driver File Version: 25.21.0014.1881 (English)
      Driver Version: 25.21.14.1881
         DDI Version: 12
      Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.4
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported
 Hybrid Graphics GPU: Not Supported
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: No Blocks
  Catalog Attributes: Universal:False Declarative:False 
   Driver Attributes: Final Retail
    Driver Date/Size: 29/01/2019 21:00:00, 958008 bytes
         WHQL Logo'd: n/a
     WHQL Date Stamp: n/a
   Device Identifier: {D7B71E3E-50C0-11CF-3774-513018C2D435}
           Vendor ID: 0x10DE
           Device ID: 0x1380
           SubSys ID: 0x105F10DE
         Revision ID: 0x00A2
  Driver Strong Name: oem14.inf:0f066de366d95723:Section012:25.21.14.1881:pci\ven_10de&dev_1380&subsys_105f10de
      Rank Of Driver: 00D10001
         Video Accel: 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        D3D9 Overlay: Supported
             DXVA-HD: Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 1
            MPO Caps: Not Supported
         MPO Stretch: Not Supported
     MPO Media Hints: Not Supported
         MPO Formats: Not Supported
    PanelFitter Caps: Not Supported
 PanelFitter Stretch: Not Supported

Heya Saint,

Would it be okay to run this winMTR test and post the results? Based on the description it sounds like it may be some kind of connection issue. This tool should help us map the connection route and find where the problem is happening.

Additional detail, this only happens in HoTS. Here’s the winMTR results, ignore the ~~ as i can’t post links.

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

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

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

| 192.168.0.1 - 0 | 1316 | 1316 | 0 | 0 | 2 | 0 |

| 2.112.208.143.pontalnet.com.br - 6 | 1076 | 1015 | 0 | 4 | 38 | 1 |

| 1.112.208.143.pontalnet.com.br - 6 | 1076 | 1015 | 0 | 4 | 39 | 0 |

| 5.196.49.201.assim.net~~ - 11 | 932 | 835 | 1 | 5 | 38 | 2 |

| 192.168.241.150 - 12 | 908 | 805 | 0 | 8 | 96 | 3 |

| 126.91.124.189.assim.net~~ - 12 | 916 | 815 | 0 | 6 | 41 | 3 |

|200-153-91-109.customer.tdatabrasil.net.br - 7 | 1040 | 970 | 0 | 12 | 53 | 8 |

| 187-100-83-0.dsl.telesp.net.br - 8 | 1024 | 950 | 0 | 20 | 57 | 16 |

| 84.16.9.109 - 6 | 1088 | 1030 | 24 | 31 | 114 | 25 |

| 94.142.120.114 - 10 | 952 | 860 | 0 | 28 | 66 | 25 |

| 94.142.103.247 - 11 | 924 | 825 | 16 | 21 | 67 | 17 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| 52.93.44.193 - 6 | 1095 | 1039 | 0 | 28 | 111 | 18 |

| 52.93.44.105 - 11 | 940 | 845 | 0 | 20 | 53 | 18 |

| 177.72.240.119 - 11 | 936 | 840 | 0 | 23 | 65 | 20 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 264 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

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

I’m getting the same issue as the guy above me. I’ve attached the WinMTR Statistics report below. I would be playing normally. then once players ( Allied or Enemy) engaged, I would get a random High ping and experience a .25 second -> .75 second lag spike. Never experienced this before.

This hasn’t happened before or last year.

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

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

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

| 192.168.0.1 - 0 | 420 | 420 | 0 | 135 | 1303 | 1 |

| 10.35.192.1 - 0 | 420 | 420 | 6 | 145 | 1302 | 8 |

| 100.127.73.130 - 0 | 420 | 420 | 7 | 148 | 1300 | 13 |

| 100.120.100.10 - 0 | 420 | 420 | 7 | 146 | 1299 | 8 |

| 68.1.4.252 - 1 | 416 | 415 | 18 | 170 | 1304 | 28 |

| 68.105.30.130 - 0 | 420 | 420 | 19 | 160 | 1302 | 22 |

| ae1-br01-eqla1.as57976(dot)net - 0 | 420 | 420 | 18 | 158 | 1300 | 49 |

| be1-pe01-eqla1.as57976(dot)net - 0 | 420 | 420 | 19 | 154 | 1302 | 23 |

| 24.105.30.129 - 0 | 420 | 420 | 19 | 156 | 1303 | 22 |

|________________________________________________|______|______|______|______|______|______|

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

@Saint, thanks for the WinMTR test! The test shows a 6% and consistent loss throughout the test, which can cause the stuttering and lag to occur. This could be mitigation or prioritization on the home network (such as the QoS setting on the router), since it is starting on the Internet Provider’s network, it’s recommended to reach out to them to address the 6-12% packet loss happening consistently on route the servers.

@Chronosoul, thank you for the test as well! This one is a different though. The problem is happening on the home network where the average latency is 135ms, the worst at 1303ms. This should be under 10ms for the home network on wireless or wired connections.

This indicates a home network or system network issue. It can help to try resetting the network devices. If it persists from there, resetting the TCP/IP and Winsock can sometimes help resolve these large latency spikes on the home network.

  1. Right click on your Windows Start Menu, and select “Command Prompt (Admin)” or just search for Command Prompt and right click, run as administrator.
  2. Now type in or copy and paste, “netsh int ip reset” Press Enter.
  3. Then do the same for “netsh winsock reset”

Once it’s complete, you’ll need to restart the computer to complete the reset.

Caterpepi,

Thanks for the response. I performed the actions you suggested and i’m still suffering from the same lag. See new report…
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

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

| 192.168.0.1 - 0 | 679 | 679 | 0 | 139 | 1233 | 0 |

| 10.35.192.1 - 0 | 679 | 679 | 6 | 146 | 1295 | 8 |

| 100.127.73.130 - 1 | 663 | 659 | 7 | 155 | 1404 | 8 |

| 100.120.100.10 - 1 | 675 | 674 | 7 | 142 | 1183 | 12 |

| lag-104.bear1.Phoenix1.Level3. net - 4 | 603 | 584 | 7 | 183 | 1695 | 12 |

| ae-1-3501.ear3.Tustin1.Level3 .net - 98 | 139 | 3 | 0 | 270 | 755 | 27 |

| 192.205.37.145 - 0 | 679 | 679 | 25 | 156 | 1397 | 30 |

| cr2.la2ca.ip.att .net - 0 | 679 | 679 | 34 | 160 | 1234 | 37 |

| gar5.la2ca.ip.att .net - 0 | 679 | 679 | 27 | 158 | 1298 | 33 |

| 32.130.250.6 - 0 | 679 | 679 | 26 | 156 | 1231 | 30 |

| 32.130.250.17 - 0 | 679 | 679 | 26 | 155 | 1186 | 29 |

I’ll look into it on my end on why my router/Modem is giving me such issues.

Thanks,

Hey Chronosoul,

If you haven’t already, try bypassing the router, and any extenders or adapters and connect the PC directly to the modem with an ethernet cable and then retest.

I’ve retested this bad boy on 3 different computers (Main, Work, Laptop) and have reached the point where I’ve identified the culprit.

My results are definitely not game related but i’ll share my research. My current computer can’t maintain less then 10ms without spiking periodically to 150->1855.

My work laptop connects fine to the Router (Wired & Wireless) and doesn’t miss a beat in terms of upload(1.96) download(17.1) speed. Modem Checks out & router in a wired configuration checks out. By check out, I mean i have consistent ping and signal for more then 30 seconds.

My regular laptop works perfectly fine in the living room and in the computer room using it’s on board wireless adapter AND the wireless adapter from my computer Netgear AC1200. Both tests yielded a ping lower then 10ms through 10 mins of regular gaming and browsing. So the Router’s wireless is working fine and the wireless net-gear adapter that I use for my Main computer wireless works fine as well.

I can say that i’m now working on trouble shooting my computer. And I have no idea where to start if I already did the “netsh int ip reset” and “netsh winsock reset”

Appreciate the help guys! time to open up 12 google tabs and “troubleshoot”

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=130ms TTL=64
Reply from 192.168.0.1: bytes=32 time=286ms TTL=64
Reply from 192.168.0.1: bytes=32 time=284ms TTL=64
Reply from 192.168.0.1: bytes=32 time=284ms TTL=64
Reply from 192.168.0.1: bytes=32 time=283ms TTL=64
Reply from 192.168.0.1: bytes=32 time=283ms TTL=64
Reply from 192.168.0.1: bytes=32 time=101ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=164ms TTL=64
Reply from 192.168.0.1: bytes=32 time=363ms TTL=64
Reply from 192.168.0.1: bytes=32 time=564ms TTL=64
Reply from 192.168.0.1: bytes=32 time=362ms TTL=64
Reply from 192.168.0.1: bytes=32 time=261ms TTL=64
Reply from 192.168.0.1: bytes=32 time=279ms TTL=64
Reply from 192.168.0.1: bytes=32 time=101ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Packets: Sent = 597, Received = 597, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1855ms, Average = 59ms
Control-C

Ping Plotter software attached as well. Remove the space

https ://share.pingplotter .com/Ca8VGD7c88n

Plugged it in direct with an ethernet cord into the router. Zero problems… still want to figure out the problem since I don’t want a wired setup…

Hey Chronosoul,

Based on what you described, your main computer only has a problem when using wireless but the wireless adapter works fine on other computers. This leads me to think that there could be a driver problem on the main computer and you could try reinstalling the wireless adapter drivers on that computer.

There could also be power settings causing issues, so make sure that you check the Windows settings for the wireless adapter and set everything to High Performance.

  1. Press the Windows key and type power
  2. Select Power and Sleep settings
  3. Click Additional Power settings
  4. Set the option to High Performance or Ultimate Performance (if you don’t see this option click the arrow at the bottom or choose Create a Plan on the left)
  5. Click Change advanced power settings
  6. Find the Wireless Adapter Settings
  7. Click the + sign and open Power Saving Mode
  8. Choose Maximum Performance by clicking on the Setting.
  9. Find the USB settings in the window
  10. Click the + sign and open USB selective suspend setting
  11. Set this to Disabled to prevent USB devices from being turned off and click Apply
  12. Press Windows key and type “device manager”
  13. Double click Network Adapter
  14. Find the device you are using and right click on it
  15. Choose Properties
  16. Go into the Power Management tab
  17. Uncheck “Allow the computer to turn off this device to save power”.

A post was split to a new topic: [TNRSalameth] Stuttering lag