I don't know anything about the motherboard screw issue, but maybe you do have some type of hardware failure. I don't have any other ideas.
Mark H
I don't know anything about the motherboard screw issue, but maybe you do have some type of hardware failure. I don't have any other ideas.
Mark H
I've a Gigabyte G1.Sniper.M3 MB with 82597V chip and the connection drop problem as well. I tried different driver, settings, cables and switches without success. Bought a € 10,- TP-Link PCIe NIC with Realtek chipset and all problems are gone. But that’s not satisfying.
For me it's clearly a driver issue and I ask myself if it's the same issue as discussed for Linux here http://communities.intel.com/thread/26804?start=0&tstart=0
Some clever guys take a look at the source code and became aware that the 92579LM chip has "K1 power save" optimization and at 1Gb speed this is causing the chaos. Disabling the K1 power save optimization in a patched driver fixed the problem.
@Intel: the Linux solution dated June 2013, Intel's latest Windows driver dated May 2013. Is it possible to disable and test the „K1 power save" optimization for the Windows driver as well?
Ralph
I have the same NIC on a ASUS P8Z68 Deluxe.
I recently updated my Intel NIC driver to 18.3 and started getting e1cexpress, Event ID 27, Network link is disconnected issues. I ran the 82579VSKUW64e in command prompt and it said no update needed.
I uninstalled 18.3 and went back to my old 16.8.1 driver and the errors stopped appearing in Event Viewer. I'm pretty sure it's a driver related issue at this point.
I noticed that 18.5 is available on Download Center, has anyone tried 18.5?
I'm seeing an issue with one of our computers that has an Intel 82579LM adapter. We were having an issue with one of our software packages generating errors and the vendor suggested it was related to a network adapter timing out or going to sleep. That didn't sound likely to me but I reviewed the event log and did find a stream of Warning messages with ID 27 saying Intel(R) 82579LM Gigabit Network Connection Network link is disconnected. I investigated that message and decided to turn off auto negotiation on the adapter and set the link speed to 100 Mbps Full Duplex. Our application issues disappeared and we are not currently experiencing problems.
When I review the event log I still see these warnings being logged. I have confirmed that the adapter is fixed at 100 Mbps Full Duplex. My guess is that the process that tries to auto negotiate and also logs the events is still active but that it is not actually having an effect on the actual adapter. Can you confirm if this is the case? I would very much like to eliminate the warnings for this issue from the event log and I'm a bit confused as to why the event log makes it appear that auto negotiation is still happening even though it is turned off on the adapter.
Thanks,
Scott
I just tried the latest 18.5 drivers and the same error shows up in the event log. However I was using 18.3 for 2 months and never experienced disconnects, at least not that I know of.
I went back to 16.8.1 and the error stops appearing in eventlog. I guess the old saying goes, if it ain't broke don't fix it.
Hi all
this is my first post as i thought id never resort to this but i have an isue with my 82579v intel ethernet adapter
i tried to install windows 8 and during the install it said it wasnt compatible and to uninstall it to continue... i uninstalled it all and then i had windows 8 with no network so i rolled back to windows 7 even though i had to put a new copy and now i have a wondows.old folder. I tried downloading every driver for this i coiuld find off intel but none work... most of them say that they are corrupt or damaged when i extract to run
i have no idea what the latest diver is as they all dont install on my machine
PLEASEE HELLPPPPP
Hi,
I'm not sure what's going on with your network connection, but I have at least one idea.
You might be seeing the problem fixed by the utility at https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22026. I would give that a try.
The Windows 8 download is at https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=21642. (This same webpack works for Windows 7 too.) If the file is causing problems, there is an older version of the download at https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23070. You don't need to extract these files to run them. Just run the exe file to install the drivers. I don't know what brand and model of your computer or motherboard you have, but you might want to try the drivers from the manufacturer's website. Those files are usually the versions tested with your system.
I hope this helps.
Mark H
hi ive tried using the utlitiy and it always says it corrupt when trying to run it, also im using a z77 asus sabertooth mobo. ive used the cd that came with it and ran the drivers and they installed but still no connection
The posted files are good, so I don't know why you are getting a message that shows they are corrupt. Possibly there is something wrong with your installation of Windows or your connection isn't allowing you to get the entire file you are trying to download. You might want to try downloading the files from a different computer.
Mark H
Hi,
For my concern I got the bad chipset detection 82579LM instead of 82579V on a Asus P8Z77-V and therefore the code error 10.
Bios is up to date together with intel drivers.
When I applied the command patch Lewisville NVM ASKU, they're are 2 independant issues, either the command line says AdaptorFailure and the prog ends or it's crash after the 'Scanning' line on the cmd terminal.
I heard on other forums that the screw located near the chipset on the MB could cause this sort of code error 10.
Any guess ?
ty
I don't know anything about the motherboard screw issue, but maybe you do have some type of hardware failure. I don't have any other ideas.
Mark H
I've a Gigabyte G1.Sniper.M3 MB with 82597V chip and the connection drop problem as well. I tried different driver, settings, cables and switches without success. Bought a € 10,- TP-Link PCIe NIC with Realtek chipset and all problems are gone. But that’s not satisfying.
For me it's clearly a driver issue and I ask myself if it's the same issue as discussed for Linux here http://communities.intel.com/thread/26804?start=0&tstart=0
Some clever guys take a look at the source code and became aware that the 92579LM chip has "K1 power save" optimization and at 1Gb speed this is causing the chaos. Disabling the K1 power save optimization in a patched driver fixed the problem.
@Intel: the Linux solution dated June 2013, Intel's latest Windows driver dated May 2013. Is it possible to disable and test the „K1 power save" optimization for the Windows driver as well?
Ralph
I have the same NIC on a ASUS P8Z68 Deluxe.
I recently updated my Intel NIC driver to 18.3 and started getting e1cexpress, Event ID 27, Network link is disconnected issues. I ran the 82579VSKUW64e in command prompt and it said no update needed.
I uninstalled 18.3 and went back to my old 16.8.1 driver and the errors stopped appearing in Event Viewer. I'm pretty sure it's a driver related issue at this point.
I noticed that 18.5 is available on Download Center, has anyone tried 18.5?
I'm seeing an issue with one of our computers that has an Intel 82579LM adapter. We were having an issue with one of our software packages generating errors and the vendor suggested it was related to a network adapter timing out or going to sleep. That didn't sound likely to me but I reviewed the event log and did find a stream of Warning messages with ID 27 saying Intel(R) 82579LM Gigabit Network Connection Network link is disconnected. I investigated that message and decided to turn off auto negotiation on the adapter and set the link speed to 100 Mbps Full Duplex. Our application issues disappeared and we are not currently experiencing problems.
When I review the event log I still see these warnings being logged. I have confirmed that the adapter is fixed at 100 Mbps Full Duplex. My guess is that the process that tries to auto negotiate and also logs the events is still active but that it is not actually having an effect on the actual adapter. Can you confirm if this is the case? I would very much like to eliminate the warnings for this issue from the event log and I'm a bit confused as to why the event log makes it appear that auto negotiation is still happening even though it is turned off on the adapter.
Thanks,
Scott
I just tried the latest 18.5 drivers and the same error shows up in the event log. However I was using 18.3 for 2 months and never experienced disconnects, at least not that I know of.
I went back to 16.8.1 and the error stops appearing in eventlog. I guess the old saying goes, if it ain't broke don't fix it.
So I have this same NIC and my computers wakes randomly and it is caused by this NIC as suggested by the "powercfg -lastwake" command. There are no magic packets sent to this specific NIC but I do not want to disable the Wake-on-LAN capability. What is wrong with this? I already upgraded the NVM and am using the latest driver.
Why can't anyone answer here? Intel REP please answer.
Support from Intel and Asus for this issue is very disappointing. I tried all suggestions mentioned here and nothing works. Intel admits that the device has issues, but doesn't realy solves it. Also the Intel NVM utility does not solve the problem.
Asus doesn't even post the latest driver for this device on their site. They still have the 17.3 driver while Intel has 18.5. (I gess they gave it up).
I reported the Issue to Asus and they only tolp me to do the driver and BIOS updates. Some weeks ago they send my issue to their experts in Taiwan, but I didn't get a solution yet.
I have an Asus P8Z77-I Deluxe and get a code 10 error after a cold boot, but after a restart the device works fine. So I tried to use the sleep mode instead, because then the device does not do a cold boot. That works fine, but then a different issue appears: the device awakes the PC from sleep for no reason.
It seems that the WOL implementation of the device is totally messed-up. Deleting al that feateres doesn't help either.
The only solution is to completely disable the device (solder it out maybe) and put a LAN card in your PCI slot (without an Intel device of course), like many other users did already.
I my case I can use the onboard WLAN device, but that will give me a 300MB connection in stead of a GB connection.
For now there is no other solution I think.
Please everyone: avoid using any motherboards with an 82579 device!!
So what can we do here? Intel NICs are known to be of higher quality than their competitors but why this error?! Intel, you better reply now!
I found a solution for my Gigabyte G1.Sniper.M3 and Windows 8 x64:
1. flashed modified BIOS found here Z77 Modified Bios
2. updated Intel ME driver found here Intel ME 8: Management Engine Driver
3. updated Intel 82579L driver found here: Intel Network Adapter Driver for Windows 8
No more connection drop problems. It looks like the whole problem is related to Intel Management engine.