It seems the device stopped working shortly after a few seconds. What are your thoughts on this?
It seems the device stopped working shortly after a few seconds. What are your thoughts on this?
So earlier today, the Intel ethernet controller (I219-V) on the motherboard began behaving erratically and eventually stopped working. It didn’t just stop when you tried to reset the network—it would freeze, refusing to restart or shut down properly. I attempted to update the drivers, but that didn’t help once it was already crashed. I managed to install it once by forcing a restart before other services started, but it still didn’t work. Eventually, I removed the USB-C Ethernet adapter from the laptop and disabled the built-in Intel controller, which resolved the issue. This has me wondering why this happened now. I recently reinstalled Windows (to version 11) just two days ago, and there seems to be no clear explanation for this sudden failure. However, I remember past instances where it occurred before, requiring a system restore or replacement of the cable. Sometimes while watching videos, the connection would stutter and then drop completely. The network monitor in Task Manager showed occasional data transfers but only temporary connections. If it weren’t for the lockup, I’d probably just replace the cable. Now I’m considering getting a different adapter or a PCIe card if I want to fix it. What do you think? Have you faced this problem with Intel’s Ethernet controller? Do you think it’s linked to the latest drivers or something new? Checking online points to the same WOL issue in the I226 chip.
Have you attempted starting from a Linux live environment to check if the problem persists? Intel's drivers appear inconsistent with their I2xx adapters, though newer models are said to resolve the issue. It seems that on non-Windows systems like Linux or BSD, these complications usually don't arise.