Software problems, Operating system problems, Operating system locks up – HP ProLiant Series ML100 User Manual
Page 73: General protection fault occurs, Operating system updates, Restoring to a backed-up version, When to reconfigure or reload software, Softw, Are problems, Work interconnect blades
Network controller stopped working when an expansion board was added
uration, requiring reinstallation
river for the malfunctioning controller in the operating system.
c.
Restart the server, and then reinstall the network driver.
rrect drivers are installed.
work interconnect blades
t blades are properly seated and connected.
Softw
s are the operating system and application software
n tools that report errors and preserve the system
fi
her utility to gather critical
information and to help with problem diagnosis.
Operating system problems
Genera
s when the Microsoft operating system
n
e into a segment register
Action:
1.
Be sure no loose connections (on page
2.
Be sure the server and operating system support the controller. Refer to the server and operating
system documentation.
3.
Be sure the new expansion board has not changed the server config
of the network driver.
a.
Uninstall the network controller d
b.
Restart the server, run BIOS Setup Utility, and be sure the server recognizes the controller and
resources are available for the controller.
4.
Refer to the operating system documentation to be sure the co
5.
Refer to the operating system documentation to be sure that the driver parameters match the
configuration of the network controller.
Problems are occurring with the net
Action: Be sure the network interconnec
are problems
The best sources of information for software problem
documentation, which may also point to fault detectio
con guration.
Other useful resources include HP Insight Diagnostics and HP SIM. Use eit
system hardware and software
Operating system locks up
Action: Scan for viruses with an updated virus scan utility.
l protection fault occurs
A general protection fault, or general protection error, occur
terminates suddenly with an error, including but not limited to:
•
Miscalculating the amount of RAM needed for an allocatio
•
Transferring execution to a segment that is not executable
•
Writing to a read-only or a code segment
•
Loading a bad valu
•
Using a null pointer
Troubleshooting 73