What is hardware health in PeakNode?
The part of PeakNode that records and rates faults on NVIDIA GPUs: Xid messages, ECC errors, row remapping, PCIe link, throttling, missing cards and driver errors. It reports critical events immediately through the server monitor’s channels.
What does Xid 79 mean, and which Xid errors are critical?
In the portal Xid 79 reads “GPU has fallen off the bus”: the card has dropped off the bus. PeakNode reports this immediately as critical, with the affected GPU. Codes 44, 48, 63, 64, 74, 92, 94, 95, 119 and 120 are critical as well. Codes 13, 31, 43 and 45 are info without a notification, all others are warnings.
How does PeakNode handle ECC errors on the GPU?
PeakNode reports new uncorrectable errors immediately as critical. For corrected errors it only warns when they reach at least 100 in 24 hours and ten times the daily mean of the 14 days before, at the earliest after about 8 days of history. The counters are those of the driver and start again at zero after it is loaded.
What does row remapping pending or failed mean?
From the Ampere generation onwards, an NVIDIA GPU replaces faulty memory rows. Pending means: the replacement row only becomes active after a GPU reset; NodeCare lists this as a task for the next maintenance window. Failed means: the card can no longer replace a faulty row and needs to go in for service; PeakNode reports this as critical.
Why does PeakNode show only a dash for some GPUs?
Because the driver does not provide the value for that card. ECC, HBM temperature and row remapping exist on data center GPUs; consumer cards report “N/A” there. PeakNode then shows “-” and creates neither an event nor a zero from it.
Does hardware health work on Windows?
No. Xid, ECC, row remapping, PCIe and throttle reasons are only provided by the Linux agent. The Windows agent reports only basic values from NVIDIA GPUs such as utilization, memory, temperature and power; the macOS agent reports no GPU values.
How does hardware health differ from NodeCare?
Hardware health records events as soon as they occur and reports critical ones immediately. NodeCare turns these events and the history into a maintenance plan with stages, dates and recommendations. Both use the same agent readings.
What do Xid 31, 43 and 94 mean?
In the portal Xid 31 reads “GPU memory page fault”, an error during a memory access, Xid 43 “GPU stopped processing” and Xid 94 “Contained ECC error”, a memory error that was contained. PeakNode lists 31 and 43 as info without a notification and 94 as critical. The rating of further codes is in the table above.
Is there a tool to check GPU health?
For a one-off check, nvidia-smi -q shows ECC counters, remapped rows, throttle reasons and temperatures of every GPU. For continuous checks, the PeakNode Linux agent reads the same fields plus the Xid messages from the kernel log at every report, and the portal rates each event and reports critical ones. Basic values such as utilization and memory are covered by GPU server monitoring.
Is a single ECC error a reason to replace the GPU?
For PeakNode a single corrected ECC error is not a finding; it only warns when they rise sharply. New uncorrectable errors and a failed row remapping are reported as critical. Whether a card is replaced is decided by the reseller or vendor; NodeCare creates the record for the warranty claim as a PDF.