Software Problems; Operating System Problems - HP ProLiant ML110 - G2 Server User Manual

Run Insight Diagnostics
7.
indicated.
Network controller stopped working when an expansion board was added
Action:
Be sure no loose connections (on page 58) exist.
1.
Be sure the server and operating system support the controller. Refer to the server and operating
2.
system documentation.
Be sure the new expansion board has not changed the server configuration, requiring reinstallation
3.
of the network driver.
Uninstall the network controller driver for the malfunctioning controller in the operating system.
a.
Restart the server, run BIOS Setup Utility, and be sure the server recognizes the controller and
b.
resources are available for the controller.
Restart the server, and then reinstall the network driver.
c.
Refer to the operating system documentation to be sure the correct drivers are installed.
4.
Refer to the operating system documentation to be sure that the driver parameters match the
5.
configuration of the network controller.
Problems are occurring with the network interconnect blades
Action: Be sure the network interconnect blades are properly seated and connected.

Software problems

The best sources of information for software problems are the operating system and application software
documentation, which may also point to fault detection tools that report errors and preserve the system
configuration.
Other useful resources include HP Insight Diagnostics (on page 48) and HP SIM. Use either utility to
gather critical system hardware and software information and to help with problem diagnosis.

Operating system problems

Operating system locks up
Action: Scan for viruses with an updated virus scan utility.
General protection fault occurs
A general protection fault, or general protection error, occurs when the Microsoft operating system
terminates suddenly with an error, including but not limited to:
•
Miscalculating the amount of RAM needed for an allocation
•
Transferring execution to a segment that is not executable
•
Writing to a read-only or a code segment
•
Loading a bad value into a segment register
("HP Insight Diagnostics" on page 48) and replace failed components as
Troubleshooting 89