- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have Intel AC7260 and there is a problem: after every wake from sleep mode i have limited access and no connection to the Internet. I can't ping router and any device in the network... Sometimes helps to reconnect but most often I need to reboot :/ Can someone help me please?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23628 Intel® Download Center
Try that one in Drivers Only: section that is appropriate for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the recommendation. I just rolled back to v16.10.0.5 Win 8.1 64bit, and have reconnected successfully out of sleep twice now. I also see I am connected at n. Will see how it goes for the next few days.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
disabling fast startup in windows 8.1 update 1 solves the problem with limited connectivity for me. (driver 17.0.6.1)
altough performance is not so good with this version
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same here. Running driver version 17.0.6.1 and disabled fast startup. Now it resumes properly after sleep and have not had noticeable issues for a couple of days.
Can't comment on performance as I have not measured it before/after but does not seem any different.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Turns out I still get times when I can't connect. I.e 17.0.6.1 with fast start-up disabled does not solve this - but it seems better than it used to be.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue as everyone else when resuming from hibernate or sleep.
System: Dell Inspiron 1747
BIOS: A14
OS: Win 7 x64 Ultimate
Memory: 8GB
Wireless Card: 7260HMW
Wireless Driver: 17.1.0.19 (7/21/2014)
I haven't tried the admin drivers nor have I tried completely removing the 7.1.0.19 drivers and re-installing them. I upgraded from Wireless_17.0.6_s64.exe -> Wireless_17.1.0_s64.exe, and I'm doubting it will help to re-install... Next thing to try though.
Looked at the event logs and noticed the following. Hope it helps with the issue:
Information9/16/2014 11:03:00 PMKernel-Power42(64)The system is entering sleep.
Sleep Reason: System Idle
Information9/16/2014 11:03:01 PMNETwNs648000None
The description for Event ID 8000 from source NETwNs64 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\NDMP5
Intel(R) Dual Band Wireless-AC 7260
The specified resource type cannot be found in the image file
Warning9/16/2014 11:03:01 PMWLAN-AutoConfig10002NoneWLAN Extensibility Module has stopped.
Module Path: C:\Windows\System32\IWMSSvc.dll
Information9/16/2014 11:03:01 PMService Control Manager7042NoneThe TCP/IP NetBIOS Helper service was successfully sent a stop control.
The reason specified was: 0x40030011 [Operating System: Network Connectivity (Planned)]
Comment: None
Information9/16/2014 11:03:01 PMService Control Manager7036NoneThe TCP/IP NetBIOS Helper service entered the stopped state.
Information9/16/2014 11:03:01 PMKernel-General1NoneThe system time has changed to 2014-09-17T04:03:01.500000000Z from 2014-09-17T04:03:03.110512400Z.
Information9/17/2014 1:26:14 AMKernel-General1NoneThe system time has changed to 2014-09-17T06:26:14.500000000Z from 2014-09-17T04:03:01.511000600Z.
Information9/17/2014 1:26:15 AMNETwNs647036NoneThe \Device\NDMP5 service entered the Intel(R) Dual Band Wireless-AC 7260 state.
Information9/17/2014 1:26:16 AMService Control Manager7036NoneThe Windows Image Acquisition (WIA) service entered the running state.
Information9/17/2014 1:26:15 AMNETwNs645010NoneThe description for Event ID 5010 from source NETwNs64 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\NDMP5
Intel(R) Dual Band Wireless-AC 7260
The specified resource type cannot be found in the image file
Error9/17/2014 1:26:15 AMNETwNs645001NoneIntel(R) Dual Band Wireless-AC 7260 : Could not allocate the resources necessary for operation.
Error9/17/2014 1:26:16 AMNETwNs645006NoneIntel(R) Dual Band Wireless-AC 7260 : The version number is incorrect for this driver.
Information9/17/2014 1:26:16 AMNETwNs645010NoneThe description for Event ID 5010 from source NETwNs64 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\NDMP5
Intel(R) Dual Band Wireless-AC 7260
The specified resource type cannot be found in the image file
<s...- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are getting the same thing philsward
We also get a BSOD from NDIS The NDIS drivers were designed from Clarkson University back in the early 90's and I have not used NDIS for years. We would use this to enable multi protocol stacks when we needed to run IPX/SPX, VINES IP, and TCP/IP on a card.
Here is what I do know. When you look at the 7 layers of the OSI Model and you introduce software to manage a firewall you look to install a SHIM between 2 of the layers to open the packets and look into them to determine what to do with the packet. Some providers use the deterministic network enhancer. I have never found these to work.
I do believe there is some junk left behind from Norton after we removed it based on the support articles from Microsoft. Here is one theory http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/windows-81-bsod-bugcodendisdriver/3c34652d-c4b0-4ad6-b308-be4811a4c785 http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/windows-81-bsod-bugcodendisdriver/3c34652d-c4b0-4ad6-b308-be4811a4c785 which is what Lenovo gave us.
Anyway as a result of my testing overnight I found that the card to not power up this morning.
The good news... is my error is a little more specific. "Miniport Intel ... had event Fatal Error. The miniport has failed a power transition to operational power"
These cards/ports are smaller than any others we are using I believe and therefor I'm stuck. I will look at finding a card but I think it is time to send 100% of these computers back to Lenovo.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unless I've had that "Norton Security Scan" (tiny little scanner installed from other software), I haven't ever had Norton installed so I doubt that would be it. I've seen weirder so I wouldn't dismiss it. Haven't noticed any NDIS issues either though.
I completely removed the ProSet software last night and checked device manager to find the 7.0.6 driver loaded after 7.1.0 was uninstalled. I removed 7.0.6 and "deleted device drivers" as well. Upon reboot, I didn't have a driver installed which I expected, so I re-installed the proset 7.1.0. Fired the computer up this morning and had the exact same problem. I honestly figured the event log that mentioned: "Intel(R) Dual Band Wireless-AC 7260 : The version number is incorrect for this driver" would be fixed but alas, it is still showing up in the logs.
Next step is to try the administrator IT drivers...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installed the 7.1.0 "Administrator IT" drivers from "Wireless_17.1.0_Ds64.zip" and after initial testing, the problem appears to have been resolved.
If I don't respond again with problems you can assume my issue was fixed with the driver only version. This would lead me to point to the ProSet software as the culprit. (crosses fingers this is fixed)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So on top of this card problem we have been working on fixing a Wireless Crashing and Network Outage issue.
As a result of extensive time and money we have determined the root cause of our network and wireless crashes coming from a bunch of systems doing all net multicast and arp broadcast storms. Every one of the systems identified was using this intel Wireless card.
This may be a result of a corrupted driver install from countless driver updates. But I can not longer afford our business being shut down so systems with these cards are banned from our network. All 170 of our new systems are heading back to the manufacturer.
Intel you really missed the boat on this one. If you would like I may have saved our packet traces. And for the record the systems we identified as having the most issues were using the Intel or Lenovo drivers verse the Microsoft drivers. But I am not going to take any more of my time to investigate a solution.
Over and out !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah, I agree.... These driver issues are a major pain in the backside.... I really would have expected Intel to do better on this front.
At worst case, get the driver to perform a full card reset on resume from power savings. That would most likely fix the problem straight away - then you can start working on debugging the issue properly....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried that one on Win 7 64. Worked mostly, then I got another failure to connect after sleep. Rolled back to 16.6.0.8 which has always worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
joe_intel:
It appears that philsward found a very simple configuration fix to this problem as described in the following post:
/message/253403# 253403 https://communities.intel.com/message/253403# 253403
I've been running on version 17.0.1 with the Power Management option "Allow the computer to turn off this device to save power" enabled and the system has not had a problem waking from sleep for 3 days now. Although the driver should work with this option enabled or disabled, I am personally considering this issue resolved on my laptop (XPS 15 L521x, Win7 Pro 64). However, it would be interesting to find out if this works for others as well so perhaps you can get a few additional folks testing this and have engineering look into why the driver fails to wake when this option is disabled.
D
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not prepared to declare victory with the 17 driver(s). The latest I've tried is 17.1 and it, like all the other 17s, periodically fails to wake up, no matter what the power saving setting. Win 7 64
16.6 is still the driver that always works for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dilburt's workaround does not appear to work for me. I still have no access to a 16.x driver for Windows 7 (the only ones I've found are for Windows 8/8.1), so I've instituted a workaround via a scheduled task that will disable and re-enable my wifi adapter on unlock. The workaround causes wakeup times to effectively be a minute long and has me very unhappy with the situation, but it is STILL better than the alternative.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
v. 16.1.5 driver, win 7: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23183 Intel® Download Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you search at Intel?
Here's 16.7: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23491 Intel® Download Center
Here's 16.10: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23628 Intel® Download Center
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There you go.
I wish Joe or Kevin would chime in here and tell us what changed between 16 and 17 that makes the 17s not wake up. Consistently wake up, that is.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page