2 Replies Latest reply on Sep 15, 2017 2:39 AM by CMS2

    DH61WW Intel 82579LM Gigabit Code 10 Windows 10

    CMS2

      Hi,

       

      We have an issue with the Intel DH61WW motherboard, with Windows 10 (currently build 1703). We are a school, with around 100 PCs that have this motherboard.

       

      Randomly, when the PC is turned on the Intel 82579LM network connection shows with the error: "This device cannot start. (Code 10) {Operation Failed} The requested operation was unsuccessful."

       

      We have updated to the latest Intel network driver (25 July 2016, version 12.15.31.4).

       

      The motherboard has the latest BIOS, 0120.

       

      The solution is simple, to turn the PC off and back on, but it can take two or three attempts, and inevitably is frustrating.

       

      Has anyone encountered this problem, and have a fix?

       

      Thanks

        • 1. Re: DH61WW Intel 82579LM Gigabit Code 10 Windows 10
          N.Scott.Pearson

          Well, for starters, this board is not supported by/with Windows 10, so I am not surprised to hear of this issue. In this case though, I am thinking it likely that this is a BIOS issue - that the BIOS is leaving the board's MAC in a bad state. If this is the case, considering that this board is in EOL status (and Intel has exited the Desktop Boards business), no BIOS fix will be possible.

           

          Are you using PXE boot? Even if not, you may have it enabled. Try disabling it. This is done in the Boot section of BIOS Setup.

           

          Hope this helps,

          ...S

          • 2. Re: DH61WW Intel 82579LM Gigabit Code 10 Windows 10
            CMS2

            I was surprised, as Intel provide Windows 10 drivers for the NIC chipset. Also in the last few years I've never had an issue with a core chipset like this failing to work in a newer version of Windows. Scanners and printers, yes, but not audio or NIC.

             

            The majority of these machines don't have PXE boot enabled, but one that does doesn't seem to exhibit the problem. I wonder if this is because it leaves time for the chipset to come live.

             

            I'm trying a second fix also, to disable fast startup in Windows 10. This is done using a registry change. Should be evident Monday morning if this has worked. http://www.edugeek.net/forums/windows-10/171184-disable-fast-startup-power-management-option-via-gpo.html