NIC only being enabled after restart

[mulderite]

We have a Stone PC manufactured in 2012 that has developed a very odd problem with its network adapter and I just wondered if anyone else has seen anything similar?

 

Earlier in the week we noticed the PC was offline following our morning power-up. On investigating we found no issue with the cable or socket so started to look at the onboard NIC. We discovered that whenever the PC is switched on from cold, the NIC would never work (it would show in device manager as 'The device cannot start (Code 10)'), until the PC was restarted - after which it would come up ok and connect with no issues. Next day same again, PC would not connect on initial power up but work fine after a restart.

 

The adapter is an INTEL 82579V model. We have tried various drivers (the current being one dated 26/7/2016), resetting/flashing the BIOS, even reimaging the PC - but it still exhibits the same behaviour with the network adapter. We have an entire IT suite full of these models which we will be replacing in Easter, but I am planning on using them in various other places around school - so just in case others started showing the same issue I was interested to see if anyone else has experienced anything like this and found the solution?

 

Many thanks!

[FragglePete]

Ah. We've this exact same issue on a number of stone PCs from the same era and NIC model - started really after moving over to Windows 10 a few years back.

 

We had to upgrade the Firmware on the NICs on all those PCs and that resolved the problem. However, we are now seeing similar behavior on a couple of PCs that we have already upgraded, and doing a BIOS update of the motherboard has seemed to resolve the issue. We're monitoring it closely but seem ok so far.

 

So, update the Firmware on the NICs, should resolve it. I've got the .exe file we've used here if you need it. PM me.

 

Pete

[Sepal]

However, we are now seeing similar behavior on a couple of PCs that we have already upgraded, and doing a BIOS update of the motherboard has seemed to resolve the issue. We're monitoring it closely but seem ok so far.

 

Do you know what model of motherboard it's been occurring with? This sounds like a far more common issue than I'd thought when it cropped up at our site.

[FragglePete]

The motherboard is a DH61CR and the BIOS updates obtained from here:

drivers.stonegroup.co.uk - /ftp/Bios/Desktop/Archive/Intel/Current/

 

Stone computers do have an advisory that you don't go higher than version 0116. And you install each on incrementally - don't go straight to 0116. https://kb.stonegroup.co.uk/index.php?View=entry&EntryID=267

 

I found that I had to do a Flash Recovery to get it onto 0116, that is removing the BIOS Jumper from the motherboard and switch on with USB in with the sole BIOS file on. Once done, you switch off, put jumper back on and cycle the power. Since doing this on two PCs we've not seen the issue again.

 

Hope it helps.

 

Pete

 

PS. Obviously, do at your own risk with BIOS updates, but we've successfully done two PCs this way.

[StoneGroup_JackW]

Hi @mulderite, if the above solutions do not work please give me a call on 01785 786831 and i will pop you down to our technical support team who will be able to help further. Kind regards Jack

[foofighterjim]

We had the same issue, we just disabled hiberboot on those machines. As we only have them in one OU we just did it via GPO, you may be able to use a WMI filter if yours are over multiple OUs or have other hardware in there.

 

Simple Reg entry will do it:

 

HKLM> SYSTEM\CurrentControlSet\Control\Session Manager\Power

Value Name: HiberbootEnabled

Value Type: REG_DWORD

Value Data: 0x0 (0)