Windows Integrity Management Agents Reference

Contact your HP support representative to check
the processor
Threshold parity errors have been detected in the
Instruction or Data Cache Memory (I-Cache or
D-Cache). The operating system has recovered
from the errors, but this is an abnormally high
failure rate10823
Contact your HP support representative to check
the processor
Threshold corrected platform errors have been
detected in the cache portion of the memory for
the processor module. The operating system has
recovered from the errors, but this is an
abnormally high failure rate10824
Contact your HP support representative to check
the processor module or the system bus for the
processor if an excessive number of these errors
are generated
Threshold corrected platform errors have been
detected on the system bus for the processor
module. The operating system has recovered from
the errors, but this is an abnormally high failure
rate10825
Contact your HP support representative to check
the processor module or the system bus for the
processor if an excessive number of these errors
are generated
Threshold corrected platform errors have been
detected on the processor bus for the processor
module. The operating system has recovered from
the errors, but this is an abnormally high failure
rate10826
Contact your HP support representative to check
the processor module if an excessive number of
these errors are generated
Threshold corrected platform errors have been
detected in the tag portion of the memory for the
processor module. The operating system has
recovered from the errors, but this is an
abnormally high failure rate.10827
Use the configuration tool released with the OS
to disable fPars mode or to configure and enable
bootable fPars.
fPars-mode EFI variable is set to enable fPars
operation but no fPars are actually enabled to
boot. So the server boots in hard partition mode.
This is a configuration usage problem, possibly
a user error such as might occur if a previously
bootable config was made unbootable by setting
the enabled fPar existence variables, e.g., 'fPar0',
'fPar1', ... 'fParN' to 0x00 (disabled) and then
rebooting10830
Use the configuration tool released with the OS
to correctly assign these resources to an fPar and
reset that fPar so they will be claimed.
An fPar was directed to reset using the ESIT
DirectedfParResetAndMigrate() service but the
target (recipient) fPar of the resources is in a state
that cannot receive ownership of these resources.10832
Reset the server, restore factory default NVRAM
and reconfigure soft partitions.
Firmware could not store to the NVRAM holding
the EFI preferred-bsp variable10833
Capture IPMI event logs, look for additional
errors. Contact your HP Support Representative
to analyze the fabric
System firmware was unable to write a fabric
hardware register.10842
Provide console log containing register dump to
HP Customer Engineer.
Probable bug in System Firmware, EFI driver,
EFI app or OS loader (prior to OS launch). The
event data field contains the IVT offset applicable
to the interrupt. See table 5-7 (Interruption Vector
Table) in the Intel ASDM Volume 2.10853
Disable rope in non-mca path, error exit in MCA
path.SBA call to LBA SetDeviceMask method fails.10871
Reseat or replace the PCI card.
The LBA component detected a card in a PCI slot,
but got no response from config register requests
to the card.10927
Platform Events – Table 2 (Windows System Log Event ID, Cause, Recommended Action) 113