Hi,
Sorry I did not. I elected to get a different adapter and it’s worked perfectly. But I’ll elaborate further for anyone else n case they have the issue.
To answer your question: Are you using an Intel® AC 9260 wireless adapter or is it an Asus* PCE-AC58BT
It is an ASUS PCE-AC58BT but the device manager recognizes it as an Intel AC9260. I have replicateed this issued
Based on the past advice moderators have given to this community and what people elsewhere have said, it looks like my issue stems from the channel width. I have tried every other option presented. Unfortunately the device driver setting only lets me choose between 20mhz and Auto. When I set it to 20mhz it worked fine, except the speed was much lower than normal (to be expected) but there were no errors and the connection was consistent.
Even more unfortunately I have the google nest so I can’t change any channel or width settings at all.
The only other option I haven’t was something about switching to Switch coding to LDPC based on this link: https://dot11.exposed/2019/09/30/wi-fi-dos-by-rf-jamming-from-faulty-intel-driver/
IDK what that means or how to do it so I didn’t do it.
Anyway since I couldn’t implement the only remaining options I went with new adapter.
Thank you
I just picked up the M141 today. Installed all Windows Updates, updated the BIOS, and started using it. I noticed an issue where the network seemed to stop working randomly every once in a while. I checked Event Viewer, and sure enough, there are errors already.
Log Name: System
Source: Netwtw04
Date: 3/18/2020 8:46:13 PM
Event ID: 5007
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-5SP4DQC
Description:
5007 - TX/CMD timeout (TfdQueue hanged)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Netwtw04" />
<EventID Qualifiers="49152">5007</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-03-19T00:46:13.216835700Z" />
<EventRecordID>2328</EventRecordID>
<Channel>System</Channel>
<Computer>DESKTOP-5SP4DQC</Computer>
<Security />
</System>
<EventData>
<Data>DeviceNDMP2</Data>
<Data>Intel(R) Dual Band Wireless-AC 3168</Data>
<Binary>0000080002003800000000008F1300C00000000000000000000000000000000000000000000000004D4D41431C009D11</Binary>
</EventData>
</Event>
So the first thing I tried was just updating the drivers using Device Manager > Right-Click > Update Drivers. It downloaded and installed new drivers. I cleared the event logs, continued testing, and while the issue is not happening as frequently, it still does occur. I took to Google and found many others having issues with Intel WLAN chipsets / drivers and that error.
https://www.google.com/search?q=5007+-+TX%2FCMD+timeout+(TfdQueue+hanged)
I also found this interesting article: Wi-Fi DoS by RF-Jamming from faulty Intel Driver
Has anybody else experienced this issue or have any ideas on how to resolve it? Thanks.
Introduction
It all started with people telling me that when they were gathered in a meeting room, everybody loses their connection to the Wi-Fi. This happened sporadically and everyone got disconnected at the same time. Obviously the AP and the Wi-Fi were thought of being the source of this problem, so I started my analysis.
After some digging and frame capturing, it showed that during the occurrence of this issue, no Wi-Fi frames were transmitted on that given channel for about 10 seconds, not even Beacon Frames.
As an example below a Wireshark IO Graph with all the Beacon Frames my sniffer received on that affected channel during the issue:
There was no logical explanation for me, so I started up Ekahau and the Sidekick to look at the RTFM (real time frequency monitor), and the following happening revealed itself:
As you
can see, there is something that interferes with the Wi-Fi and jamms up the
whole channel for about 10 seconds. Upon further investigation, it was
noticeable that not the AP was the source of that interference, but one of the
notebooks in the room.
Reproduce Issue
It seemed
that the RF-Jamming was happening mostly after the notebooks were woken up from
some power saving or hibernation modes. I looked for a way to reproduce it and
was able to find the following process to do so 100% of the times:
Please note: During the RF-Jamming, the notebook reinitializes the Wi-Fi card (happens automatically) and reconnects to the Wi-Fi. After that, the issue does not occur any more when you start the speedtest again. It looks like the reason for this is that after the reinitialization, the notebook does not use TXOPs with CF-End frames any more (see section “Setup that causes issue” for more details).
But when you follow the steps above, you can reproduce it again.
Observe Issue
You can use different methods to observe the test above.
- Frame Capture next to the notebook that causes the RF jamming (see section “Introduction”)
- Spectrum Analysis next to the notebook that causes the RF jamming (see section “Introduction”)
- Ping from or to a client within the affected BSA (Basic Service Area)
- Check Eventlog from the notebook that is causing the issue. There is a Netwtw06 5007 Error “5007 – TX/CMD timeout (TfdQueue hanged) and a 10400 NDIS Warning that indicates that the Wi-Fi NIC got reinitiated.
Setup That Caused Issue
With a lot of “try and error”, I tried to narrow down the setup and combination of variables that causes this behaviour. Please note that this is based on my lab results with the equipment I had available, so your situation may vary (especially the part “Wi-Fi Specific Characteristics”). You are more than welcome to ping me with your results, and I will update this post accordingly.
Notebook Characteristics
- WiFi Card: Intel® Dual Band Wireless-AC 8265
- Driver Version: 20.50.0.X
Wi-Fi Specific Characteristics
- SSID with 802.11ac (VHT) capabilities
- Coding: BCC
- Notebook using TXOPs with CF-End Frames
Setup That Caused Issue
I found two ways to remedy this problem:
- Update Driver: The simplest way to solve this problem is to upgrade the Intel® Dual Band Wireless-AC 8265 to a version other than 20.50.0.X. However, if you have hundreds of clients with the faulty driver version, this might be a drag and needs proper planning and execution
- Switch coding to LDPC: An alternative solution I found working for myself is to switch the coding from BCC to LDPC on the AP/radio. Please note that LDPC is only an optional feature in the Wi-Fi Certified ac program (and Wi-Fi Certified n for that matter), so there might be clients that have issues with that.
As
always, please don’t hesitate to hit me up if you have any questions or
different results with this topic
Cheers,
Renzo
Introduction This post is about the effect of rate limiting on Wi-Fi and is inspired by the presentation Troy Martin (@troymart) gave […]
Back in spring 2019, Windows 10 introduced support for WPA3-Personal with its version 1903 update.Almost exactly one year later, they now also […]
Introduction In this blogpost, I’d like to show you how a single SSID with both 802.1X & PSK enabled looks like, what […]
Introduction Many times, there are small adjustments you have to implement in your live Wireless LAN environments. I personally am often faced […]
I recently purchased a refurbished HP Laptop 17-bs1xx. It has an Intel Dual Band Wireless-AC 3168 network adapter, running Windows 10 Home, 64-bit.
Periodically, sometimes every few minutes to every few days, whatever I’m streaming or downloading just stops, and after about 10-20 seconds, the Wifi icon flickers from connected to the not-connected-but-connections-available, and then a few seconds later goes back to being connected.
After complaining to my ISP, they told me it was a device issue, as my modem showed no downtime. So, my next attempt was to update the drivers and see if that helps. Using the built-in HP Support tool, I updated all drivers to the latest version. Using Intel’s Device Driver tool, I also updated the drivers there, too (both Wifi and Bluetooth were updated). I also made sure to check Windows Update to make sure I’m on the latest version.
After all the updates and reboots, it happened again, and so I checked the Windows Event Viewer. In there, corresponding to each time the Wifi disconnected, I see either one of two messages:
Log Name: System
Source: Netwtw04
Date: 8/12/2018 3:58:21 PM
Event ID: 5035
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: LAPTOP-553FAOH6
Description:
5035 - Driver OSC Pending OID watchdog
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Netwtw04" />
<EventID Qualifiers="49152">5035</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-08-12T21:58:21.374492400Z" />
<EventRecordID>11334</EventRecordID>
<Channel>System</Channel>
<Computer>LAPTOP-553FAOH6</Computer>
<Security />
</System>
<EventData>
<Data>DeviceNDMP2</Data>
<Data>Intel(R) Dual Band Wireless-AC 3168</Data>
<Binary>000004000200340000000000AB1300C000000000000000000000000000000000000000000000000057445256</Binary>
</EventData>
</Event>
Log Name: System
Source: Netwtw04
Date: 8/12/2018 3:48:51 PM
Event ID: 5007
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: LAPTOP-553FAOH6
Description:
5007 - TX/CMD timeout (TfdQueue hanged)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Netwtw04" />
<EventID Qualifiers="49152">5007</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-08-12T21:48:51.688121200Z" />
<EventRecordID>11327</EventRecordID>
<Channel>System</Channel>
<Computer>LAPTOP-553FAOH6</Computer>
<Security />
</System>
<EventData>
<Data>DeviceNDMP2</Data>
<Data>Intel(R) Dual Band Wireless-AC 3168</Data>
<Binary>0000080002003800000000008F1300C00000000000000000000000000000000000000000000000004D4D41431C001509</Binary>
</EventData>
</Event>
Searching through HP and Intel support forums, I’ve seen people asking this question, but no other solutions than «try updating your drivers.» There also doesn’t seem to be any relevant answers here on SU, either.
Is there anything else I can do besides invoking my extended warranty plan, which will take 1-2 weeks? It’s not annoying enough to warrant losing my box for a few weeks, but it is annoying enough that I’d really like to try and fix it.
Im posting this here because it has taken me over a week to find a solution to this problem with has driven me beserk. I couldn’t find any info on any forum, so I thought I would post the info here in case its of use to anyone else.
I have an HP Spectre running WIndows 10. It has a Intel Dual Band Wireless-AC 8260 wifi card running teh latest drive v 20.70.0.5
It was continually having wireless connectivity issues. Although the wireless didn’t disconnect I experienced up to 100% packet loss. During my troubleshooting I noticed these two events continually appearing in the Windows System Event Log:
Event 5007, Netwtw06
5007 — TX/CMD timeout (TfdQueue hanged)
Event 10400, NDIS
The network interface «Intel(R) Dual Band Wireless-AC 8260» has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver requested that it be reset. This network interface has reset 5 time(s) since it was last initialized.
Other devices on the wireless network were functioning perfectly, including notably several HP Elite Books with the newer 8265 card.
After some time trying to diagnose the fault I contacted HP support, who actually responded very quickly. Their advice was a clean install of the network card driver. When that failed it was then recommended to reinstall the laptop, which in this case was easy for me as it didn’t have any critical files on it. However, neither solution worked. I even tried rolling back the driver to every version between 19 and 20. Still nothing.
I then spoke with Ruckus technical support. They also were very quick to answer. They were aware of a known issue with these specific network cards, and gave me something to try — which ultimately worked!
The problem affects Intel Intel Dual Band Wireless-AC 8260 connecting to 5Ghz 802.11ac networks with Channelization set to 80Mhz. Changing the channelization setting from 80Mhz to Auto on the AccessPoint resolved this issue.
Hope this info is useful.
Недавно я приобрел восстановленный ноутбук HP 17-bs1xx. Он имеет двухдиапазонный сетевой адаптер Intel Wireless-AC 3168, работающий под управлением Windows 10 Home, 64-разрядный.
Периодически, иногда каждые несколько минут или каждые несколько дней, все, что я транслирую или скачиваю, просто останавливается, и примерно через 10-20 секунд значок Wi-Fi мигает из подключенного к не подключенным, но доступным соединениям, а затем несколько секунд спустя возвращается к соединению.
После того, как я пожаловался моему провайдеру, мне сказали, что это проблема с устройством, так как мой модем не показывал время простоя. Итак, моей следующей попыткой было обновить драйверы и посмотреть, поможет ли это. Используя встроенный инструмент поддержки HP, я обновил все драйверы до последней версии. Используя инструмент Intel Device Driver, я также обновил там драйверы (были обновлены и Wifi, и Bluetooth). Я также проверил Центр обновления Windows, чтобы убедиться, что у меня последняя версия.
После всех обновлений и перезагрузок это произошло снова, и поэтому я проверил Windows Event Viewer. Там, в соответствии с каждым разом, когда Wi-Fi отключался, я вижу одно из двух сообщений:
Log Name: System
Source: Netwtw04
Date: 8/12/2018 3:58:21 PM
Event ID: 5035
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: LAPTOP-553FAOH6
Description:
5035 - Driver OSC Pending OID watchdog
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Netwtw04" />
<EventID Qualifiers="49152">5035</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-08-12T21:58:21.374492400Z" />
<EventRecordID>11334</EventRecordID>
<Channel>System</Channel>
<Computer>LAPTOP-553FAOH6</Computer>
<Security />
</System>
<EventData>
<Data>DeviceNDMP2</Data>
<Data>Intel(R) Dual Band Wireless-AC 3168</Data>
<Binary>000004000200340000000000AB1300C000000000000000000000000000000000000000000000000057445256</Binary>
</EventData>
</Event>
Log Name: System
Source: Netwtw04
Date: 8/12/2018 3:48:51 PM
Event ID: 5007
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: LAPTOP-553FAOH6
Description:
5007 - TX/CMD timeout (TfdQueue hanged)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Netwtw04" />
<EventID Qualifiers="49152">5007</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-08-12T21:48:51.688121200Z" />
<EventRecordID>11327</EventRecordID>
<Channel>System</Channel>
<Computer>LAPTOP-553FAOH6</Computer>
<Security />
</System>
<EventData>
<Data>DeviceNDMP2</Data>
<Data>Intel(R) Dual Band Wireless-AC 3168</Data>
<Binary>0000080002003800000000008F1300C00000000000000000000000000000000000000000000000004D4D41431C001509</Binary>
</EventData>
</Event>
Просматривая форумы поддержки HP и Intel, я видел людей, задающих этот вопрос, но нет других решений, кроме как «попытаться обновить драйверы». Там также, кажется, нет соответствующих ответов здесь, на SU, либо.
Могу ли я сделать что-нибудь еще, кроме того, чтобы вызвать мой расширенный гарантийный план, который займет 1-2 недели? Это не достаточно раздражает, чтобы оправдать потерю моей коробки в течение нескольких недель, но это достаточно раздражает, что я действительно хотел бы попытаться исправить это.