Intel® Desktop Boards
Peer-to-peer support only
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
11462 Discussions

Network Adapter will not start on cold startup.


Hey guys, I need your help.


I have been trying to fix this problem for 3 days now with no success.

Symptoms: On COLD STARTUP during BIOS POST initializing, network adapter will not turn on, no green light. After boot, device manager shows correct name of adapter Intel 82579V (FYI integrated) with yellow marking. The driver is loaded but has not started as indicated in the System information. If I reboot or disable the driver and then enable it, the network adapter will then turn on. Subsequent boots will keep the adapter working, but if I shutdown the PC completely and then restart, then the network adapter will be turned off. When I startup the PC with the power off (cold start S5 soft-off state), the network adapter will not start and when I check the adapter's properties-details-power data, the current power state will be D3, which means no power provided.

What I have tried:

1. Installed latest driver, resulted in same problem.

2. Installed the Intel NVRAM update to correct the chipset name of the adapter 82579V from 82579LM, resulted in same problem.

3. Installed a new CMOS battery, resulted in same problem.

4. Defaulted BIOS settings, resulted in same problem.

5. Jumped the BIOS pins and reset with full power cycle, resulted in same problem.

6. Jumped the Intel ME Engine pins and reset, resulted in same problem.

7. Basic checks: Reseated all cables. Checked the integrated adapter, no visual problems. Motherboard is less than 1 year old. Capacitors look fine.

8. Re-installed Windows, resulted in same problem.

9. Checked the network adapter WITHOUT Windows installed, resulted in same problem. Cold start, no power, but if you reboot from BIOS again, the adapter will turn on.

10. Tested with different Power Supply, resulted in same problem.

11. Oh yeh, unchecked all the power saving features under power management for network device, resulted in same problem.

12. Check BIOS LAN was enabled, resulted in same problem.

Now here's where I need your help. I already did all of the above. The key check that I made is that WITHOUT the Windows and drivers installed, the problem still occurs, adapter does not start on cold startup, but if you reboot with just the BIOS installed, the green light will come on indicating the adapter now has power. That would indicate a problem in the BIOS POST not starting the adapter from a soft-off state or a mechanical off state.

Note: A related problem that occurred at the same time that this network adapter issue occurred is that if I shutdown the PC and then I shut off the surge protector that the PC is connected to, or if I just remove the plug from the PC, then I cannot restart the PC with the power button switch. Even with the new CMOS battery in, if I go from no power (G3 Mechanical Off), to plugging back in and starting the PC, it will not turn on. If I remove the battery while the PC is still plugged in, it still will not start. It will only start if I disconnect the power (Mechanical Off) and then remove the battery and then plug back in, and then hit the power button, then the PC will start.

It seems like there is a problem in the power settings within the BIOS, but even with a fresh BIOS Jump and default settings, results in the same problem.

My Specs:

Windows 7 32bit

DH61CR Motherboard (integrated Network adapter 82579V)

I5-2500 CPU

No additional PCI cards

Corsair PSU VS650

All Drivers are up-to date.


All Windows Updates installed.


Latest BIOS installed.

Thanks in advance for your help.

0 Kudos
7 Replies
Community Manager

Hi Ralph50,



Thank you for posting at Wired Communities and provide all the detail information. In case you have a spare standalone network adapter, you can try installing on the board and check if the same issue occur. As this is an onboard NIC on the Intel board, I can assist you to forward your inquiry to the board support ,they can further check on this.








Thanks for your suggestion, but installing a standalone network adapter is not going to help the issue of understanding why this is happening.

There has to be someone out there that has some knowledge regarding a BIOS conflicting with its own MB network adapters.


I'm having the exact same problem, but under Windows 10. Machine specs are:

I5-2500 CPU @ 3.3 GHz LGA1155

ASUS motherboard, P8Z68-V-PRO-GEN3-ASUS 3802N

4 gigs of DDR3 1333 memory

INTEL 82579 Gigabit LAN onboard.

After a cold start, no LAN connection, but after a Windows restart the LAN will connect. Sounds almost like a timing issue.

Has there been any progress on a fix for this?

Super User Retired Employee

This is more of a question for Asus than for Intel. Based upon my experience, this set of symptoms points to an issue in the Asus BIOS...




I have the same problem with my packad bell system, as TKF750 user above.

I discovered that I got this problem when upgrading from Windows 7 to Windows 10, and after

a Windows 10 larger updates that was pushed out from Microsoft.

But after that update I have continues problem.

I have the Intel 82579V, with driver version

The system is Packad Bell with Intel Core i5-2320 CPU.

At power on, in 90-95 % of the times the LAN connection does not start. After restart it works, until I power off.

When power on again I have the same problem.

It could be HW, but why at the same time when updating the SW, and also some times the LAN HW Intel 82579 starts OK.

Seems to be some race condition between HW start and Driver to start?

Or it is just an unlucky case that HW error was coming the same time of SW update....

(Changed to SSD disk when upgrading to Windows 10, but that should not impact this)

When the system is up an running I have never seen any problem with the Intel 82579V, it works perfect without any problems on the gigabit LAN network even under high load conditions.

Anyway if there is a way to trace this problem, suggestions or test that could be done, I would be happy.

All the best


Super User Retired Employee

See information in this conversation: . Try using the script I described.

Hope this helps,


Valued Contributor II


I had the same problem after some Windows 10 update on my notebook with embedded 82579V card.

To fix this problem I used this tool:

Execution report for Intel(R) "LVDASKU" tool.

Generated on Sun Nov 26 00:54:12 2017

1 Intel(R) device(s) were discovered.

1. Adapter # /Bus/Device/Function: (1, 0/25/0)

1. ID: 8086/1503/1179/0001

1. Branding: Intel(R) 82579V Gigabit Network Connection

1. MAC Address: E8xxxxxxxxxx

1. EEPROM size: 2048

This device matches the [match] section.

Value read from 776:20: C069

This is an 82579V device.

There are 1 device(s) that match the required inputs.

Of these, 1 need(s) updating.

This device's NVM/EEPROM needs updating.

This device's Flash will not be updated.

Wrote 1503h to NVM offset 000Dh

Verified 1503 at offset 000D

Special: writing 00D6 at 0005

Checksum updated.

1 matching devices found.

1 devices updated.