Windows Integrity Management Agents Reference

Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone far outside the
factory set range and could damage system
components. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.12
Close any open panels or chassis doors.
The server has detect that the chassis door or
other access panel is not securely closed.26
If the drive is redundant + hot-swappable, no
immediate action is needed. Otherwise, the
system likely will crash. Replace + repair disk
drive.One of the server's drives has been removed.76
Ensure that all the required SCSI cables, jumpers
or duplex connectors are correctly connected to
the cage, disks, and/or the controller.
This alert indicates that a SCSI cable, Jumper or
Duplex Connector has either been disconnected
or removed. This may make some SCSI devices
inaccessible.113
Make a note of the failed memory bank/board
number and slot number, contact HP support to
replace the failed module.
There has been an ECC double-bit error in one
of the server's ECC memory modules. When an
ECC double-bit memory error is detected, the
system generates a Non-Maskable Interrupt that
halts the system to prevent errors from
propagating to other subsystems. Data being
written or transmitted at the time may have been
lost.518
When this event is generated, it is highly
advisable to consult both the operating system
and hardware event logs to find out if there are
other events that may help identify the cause of
the MCA. If an MCA event occurs that causes the
system to reboot, the failing component may be
automatically disabled and the system continue
to run but at a degraded performance level while
awaiting repair. Therefore, for an MCA event,
HP recommends contacting HP Customer
Support to determine if a repair is needed.
A Machine Check Abort event means the
hardware detected a critical error. This event is
generated whenever a system error due to
processor, firmware, hardware and operating
system is encountered. MCA events may be either
recoverable or non-recoverable. If it is
recoverable, the system will attempt to recover
from the error for the purpose of maintaining
high availability. An example of which is
automatic disabling of a failing processor. For
non-recoverable errors, the system will either
stop or reboot to prevent data corruption and
unreliable operation.699
Contact HP Support for best course of action. HP
may require a reboot, reconfiguration, or reflash
of firmware.
This event is generated when a critical or fatal
event has occurred as reported by system
firmware. The server is not operational and is in
a state where it cannot provide more details about
the failure. To obtain more information, log into
the server's Management Processor Card and
look at the event log for more details on the
failure.700
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The input voltage for the system is not sufficient
for operation.704
When this condition was detected the system
should have been immediately shutdown to avoid
damage. Contact your HP support representative
as soon as possible to have the unit checked.
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone outside the
factory set range. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.705
Check all boards, power supplies, and modules
that either supply or use this voltage rail.
The voltage in the server has gone outside the
factory set range. A bad component, blown fuse,
poorly seated module, loose cable, or debris could
be responsible for this failure.706
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action) 63