Built in ethernet - switching ID

Soldato
Joined
2 Nov 2013
Posts
4,321
This is a bit of a weird one. My motherboard has a built in ethernet port, which is an Intel 82579V Gigabit network connection.

Occasionally when I start up the computer, it will instead be identified in device manager as an 82579LM, and will not work. It shows with the little exclamation mark symbol next to it saying it isn't working.
If I right click anything in device manager, and choose scan for hardware changes, it immediately re-identifies correctly, and works fine.

I've tried making sure the drivers are fully up to date, but still happening.
 
download the correct drivers.

unplug your ethernet cable
go to device manager
right click the device uninstall the device.
Install the correct drivers.
reboot if required.

Sounds very much like Windows Downloading a generic driver & using that instead of the one you provided

this should fix the issue
 
Sorry for the delayed response, had a hectic few weeks!

Thanks for the advice. I have given it a try - also had to uninstall the Intel network connections software before it would allow me to re-install the lot.

I will let the forum know after a few restarts whether it seems to have done the trick.
 
Unforetunately, the re-install has not done the trick.

I haven't yet dared the Bios update. It's an Asus P8Z68-V, and has different Bios files listed for XP and Vista, and for 7 and 8 - but nothing listed against windows 10. Knowing horror stories about Bios flashing being very delicate and prone to lunching your mobo, I'm a bit reluctant...
 
The ethernet port you mean?

I'm only using it because my wireless connection is also a bit dodgy (occasionally ping to the router will be terrible, and the router has to be reset). It seems like whatever method I want to use, I sometimes have to reset something when I turn my computer on!

I'm about to move house anyway, and will sort out the router one way or the other then (I've hesitated in case it's because there's some form of interference where I am currently). I will have to use wireless at the new house, because the internet socket is in the dining room of all places. :rolleyes:
 
Unforetunately, the re-install has not done the trick.

I haven't yet dared the Bios update. It's an Asus P8Z68-V, and has different Bios files listed for XP and Vista, and for 7 and 8 - but nothing listed against windows 10. Knowing horror stories about Bios flashing being very delicate and prone to lunching your mobo, I'm a bit reluctant...
Win7 version should work fine with win10, whats your bios version btw?
 
Hi OP
Thanks for pointing out that the difference between the Intel 82579V and Intel 82579LM. I gave up fixing the issue ages ago and just kept doing the scan for hardware changes trick to fix it. Not sure if I can still be bothered to play around and find the fix though :D

I have the exact same issue with the same board.

For what its worth I am running 3603 bios with P8Z68-V board and I still have the issue.

EDIT: Have you tried the drivers from Intel directly? I have not tried this yet but might be worth the shot. https://downloadcenter.intel.com/do...k-Adapter-Driver-for-Windows-10?product=52963
 
Last edited:
I'm still using an Asus P8Z68-V Gen3 board, the Lan drivers I use are latest ones from Intel, no issues with my ethernet (Intel 82579v) at all, running latest BIOS as well.

Checking device manager, drivers are dated 25th July 2016. Yes I'm using Win10 Pro x64.
 
Try the latest bios as that will also update the firmware for onboard devices such as lan, if that doesnt work i can do a custom bios and update the lan rom to latest version.
 
Mobo Bios do not update LAN etc. Firmware's.

This was a known issue back on my Asus Rog Z68 AFAIR, Intel fixed it via a Firmware update.

If you keep the Win Dev Man open and refresh it you can see it swaps between the two device names.
 
It is fixed as I said above, its on Intel Download site and its a Firmware for the NIC not a Bios or Driver.

"Detailed Description


This utility resolves an issue where during system resume, the Intel® 82579V Gigabit Ethernet PHY Network Connection erroneously reports the device id as an Intel® 82579LM Gigabit Ethernet Controller Network Connection, resulting in a Windows* Code 10 error and loss of network connection.

Not all systems with the Intel 82579V Network connection will see this problem. Systems using Microsoft Windows* 8 are more susceptible to the issue."


https://downloadcenter.intel.com/do...Ethernet-PHY-Network-Connection?product=52963
 
Back
Top Bottom