Thanks for the heads up - good to know. I'm guessing Intel labs are struggling to replicate the root cause. I hope they read these posts. Seems I have a handle on personal workarounds and the error that's at the root of the issue. It's clear this is a bad code problem. I hope it won't be long for a reliable fix to come along - assuming Intel are treating the issue with the seriousness it deserves. As I say, in the short term look on the web for a USB N transceiver and use that for the APs that are causing the issue. My Cisco AP seems relatively fine (but not perfect) with N on the old Microsoft drivers and others such as work's TP LINK I have to use the USB N transceiver as I can't get a stable session on that. Means I have to disable and enable the on-board Intel when I move around but at least it's a working solution.
C-