Windows Integrity Management Agents Reference

It is likely the GSP is not present or the device
specified is not present. Solve these problems and
try again.5812
Most likely cause is a bad cpu module connection
on the cell board. Replace the cell board.5813
panic occurred5823
fault/panic5824
No action required
panic, mca, or INIT path: attempt to write out the
dump is complete5825
Reboot if necessary, if problem persists contact
your HP representative for support.A PAL call made by SFW has failed.5827
Reset the BMC. Update BMC FW. Contact your
HP representative to check the BMC.BMC failed.5832
Reset the system. Upgrade system firmware. If
problem persists, contact HP support to
troubleshoot the problem.SAL failure.5833
Reset the BMC. Update BMC FW. Contact your
HP representative concerning the BMC.BMC failure.5834
Reboot the system. Update SFW. If problem
persists, contact HP support to troubleshoot the
problem.SAL failure.5836
Reboot the system. Upgrade system firmware. If
problem persists, contact HP support to
troubleshoot the problem.SAL is not in ADMIN or USER mode.5837
panic path forward progress5853
Analyze the Deadlock Recovery logs (like MCA
logs) to determine the cause of the failure.
Coherency controller (CC) resources are
deadlocked and the CC is resetting the cell.5896
Reseat DIMMPoorly seated DIMM6002
Install the DIMMs in the correct order. DIMMs
are installed in ranks of DIMMs , starting with
DIMM 0A, 0B, etc. Subsequent ranks are loaded
in ascending order , i.e., rank 1, 2, 3, 4, 5, 6 and 7.Incorrect loading of the DIMMs on the cell6074
Contact HP Support personnel to troubleshoot
the problem
At start of memory refresh, timing out waiting
for ready bit to be set6146
Contact HP support to troubleshoot the problem
Memory extender and baseboard are
incompatible6180
Contact HP Support personnel to analyze the cell,
XBC flex cables, system backplane
There is a fabric topology mismatch with XBC in
complex.6730
ResetLoss of Lockstep6795
Check XBC link connections Reset the system
backplane Contact HP Support personnel to
troubleshoot problemDefective XBC link Defective XBC7652
Check for hardware failure: flex cables, crossbar
chip, etc.
Another cell already attempted routing for the
XBC and found an error.7653
The error event will not be logged.7655
Check flex cables
A port was landmined so it had to be routed
around.7657
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action) 83