1 2 3 Previous Next 78 Replies Latest reply on Aug 31, 2017 7:29 AM by Actinolite

    AC 7260 frequent ping spikes

    samthebam

      Anyone has had issues with this card? I cant seem to get rid of the regular and frustrating ping spikes. Im on Windows 7, running a Dell Precision 3800 laptop. I'm on an ASUS AC68U router, though Ive tried others with the same result. Ive also tried different driver versions and even reformatted my system to no avail. Anyone know whats going on? The collective knowledge of the internet seems rather divided and inconclusive on this matter despite my scouring of its depths over the last few days. Its definitely something to do with the wireless card. I just dont know what.

       

      Here is the results I get when I ping my router. As you can see its sitting pretty dandy at 1ms and then it suddenly decides to explode to some ridiculous number for a second or two then it goes back to normal again.

       

      Pinging 192.168.1.1 with 32 bytes of data:

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=160ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=80ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=190ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=109ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=82ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=80ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=217ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=171ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=177ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=96ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=16ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=208ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=128ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=84ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time<1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=96ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=18ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=165ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=206ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=128ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=46ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

      Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

       

       

      Ping statistics for 192.168.1.1:

      Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),

      Approximate round trip times in milli-seconds:

      Minimum = 0ms, Maximum = 217ms, Average = 25ms

        • 1. Re: AC 7260 frequent ping spikes
          theveterans

          I would guess that your neighbor has a device that operates on 5 GHz that interferes with your WiFi. 5 GHz interference isn't too common even in RF congested areas unless your neighbor is using 5.8 GHz home phone for example.

           

          I just tested mine and only got  exactly 1 random spike to 44ms (probably router is busy as I have other 5 GHz devices streaming internet at the same time as I'm doing this test) so I don't consider that it's wireless card fault unless yours is a hardware fault

           

          Capture.JPG

          • 2. Re: AC 7260 frequent ping spikes
            samthebam

            Thanks for the reply. I actually just checked, and my 5Ghz spectrum is dead empty (unlike the 2.4Ghz which is really full). Both give me similar ping issues. Ive also tried this at my girlfriends house on her router to the same effect. Ive got another laptop which I upgraded with the same card. After the upgrade it gives me similar issues.

            • 3. Re: AC 7260 frequent ping spikes
              theveterans

              Make sure to set every power management options to high performance. However, I don't ever need to do this on my laptop. In fact, the ping test that I did was on the default balanced power plan.

               

              I'm probably thinking it's a hardware issue if it happens on multiple locations. I would say (not a fact of course) that you just got a bad batch of 7260s like from many previous posts here.

              • 4. Re: AC 7260 frequent ping spikes
                samthebam

                Thanks for the advice. Didn't help though. Gonna see if I can get the replaced. Definitely a hardware issue because all the rest of the computers in my house run perfect on the router.

                • 5. Re: AC 7260 frequent ping spikes

                  Let us know.

                  • 6. Re: AC 7260 frequent ping spikes
                    Mantissa

                    Hi there,

                     

                    I'm facing the exact same issue.

                     

                    Were you able to figure out the cause?

                     

                    Thanks!

                    • 7. Re: AC 7260 frequent ping spikes
                      Vigz

                      Hello,

                       

                      After doing a bit of research, the ping spikes are caused when the wireless card scans for networks. I was actually able to reproduce the issue and can confirm this. You can do so yourself.

                       

                      Go to cmd, type ping www.google.com -t

                       

                      If you're on Windows 8 or 8.1, all you need to do is access the wireless network list by clicking on the wireless icon on the bottom right and it will automatically refresh. For those on Windows 7, click the wireless icon on the bottom right and click on the refresh button next to your connected network. As you are doing this, you'll notice that the ping counter on the command prompt will spike up. I thought it was an issue with the card as well and I was wondering about getting a replacement as well. It can be ridiculously annoying for gaming. It seems as though Windows likes to re scan for networks periodically causing random lag spikes. If there was a way to stop scanning while you're connected to a network, that would be great.

                       

                      UPDATE: Oh boy, I was able to find a solution. It involves using the Registry Editor. Be careful not to change anything else except for the things that are listed.

                       

                      1. Open Registry Editor (Windows 8/8.1, right click where Start button was, click Run, type regedit. Windows 7, click Start, click Run, type regedit)

                       

                      2. Head to 'HKEY_LOCAL_MACHINE \ System\ CurrentControlSet \ Control \ Class \ {4d36e972-e325-11ce-bfc1-08002be10318} [Be sure to expand the 4d36e.... folder]


                      3. Inside will be a number of folders named 0000, 0001, 0002, etc. Look through all these folders until you get one that says Intel(R) Dual Band Wireless-AC 7260 in the registry.


                      4. Once the device has been found, search for a value called ScanWhenAssociated.


                      5. If you see this value, set it to 0 on hexadecimal. If you don't see the value, click edit from the top, select new, and click DWORD (32-bit) value. Rename this value to ScanWhenAssociated (exactly as shown). Make sure this value is set to 0 on hexadecimal.


                      6. Restart the computer. This is important. The changes won't take effect unless you do.


                      I rebooted and tried using cmd to ping google.com. I refreshed the networks and PRESTO! There were no more lag spikes!!! Try it out yourself. I'll give this a couple more days of testing. Big thanks to Lenovo for the guide: [SOLUTION] latency spikes and network unstability ... - Lenovo Community



                       


                      Here's mine (bold is when I clicked on refresh):

                      Pinging www.google.com [173.194.46.112] with 32 bytes of data:

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=27ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=24ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=146ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=121ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=34ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=29ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=270ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=237ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=157ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=27ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=27ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=431ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=119ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=36ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=80ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=33ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=26ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=28ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=25ms TTL=248

                      Reply from 173.194.46.112: bytes=32 time=24ms TTL=248

                       

                       

                      Ping statistics for 173.194.46.112:

                          Packets: Sent = 33, Received = 33, Lost = 0 (0% loss),

                      Approximate round trip times in milli-seconds:

                          Minimum = 24ms, Maximum = 431ms, Average = 67ms

                      • 9. Re: AC 7260 frequent ping spikes
                        Vigz

                        Sorry but disabling U-ASPD doesn't do a thing. It is absolutely, ABSOLUTELY atrocious that this wireless card is shipped on so many computers worldwide yet Intel didn't have the time to test the thing correctly.

                        • 10. Re: AC 7260 frequent ping spikes
                          stasiek01

                          Thank you so much for this Vigz. It's the only solution I've found to be helpful. I have intel 3160 wireless card and now everything works smoothly, without lags and spikes.

                           

                          I wish there were more people like you, since everyone else just threw some random solutions like changing the power management, increasing aggressiveness or changing channels of the wifi and so on, without even looking checking the problem. You described everything about the problem and solution.

                           

                          Thank you again!!!

                          • 11. Re: AC 7260 frequent ping spikes
                            theveterans

                            stasiek01 wrote:

                             

                            Thank you so much for this Vigz. It's the only solution I've found to be helpful. I have intel 3160 wireless card and now everything works smoothly, without lags and spikes.

                             

                            I wish there were more people like you, since everyone else just threw some random solutions like changing the power management, increasing aggressiveness or changing channels of the wifi and so on, without even looking checking the problem. You described everything about the problem and solution.

                             

                            Thank you again!!!

                             

                            All Vigz did there was to completely disallow roaming by completely disabling background scanning. Doing this tweak isn't good for those who roam a lot, but almost 99% of WiFi users are stationary so not having roaming capability isn't really a con. BTW, I don't have recurring ping spikes at all without the need to do this tweak. Once the drivers detect streaming, background scanning turns off COMPLETELY.

                            • 12. Re: AC 7260 frequent ping spikes
                              Vigz

                              @stasiek01 Wow, so this issue occurs on other Intel Wi-Fi cards too?

                               

                              I wish I could test using the card on a 5ghz network. Perhaps this problem only occurs on 2.4ghz bands?

                               

                              @theveterans

                               

                              It stops scanning when you are connected to a network. When you disconnect from the network, the card will resume scanning for networks in the background hence the term disable ScanWhenAssociated. This tweak does not render network scanning useless.

                              • 13. Re: AC 7260 frequent ping spikes
                                theveterans

                                The registry tweak stops background scanning after WiFi connection is associated. You can understand it clearly using the registry entry name "scan when associated" That's why it's bad for roaming since it'll not background scan for a stronger signals in multi-access point setup such as those found in universities, hospitals, etc. You can always manual (not background) scan for a better AP but this registry tweak will render your 7260 like a "sticky client"

                                 

                                Read this stuff to know what I mean: A sticky problem – Wi-Fi clients that won’t roam | WiFi Kiwi's Blog

                                 

                                In my case, my Intel 7260 on my laptop works without the need to completely disable background scanning. When packet streaming are detected such as gaming, DLNA, Netflix, my Intel 7260 disables background scan completely, eliminating periodic ping spikes that you experience without the registry tweak. Then after packet streaming is done, my 7260 will background scan for to roam for better signals. Refreshing a page will sure cause ping spikes regardless of disabling or enabling background scan. That is an example of drivers working perfectly on my system.

                                • 14. Re: AC 7260 frequent ping spikes
                                  ethaniel

                                  GUYS I SOLVED THE PROBLEM

                                  however, you will not like the solution.

                                   

                                  i tried all the drivers from the different threads and the problem still persists. I assume that Intel has a technical design flaw in the card which they are not willing to admit (otherwise the company will go bankrupt).

                                  So, the only solution is to switch to another card. As someone suggested in another thread, I chose Broadcom 94352 (Broadcom 4352), otherwise known as Azurewave AW-CE123H.

                                   

                                  It has all the same functions (b/g/n/ac, bt4.0) and works flawlessly.


                                  7260 is unfixable, unreliable crap. Same as 6235.

                                  Intel can go **** itself.

                                  1 2 3 Previous Next