Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
8038 Discussions

How can I fix large lag spikes that started when I got an Intel Dual Band Wireless-AC 8265

RBrew1
Beginner
‎04-26-2018 01:02 AM
5,709 Views

Hi I recently got an Intel Dual Band Wireless-AC 8265 and ever since I have used it my ping randomly spikes to 300-800 every now and then. eg

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=84ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=894ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=748ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=46ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=351ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=337ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=14ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=501ms TTL=51

Reply from 216.58.203.100: bytes=32 time=13ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=802ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=329ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply...

0 Kudos

Link Copied

8 Replies
idata
Employee
‎04-26-2018 07:33 AM
3,658 Views

Hello RyanB,

 

 

Thanks for posting in our communities.

 

 

In order to better assist you, please provide us with the following files:

 

 

- Intel® System Support Utility report.

 

1. https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91600 Download the latest Intel® SSU.

 

2. While connected to your WiFi network, run the scan. Select to include "everything."

 

3. Name and save the report.

 

- Your WLAN Auto-Config log.

 

1. In the search box on the taskbar, type Command prompt, press and hold (or right-click) Command prompt, and then select Run as administrator > Yes.

 

2. Enter: netsh wlan show wlanreport

 

3. Go to: C:\ProgramData\Microsoft\WlanReport\ locate wlan-report-latest.html

 

 

The attach button is located at the lower right corner of the reply box.

 

 

Best regards,

 

Eugenio F.
0 Kudos
Copy link
RBrew1
Beginner
‎04-26-2018 11:52 PM
3,658 Views
In response to idata

Thanks for replying, the files have been attached.

In response to idata
539873.zip
0 Kudos
Copy link
idata
Employee
‎04-27-2018 10:47 AM
3,658 Views
In response to RBrew1

Hello RyanB,

 

 

Thanks for providing the requested files.

 

 

On the adapter advanced settings, please test changing "Channel Width for 5GHz" to "Auto".

 

 

What is your router brand and model? Do you have the chance to connect to other wireless networks for testing? If so, please let us know the results.

 

 

Best regards,

 

Eugenio F.
In response to RBrew1
0 Kudos
Copy link
RBrew1
Beginner
‎04-27-2018 10:39 PM
3,658 Views

Changing the channel width didn't change anything I'm afraid, and I can't find out the router brand and model or connect to another wireless network as I'm living in university accommodation on their internet.

0 Kudos
Copy link
idata
Employee
‎04-30-2018 11:08 AM
3,658 Views
In response to RBrew1

Hello RyanB,

 

 

Thanks for your reply.

 

 

Please notice that occasional ping spikes are expected on wireless connectivity. Even though 300-800ms is a high number, it's still under normal values considering you're connected to a network shared with several clients.

 

 

As a general recommendation, please https://www.asrock.com/MB/AMD/AB350M-HDV/index.asp# BIOS update your system BIOS to the latest version. If your wireless adapter comes with a branded PCIe adapter, please check the manufacturer site for drivers and perform a https://www.intel.com/content/www/us/en/support/articles/000022173/network-and-i-o/wireless-networking.html clean installation.

 

 

NOTE: Links to third party sites are being offered for your convenience and should not be viewed as an endorsement by Intel of the content, products, or services offered there.

 

 

Please let us know if there's anything else we can do for you.

 

 

Best regards,

 

Eugenio F.
In response to RBrew1
0 Kudos
Copy link
idata
Employee
‎05-09-2018 05:51 AM
3,658 Views
In response to RBrew1

Hello RyanB,

 

 

We were reviewing this post. For documentation purposes, can you confirm if the instructions provided by Trilby in the previous post were useful for you?

 

 

Best regards,

 

Eugenio F.
In response to RBrew1
0 Kudos
Copy link
NAspi
Novice
‎05-01-2018 11:32 AM
3,658 Views

Try following the ScanWhenAssociated registry instructions but in the same place you would have set "ScanWhenAssociated" to 0, instead set "ScanDisableOnLowTraffic" to 1 (and restart Windows afterwards).

Copy link
MItal
Beginner
‎05-16-2018 04:41 PM
3,658 Views
In response to NAspi

Thank goodness for you Trillby! Just registered to say, "Get em Trillby!" These "official" Intel techs don't know what they are doing. I trust you more than anything they have to say. (I also saw your posts from that year or more old thread that is now locked... Talk about bashing your head against the wall. Haha.)

In response to NAspi
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.