Adobe “the memory could not be read” errors point to a crash from a plugin, a damaged preference file, or a Windows driver clash you can track down.
You open a PDF or launch an Adobe app, it blinks, then Windows throws a box that says the instruction referenced memory and “the memory could not be read.” The message is Windows reporting that the Adobe process tried to read memory it shouldn’t, then crashed.
If you’re seeing “adobe the memory could not be read” on repeat, the fix is almost always one of three buckets: user settings, third-party add-ons, or system components. The steps below help you find which bucket you’re in, then apply the smallest fix that sticks.
What “The Memory Could Not Be Read” Means In Adobe Errors
The pop-up is a Windows application error, not an Adobe dialog. Adobe is the program that crashed, Windows is the one reporting the crash. That matters because the same message can come from different roots: a bad plugin, a broken runtime library, a GPU driver issue, a corrupted cache, or a damaged user profile.
In plain terms, something inside the Adobe process touched a memory address that wasn’t valid. Windows ended the process to protect the system. You’ll often see an address like 0x00000000 or 0x00007FFF… in the message.
Fast Checks That Narrow The Cause In 10 Minutes
Start here. These checks tell you whether you’re dealing with a file problem, an app setup problem, or a wider Windows problem.
- Try A Different File — Open a different PDF or project. If only one file triggers the crash, the fix is often about that file.
- Open The Same File In Another App — Test a PDF in a browser viewer or a different reader. If it fails everywhere, the file is the suspect.
- Restart Windows — A restart clears stuck GPU sessions, hung background processes, and temp files.
- Pause Overlays — Turn off screen recorders, FPS counters, RGB tools, and chat overlays for one test.
If the crash still happens, match your scenario to the sections below.
Adobe The Memory Could Not Be Read On Windows 11 And 10
This is the common setup: an Adobe desktop app crashes on launch or when opening a file, and Windows shows the memory error. The goal is to isolate whether the crash comes from user settings, third-party code, or shared system pieces.
Reset Preferences First
Preference files store lots of small settings. When they get corrupted, Adobe apps can crash before the interface appears. Adobe publishes reset steps for several products.
- Reset Photoshop Preferences — Follow Adobe’s official steps to restore defaults and rebuild preference files: Reset Photoshop preferences.
- Reset Premiere Pro Preferences At Launch — Use Adobe’s launch reset instructions to rebuild preferences on startup: Reset Premiere preferences at launch.
- Reset After Effects Preferences — Adobe documents preference troubleshooting and safe launch paths here: After Effects preferences.
If the crash disappears after a preference reset, re-apply custom settings one group at a time so you can spot the trigger.
Disable Plugins And Add-Ons
Plugins load early. A plugin built for an older version can crash a newer build, even if it “worked yesterday.” Overlays can do the same by injecting into windows and GPU calls.
- Move Third-Party Plugins Out — Rename the plugin folder or move third-party files out, then launch again.
- Update One Plugin At A Time — Install one update, test, then move to the next so you know what fixed it.
- Remove Startup Utilities — Disable GPU overlays and capture tools on startup, then retest.
Use Windows Compatibility Settings When A New Build Clashes
For Acrobat and Reader, many users report that Windows compatibility settings stop the crash when a recent build collides with a Windows patch. Many users report success using the Compatibility tab or Windows’ troubleshooter.
- Open App Properties — Right-click the Adobe shortcut, then select Properties.
- Test Compatibility Modes — Under Compatibility, run the troubleshooter or try a recommended mode.
- Test Admin Launch — Run once as admin to rule out permissions blocks.
Fixes Inside Adobe Apps That Stop The Crash Loop
Once you’ve ruled out a single bad file, work through these app-level fixes. They target caches, security settings, and install files that can trigger memory read crashes.
Repair Or Reinstall The Adobe App The Clean Way
A standard reinstall can leave old settings behind. For Acrobat or Reader, start with a repair from the app’s own tools, then move to a clean reinstall only if repair fails.
- Run Built-In Repair — Use the app’s repair option if available, then restart Windows.
- Reinstall From Adobe Downloads — Install using Adobe’s installer for your product and version.
Test Hardware Acceleration And Caches
GPU acceleration can crash during rendering, scrolling, or zoom. Use this section as a controlled test: change one setting, retest, then decide.
- Disable GPU Acceleration — Switch to a software renderer in Premiere Pro or After Effects, then restart the app.
- Clear Media Cache — Clear cache from within the app so it rebuilds clean files.
- Move Scratch Disks — Point scratch and cache folders to a drive with lots of free space.
Acrobat And Reader Security Settings To Test
On some systems, Acrobat’s sandbox can clash with drivers or older plugins. Adobe staff have suggested a Protected Mode toggle as a diagnostic step. Treat it as a test, then turn protection back on once you’ve found the trigger.
- Toggle Protected Mode — In Preferences under Security (Enhanced), uncheck Protected Mode at startup, restart, then retest.
- Patch Acrobat Or Reader — Install the newest update once the app launches cleanly.
- Restore Protection — After driver or plugin updates, turn Protected Mode back on and confirm stability.
Windows Fixes That Often Resolve Adobe Memory Read Errors
If multiple Adobe apps show the same crash, or if app resets don’t stick, Windows pieces are a strong suspect. These steps target shared dependencies: runtime libraries, drivers, and system files.
Use This Table To Pick The Next Step
| What You Notice | Common Root | Next Step |
|---|---|---|
| Crash right on launch | Prefs, plugin, runtime | Reset prefs, disable plugins, fix VC++ |
| Crash when zooming or scrolling | GPU driver or acceleration | Update GPU driver, test software mode |
| Crash after a Windows patch | Compatibility clash | Try compatibility settings, update Adobe |
| Only one Windows account breaks | Profile damage | Create a new profile, migrate files |
Repair Microsoft Visual C++ Redistributables
Adobe apps rely on Microsoft Visual C++ runtime libraries. When those packages are corrupted or mismatched, apps can crash with memory access errors. Microsoft’s troubleshooting guide outlines common fixes and safe install practices.
- Update Windows Fully — Install pending updates, then reboot.
- Reinstall VC++ Packages — Download the latest redistributables and run as admin: VC++ redistributable troubleshooting.
- Retest Adobe — Launch the same app and repeat the same action that caused the crash.
Update Graphics Drivers Cleanly
Do a clean driver update from the GPU maker, then test with acceleration off and on.
- Install Vendor Drivers — Use NVIDIA, AMD, or Intel packages, not random driver sites.
- Restart After Install — Reboot so the new driver fully loads.
- Retest With One Change — Switch acceleration back on only after the crash is gone.
Run Windows System File Checks
If crashes started after power loss, disk errors, or forced restarts, damaged system files can be in play. Windows includes built-in repair tools.
- Run SFC — Open an elevated Command Prompt and run
sfc /scannow, then reboot. - Run DISM — If SFC can’t repair files, run
DISM /Online /Cleanup-Image /RestoreHealth, then reboot. - Repeat The Trigger — Use the same PDF or project step so you can tell what changed.
When The Error Ties To One File Or One Task
Some crashes are tied to one document, one font, one codec, or one export step. This section helps you spot that pattern and fix the narrow cause without changing your whole system.
PDF-Only Crashes In Acrobat Or Reader
If the memory read error appears only when opening a specific PDF, start with the split test: open that PDF in a browser viewer. If it opens fine there, the file is likely fine and your local Acrobat setup is the suspect.
- Download A Fresh Copy — Save the PDF again, then open the new copy.
- Remove Signing Add-Ons — Disable third-party signing or encryption tools tied to PDFs.
- Test A New Windows User — If it works in a new profile, migrate Adobe settings slowly.
Premiere Pro And After Effects Project Crashes
Video projects can hit bad cache entries, broken media links, or one corrupted clip that makes the app fall over. The fix is a steady cleanup plus one controlled test.
- Clear Media Cache — Clear cache inside the app, then reopen.
- Import Into A New Project — Create a blank project, then import the old one to rebuild metadata.
- Transcode One Suspect Clip — Convert a clip to ProRes, DNxHR, or H.264, then swap it in.
Photoshop Font Scans That Crash Startup
Fonts can crash design apps during startup scans. If the crash showed up after installing a font pack, test with a smaller font set.
- Remove Recent Fonts — Uninstall the newest fonts, reboot, then relaunch.
- Test With Default Fonts — Move extra fonts out for one test, then add back in small groups.
- Reset Preferences Again — After font cleanup, reset preferences once more.
Keep The Fix From Coming Back
Once the crash stops, a few habits cut repeat failures. Keep changes small, keep backups, and keep a clear way to roll back.
- Update In Batches — Don’t update Windows, GPU drivers, and Adobe apps on the same day.
- Keep Plugins Current — Check for plugin updates, remove what you don’t use.
- Read Event Viewer Logs — The faulting module name often points to the DLL or plugin that caused the crash.
- Leave Disk Headroom — Keep scratch disks and the system drive roomy for caches and temp files.
One-Page Checklist For The Next Time It Hits
- Write Down The Trigger — Note the exact click or step that causes the crash.
- Swap The File — Try a different file to see if the crash follows the file or the app.
- Reset Preferences — Use the app’s reset method before deeper system changes.
- Strip Third-Party Code — Remove plugins and overlays for one clean test.
- Repair The Adobe Install — Repair first, then reinstall from Adobe sources if needed.
If you still see “adobe the memory could not be read” after every step above, grab two items before you get help: the exact app version and the faulting module from Event Viewer. That pair points to the real break point far faster than reinstalling again and again.
Editor notes only: Links point to Adobe help pages for preference resets and Microsoft’s VC++ troubleshooting page.