How to Test the Intel® Xeon® Processor Using Intel® Data Center Diagnostic Tool

How to test the Intel® Xeon® Processor

On Linux* systems Intel® Data Center Diagnostic Tool may be enabled by the system administrator for background execution.

If any errors are detected while the Intel® Data Center Diagnostic Tool executes in the background, the tool will log them to the system log. The tool can also query if any errors were detected in the background scan using the --query argument.

# dcdiag --query
Intel® Data Center Diagnostic Tool Version 603
Test completed successfully. No issues detected.

The background execution mode is currently not supported for the Windows* version of the tool.

This tool can also be run manually in the foreground by executing at a Linux* or Windows* command prompt:

# dcdiag

>"C:\Program Files\Intel\Data Center Diagnostic Tool\dcdiag.exe"

The manual test runs for about 45 minutes and has high CPU utilization.

When the diagnostic completes, the system returns one of the following messages:

• Test completed successfully. No issues detected.
• Test completed successfully. One or more machine check errors occurred. Check the system logs.
• This processor is not supported by this version of the tool.

  Check the system's processor model and version. This message appears if the Intel® Data Center Diagnostic Tool does not detect a production version of the supported processors. Engineering samples are not supported by this tool.

  Find help in identifying the processor.

• Test completed. Results are inconclusive due to an outdated version of the microcode.

  The latest version of the microcode addresses known issues. Update the microcode. Microcode updates are usually delivered by your Linux* distribution vendor alongside security fixes and other firmware updates for various components. If your system does not have these updates enabled, we recommend that you enable them. The microcode is automatically loaded by the Linux* kernel on every boot and can be reloaded at runtime with the following command as root:

  echo 1 > /sys/devices/system/cpu/microcode

• Test failed. Contact your system manufacturer or processor vendor for support.
• Test failed. Test completed, and an error was detected on the physical processor containing /sys/devices/system/cpu/cpuXX.
• Test failed. Test is unable to determine which physical processor caused the failure. Contact your system manufacturer or processor vendor for support.

On Windows* microcode updates are delivered using standard Windows* Update channels. If your system does not have these updates enabled, we recommend that you enable them.

• Test completed successfully. No issues detected.
• Test completed. Results are inconclusive due to the system exceeding temperature limits

  This could be due to a variety of issues with the system that is not providing enough cooling for the CPU to operate within the required temperature limits. We recommend that you check your system to ensure that the required cooling is operating correctly. This may include faulty fans, incorrect airflow, or some other environmental issue.

• Test completed. Results are inconclusive, one or more machine check errors occurred.

  Check system logs.

• Test failed. Contact your system manufacturer or processor vendor for support.
• If test results show fail, check if your server node's processors are still under warranty:
  • If you have a Boxed Intel® Xeon® Processor still under a 3-year warranty, contact Intel Customer Support for assistance.
  • If you have a tray processor, contact your system or processor vendor or place of purchase to check if the processor is still under warranty.
  • Be aware that Intel does not have an out-of-warranty replacement program.

Note that in Windows*, the Intel® Data Center Diagnostic Tool installer does not automatically update the system’s PATH variable, so full absolute or relative path is needed to start the tool.

Other names and brands may be claimed as the property of others.