Start by collecting useful data. The NIC is a computer. One side
talks to Windows. The other side talks to the network. Device Manager
simply suggests that Windows is talking - or believes it is talking -
to the NIC. Now get basic information about the other side of that "NIC
computer'..
Simple test from Windows Command Prompt will report useful symptoms.
Enter a command such as:
PING -t 192.168.0.xxx where that is the IP address of this
computer. Repeate command using IP address of some other network
computer or router. As this test runs continuously, confirm that
lights on this NIC, that NIC, and on router all report activity.
Assuming this computer connects to an internet router, then one
version of that command that should work is:
PING -t 192.168.0.1 or maybe
PING -t 192.168.1.1
Important and useful information is also available from an NIC
hardware diagnostic provided by your computer manufacturer. Diagnostic
either on a separate hard drive partition or downloaded from computer
manufacturer. If not, then download a diagnostic from NIC
manufacturer.
Diagnostic, of course, loads and executes without Windows. First
diagnostic will test everything between motherboard computer and NIC
including things that Device Manager does not notice. That should test
OK. Then second half of diagnostic tests communication between this
NIC and another. Necessary that both computer uses an NIC that is from
same manufacturer. As this worse case testing procedes, corresponding
lights should appear on router. This last test requires same
diagnostic to be loaded on other computer. Often intermittents that
cannot be detected using normal activity (because normal operation is
very tolerant of errors) are firmly detected by this worst case
testing.
For example one NIC would work just fine (mostly) until the hardware
diagnostic ran for a while. Then the NIC just stopped working
completely. Only the comprehensive hardware diagnostic could find this
failure that everyone kept fixing by rebooting.