Network controller stopped working when an expansion board was added to the computer.
Cause
Solution
The network controller requires drivers.
Verify that the drivers were not accidentally deleted when
the drivers for a new expansion board were installed.
Network controller stops working without apparent cause.
Cause
Solution
The files containing the network drivers are corrupted.
Reinstall the network drivers using Windows recovery tools in
Windows 10.
If necessary, download the softpaq from the web (from a different
computer).
The cable is not securely connected.
Ensure that the cable is securely attached to the network
connector and that the other end of the cable is securely attached
to the correct device.
Cannot connect to network server when attempting Remote System Installation.
Cause
Solution
The network controller is not configured properly.
Verify Network Connectivity, that a DHCP Server is present, and
that the Remote System Installation Server contains the NIC
drivers for your NIC.
System setup utility reports unprogrammed EEPROM.
Cause
Solution
Unprogrammed EEPROM.
Contact an authorized service provider.
Solving memory problems
If you encounter memory problems, some common causes and solutions are listed in the following table.
CAUTION:
Power may still be supplied to the DIMMs when the computer is turned off (depending on
the Management Engine (ME) settings). To avoid damage to the DIMMs or the system board, you must unplug
the computer power cord before attempting to reseat, install, or remove a memory module.
For those systems that support ECC memory, HP does not support mixing ECC and non-ECC memory.
Otherwise, the computer will not boot the operating system.
NOTE:
The memory count will be affected by configurations with the Management Engine (ME) enabled. The
ME uses 8 MB of system memory in single channel mode or 16 MB of memory in dual-channel mode to
download, decompress, and execute the ME firmware for Out-of-Band (OOB), third-party data storage, and
other management functions.
60
Chapter 6 Troubleshooting without diagnostics
