In this article
History and agreed test results are more useful than the label “used.” Checks describe current condition but do not predict a graphics card’s service life.
A GPU does not become unsuitable for inference simply because it has been used. Its current condition, software compatibility and behavior in a specific machine matter. Owners can offer existing equipment with a clear history instead of rushing to buy replacements.
Pilot preparation should not become an endless series of random stress tests. Use a short plan, agreed environment and explainable results.
Collect the history honestly
State previous workloads, known repairs, firmware changes and instability. Say if some cards have unknown histories. Note reboots, disappearing devices and cooling problems separately.
This helps choose the check sequence. It does not automatically justify accepting or rejecting a batch. Similar-looking cards can behave differently, and the host, power or connection may cause a problem.
Record the starting state
List exact models, memory capacities and environment versions. Before active tests, inspect the site and confirm equipment can leave primary work. Diagnostics must not interfere with other users’ jobs.
The NVIDIA DCGM guide distinguishes workload diagnostics from condition monitoring. Support depends on GPU class, version and environment. Do not apply a test available on one model to the whole fleet without checking applicability.
Compare cards under equal conditions
Imagine four identical cards. After checking the host, run one fixed test with the same model on each in turn. Log success, execution time, temperatures and error messages.
A differing card calls for further diagnosis rather than an immediate fault verdict. Exclude slot, cable and background-load effects. Change one material condition at a time or the cause will remain unknown.
Add a real-service test
Synthetic testing and language-model operation answer different questions. After hardware assessment, test the selected request profile, sustained operation and readiness recovery after an ordinary restart.
Do not chase results through nonstandard modes. Future operation needs a reproducible mode the owner can maintain. Complete needed maintenance before discussing continuous load, then repeat relevant checks.
For batches, assign internal card identifiers and tie each result to a specific unit. Otherwise a healthy card may inherit another’s error history after a server swap. An external operator initially needs only a summary; retain detailed logs until technical review is agreed.
Prepare a short result record
Include configuration, check dates, tools, observations and open questions. “Test passed” should name the test and conditions. It neither guarantees future health nor determines warranty status.
Agree the full technical stage separately. See the pilot plan and former mining equipment checks. An honestly described machine is easier to assess than “works perfectly.”