Help Center/ Elastic Cloud Server/ Troubleshooting/ Self-diagnosis of Faulty GPU-accelerated ECSs/ Self-recovery from Non-hardware Faults/ How Do I Handle Recoverable Xid Errors?

Updated on 2025-07-30 GMT+08:00

View PDF

How Do I Handle Recoverable Xid Errors?

Possible Causes

Xid	Description
13	Graphics Engine Exception, a non-hardware fault, maybe an instruction error.
31	GPU memory page fault, a non-hardware fault, maybe an error of accessing an invalid address.
43	GPU stopped processing, a non-hardware fault, maybe a software error.

For details, see https://docs.nvidia.com/deploy/xid-errors/index.html.

Solution

Run the job again and check whether the Xid error disappears.
If the error persists, check the code or analyze logs to determine whether the Xid error is caused by the program.
If the Xid error is not caused by the program, contact technical support.

Parent topic: Self-recovery from Non-hardware Faults

Previous topic: How Do I Handle Driver Compatibility Issues?

Next topic: What Do I Do If the Error Message "Windows has stopped this device because it has reported problems" Is Displayed?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.