Other PDF Issues

How to Fix High CPU Usage and Screen Blinking in Acrobat Pro DC

Steven ParkerSteven Parker Nov 10, 2026 869 views

Question details

The user needs to resolve an issue where the PDF application consumes excessive processing power and causes the display to flicker.

How to Fix High CPU Usage and Screen Blinking in Acrobat Pro DC
Product
Adobe Acrobat Pro DC
Device & OS
Windows 10
Scenario
Using the professional PDF software for viewing or editing documents on a Windows 10 machine.
Observed behavior
The application causes the main window to blink or flicker and shows abnormally high CPU usage in Task Manager, whereas the basic reader version functions normally.
Before you start

Before troubleshooting, save your current work and verify your current versions of Windows, Acrobat, and your graphics drivers. It is also helpful to close unnecessary background applications.

Solution 1Recommended

Update Software and Disable Hardware Acceleration

Outdated graphics drivers or conflicts with hardware rendering often cause screen blinking and excessive CPU consumption.

Hardware acceleration offloads graphic rendering to your GPU to improve performance. However, if your graphics drivers are outdated or incompatible with the specific version of your PDF software, it can result in visual glitches like screen blinking and force the CPU to overwork.

1
Update Acrobat and Windows

Open Acrobat Pro DC, navigate to the Help menu, and select 'Check for Updates'. Next, open Windows Settings > Update & Security to ensure your Windows 10 operating system is fully up to date.

2
Update Graphics Drivers

Press Win + X and select Device Manager. Expand the 'Display adapters' category, right-click your graphics card, and choose 'Update driver'. Follow the prompts to search automatically for drivers.

3
Disable Hardware Acceleration

In Acrobat, go to Edit > Preferences > Page Display. Under the Rendering section, uncheck 'Use page cache' and 'Use 2D graphics acceleration', then click OK and restart the application.

Performance Check: After restarting the application, open the Task Manager (Ctrl + Shift + Esc) to verify if the CPU usage has stabilized.

View and Edit PDFs Smoothly with WPS Office

If your current PDF software continues to cause screen blinking or high CPU usage, switch to WPS Office. It includes a built-in, highly optimized PDF editor that allows you to view, edit, annotate, and convert PDFs smoothly without draining system resources.

  1. 1. Download WPS Office: Download and install the free version of WPS Office from the official website.
  2. 2. Access the PDF Tools: Launch WPS Office and click on the 'PDF' tab located on the home screen.
  3. 3. Open Your Document: Click 'Open' to load your PDF file instantly. The optimized engine will render the pages without high CPU load.
  4. 4. Edit and Save: Use the intuitive top toolbar to edit text, add annotations, or convert the PDF to Word, Excel, or PowerPoint as needed.
Lightweight architecture ensures low CPU and RAM usage, eliminating screen flickering.Fully compatible with Adobe PDF formats and all standard Microsoft Office file types.Comprehensive PDF toolkit including advanced editing, merging, splitting, and OCR capabilities.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Acrobat Pro DC use so much CPU compared to the Reader version?

The Pro version includes more advanced editing tools, OCR background processing, and continuous cloud syncing features that consume significantly more processing power than the lightweight, viewing-only Reader version.

Can hardware acceleration cause screen blinking in PDF readers?

Yes, if your graphics driver is outdated or has a compatibility conflict with the application's rendering engine, enabling hardware acceleration can cause visual glitches such as screen flickering or blinking.

Where can I find the crash logs if my PDF software closes unexpectedly?

You can find application crash logs by opening the Windows Event Viewer, expanding 'Windows Logs', and clicking on 'Application'. Look for 'Error' entries related to the software's executable file to see the fault module.