Check the GPU Driver Version

Oct 13, 2025 by wbrum.org 84 views

Introduction

PaddleOCR is a popular open-source OCR (Optical Character Recognition) engine that can be used with OpenVINO for GPU acceleration. However, we encountered an issue where PaddleOCR with OpenVINO (GPU) sometimes produces garbled OCR results for images. In this article, we will discuss the issue, its possible causes, and provide some useful suggestions to resolve it.

Issue Description

We referred to the OpenVINO GitHub notebooks: PaddleOCR Webcam to run PaddleOCR. During testing, we encountered the following issue:

Issue 1: After the second inference, PaddleOCR with OpenVINO (GPU) sometimes produces garbled OCR results for images. However, if we recompile the model for each image, the GPU results are correct and match the CPU results. This approach wastes time on model compilation. Is there any other way besides recompiling the model?

Issue 2: We found that the OCR results from PaddleOCR with OpenVINO (GPU) change depending on the rec_batch_num setting, while the CPU results remain unaffected. We’d like to confirm whether this is a GPU-related bug and how we can fix it.

Possible Causes

There are several possible causes for this issue:

GPU Driver Version: The issue might be related to the GPU driver version. Intel suggests that we downgrade the GPU driver version from 32.0.101.6557 to 32.0.101.6449.
Model Compilation: The issue might be related to the model compilation process. If we recompile the model for each image, the GPU results are correct and match the CPU results.
Batch Size: The issue might be related to the batch size. We found that the OCR results from PaddleOCR with OpenVINO (GPU) change depending on the rec_batch_num setting.

Debugging Steps

To debug this issue, we can follow these steps:

Check the GPU Driver Version: Check the GPU driver version and ensure that it is up-to-date.
Recompile the Model: Recompile the model for each image and check if the GPU results are correct and match the CPU results.
Check the Batch Size: Check the batch size and ensure that it is set correctly.
Use a Different GPU: Use a different GPU to see if the issue persists.
Check the PaddleOCR Model: Check the PaddleOCR model and ensure that it is correct and up-to-date.

Step-by-Step Reproduction

The attachments include a script and image files that can reproduce this phenomenon.

Installation: pip install -r requirements.txt
Execution: python ov_ocr_runner.py

Relevant Log Output

Issue Submission Checklist

[x] I'm reporting an issue. It's not a question.
[x] I checked the problem with the documentation, FAQ, open issues, Stack Overflow, etc., and have not found a solution.
[x] There is reproducer code and related data files such as images, videos, models, etc.

Conclusion

In conclusion, PaddleOCR with OpenVINO (GPU) sometimes produces garbled OCR results for images. The possible causes of this issue include the GPU driver version, model compilation, and batch size. To debug this issue, we can follow the debugging steps outlined above. We hope that this article has provided some useful suggestions to resolve this issue.

Future Work

In the future, we plan to investigate this issue further and provide a more detailed analysis of the possible causes. We also plan to provide a patch or a workaround to resolve this issue.

Acknowledgments

We would like to thank the OpenVINO team for their support and guidance in resolving this issue. We would also like to thank the PaddleOCR community for their contributions and feedback.

References

PaddleOCR Webcam
PaddleOCR
OpenVINO
Q&A: PaddleOCR with OpenVINO (GPU) Sometimes Gives Messed-up OCR Results ================================================================================

Q: What is the issue with PaddleOCR with OpenVINO (GPU)?

A: PaddleOCR with OpenVINO (GPU) sometimes produces garbled OCR results for images. This issue occurs after the second inference, and the results are correct and match the CPU results only when the model is recompiled for each image.

Q: What are the possible causes of this issue?

A: The possible causes of this issue include:

GPU Driver Version: The issue might be related to the GPU driver version. Intel suggests that we downgrade the GPU driver version from 32.0.101.6557 to 32.0.101.6449.
Model Compilation: The issue might be related to the model compilation process. If we recompile the model for each image, the GPU results are correct and match the CPU results.
Batch Size: The issue might be related to the batch size. We found that the OCR results from PaddleOCR with OpenVINO (GPU) change depending on the rec_batch_num setting.

Q: How can I debug this issue?

A: To debug this issue, we can follow these steps:

Check the GPU Driver Version: Check the GPU driver version and ensure that it is up-to-date.
Recompile the Model: Recompile the model for each image and check if the GPU results are correct and match the CPU results.
Check the Batch Size: Check the batch size and ensure that it is set correctly.
Use a Different GPU: Use a different GPU to see if the issue persists.
Check the PaddleOCR Model: Check the PaddleOCR model and ensure that it is correct and up-to-date.

Q: What is the recommended approach to resolve this issue?

A: The recommended approach to resolve this issue is to recompile the model for each image. However, this approach wastes time on model compilation. We are looking for alternative solutions to resolve this issue.

Q: Is this issue related to the PaddleOCR model or the OpenVINO framework?

A: This issue is related to both the PaddleOCR model and the OpenVINO framework. We are working with the PaddleOCR community and the OpenVINO team to resolve this issue.

Q: Can I use a different OCR engine with OpenVINO?

A: Yes, you can use a different OCR engine with OpenVINO. However, we recommend using PaddleOCR as it is a popular and well-maintained OCR engine.

Q: What is the status of this issue?

A: This issue is currently under investigation. We are working with the PaddleOCR community and the OpenVINO team to resolve this issue.

Q: How can I get updates on this issue?

A: You can follow the PaddleOCR community and the OpenVINO team on GitHub to get updates on this issue.

Q: Can I contribute to the resolution of this issue?

A: Yes, you can contribute to the resolution of this issue. We welcome contributions from the community to help resolve this issue.

Q: What is the expected timeline for resolving this issue?

A: We expect to resolve this issue within the next few weeks. However, the timeline may vary depending on the complexity of the issue and the resources available.

Q: What is the next step in resolving this issue?

A: The next step in resolving this issue is to investigate the possible causes of the issue and to provide a patch or a workaround to resolve the issue.

Q: Can I get help with implementing the patch or workaround?

A: Yes, you can get help with implementing the patch or workaround. We recommend reaching out to the PaddleOCR community and the OpenVINO team for assistance.

Q: What is the expected outcome of resolving this issue?

A: The expected outcome of resolving this issue is to provide a stable and accurate OCR engine with OpenVINO. We expect to resolve this issue and provide a patch or a workaround to resolve the issue.