4695AGN Adapter Hang and Event ID 5002, 5005 In System Event Log

[idata]

Intel Incident 8000385293

Event ID 5002 (many) followed by 5005. Tried updating driver. Newer ones would hang the adapter causing re-boot to reset it; older ones would recover, but still 5002's and 5005 in the log. Only happened when streaming (like watching a ball game, etc.). Bought a Mini USB-connected wireless N adapter for $10 and the problem(s) went away - must be in the 4695AGN adapter or driver(s), I thought! Continued searching for answer (techies do this by nature). 'net searches on OEM sites and general showed MANY folks having same/similar problem with Intel wireless adapters. Decided to try enabling/disabling stuff in my router. Noticed an option for WMM. Researched it on the 'net. Seemed to only apply to streaming, and other bandwidth-hogging xmissions. Was advised that WMM is sometimes called Ad Hoc Qos Mode. Disabled it in the router (was called WMM there). Found Ad Hoc Qos Mode option under the Advanced Tab in the Configuration Option for my 4695AGN adapter. Changed it to WMM disabled! Re-booted and did some streaming every day for 3 days. No more symptoms!

Changed everything back! Within 15 minutes had an adapter hang while streaming! My driver is ver. 13.4.0.139, which is current distribution for W7 64-bit.

I am soooooo happy! Hope this will help you not to go through a month of maddening trials, or throwing out a perfectly good adapter! I still think the driver is not handling something properly, because the older ones (12.0... and below) keep working without hanging, although you still get a boatload of 5002,5's every 1 - 60 minutes in your System event log!

P.S. I am NOT saying this is your problem; but it sure fixed mine!

[idata]

Hello Wickham,

We at Intel appreciate your feedback in this matter. I will make sure your comment reaches

the proper department for future consideration. Thank you for taking the time to communicate

this issue to us.

We would also recommend contacting your computer manufacturer for an escalation on this behavior, and check if they have also seen this on their systems.

Cheers!