But that's some other problem you have right now, could be anything system related, or your fault. Did you try to remove the device and do a PnP scan to let it be reinstalled again?

I've done a lot of things to try and solve this mess.

What I know is the event error is the same for both drivers when N is enabled. Turn N off and I get a mostly stable connection for both 14.8.8.75 and 15.5.6.48. It seems N is the underlying problem. I do know that I can't uninstall the Intel Proset wireless software 15.6.1 as it reports this version can not be upgraded from the current older product. Uninstall the older product manually. No idea how I am meant to do that. Funny thing is I have 2 instances of that software in my programs and features window. I am guessing there is a mixed up or lost file in there somewhere that prevents me moving back to 14.8.8.48.

Looks like Intel software is not Intel's strongest feature.

C-

Possibly solved issues. As you say klumsch, go back to Microsoft's own WiFi driver version 14.8.8.75 per your instructions. Then reboot.

Then open the wireless driver advanced tag and: Update Driver> Browse My Computer> Let Me Pick From List Of Device Drivers On My Computer> select the Intel WiFi driver and hit OK. This reinstalls NETwNe64. Then reboot. The event errors go away. So the final config is:

• 14.8.8.75 Microsoft WiFi driver with 'N' enabled
• Update the driver to fix the corrupt NETwNe64 file

Only been running for an hour or so, but I'm not seeing the drop-offs or errors yet.

I suspect Intel's newer drivers break the NETwNe64 file in some way and this is what causes the 'N' instability...that's just a guess.

Two points:

1. Intel, get a working driver for your customers. We've bought the kit... you need to keep your end of the bargain
2. Intel, fix your program software. Windows 8 can not uninstall it and there's no manual process to do it either. This is a basic requirement of all windows software. I'm surprised it passed a windows compatibility test.

C-

Thanks for your help, buddy. You got me half way there, the web did the rest

C-

For what it's worth guys - we've been experiencing these same issues in Linux for months.  Sadly when it comes to the Intel drivers there, it's either Intel's way or the highway.  Since these issues rendered my Linux install unusable at client sites, I was forced to transition back to Windows 8.  Luckily I only install driver updates when required so I stuck with the MS Intel wireless drivers.  So based on this thread I dodged a bullet there for my Centrino Advanced-N 6235.

In any event I've decided to transition away from Intel's wireless hardware  These issues have been allowed to continue for far too long both on the Linux and the Windows side.  I'll be receiving the following Linux compatible  component in the mail tomorrow:

WPEA-251N(BT) - 802.11n Wi-Fi + Bluetooth Half Mini Card with Atheros AR9462, WB222

So yeah after years of using Intel hardware nearly exclusively because they were the best - I've decided to move on.  At least in regards to wireless adapters.  I would suggest you all consider doing the same.  However be aware that some laptop manufacturers will lock down the type of wireless adapters you can install on a laptop via the bios.  Thankfully mine does not.

Well, I thought it was all better. Turns out my home Cisco AP is fine running N. My work AP,  a PT Link WA901ND fails on N. The error is:

>>>>>:

The description for Event ID 5060 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP6

Intel(R) Centrino(R) Advanced-N 6235

The specified resource type cannot be found in the image file

>>>>

This seems to be the root cause. I don't get this error on my Cisco AP with N enabled and do get it on the TP Link with N enabled. Go figure.

C-

@cam116 about the event error, try to deactivate LinkLayer (Microsoft LLDP Driver) under network device properties, also if that doesn't work, try deactivating also IPv6 and QOS. Also it's some kind of problem with you Windows installation, I had no problems deinstalling the Intel ProSet software.

Thanks I've done that. Isn't this weird:

LLDP was not enabled. I switched off QoS and IPV6. I then saw the usual error:

>>>

The description for Event ID 8000 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\NDMP46

Intel(R) Centrino(R) Advanced-N 6235

The specified resource type cannot be found in the image file

>>>

Then 1 second later I got this event with the same heading of (NETwNe64):

>>>

The \Device\NDMP49 service entered the Intel(R) Centrino(R) Advanced-N 6235 state.

>>>

Now it's stable on N on the TP Link Access Point.

It may be the TP LINK AP is handling QoS or IPV6 in a strange way than my Cisco at home... or this error is so sporadic that the NETwNe64 part of the driver is not consistent in operation. I'll update later on results.

Do you see these same events after each other in the eventvwr?

C-

Within 10 minutes the same error reoccurs on N and the second event does not show. It must be that there is an inability for the driver to:

The \Device\NDMP49 service entered the Intel(R) Centrino(R) Advanced-N 6235 state.

So it seems to be something to do with the way the AP is interacting with the adaptor that stops the adapter entering the Intel state when using N. This is down to Intel as sometimes it works and other times it does not. Bad code period. The only remedy seems to be to turn off N.

C-

Managed to find a work around until Intel get the driver sorted. I picked up for $45 New Zealand dollars a CNet N wireless USB chip running 'N'. The install is not great as it's for Win 7, so had to clear the hang by killing the install on Cisco EAP install part. But after a reboot, plug the little thing it in to the USB socket and it flies. This is a cheap way to get you going until Intel deliver. All for $20 US or there about. Website for CNet is www.Cnet.com.tw and the product is CQU-906. Short term fix to get you over the line.

Thx

C-

Tried the new 15.8.0 driver and its much worse now. Even though I disabled 802.11n its really unstable.

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-

Well, I looks like it has been 6 months since this issue first appeared, with 34 pages of users here reporting the same issue. It appears clear to me that Intel isn't going to fix this issue. Wireless isn't where they make their big money (as opposed to, say, Netgear or Linksys), and they're probably already rolling out the successor to this awful card, so I expect they're just going to let us all suffer.

So, here's what I did to finally solve the problem once and for all:

1. Remove the cover from the bottom of the laptop covering the wifi card (for the Samsung, this requires taking the entire bottom cover off)
2. Remove the Intel card.
3. Replace it with any of: Raylink RT3592 or RT3290 or Broadcom 94313 or 94312 or an Atheros AR5B195 or AR5B22 card.
4. Throw the Intel card into the trash. Do *not* sell it on eBay to some other un-suspecting Windows user (you *may* sell/give it to a Linux user, as those drivers *work*)

There. You're done. Basically, you can just search eBay for *any* half-height mini-pci-express wifi/bluetooth card (for a bonus, look for one with bluetooth 4.0) which doesn't say Intel on it. They're only about $20-$25. A small price to pay to have the problem in your past.

Sure, you can rail about the injustice of this... that you shouldn't have to pay extra for a working product.... Intel should stand behind their products.... someone should hold them accountable....    yeah... I get all that. But how much of your life are you willing to give up for that sense of justice? The price of purchasing a *working* wifi card will cost less than 1 hour's worth of your time. How many more hours of your life was this Intel card going to cost you (both in trying suggested workaround settings which don't really work or in lost productivity because your wireless isn't working)?

Thanks bud.

My Samsung 700T is still in warranty so I'll have to wait till December. I agree replacing the card is the best option right now if you can do that as it's not clear if Intel is looking to remedy the issue??? On searching the web Microsoft refer all these issues back to Intel. Samsung is no help and so It's clearly in Intel's court. I have faith we won't be forgotten, but who knows. If not remedied by December the only answer for me is replace the card as a year is a long time to wait for working drivers. The little CNET USB N transceiver is the best option right now. It is reliable and fast.

I do find the original windows drivers stable on N for my Cisco AP so that's a partial win. If you're reading this for the first time read up the thread on klumsch for instruction to roll back to the windows 8 original driver. For many this will help depending on your Access Point. If it does not then disable the on board and grab a CNET N transceiver per my earlier notes for quick fix and either wait for a driver that works from Intel or replace the card per jemenake above. I also grabbed an Ethernet USB3 NIC for $50 NZ that allows you to plug into a wired network. That's really useful for big downloads if your wireless is unstable. Very hand to have.

Intel, if you do read these notes; in the thread above are details of the problem, an AP model that's affecting me and the events that illustrate the failure of the driver. Good luck.

C-

Well, I'm not worried about warranty issues. My Samsung is less than a week old. There aren't any stickers over the screw-holes which say that I'm voiding the warranty and, frankly, I'm not interested in a warranty which is going to replace a broken-as-designed Intel wifi card with *another* broken-as-designed Intel wifi card. Every account I've read here of people who have sent their laptops back to Samsung for service has reported that it didn't help.